4 ms·
I think that for programmers, if you’re working on more than 2 features, you’re working on too much. Cal Newport’s latest basically says: Take in fewer things.
by FigurativeVoid 2y ago
I think that for programmers, if you’re working on more than 2 features, you’re working on too much.
Cal Newport’s latest basically says: Take in fewer things. Work at a natural pace. Produce at the highest quality. I think that’s correct.
- karmakaze 2y agoThis sounds about right. I can switch tasks whenever I'm waiting for feedback on one, or I need to let a problem with one simmer unconsciously. Sometimes I'll pick up a quick chore if I don't have a block of time or energy to get into a meaty part of one. But sometimes you just gotta power through it regardless.
- acuozzo 2y ago> if you’re working on more than 2 features (Honest question because I've always worked in R&D...) What counts as a feature when you're starting from scratch?
- mckn1ght 2y agoAnything that’s not a bugfix? That helps cover that infrastructural kind of work that’s not immediately visible to an end-user.
- lasereyes136 2y ago2 features here really mean 2 development tasks however a task is defined for your team. The idea is to have one to work on while the other is in the background (maybe being worked on by your subscience) and to take a new one once one is done, even if it isn't worked on immediately. The main goal of work in progress limits to get work to done rather than starting new work (that doesn't get to done). Ideally in Scrum your sprint commitment is a work in progress limit but in practice it isn't treated as such for reasons. Kanban can allow expedited issues to address an "emergency" issue but even that has a WIP of 1 so emergencies have to be prioritized.