Comment on Most slopcode projects are abandoned and deleted within months of release
yggstyle@lemmy.world 6 days ago
In a shock to absolutely not a single person who has had to “hand craft” and maintain code… Its hard enough maintaining shit you wrote last week let alone adapting or collaborating on stuff you didn’t.
… so people who shit out recycled code from other people passed through a randomization algo are totally lost from step one. And easy come… easy go.
Oh I need to maintain this? Oh the magic box can’t do it? Technical debt?! Oh, I’m bored now… guess I’ll go inject my brilliance somewhere else.
partofthevoice@lemmy.zip 6 days ago
Discipline is part the recipe for brilliance. So often, I find myself hearing of people’s problems and I realize that the problem is a manifestation of your poor discipline. It’s not necessarily that you did something wrong, misconstrued requirements or misconfigured procedures, no… it’s that you didn’t actually try to read the error message, look at the docs, catalog your technical debt, make a phased rollout plan, decide on what tests you’ll need, write a well bounded scope, … no. You just stuck your balls to the wall and said “boss, I think it’s cold outside.” How about you go open the fucking door and check?
/s… I got a little carried away there.
yggstyle@lemmy.world 6 days ago
I feel that. Theres a strict requirement of fortitude in this industry. Fighting against an unknown bug/challenge is draining and requires admitting you lack knowledge and being willing to persevere in the face of a fruitless result. Shits hard and will beat you down if you let it.
partofthevoice@lemmy.zip 6 days ago
Yeah. I’m currently in a situation where we picked up a new hire and she keeps dropping these problems on me. Whenever she runs into something she doesn’t understand, I get a Teams message:
By this point, I’m already fucking irritated and I haven’t even responded yet.
… she proceeds to create the ticket. MRE is a bunch of pseudocode referencing nonexistent tables with footnotes like, “this is the kind of tests we should check.” Oh, but you couldn’t be bothered to write the fucking test?
At a certain point, the ticket just falls into chaos:
So after explaining (10x) that, to troubleshoot the dashboards discrepancy, we actually need the filter values from the dashboard… we end up on a 3 hour call, because none of this is fucking landing.
So here I am doing other people’s jobs while I’m already busy enough from my own. I get so burnt out sometimes.
yggstyle@lemmy.world 6 days ago
I’ll admit I let out a pained chuckle while reading that. We all have at least one like that who, almost like a savant terrorist, can pick the worst time after being ‘just dangerous enough’ to inflict maximum pain for minimum effort. And then youre left with all that energy from exasperation just bouncing around inside.
ChickenLadyLovesLife@lemmy.world 6 days ago
I’ve long said that the more people you add to a software project, the longer it will take and the worse the final product will be. Your scenario describes one of the many reasons why this is the case.
Bluescluestoothpaste@sh.itjust.works 6 days ago
Interesting because i think i identified the same problem as you but i think of it as delusion. A lot of people (most people?) honestly believe that being smart means figuring things out with little effort. But all the smartest people ive ever met are extremely well organized and hardworking BECAUSE they’re so smart. They’re able to see the big picture and have a very sharp insight that problems are solved with an organized well planned approach, which often involves a lot of tedium.
Smart people aren’t bored by that, they see how the tedium ties directly into success/solutions/rewards. Dumb people really believe that they can be smart by divining solutions and that could not be further from the truth