deechFascinating to watch industry getting a crash course in one of the fundamental asymmetries in software, that reading code is 10x harder than producing it.
| github | https://github.com/danicheg |
Daniel Esik
- 88 Followers
- 39 Following
- 715 Posts
Proud catamorphism fanatic. Or something like that.
June"The most wildly successful project I’ve ever released is no longer mine. In all my years of building things and sharing them online, I have never felt so violated."
https://beyondloom.com/blog/onwigglypaint.html
Edit: I am not the author of this. Please go check out https://beyondloom.com/ for more of the author's work.
My excitement about the evolution of industry standards, illustrated by incident reports from the past to now.
[ignorant times] Junior dev wiped a production database entirely: that's a tooling failure, not an operator one.
[awesome nowadays] Senior dev equipped with agentic AI wiped a production database entirely: that's an operator failure, not a tooling one.
> Cloudflare rewritten Next.js in just one week
> What would take years in engineering terms was executed in one week with some tokens.
You can't imagine how full I am of this bullshit. I open that project and see roughly 60-70 kloc written in that period of time. Which basically means two funny things — no one actually read that "produced" code; and the author expects readers to believe that stealing the library with some rewrites would take "years in engineering terms".
Funnily enough, the forceful push of agentic AI comes with the absolute justification of production downtime caused by misuse of these tools across the industry. I'm starting to think it'll even be encouraged soon.
What a bad time to be DevSecOps minded. I mean, it's the time when we need it so badly, but the ship handling is invaded by the blessed, willing to expose any third-party access to your production from their phones while sitting on the toilet. On the other hand, that industry gets what it deserves.
Today I read that the use of agentic AI "saves energy" (implying life energy, otherwise it'd be even more outrageous), which is yet another example of "ex falso quodlibet". One can only save (or even increase) life energy while working on something interesting, joyful, something one actually likes. Otherwise, you drain your energy. By saying "the use of agentic AI saves energy", they imply that everyone using it likes it. That drifts quite far from reality, I suppose.
TypelevelWe just launched a new typelevel.org built with the #typelevel stack! Read the blog post by @armanbilge and @valencik to find out what's next and how you can help 😸
https://typelevel.org/blog/typelevel-org-built-with-typelevel.html
By the way, I think I'm starting to understand this take "don’t read the code you produce", because otherwise, if you actually read the code, you'll die validating/reviewing/forcing these tools to produce something you'd write yourself (pursuing quality, stability, maintainability, security concerns). And ultimately, you won't gain any of the promoted boosts. Everything exists for a reason!
In one of the greatest books about software engineering "Peopleware: Productive Projects and Teams" (published in 1987, just for the record), Tom DeMarco and Timothy Lister wrote that developers’ ability to deliver quality work (at their own standards) at a sustainable pace (and the environment that supports this) is crucial to team success and individual satisfaction. It seems this is no longer considered important.