←back to thread

378 points todsacerdoti | 2 comments | | HN request time: 0.408s | source
Show context
ascendantlogic ◴[] No.44984607[source]
> Here’s the thing - we want to help. We want to build good things. Things that work well, that make people’s lives easier. We want to teach people how to do software engineering!

This is not what companies want. Companies want "value" that customers will pay for as quickly and cheaply as possible. As entities they don't care about craftsmanship or anything like that. Just deliver the value quickly and cheaply. Its this fundamental mismatch between what engineers want to do (build elegant, well functioning tools) and what businesses want to do (the bare minimum to get someone to give them as much money as possible) that is driving this sort of pulling-our-hair-out sentiment on the engineering side.

replies(4): >>44984704 #>>44984720 #>>44984767 #>>44984975 #
Lauris100 ◴[] No.44984767[source]
“The only way to go fast, is to go well.” Robert C. Martin

Maybe spaghetti code delivers value as quickly as possible in the short term, but there is a risk that it will catch up in the long term - hard to add features, slow iterations - ultimately losing customers, revenue and growth.

replies(4): >>44984776 #>>44984798 #>>44985172 #>>44985235 #
ascendantlogic ◴[] No.44984798[source]
Anecdotally I'm already seeing this on a small scale. People who vibe coded a prototype to 1 mil ARR are realizing that the velocity came at the cost of immense technical debt. The code has reached a point where it is essentially unmaintainable and the interest payments on that technical debt are too expensive. I think there's going to be a lot of money to be made over the next few years un-fucking these sort of things so these new companies can continue to scale.
replies(2): >>44984866 #>>44984879 #
busssard ◴[] No.44984866[source]
if i have 1mil ARR, i can hire some devs to remake my product from scratch. and use the Vibecoded Example as a design mockup.

If i manage to vibecode something alone that takes off, even without technical expertise, then you validated the AI usecase...

Before Claude i had to make a paper prototype or a figma, now i can make Slop that looks and somehow functions the way i want. i can make preliminary tests, and even get to some proof of concept. in some cases even 1million $ annual revenue...

replies(5): >>44984893 #>>44984991 #>>44985027 #>>44985103 #>>44988770 #
ascendantlogic ◴[] No.44984893[source]
Yes, this is exactly where AI shines: PoCs and validating ideas. The problems come when you're ready to scale. And the "I can hire some devs to remake my product from scratch" part is the exact money making scenario some of my consulting friends are starting to see take shape in the market.
replies(2): >>44984984 #>>44985202 #
1. const_cast ◴[] No.44985202[source]
But people say this about technology in software engineering time and time again.

VB? VBA macros in Excel? Delphi? Uhh... Wordpress? Python as a language?

Well you see these are just for prototypes. These are just for making an MVP. They're not the real product.

But they are the real product. I've almost never seen these been successfully used as just for prototyping or MVPs. It always becomes the real codebase and it's a hot fucking mess 99% of the time.

replies(1): >>44985417 #
2. disqard ◴[] No.44985417[source]
You're not wrong about that.

What ends up happening is that humans get "woven" into the architecture/processes, so that people with pagers keep that mess going even though it really should not be running at that scale.

"Throw one away" rarely happens.