Jaana was a distinguished engineer at GitHub and is now a principal engineer at Google. I expect to see more testimonials from accomplished software engineers in 2026 about how AI agents are making them more productive.
Engineers posting about how AI tools don’t work will increasingly look like a skill issue than a problem with AI tools.
If you have a fediverse account, you can quote this note from your own instance. Search https://mas.to/users/carnage4life/statuses/115832534415373032 on your instance and quote it. (Note that quoting is not supported in Mastodon.)
RE: https://mas.to/@carnage4life/115832534415373032
keeping up to date with "AI" skills is extremely easy actually, the most sophisticated setup i've seen is just a bunch of markdown files begging the necrotic grooves left in the statistical skin of language to pretend like they are different character archetypes wrapped by a (n assemblage of) IDE and CLI tools.
the "skill issue" FOMO trap is just a trap and the question was never "whether they work or not" but rather "how they reconfigure the dynamics of informational power by dramatically consolidating it in the owners of informational capital."
RE: https://mas.to/@carnage4life/115832534415373032
The sleight of hand – or the fundamental flaw – of this observation, is that it took their team a year to understand the problem by actually building a thing. Once you deeply understand a problem, it's trivial to get the dumb code vomit machine to produce code.
But producing the code is not the hard part, and using the code vomit machine is not a great way to build a system you understand from scratch if you haven't already solved the problem.
So the shortcut is a mirage.
If it's a skill issue, what's the skill?
