|
|
|
|
|
|
by lbriner
1724 days ago
|
|
|
My worry about these types of articles is that can make conclusions that sound like they should be universal but are not. Company size and nature of work; turnover of staff; existing teams vs new teams all have an effect on whether you can give people the freedom to work asynchronously, work offline, have creative freedom. I know plenty of devs who simply would not be productive if left to themselves, they need direction, they lack the skills to creatively solve problems and that's fine. Build them a backlog and let them tick things off. If they need help, let them message somebody and disturb them to get them unstuck. A lot of the cult of independent and async working sounds like people who are introvert and just want to do what they want to do. This often doesn't work in business where we want people to be proactively working together to achieve a goal and some of this does require our time being "wasted" actually discussing things. |
|
|
Do you? Or do you just want that goal achieved with a great solution?
Sure, there are times that necessitates a team to solve it. That’s far from always, though.