Daniel - Bountycaster
@pirosb3
Allocating 5-10% of development time to addressing technical debt for each new feature has a compounding positive effect on the codebase, it allows us to release faster and with fewer errors
2 replies
3 recasts
10 reactions
Daniel - Bountycaster
@pirosb3
This is of course not possible all the time, we will always prioritize feature work that can help us tune PMF
2 replies
0 recast
4 reactions
Zenigame
@zeni.eth
Feel this, even with small projects like moxiescout. The decision just comes down to, will this help us reach pmf faster or not?
1 reply
0 recast
0 reaction
Daniel - Bountycaster
@pirosb3
Imo, the answer is Yes because you are playing the long game, but there is a way to do it: bundle with other work At this stage of the startup, refactoring should always be paired with feature development. Building new features is a priority all of the times, and dedicating a small portion of time to refactoring on every feature will greatly reduce burnout, minimize frustration, and decrease context switching (my productivity killer)
1 reply
0 recast
1 reaction
Zenigame
@zeni.eth
Context switching when coding truly is the productivity killer. The only exception I've found is using 50m on 10m off Work Cycles (https://ultra.work/cycles). There's a bit of context switching during the breaks, but the planning and debriefs minimize the penalty and altogether allow for a longer session of focused work. I like how thoughtful you are with refactoring. Looking forward to learning more from how you approach building.
1 reply
0 recast
0 reaction
Zenigame
@zeni.eth
Not sure why that requires sign-in now. Will take a look at some point, sorry!
0 reply
0 recast
0 reaction