@antirez but how then will the less experienced grow the intuition and taste to understand or extend these “ideas” without years of reading code and comparing approaches.
looks like for me late 2026 will be full of jblow creations: i’ll either be cracking this game’s mysteries or coding in jai once it’s finally released.
Cashing out crypto soon? Don’t trigger an IRS headache or bank freezes:
• Cash-out risks
• Tax mistakes
• Compliant off-ramps
• Large exits
Join our LIVE AMA today
March 23 | 2PM ET
Clinton Donnelly (@CryptoTaxAudit ) + Hugo Leijtens (@CenseAG) Learn how to off-ramp safely👇
https://t.co/hJpMidT88R
as a software engineer: its surprising to me how frequently we are forced to explain "state reduction" even though how fundamental it is.
i wanted to have a structralized reference to it for this very specific purpose:
https://t.co/ZgRCkQj3Ph
AI can make work faster, but a fear is that relying on it may make it harder to learn new skills on the job.
We ran an experiment with software engineers to learn more. Coding with AI led to a decrease in mastery—but this depended on how people used it.
https://t.co/lbxgP11I4I
when it comes to using LLM’s in software, one thing almost everyone seems to agree on is that we still need a human in the loop.
this is why due to amdahl’s law, it cannot improve productivity as drastically as people claim unless it gets rid of this limitation.
@matteocollina@MichaelArnaldi@nodejs@fastifyjs while i agree what i cant get out of my head is: due to amdahls law, if a human is in the loop then these tools will never live up to the productivity increase claims people make
A few things I've noticed as all devs write code with AI.
When you write foundational / architectural code of a new project by hand, you "feel" the code pushing back if your abstraction isn't right. You feel when something is harder than it should be. The code is telling you it's not in the right shape. Good engineers are sensitive to this.
When you're using an LLM, you keep pushing right through this in a way that feels like you're making progress, and it may even be directionally correct in a sense, but the underlying foundation of it all is actually bad in a way that either kills progress of the LLM later as it buckles under the complexity it has created or destroys your ability to maintain the code long term.
Related to this, I see a general restlessness with just sitting and thinking about a problem for a while.
As I've been working on a new library here at Laravel, there have been days where it feels like I mainly just stare at my screen thinking about something. When Claude Code is at your fingertips, it's tempting to just start yapping into the terminal and watching code come out the other end. Again, directionally correct in some ways, but often doesn't land on the elegant solution that is waiting to be discovered.