3 ms·
Of course, but engineers are expensive. When is it ever in the employer's interest to get less output from them? Meet with them in person, do code reviews and
by babygoat 11y ago
Of course, but engineers are expensive. When is it ever in the employer's interest to get less output from them? Meet with them in person, do code reviews and such as often as you'd like, but once you've defined a problem for them to solve, what possible value could you get by keeping them in a distracting work environment?
- jmilloy 11y agoIn the very rare case that there is a clearly defined Problem which has been presented to from Above, which you can work on in isolation, and which you should prioritize to the exclusion of all else, then sure, distracting them will cause the Solution to be delayed. Many engineers like to view this kind of situation as their only responsibility and only avenue for adding value. I'm not sure it's accurate. We have to use a more broad and nuanced perspective on the value we provide when we talk about how that value is affected by our work environment.
- babygoat 11y ago> ...more broad and nuanced perspective on the value we provide ... This sounds like "leveraging synergies". If it was possible to explain any tangible benefit to such an environment, the conversation would move forward. Really, with the Very Rare Case? Developers don't have enough work to do where they don't need to stop and talk every 10 minutes?