|
|
|
|
|
|
by nradov
1870 days ago
|
|
|
There's no relationship between role specialization and working hours. If you're being overworked then push back, or look for a different job. In general it's best to "shift left" with quality control activities and write automated functional and system test scripts simultaneously with product code. Otherwise developers tend to write garbage, then pitch it over the wall to testers and wait for defect reports to come back. That back and forth is a total waste which causes long release delays. |
|
|
How so? More responsibilities surely equals more work. Furthermore, if you can focus on one role, you are more likely to optimize it.
> Otherwise developers tend to write garbage,
Then the developer is not good enough. Perhaps the problem has always been a lack of appreciation of CompSci skills.
> If you're being overworked then push back, or look for a different job.
You can't really push back, you get replaced, and all jobs right now are this way. People are asking why is there a culture of overwork... this is my explanation. If we want less overworking, perhaps we should go back to DIVIDING the work such that people can properly estimate and optimize for their role and eventually find a balance that works for them. As it stands now, you can't optimize for all the responsibilities properly, and are always catching up in learning, while trying to deliver features that have tight deadlines.