@SmartFella @DeveloperMemes gitlab, or even considering #sourcehut and raw git.
@SmartFella @DeveloperMemes Nope. I am fleeing github as quickly as I can.
RT @MacbethIII
Cool #babashka #clojure is now in assess mode in Thoughtworks Technology Radar.
Time to use it now.. ;-)
https://www.thoughtworks.com/radar/platforms/babashka
This is a terrific post that describes why functional programming feels so much more satisfying to learn than imperative programming. Realizing I can use (map) and (reduce), for example, feels so much more valuable than learning how to use that PDF Factory class with its inheritance hierarchy and overloaded interface specifications. Yeah, I'll be teaching that to my children.
@valerauko Clojure itself should count as "non-trivial", and they use it there.
One step is to be careful with semantic versioning, which implies breaking changes as a built-in assumption.
Non-breaking versioning has been very usefully demonstrated in high-usage Clojure projects like Figwheel, HoneySQL, Clojure JDBC, and others.
This will be harder if your codebase is a monolithic system of some kind, where there are many coupled parts. But this is a problem of the design more than a critique on [un]breakability itself.
@valerauko Clojure itself should count as "non-trivial", and they use it there.
One step is to be careful with semantic versioning, which implies breaking changes as a built-in assumption.
Non-breaking versioning has been very usefully demonstrated in high-usage Clojure projects like Figwheel, HoneySQL, Clojure JDBC, and others.
This will be harder if your codebase is a monolithic system of some kind, where there are many coupled parts. But this is a problem of the design more than a critique on [un]breakability itself.
RT @RobStuttaford
#Clojure, and it’s not an hour, it’s more like weeks at a time! 😃 https://twitter.com/dev_avocado/status/1452733200866975746
accidental #holywar
---
RT @agambrahma
Gold https://twitter.com/wcrichton/status/1450871977552629767
https://twitter.com/agambrahma/status/1453207710560784388
@valerauko I'm actually a big fan of both. The "don't break things" philosophy is related to the proper use of namespaces, and isn't actually that hard to pull off as a developer. Treat your codebase itself as immutable like you treat your data structures. A simple extension of the logic.
Why is it that the more I research the decentralized web, the more things seem to center on Etherium? #web3
Very interesting exploration of non-Git* solutions. I particularly liked his point warning of vendor lock-in.
https://sumnerevans.com/posts/technology/migrating-to-sourcehut/
RT @bravecljobs
Senior Software Engineer at Crescent
https://jobs.braveclojure.com/company/crescent/listing/senior-software-engineer/lxS9TwaPBt_88x5FrJB0L
RT @programmerjoke9
Meetings as a developer#100Daysofcode #javascript #programming #dev #linux #java #programming #CodeNewbie #python #reactjs #bugbounty #DataScience #infosec #gamedev #BigData @programmerjoke9
Full Stack Clojure web app engineer