4 ms·
> Instead, he used the odd hours to force us to give him only work that could be accomplished alone Ding ding ding. We have a winner! A big problem with peopl
by shados 7y ago
> Instead, he used the odd hours to force us to give him only work that could be accomplished alone
Ding ding ding. We have a winner!
A big problem with people like that is that at the end of the day, writing code or building stuff is the easy part. Communication, coordination, mentoring, onboarding, figuring shit out, etc, is the hard part.
People who hide for large parts of the day or multiple days are usually just dumping the hard part on others. Since the industry is often stuck thinking that line of codes === worth, these people seem more productive. Often, it's the polar opposite. They're freagin useless and anyone else in their situation would do the same or better. Everyone else is slower because of the increased burden (who's answering questions when Mr "I work from 5pm to midnight" isn't around?
- spease 7y agoIf people are regularly interrupting their development work to answer questions, then it suggests that documentation isn’t a priority and/or the team isn’t being very productive. Async communication often works fine as long as people are willing to read and write in detail. And you can often work faster if the code is better organized and self-documenting than if you have to spend an hour meeting with another dev to understand it.