The free influx of money, and particularly investor money that gave the US an evergreen advantage will seize. Slow at first, then more and more as time moves on.

The problem is systemic and blaming other people for their lifestyle choices is neither effective nor helpful and just leads to further division. It's exactly this sort of division that helps fossil companies to destroy the planet and keep making money.

For methane produced by farming all components remain in a cycle. Everything released by animals eventually finds its way back to plants, which get eaten, which become exhaust of animals, etc.

This sounds to me more like a spin by big oil to finger point at another industry.

And the more you see an abstraction as a "wad of API calls and functionality", the more leaky the story gets.

Some systems are notoriously difficult to get this statement right because they are volatile and prone to changes. But I think as in live or in academia, our aspirations should be to strive for a better abstract understanding and keep building better abstractions.

For private projects, being able to code things quickly is a godsent. Also for professional environments with clear rules and mutual respect, this can be solved. But on the internet, with people you don't know? You must have some hard barriers.

We did do that and that's why our queries ended up being several lines long. But if you missed just one model? You openly walk a knife again.

It's a mess and it only gets longer and longer. I ended the project with having some proper aggregates, only for that to be thrown out of the window by the guy after me.

Never in my life did I have a problem with lazy loading causing unbearable performance until I joined a Python Django team. I really tried to find sympathy for the "dynamically typed" folks (please spare me saying Python is technically statically typed), but coming from writing apps and backends in Java, Swift, C#, Objective-C and PHP, Python with Django was the worst experience bar none.

I worked on the project for 10 months, could at least refactor the project to something semi-sane where obvious mistakes (which would not be possible in other languages) could not happen. Then along comes a "good Python dev" and threw it all out of the window and start doing SQL queries all over the place (typically 3-6 lines long), remove the domain objects and cause the same problems I started with to begin with. But his approach was saying that the other developers were "not good enough".

Yeah, have fun with schema changes going forward. Good riddance.

https://www.geeksforgeeks.org/nlp/what-is-llm-distillation/

Mistral is playing the smart money on vertical products rather than horizontal ones. The former requires finesse, the latter brute strength.

We have focused so much on technological advancement, but our understanding of human systems and building an environment of trust that is not eroded by perverse incentives atrophies.

Java always had a focus on enabling library authors over empowering call-site users. And I think approach has proven its dividend.

What were the emerging problems that you talk about? I am actually curious because I was quite fond of the DevEx