misja111
Joined 11 years ago
Joined 11 years ago
If you don't understand what you are building, chances are you'll take suboptimal decisions or even come up with a solution that completely misses the point.
To properly understand what you are going to build, it's not enough to read specifications from some manager as gospel. You need to ask questions, and challenge the requirements sometimes, to make them your own.
This will nullify the advantage of being able to treat sealed classes as algebraic datatypes by using the exhaustiveness check.
I think this is quite bad. I think such a change should break binary compatibility between the consumer and the producer api jar. Now any consumer might or might not run into runtime errors when switching to a new producer jar that is binary compatible.
My experience with Python is different. I noticed that my LLM (Claude) frequently gets stuck in cycles when coding larger features in Python. I'm also doing a lot of work in Scala, a language where much less code is on the Internet, yet Claude does way better, it hardly ever gets stuck at all.
My theory is, that while there is a lot of Python code on the Internet, a lot of that code is crap. This will trap LLM's into coding crappy solutions which will eventually bite them in the tail.
Also, I believe that, especially for larger codebases, a strong type system helps not just humans but LLM's as well.
Well moving to sustainable energy is good, but California being on 100% clean electricity won't have any measurable effect on its warming.
exactly today, a major farmer demonstration was already planned. They way they usually go ahead in the Netherlands is drive with their tractors over the highways towards The Hague, where our government is based. Obviously this leads to massive traffic jams.
A simultaneous disruption of the Dutch railways would add some extra effect to the expected traffic chaos.
(I'm using mostly Scala as a language in a large microservices environment)