Kabir Suleman kusfa

Been thinking about this a lot lately. Every time we plan the next quarter, there s an internal debate: do we put our feature plans out in the open, or keep them internal until code actually hits production?

Do you think early-stage products need a public roadmap even a simple Trello board? Or does that only backfire the moment priorities shift and a promised feature gets delayed?

Should it live on a public page like Canny or Notion? Be sent out in monthly newsletters? Or is sharing upcoming plans just setting yourself up for unnecessary pressure?

In our case, we ve started realizing that being brutally honest about why something got delayed actually builds more trust than making shiny timeline promises.

My browser tab bar gets messy quick and constantly using the trackpad to click around really slows down my workflow. I spent the afternoon looking for a basic keyboard shortcut extension to hop back and forth between active tabs.

Instead of simple hotkey tools everything on the Web Store feels like an over engineered workspace manager requiring full access to reading browser data.

What tiny privacy friendly extension do you use that handles basic tab cycling without any extra fluff?

Set a bunch of strict rules for myself when starting out about keeping things simple and never taking quick shortcuts.

A couple years in half of those rules are gone because real life hit and decisions got way more complicated.

How do you tell if you're just adjusting to real business needs or actually losing your original vision?