4 ms·

I’ve been in this situation (worked too long on something without syncing with others). But I’ve also been on the opposite side. Some of my biggest accomplishme

I’ve been in this situation (worked too long on something without syncing with others). But I’ve also been on the opposite side. Some of my biggest accomplishments in my career, where I really added value, were when I went deep on my own and figured something out. Think of software design as a space with dimensions. You’re trying to optimize for something over that space. Development is ideally a series of incremental steps toward the optimum. The daily standup is where you check in and make sure your last incremental step was in the right direction. Generic developer of level N can make those steps. But what if you are stuck in a local minimum? How are you and your teammates going to find what is over that next mountain unless someone goes out there and brings enough provisions to spend the night? There’s gold in them there hills.

pixelrevision 5y ago
There’s a balance to be kept. It’s definitely not good when someone spends too much time on their own trying to get things just right. On the other hand a lot of modern agile trends seem to result in a lot of folks losing site of the big picture. Sometimes a problem is hard and needs time to figure out. In a lot of cases adding too many people to the discussion can result in distractions and churn due to their individual priorities and limited understanding of the problem. The best I’ve figured out here is to constantly ask for feedback from only the people who would be directly effected by the immediate task I’m working on. But that’s also deceptively hard to figure out sometimes.