This is a very naive take. AI output still needs to be guided and iterated over, architecture decisions (even at the code level) still need experience to judge correctly.
>battery electric vehicles
>if it is the wrong thing you produce
Says you and not the guys with the big pockets that actually do market research? Until you solve the charging times problem, the mileage problem and the amount of available charging stations problem you will not see wide adoption. Most people don't want them and petrol is still king for many years to come.
Just a bit of cursory research provides some evidence counter to your confident assertions. It's fine if you don't like EVs or like the idea of them becoming popular, but it's worth doing a little reading first.
- In the US in 2025, 35% of vehicle shoppers say they are at least "somewhat likely" to consider purchasing an EV, with 24% saying they are "very likely" to do so. [1]
- Among younger consumers, more than two-thirds of Gen Z (72%) and Millennials (70%) say they would consider purchasing an EV. [2]
- In Germany, EV purchase intent rose 8 percentage points in a single year, with 30% of consumers planning a fully electric vehicle as their next car, which is the highest BEV intent of any surveyed European country. [3]
- The median range of new EVs hit a record high of 283 miles per charge for the 2024 model year, more than four times higher than in 2011. [4]
- The average EV range in 2025 has increased a further 4% over 2024, now reaching 293 miles, while fast charging speeds have improved 7% over the 2024 model year. [5]
- DC fast chargers can bring an EV battery to 80% charge in as little as 20 minutes. [6]
- In 2025, battery electric cars reached a historic 19% share of all new car registrations across Europe - the highest annual share ever recorded - with total volumes up around 31% compared to 2024. [7]
- Germany and France reached a combined battery electric and plug-in hybrid market share of 30% and 27%, respectively, while Italy and Spain are catching up at 12% and 20%, respectively. [7]
- Several smaller EU markets are already well ahead of the European average, including Belgium at 34%, Luxembourg at 27%, and Portugal at 23% BEV market share in 2025. [8]
- Europe's public charging network surpassed 1 million charge points in 2024 - a 35% growth in a single year with fast chargers now available every 50 km on over 75% of European highways. [9]
I own both an EV and a gasoline car, and feel there are upsides and downsides to both.
I have a hard time understanding what "increased productivity by 4%" actually means and how this metric is measured. One low-digit does not seem high when put into the context and promises, is it?
>Following this hypothesis, what C did to assembler, what Java did to C, what Javascript/Python/Perl did to Java, now LLM agents are doing to all programming languages.
What did Javascript/Python do to Java? They are not interchangeable nor comparable. I don't think Federico's opinion is worth reading further.
Most serious banking apps and financial services are still written in Java, it hasn't displaced much of anything. Big data is a relatively 'new' fad that is already becoming less and less relevant.
Someone might join if they are desperate enough and hop at the next better opportunity, that's what I would do. Aren't you worried this will be a waste of time?
It's so easy to measure too. 15k is 750 lines per working day.
There's no way any developer can meaningfully test, read and review 750 lines worth of changes per day.
And with AI code you've got to really go through it with a fine tooth comb, you can't scan the code. There's loads of subtle, but bad, bugs and assumptions it makes without telling you. I really want to emphasise the assumptions bit. A good example I saw recently was it assuming the sort order of a DB call should be something totally wrong, but easy to miss unless you read every line meticulously.
So either the OP is lying about how many lines their AI is pumping out, or they're checking complete AI slop untested and unreviewed into the codebase.
What I've learned from all these disaster stories: have backups for everythig. I have an iCloud+ subscription but also a OneDrive subscription, photos are sync'ed to both storages. On gmail, I set up fwd for all emails to another email address (non-Google related) just in case. Of course you can't do this for every service but do it for the ones you can.
On a meta note, Fuck Apple, I'm so glad I didn't pursue an iOS developer career 10 years ago.
Having people making tools be responsible what their users do with them is not a just system that blames the person that is really responsible. Even if you cannot locate or identify that person.
Sometimes arguments can be made if a tool is very dangerous, but liability should stay where it belongs.
This is a very naive take. AI output still needs to be guided and iterated over, architecture decisions (even at the code level) still need experience to judge correctly.