42 karma · joined March 29, 2026
https://www.pangram.com/history/93f9ec71-f7b3-4680-86b1-ff12...
Imagine for a moment that, rather than using a compiler to translate c++ into assembly, that it instead has to be done by a person on the team. If that were the case, the resulting assembly code would certainly have to be reviewed and assessed before it was accepted.
Why?
Because people can also be leaky, non-deterministic abstraction layers. The only reason that the output of a compiler isn't regularly reviewed (in 99% of cases) is because it's extraordinarily reliable and consistently correct, or correct enough for most cases.
It's not terribly dissimilar from delegating engineering tasks to other engineers. When I ask someone else to develop one component of a larger application, I'm not telling them exactly what lines to write, I'm giving them some kind of structure and they're filling in the rest. The communication to them is above the implementation layer.
Agents are increasingly letting us work at that same boundary. Just because the current state of LLMs requires engineering knowledge to review the result doesn't mean an abstraction hasn't occurred. It speaks more to the current quality of that abstraction than the absence of one.
I think that if LLMs were able to achieve the same consistency as a compiler, most people wouldn't ever bother to check the underlying code it produced. I also think it would be difficult to not acknowledge that LLMs have gotten better at converting natural language into functioning software. The abstraction is certainly not perfect, but it is clearly improving.
I've been trying to map the LLM advancements and the current state of software development onto prior technological improvements. History is littered with similar cases where the abstraction layer ends up getting lifted, and people struggle with getting accustomed to working at that higher abstraction level.
For the people that fall in love with a single abstraction layer or don't have an interest in learning new paradigms, when their known pattern is abstracted away, they're condemned to being left behind, either unwilling or unable to adapt.
I don't think any industry is free from this, any person in any industry/profession over a period of 20 years or more has likely had to undergo massive adjustments as technology changed their field.
We're not unique, but that doesn't stop it from feeling so jarring when it happens to us
Again knowing nothing about tape, if I were tasked with this I would probably try to record the same audio to each of the tapes and then compare it with the original.
https://www.dcrainmaker.com/2025/10/oakley-meta-vanguard-rev...
I think my main issue with vibe coded apps is that the signal to noise ratio got flipped upside down.
Things that may have been positive signals in the past aren't really great indicators anymore. Maybe they shouldn't have been positive in the past, but they certainly aren't now. Broadly, things like polished website design, punchy language, clean branding, slick landing page, etc were all indicators. At a minimum, they at least meant that time and effort was put into it. It didn't really mean anything about the product, but it would display at least some level of time and effort.
Now, the outward appearance of a project no longer conveys anything about effort or durability, I can easily spin up a home page that would have taken me weeks pre-AI, then never touch it again.
The site states that it took roughly a hundred hours to develop. I have no real way of verifying that and I don't even think that it matters. The most evident signal that I feel I can still get a pulse on is when something is clearly, heavily AI written. All other signals that would supersede it require additional time to evaluate. Things like reading the docs, skimming the codebase, testing the product etc.
With a project like this, the ask made to the end user is to spend the time to, at a minimum, read the docs to see if it's a good fit. If they think it's a good fit, the next ask is to spend the time to integrate it with their current inventory. Then learn the workflow. Then learn the idiosyncrasies. All of these things involve, real human, time.
When an end user is asked to invest this time, there are only so many signals available to them to help decide if it's a good use of their time, energy and resources. For better or for worse, it seems like that list of signals is shrinking and right now, something that appears vibecoded is still one of the clearest visible signals.
I (like many other software folks) are aware of AI-isms in writing, so when I see something that it so obviously AI generated in a project, it's equivalent to a giant red waving flag.
For someone who doesn't interact with LLMs regularly? I have no idea, maybe it sounds great to them. Most non-tech folks I interact with to don't seem to have as well-tuned AI sense, whether it be image, video or text
Seeing it at the end of the trip after riding so many different trains made it especially impactful. Two highlights were the massive 100ft-wide railway diorama and the working vintage steam trains, which they drive (run?) out onto a turntable before rotating and returning to their stalls.
Well worth a visit if you’re ever in Kyoto.