Bad habits that stop engineering teams from high-performance
sdtimes.comDespite the author’s stated experience, the degree of absolutism in this article stank of inexperience. You’ve really gotta be firing on all cylinders to, frankly, write like this much of a dick. The author missed the mark.
Agreed. Most of the issues stated here are communication issues roughly.
If standup is not enough and there are still confusions, just talk to people, get in a huddle or short call, I mean all adults do it daily.
Tests take upfront effort but if the codebase is fairly decent tests can be written with much less pain. However, if the code suffers from super coupling and other tangled mess, it is natural for people to skip writing tests as that will require refactoring the code … and eventually momentum sets in and coverage goes to bottom.
Refinements are frequently necessary for large scale projects with tiny manpower or unclear requirements still being worked on. Then again, if there are issues, talk to people please.
Overall, interesting article but did not learn anything new.