Tricking a vibe coder?
Maybe we can trick vibe coders into becoming coders?
🤔 Interesting read-up on how to incorporate coding agents and testing into a software project:
I proposed “vibe engineering” as the grown up version of vibe coding, where expert programmers use coding agents in a professional and responsible way to produce high quality, reliable results.
The journey of Emil Stenström is really interesting, as it shows the iterative approach and thinking from going from 0 to 100.
Well, they had to do it, to break out of the plugin sandbox to get a real agentic system:
But having a sandbox also keeps the AI from doing really bad stuff -- like deleting a hard drive:
Why owning a product matters in engineering:
Without owning something over an extended period of time—like a few years—where one has a chance to take responsibility for one’s recommendations, where one has to see one’s recommendations through all action stages, and accumulate scar tissue from the mistakes, and pick oneself up off the ground, and dust oneself off, one learns a fraction of what one can. Coming in and making recommendations without owning the results, without owning the implementation, I think is a fraction of the value, and a fraction of the opportunity to learn and get better.
Interview by Dwarkesh Patel with Richard Sutton on LLMs, AGI and why he believes AGI will not be born from using LLMs.
In his essay The Bitter Lesson, he argues for not building AI from mimicking human behavior in our systems: "breakthrough progress eventually arrives by an opposing approach based on scaling computation by search and learning."
Wow! Doing Towers of Hanoi by LLM is something that can be done, by voting on small tasks.
Oh wow... come to think of it... most of the stuff we do on AWS is abstracted away as well...
Postgres 18 is coming. Async IO seems big!
Postgres 18 is adding asynchronous i/o. This means faster reads for many use cases. This is also part of a bigger series of performance improvements planned for future Postgres, part of which may be multi-threading. Expect to see more on this in coming versions.
Holy moly... et tu, NX?
When a programmer runs the hacked version of NX, the malware drops the exploit into their GitHub and runs that code. The malware stole a lot of people’s login keys and, apparently, their crypto wallets.
Here’s the novel bit — the malware code doesn’t steal your logins or crypto directly. Instead, it sends a prompt to Cursor, Claude Code, or any other AI coding bot on your computer, and it tells them to steal your stuff.
There is a bit of schadenfreude in the article, but the NX-case makes a great cautionary tale.
Hahaha... Alberta makes an excellent point!
It all comes back to skill!