3 ms·

I worked at a software company where we did pair programming and test first 100% of the time. We shipped amazing code in timeframes I wouldn't have believed pos

I worked at a software company where we did pair programming and test first 100% of the time. We shipped amazing code in timeframes I wouldn't have believed possible for system than could handle scale unheard of at the time (think of the datacenters powering Walmart). All I can say is this guy has some valid points even though I remain a huge advocate of this process. While I loved my time at this place, I had to quit after 3 years because of burn out. The trick is to have a way for developers to power down somewhat. I'm not sure how you would do that. I never got the chance to figure it out.

neandrake 10y ago
>The trick is to have a way for developers to power down somewhat. I'm not sure how you would do that. I never got the chance to figure it out. When it's time to change pace one of the things I think helps "power down" is to let team members work on things they are interested in or find important. Instead of priorities coming from up high it lets their minds breathe and explore something on their own. The difficulty is in managing to find the time for it.