4 ms·
I kind of agree, but for different reasons. C1 isn't for fast-but-low-quality. It's for instances where you have a detailed spec. Maybe there isn't much ambigu
by dalbasal 5y ago
I kind of agree, but for different reasons.
C1 isn't for fast-but-low-quality. It's for instances where you have a detailed spec. Maybe there isn't much ambiguity. Maybe there is, but you're working with an iterative process or something where building the wrong thing right is ok.
In my experience though, there's a never enough C1 type of work to go around. C2 is always the bottleneck. Requirements, specs, stories or whatnot do not reliably make good sense at the point where someone is actually making thee thing.
So to OP's question, I'd take the C2. Not because you don't need C1s, because you probably already have enough.