3 ms·
This was entirely a commentary on the social aspects of developers. We had an initial surge in productivity and then a lull. Product quality suffered a bit due
by nobleach 5y ago
This was entirely a commentary on the social aspects of developers. We had an initial surge in productivity and then a lull. Product quality suffered a bit due to mis/non-communication. Not everyone made the transition to WFH in an effective way.
The engagement factor is realized with a very terse "yesterday I worked on recommendations, today I'll do the same". At that point the developer disappears for a few hours, never participates in any chat where less senior developers are asking questions. It's very siloed. The hardest part for leaders is to see how this translates into metrics they can understand. I'm absolutely ecstatic our org has adopted a "forever" WFH policy. I'm just cautious in how it'll all play out.