In my previous job, the engineering leadership insisted on kanbanish minimization of work in progress, making sure everything is well prepared to minimize the risk of people getting blocked, and accurate sprint planning. At Meta, I’m encouraged to work on multiple projects in parallel and switching between them based on where I’m blocked at the moment. I personally like the second approach. I understand it’s probably not ideal for programming nuclear reactors but perhaps good enough for most of most of tech companies. What do you think?
Really liked multiple, unless all are boring
Tech Industry
4h
452
Got an opportunity to invest in perplexity
Tech Industry
Yesterday
5115
BREAKING: Internal sources confirm another round of layoffs just hit emails at Tesla. For real.
Health & Wellness
Yesterday
1146
Low Testosterone
Ask Blinders
11h
479
Why no one cares about the lives lost in Gaza, Israel and busy in their own lives?
Tech Industry
4d
44695
What happens when most of your team is Indian?
Easy to get overwhelmed with the latter
Well, you can still limit the number of open ones to 5 and prioritize.
… as long as each of them means “an outcome I want to achieve” rather than “another business person bugging me with random requests”