Maybe I'm a sentimental fool, but I feel like there should be some kind of basic respect for the craft, and doing things the right way just because. I get making bad code to meet a deadline, but not if you have a choice.

Then again, I've never done coding as my main job.

[–] fuzzzerd@programming.dev 4 points 3 months ago (1 children)

I have done it as my main job and I echo your sentiment. It's inevitable that sometimes you have to meet a deadline or get something more important working first, but if you write bad code because you are lazy or unwilling to read the docs to do it right, shame shame shame.

[–] mstrk@lemmy.world 6 points 3 months ago

Some people just don't care. To me it really feels like they are trying to create the problems to later sell the solution, and it's a never ending cycle. I've quit my recent job because 90% of the team just sucks, security risks everywhere, the API just doesn't respect contracts, there's no contract actually, we just ask on private chats how to integrate with it really. New features on top of buggy code while support is on fire with the 100th bug ticket reported in just a week. Not to mention that you have a design team, a project manager and a "VP of engineering" but the epics they want you to do are almost just the title of the idea they had at lunch 😅.

This guys are very lucky because the operation teams is able to cash in millions of revenue a year by combining excel, monday and WhatsApp to do their jobs, while a few are still forced to interact with a piece of shit of software that the engineer department provides to them...

Anyway, some people just don't care.

[–] psud@aussie.zone 3 points 3 months ago* (last edited 3 months ago)

We do. We make the best we can in the time we're given. People say "minimum viable product" but we never deliver that

[–] corsicanguppy@lemmy.ca 2 points 3 months ago* (last edited 3 months ago) (1 children)

Can confirm - you work like a dumber, more tired version of you needs to maintain it, so comment accordingly. Also, you do the work right but also fast; and you see how right you can do it in a reasonable timeframe of course.

But we fired a lot of our mentors after Y2K to save money that quarter. And the juniors there had no learning as to the whys of the whats when it comes to best practice. Those juniors became seniors and their juniors are 2nd-gen flying blind. We're doing dumb things because we know why we shouldn't, but we don't understand that we shouldn't. (Hint: if someone says "Yeah But," they may not get it)

We need to rediscover the whys we lost; and it's gonna be hard to really understand it, but we'll figure it out. A few more ClownStrikes and we wont have a choice!

[–] Revan343@lemmy.ca 1 points 3 months ago

Yeah but, move fast and break things is management's motto, they don't want to pay for the time it will take to write good code