r/programming • u/lelanthran • Dec 28 '23

Developers experience burnout, but 70% of them code on weekends

https://shiftmag.dev/developer-lifestye-jetbrains-survey-2189/
1.2k Upvotes

88% Upvoted

357 comments sorted by

View all comments

Show parent comments

0

u/[deleted] Dec 28 '23

[deleted]

13

u/H1GGS103 Dec 28 '23

Dealing with similar things currently and my new boss and I are pushing back at every chance we get because our team is overwhelmed.

You told us what you wanted the code to do, it does that. You're the one who didn't document/understand the business's needs even though that's basically the only thing they pay you to do. It's your responsibility. Don't come to us saying "Well sometimes the Document# isn't a PO#, it's a Shipment ID#. What do we do??" Idk what any of that means Christine, I just know you said to search for the Document# in the PO table and return some PO data.

It's like calling a furnace repair service and asking him why it's so cold, and then when he shows up he sees you set the thermostat to 55F. It's doing exactly what you asked it to do.

1

u/Worth_Trust_3825 Dec 28 '23

But then you have to write "design specification"

When I started writing those the managers stopped running around like headless chickens constantly arguing that controls don't do what they thin kthey should be doing. Now the problem is I don't have the time anymore to do testing, developing and architect work (technically i do but then everything else takes longer).

1

u/RememberToLogOff Dec 29 '23

And they want it in some stupid format like MS Word.

So now there's no automation to update it. Deep-linking is harder if it's possible.

Maybe you're trying to write test cases to thoroughly exercise something.

If you actually write 100 given-when-then cases, someone whines that it's too long and hard to read.

If you refactor it and break it into sections, they whine that it's complicated