California is "bending the duck curve" with batteries:

Grid batteries reach stunning new peak of 44 pct of evening demand in world’s fourth biggest economy

https://reneweconomy.com.au/grid-batteries-reach-stunning-new-peak-of-44-pct-of-evening-demand-in-worlds-fourth-biggest-economy/

#renewableenergy

If you don’t have the resources to write and understand the code yourself, you don’t have the resources to maintain it either.

Any monkey with a keyboard can write code. Writing code has never been hard. People were churning out crappy code en masse way before generative AI and LLMs. I know because I’ve seen it, I’ve had to work with it, and I no doubt wrote (and continue to write) my share of it.

What’s never been easy, and what remains difficult, is figuring out the right problem to solve, solving it elegantly, and doing so in a way that’s maintainable and sustainable given your means.

Code is not an artefact, code is a machine. Code is either a living thing or it is dead and decaying. You don’t just write code and you’re done. It’s a perpetual first draft that you constantly iterate on, and, depending on what it does and how much of that has to do with meeting the evolving needs of the people it serves, it may never be done. With occasional exceptions (perhaps? maybe?) for well-defined and narrowly-scoped tools, done code is dead code.

So much of what we call “writing” code is actually changing, iterating on, investigating issues with, fixing, and improving code. And to do that you must not only understand the problem you’re solving but also how you’re solving it (or how you thought you were solving it) through the code you’ve already written and the code you still have to write.

So it should come as no surprise that one of the hardest things in development is understanding someone else’s code, let alone fixing it when something doesn’t work as it should. Because it’s not about knowing this programming language or that (learning a programming language is the easiest part of coding), or this framework or that, or even knowing this design pattern or that (although all of these are important prerequisites for comprehension) but understanding what was going on in someone else’s head when they wrote the code the way they wrote it to solve a particular problem.

It frankly boggles my mind that some people are advocating for automating the easy part (writing code) by exponentially scaling the difficult part (understanding how exactly someone else – in this case, a junior dev who knows all the hows of things but none of the whys – decided to solve the problem). It is, to borrow a technical term, ass-backwards.

They might as well call vibe coding duct-tape-driven development or technical debt as a service.

🤷‍♂️

#AI #LLMs #vibeCoding #softwareDevelopment #design #craft

Brutal.

When Microsoft acquired GitHub.

All the devs saying that Anthropic’s code quality is “normal” are telling on themselves and everybody they’ve worked with

(Also supports what many have been saying about software quality being a crisis that precedes LLMs, but that’s another story)

RE: https://mastodon.social/@arstechnica/116329758913971375

I hope more countries start looking at Sweden's lessons.

Learning is not about giving people tech skills but about shaping and environment, relationships, and mentorship in a way that lets people become who they want to be.

Mic. Drop. 🎤 ⬇️

(edited to use a more neutral emoji)

https://youtu.be/h3AtWdeu_G0

Historic Chat Control Vote in the EU Parliament: MEPs Vote to End Untargeted Mass Scanning of Private Chats

In a sensational turn of events in the fight against Chat Control, a majority in the European Parliament voted today to end the untargeted mass scanning of private communications. In doing so, the Parliament firmly rejected the error-prone and unconstitutional surveillance practices of recent years.

https://www.patrick-breyer.de/en/historic-chat-control-vote-in-the-eu-parliament-meps-vote-to-end-untargeted-mass-scanning-of-private-chats/