Hacker News new | ask | show | jobs
by Swizec 10 days ago
> Now, a comparable energy budget we used to use "deciding what to build" (because labour was scarce) is now energy we can divert toward "unbuilding stuff that was a mistake"

The hard part is that you very quickly become Salesforce or Jira or <insert large confusing product>.

You have thousands of users who love your product and pay lots of money and find the features absolutely essential to their workflow. Everyone says your product is bloated and has too many useless features, if only you could delete a bunch of crap they don’t use your software would be perfect.

They all use a different 20%. Delete a feature, lose a fifth of your users.

1 comments

Great point. It's probably obvious from my take that I build a lot of bespoke software, and have blind spots about the pitfalls of building at scale :)