Earlier quoted context omitted.
Because the cost of faults is much higher than getting a new bookshelf from IKEA. When talking about craftsmanship I’m not talking about artisanal, hand crafted source code that is aesthetically pleasing. Nobody but programmers care. I’m talking about CVEs that allow RCE on your phone so that authoritarian governments can exfiltrate your contact lists and arrest all of the people they suspect of participating in prot…
I don´t see why industrialized software development with AI Agents could not be better at quality. Medical equipment or airplane safety requirements validations are also done in an industrialized manner. We don't really care if engineers working on these products like what they are doing or they feel like a craftsman.
Vibe engineering
661–670 of 759 posts
Re: Vibe engineering
#662Earlier quoted context omitted.
Many Luddites were fine with using the new Loom machines. They smashed them because they were precious to the capital holders and in a time when there were no labour laws. The Luddites were protesting child labour, forced labour, and having no social safety net when they were discarded by their employers other than workhouses.
This has been the dream of the capital classes since time immemorial. And unfortunately (for humanity) this has been the status quo for the whole civilization. Small ruling elite class (you might designate them as masters, lords or employers) with all the wealth, minimal or no "middle class" and lots of poor people (you might designate them as peasants or slaves or workers). The only exception to this has been the pe…
Somewhat unprecedented in human history. All because intelligence had scarcity. AI changes that.
AI is the real dream of the capital classes. It makes intelligence cheap potentially undoing the very thing that gave birth to the last century's middle class. In the long term, given current trends, I wouldn't be surprised if these AI technologies revert us back to most of human history -> where the world is very unequal, meritocracy dies and most of us are trying to just exist/survive whilst the capital holders have abundance. It explains the large valuations as well of AI/Tech lately and the weird deals going on; this isn't a game of economics anymore; its an arms race of power in the new world structure. I suspect to these people no amount of money is enough; if you win you win for the next era of humanity.
Re: Vibe engineering
#663I just feel so discouraged reading this somehow. I used to have this hard-to-get, in-demand skill that paid lots of money and felt like even though programming languages, libraries and web frameworks were always evolving I could always keep up because I'm smart. But now with these people like Simon Willison writing about the new way of coding with these agents and multiple streams of work going on at a time and it so…
>I used to have this hard-to-get, in-demand skill that paid lots of money and felt like even though programming languages, libraries and web frameworks were always evolving I could always keep up because I'm smart. Tools always empower those with knowledge further than those without knowledge.
Re: Vibe engineering
#664Earlier quoted context omitted.
I really don't get the idea that LLMs somehow create value. They are burning value. We only get useful work out of them because they consume past work. They are wasteful and only useful in a very contrived context. They don't turn electricity and prompts into work, they turn electricity, prompts AND past work into lesser work. How can anyone intellectually honest not see that? Same as burning fossil fuels is great an…
> How can anyone intellectually honest not see that? The idea that they can only solve problems that they've seen before in their training data is one of these things that seems obviously true, but doesn't hold up once you consistently use them to solve new problems over time. If you won't accept my anecdotal stories about this, consider the fact that both Gemini and OpenAI got gold medal level performance in two ext…
Re: Vibe engineering
#665Earlier quoted context omitted.
Many Luddites were fine with using the new Loom machines. They smashed them because they were precious to the capital holders and in a time when there were no labour laws. The Luddites were protesting child labour, forced labour, and having no social safety net when they were discarded by their employers other than workhouses.
If you think about it, Luddites were the original victims of capitalist propaganda.
Many Luddites were shot against the wall or jailed. History often lies because it is written by the winners.
Re: Vibe engineering
#666Re: Vibe engineering
#667Earlier quoted context omitted.
We live in an objective reality. LLM's help a damn lot in speed of development. As someone who has been coding since 5th grade for over 20 years who is known to be a LIGHTNING FAST implementor by many people I have been scaled ridiculously with LLM's. Genie is out of the bag, you have to go with the flow, adapt or else.... I am just as pissed as anybody else at the lack of certainty in the future.... Thought I had my…
Good lord I wish I could have as many certainties as well, one point at a time: * There is no objective reality, there isn't one in physics, it's just a non argument * "LLM's help a damn lot in speed of development" That may be your experience and my whole point was arguing that speed may not matter * "Genie is out of the bag, you have to go with the flow, adapt or else" I choose else if this the apex of the argument
Re: Vibe engineering
#668I don't get the obsession some tech people have to push the idea that this stuff accelerate your coding, increase your productivity. It's all about fast and faster output. In my experience LLMs have mostly produced gibberish oververbose code, surely faster than me, but my lower speed usually produce better code. I don't like this present state of things where we need to chat faster to quickly get out results and go f…
> that is the kind of mentality that pushed subpar products on the web for so many years Famously, some of those subpar products are now household names who were able to stake out their place in the market because of their ability to move quickly and iterate. Had they prioritized long-maintainable code quality rather than user journey, it's possible they wouldn't be where they are today. "Move fast and break things"…
Re: Vibe engineering
#669Just added this note to the end, as part of my justification for picking such an obviously stupid term for this: > I’ve tried in the past to get terms like AI-assisted programming to stick, with approximately zero success. May as well try rubbing some vibes on it and see what happens.
Question, why is it seemingly so super important for you to coin a term for this? Especially a term which comes across as so demeaning and devaluing to engineers (like me and yourself!) I absolutely do not want my non-engineer friends and colleagues think I am "vibe engineering", it sounds trivial and dumbs down the discipline. I personally believe being an engineer of some kind requires work, learning, patience, dis…
But the act of working on GitHub Actions could be referred to as "continuous integration engineering", just like the act of figuring out how best to build software engineering processes around LLM tools could be called "vibe engineering".
Re: Vibe engineering
#670I don't get the obsession some tech people have to push the idea that this stuff accelerate your coding, increase your productivity. It's all about fast and faster output. In my experience LLMs have mostly produced gibberish oververbose code, surely faster than me, but my lower speed usually produce better code. I don't like this present state of things where we need to chat faster to quickly get out results and go f…
> why do we need all these unit tests in the first place? The same reason we've always needed them: 1: They prevent regressions. (IE, bugs in features that were shipped and already working.) 2: They are very easy to run at the push of a button in your IDE. (But in this context the LLM runs them.) 3: They run in CI. This is an important line of defense in making sure a pull request doesn't introduce a bug. Now, depend…