Bloated files are the worst part of maintaining a growing project.

We tend to hold onto old code because it feels like throwing away actual work, even when nobody has used that feature in months.

Cleaning up dead code always makes the app faster and cuts down build times, but it is super hard to convince the team to delete it.

Have you ever deleted a large chunk of code only to realize later that you actually needed a piece of it back?

Okay, small confession. For the last few months I've been "busy" all day but somehow shipping almost nothing. Tabs open everywhere, jumping between Slack, notes, half-written docs and by 6pm I couldn't tell you what I actually finished.

Last week I stripped everything back to three things: one notes app, a timer, and physically closing Slack for 90 min blocks. First time in ages I actually felt like I made progress instead of just looking productive.

But I know I'm probably still doing this wrong. :)

So I'm curious what's the one habit or tool that genuinely keeps YOU focused?

When I'm trying a new SaaS tool, I'm much more interested in signing up if I've already seen what it can actually do. Being asked to fill out a form before seeing any real value can make me leave before giving the product a chance.

I get why founders ask people to sign up upfront, though. It helps them save their work, personalize the experience, and understand who's using the product. And some tools need a bit of setup before they can show useful results.

Personally, I like the idea of letting someone try one small part of the product first, then asking them to create an account when they want to save their work or go further. But I'm not sure that approach makes sense for every type of SaaS.

When you re hungry for feedback, it s tempting to listen to every user who has an opinion on what to build next. But recently, we realized that building for high volume free users was actually diluting the core experience for our ideal paying customers.

Saying no to enthusiastic users is tough, especially when you want to keep your community active and engaged.

For founders who have balanced early feedback loops: how do you systematically separate high-value signal from broad feature request noise?

Some time ago, I cleared off my entire desk getting rid of extra monitors, gadgets, and RGB lights and stuck to just a laptop on a bare table. No aesthetic plan, no productivity setup. Years later, I m still working this way, and my output has never been higher. Meanwhile, the elaborate productivity gear I spent hundreds on just created distraction. It taught me that removing friction beats adding fancy tools.
Have you ever simplified your workspace and found it actually improved your focus?

Whether you're a solo builder or part of a fast-moving product team, documentation always seems to lag just behind reality.
Is it the speed of product changes?

• Getting engineers or PMs to consistently update docs?

• Lack of ownership?

• Tooling limitations?

• Or is it something else entirely?

  Would love to hear your thoughts on this.