(I'm using mostly Scala as a language in a large microservices environment)
4,511 karma · joined April 1, 2015
(I'm using mostly Scala as a language in a large microservices environment)
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.
> Being a craftsman is a deeply human desire that AI is destroying, not sure if this is a fun future to look forward to.
AI is giving me back the feeling I had when I first learned to program, when I was 14. At 14, I suddenly had a tool in my hands that was like an extension of my imagination. I could create tools, games and what not with it, this is what I loved. AI is that same tool on steroids. If what you like is creating things, AI lets you do it at 10 times the speed.
What used to tire me: being forced to have a sharp eye for syntax errors when programming, or simply the effort of all the typing and navigating through source files. Trying to visualize details of the codebase I was changing, while at the same time keeping a high level picture in my head of the feature I was changing.
With AI, I can focus on the high level picture. I can focus on the steps to get there and the steps to verify that it works. I don't have to focus on syntax anymore and there is much less need to visualize large parts of my code base. With AI, work is still tiring but much less, and in a different way.
AI companies are more and more interweaved with the economy because half the world is owning their stocks or has lent them money. Or, they have invested in companies that in turn have invested in AI. It is very similar to the situation before the credit crisis.
Let's say you're discussing the next release and someone brings up some disastrous idea. You know he won't listen so you decide to keep quiet. The release comes, things blow up as expected.
Don't be surprised if you find your manager at your desk a bit later asking you to work late shifts to fix it. After all you are all in the same team, and you didn't speak up when the plan was discussed.
So in a meeting, speak up and don't give in if you are sure you are right. I have learned this lesson the hard way.
1. stop any inflammation, by taking NSAIDs for a few days
2. detect and correct any behavioral patterns that could have caused the presumed overwear of the tendon
2. start physiotherapy to strengthen those muscles that can take over the load from the damaged tendon
These are not quick fixes, because quick fixes don't exist here. Stuff like shockwave treatment, massages etc will only lessen the problems for a few hours at most, after which they will come back.