We're deprecating some features with low usage on Bountycaster (bookmarks on our website + recommended bounties + cast action checking # of bounty completions)

Goal is to simplify our system so less eng complexity + maintenance which allows us to ship faster. There's a lot of stated vs revealed preferences but want to reduce bloat from it over time

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

Hi! My name is Daniel. I am building bountycaster.xyz

Ex Phantom, 0x Project engineer.

From Italy originally, currently live in NYC

This is of course not possible all the time, we will always prioritize feature work that can help us tune PMF

Feel this, even with small projects like moxiescout.

The decision just comes down to, will this help us reach pmf faster or not?

Wanna be the very best. Building @moxiescout. ゼニゼニ 



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.

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)