2,947 karma · joined January 28, 2009
http://sunir.org
Making clay pottery can be simple. But to make “fine china” with increasingly sophisticated ornamentation and strength became more complex over time. Now you can go to ikea and buy plates that would be considered expensive luxuries hundreds of years ago.
If you are talking about code which isn’t what I said, then we aren’t there yet.
It’s not simpler. It’s faster and cheaper and more consistent in quality. But way more complex.
It incorporates also complaints from a static analyzer for Python and Javascript that detects 90+ vibe slop anti-patterns using mostly ASTs, and in some cases AST + small language models. The complaints give the local class and methods a sense of how much pain they are in, so I give the code a sense of its own emotional state.
I also build data flow schematics of the entire system so I can visualize the project as a wire diagram, which is very helpful to quickly see what is going on.
p.s. thanks for making this; timely as I am playing whackamole with sandboxing right now.
What is definitely going to be abundantly clear is just how much better machines can get at creating correct code and how bad each of us truly is at this. That's an ego hit.
The loving effort an artisan puts into a perfect pot still has wabi sabi from the human error; whereas a factory produced pot is way more perfect and possesses both a Quality from closeness to Idealism and an eerieness from its unnaturalness.
However, the demand for artisan pottery has niched out compared to Ikea bowls, so that's just how it is.
Repos also message each other and coordinate plans and changes with each other and make feature requests which the repo agent then manages.
So I keep the agents’ semantically compressed memories as part of the repo as well as the original transcripts because often they lose coherence and reviewing every user submitted prompt realigns the specs and stories and requirements.
However, then I discovered MCP servers on Claude Web are forced onto my laptop for Claude Code, which is very confusing. I don't know if there is a way to stop that, but it has messed up my Claude Code agents.
Is this experience common, and is there a known way to stop this?
And therefore in my experience not every senior engineer would hack it as a senior engineer at a more intense company myself included.
This isn’t a software unique experience. It’s life.
Kraft 1977 Programmers and Managers talked about this if I recall. Still the best alternate take on our industry I have ever read.
We don’t need the same volume of developers to have the same or faster speed of innovation.
And conversely if there is stagnation there is a capital opportunity to out compete it and so there will be a human desire to do the work.
Tl;Dr. People like doing stuff and achieving. They will continue to do stuff.
ps it’s too much to claim other people don’t experience creative ideas using AI. You don’t really know that’s true. It hasn’t been my experience as I have had the capability and capacity to complete ideas on my back burner for decades and move onto the next thing.
- Open source - Outsourcing - Offshoring
It was driving the labour cost of an engineer to zero I felt as a young man.
Then time passed, and I learnt that engineers aren't paid to code. Engineers are paid to solve problems for a business.
If you recall, the dot.com bust and 9/11 crashed finances for a few years. When the money printing gun went whir because "Deficits don't matter" Washington, then engineers were in demand again.
Right now we are in a weird situation where money is being printed and it is also tight. Most of it is going to the hardware and infrastructure layer, like the fiber optic bubble in the dot.com. Software will have its time in the sun again.
The basic social skill is to avoid conflict and seek acceptance. Go along to get along.
One wouldn’t rewrite the app on one’s on recognizance without peer approval first if this is your vibe.
It’s not like it changes our industry’s overall flavour.
How many SaaS apps are excel spreadsheets made production grade?
It’s like every engineer forgets that humans have been building a Tower of Babel for 300000 years. And somehow there is always work to do.
People like vibe coding and will do more of it. Then make money fixing the problems the world will still have when you wake up in the morning.
A framework calls you. You call a library.
A framework constrains the program. A library expands the program.
It’s easier to write a library that is future proofed because it just needs to satisfy its contract.
It’s harder to write a framework because it imposes a contract on everything that depends on it.
Just like it is hard to write tort law without a lot of jurisprudence to build out experience and test cases, it is hard to write a framework from only one use case.
No one likes lawyers because they block you from doing what you want. This is the problem with frameworks.
However the government likes laws because they block you from doing what you want. Same with whomever is directing engineering that wants all other programmers to work in a consistent way.
A real Wesley Crusher moment.
The word thinking is going too much work in your argument, but arguably “assume it’s thinking” is not doing enough work.
The models do compute and can reduce entropy; however, they don’t match the way we presume things do this because we assume every intelligence is human or more accurately the same as our own mind.
To see the algorithm for what it is, you can make it work through a logical set of steps from input to output but it requires multiple passes. The models use a heuristic pattern matching approach to reasoning instead of a computational one like symbolic logic.
While the algorithms are computed, the virtual space the input is transformed to the output is not computational.
The models remain incredible and remarkable but they are incomplete.
Further there is a huge garbage in garbage out problem as often the input to the model lacks enough information to decide on the next transformation to the code base. That’s part of the illusion of conversationality that tricks us into thinking the algorithm is like a human.
AI has always had human reactions like this. Eliza was surprisingly effective, right?
It may be that average humans are not capable of interacting with an AI reliably because the illusion is overwhelming for instinctive reasons.
As engineers we should try to accurately assess and measure what is actually happening so we can predict and reason about how the models fit into systems.