Just keep coding
Just keep coding
31 comments
-
-
I mean, when you look at old walls made of quarry stone, they kinda look like this and still hold.
-
You can’t really look at the ones that didn’t hold.
-
-
Excellent point. For those who are unfamiliar: Survivorship bias
-
-
-
Also brick walls don't really go through iterative changes, which is an important issue with tech debt.
If the wall works, then it works
A software project will work now, but may not hold up when you need to change something
-
Well that's not true. I live in a Soviet era house that had an entire second floor built on top of it. We've had to drill through the brick walls to replace the natural gas pipes with pipes that run outside the walls, we've had to dig under the foundation when we got connected to the city's sewer system (again, Soviet-built), and again when the main water pipe burst and threatened to wash out the foundation. If the load-bearing walls had been constructed to the same "it works" standard as the things we've had to fix, we wouldn't have a house anymore.
-
You don't ever HAVE to update software though. That's just the way it's usually done now. It's a choice. Usually updates are made to add more features or monetization or whatever but you could just not do that.
If you look at old video games for example those were released and never updated again. They will still work today too.
-
-
Uhm...
-
-
My thought as well, but those stones were shaped to match each other, reducing the amount of grout needed. It just goes to show the old ways still work, but you have to commit.
-
-
I've seen worse. There are no big holes in the wall.
-
this plan called for windows gothy
-
yet
-
-
That’s just the unreal engine
-
@cm0002 lol. The post after yours...
-
I'm not gonna lie, I like how that wall looks lol.
-
That's why they call it a vibe wall
-
-
"Waterfall? Won't the water break our computers?"
-
Me when Claude code writes bullshit I don't need
-
Geez, it's like coders are only happy when bashing other people's codes...
What do coders say when they're tasked with continuing some other coder's task? "This is all wrong".
-
That's also what we say when continuing our own task
-
I've rewritten much of my code as needs changed, I call myself an idiot a lot since I've worked on this program nearly a decade and was my first professional software so often change old code I wrote. Though it was more additional at first since I used a lot of code the lead programmer did. Though he duplicated everything as needed for a tiny change ugh. Least I know how not to do it.
-
-
isn't that every job?
-
-
With the difference that code actually is easily changeable, if you need to change a wall you actually need to tear it down, get rid of the waste, likely tear everything down that was supported by it, and completely rebuild it with new materials.
If you need to change the foundations of your code, yes, it's not always super easy, but it is actually possible and I've done it before without super big headaches.
It's just not comparable.
-
It absolutely is, you can partially tear down even a load bearing wall but it's expensive, difficult, and should have been avoided from the start.
Kind of like building a whole infrastructure on spaghetti code.
-
31 comments
"Look, guys, I vibecoded a wall!"
"It goes almost all the way to the ceiling. I just need you to connect the last layer into the structure, it should be a 15 minutes work, right? I already settled the deadline with your boss. Tanks; bye."