Just keep coding
-
Your options are an ugly wall that works or the beautiful lack of a wall.
wrote last edited by [email protected]* For a very specific value of "works". Offer is limited in time. No refunds. Warranty doesn't cover damage caused by the elements, presence, or lack of gravity. Other conditions may apply.
-
Sure, though having gone through an entire monorepo refactoring of like half a million lines to basically destroy the codebase and switch from vue 2 to vue 3 among other things, it’s also possible to build the new, better designed wall right behind the old one, test like hell against that wall, and then shift that wall in when it’s ready in a planned release, ready for the issues that come because that wall isn’t quite like the old wall
Making the new wall is not a money generator. You would be insane if you think suits would waste money to rebuild something when it generated minimal to no additional revenue.
-
Making the new wall is not a money generator. You would be insane if you think suits would waste money to rebuild something when it generated minimal to no additional revenue.
True, I'm lucky to work for a company that was half founded by engineers who know the cost of compounding technical debt, which is almost never the case.
-
This post did not contain any content.wrote last edited by [email protected]
I've seen worse. There are no big holes in the wall.
-
You can’t really look at the ones that didn’t hold.
Excellent point. For those who are unfamiliar: Survivorship bias
-
You can’t really look at the ones that didn’t hold.
-
"Look, guys, I vibecoded a wall!"
wrote last edited by [email protected]"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."
-
I've seen worse. There are no big holes in the wall.
this plan called for windows gothy
-
This post did not contain any content.
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".
-
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
-
This post did not contain any content.
I'm not gonna lie, I like how that wall looks lol.
-
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.
-
Sure, though having gone through an entire monorepo refactoring of like half a million lines to basically destroy the codebase and switch from vue 2 to vue 3 among other things, it’s also possible to build the new, better designed wall right behind the old one, test like hell against that wall, and then shift that wall in when it’s ready in a planned release, ready for the issues that come because that wall isn’t quite like the old wall
wrote last edited by [email protected]no one has a budget for that
your whole team is fired, we got ‘Bob’ from India handling this now
-
Weird to see a Men at Work gif.
-
Weird to see a Men at Work gif.
-
I'm not gonna lie, I like how that wall looks lol.
That's why they call it a vibe wall
-
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".
isn't that every job?
-
This post did not contain any content.wrote last edited by [email protected]
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.
-
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.
wrote last edited by [email protected]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.
-
Build the new wall airgapped from the old one
Ah, yes: weaponizing cybersecurity requirements to trick - I mean “motivate” - higher management to do things “right.”
