4 ms·
As a dev in the 80s & 90s I found that it seemed to work well to state in a job interview that I expected to work normal business hours - BUT that when a deadli
by euroderf 3y ago
As a dev in the 80s & 90s I found that it seemed to work well to state in a job interview that I expected to work normal business hours - BUT that when a deadline was imminent I could commit to the mega OT grind for a day or two or a few. Like (for example) Fri-Sat-Sun.
The key word here was "deadline": a shared understanding that this meant one of those customer deadlines - a big deliverable - that comes only a handful of times a year.
What's dev work like nowadays ? Does every week have a "big deadline" ?
- hirvi74 3y ago> Does every week have a "big deadline" ? Once my employer implemented Agile/Scrum, "big deadlines" seemed to occur much more frequently -- seemingly in two week intervals when sprints would end. Now, I know many are foaming at the keyboard getting ready to state how my employer is not doing Agile/Scrum correctly. Those individuals are probably be correct, but that does not change my experiences nor many others' experiences. I am not trying to shit on Agile either. I just noticed a strong change from how we did things pre-Agile and post-Agile. Every sprint is a new deadline. The overall quality of my work has suffered as a result too.
- gofreddygo 3y ago100%. Scrum makes it incredibly easy to sneak in poor quality work and cover it up with a web of user stories and tasks. The "board" takes the focus away from the product.