Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

There is a meta-meta situation surrounding really good software management.

You can knock up some code that say solves a specific business problem right now. (meta:0)

But you need an environment that can take a new piece of code and deploy it and test it (meta:1)

how is that code running - this is shadingnfrom production monitoringninto QA and performance (meta:2)

Compare all the running code and its performance against the benefits of replacing code or going back to level 0 and just fixing a business problem (meta:3)

Then this death eater - meta 4 I think.

And to me this is why comments like "software needs to solve business problems" is naive - once you start using software you need more software to manage the software - it's going to grow till it consumes the business.



> once you start using software you need more software to manage the software - it's going to grow till it consumes the business.

You can replace "software" with "people" and you'll end up with a sentence that's equally true.


True. Which is why it's important to not measure the ROI of a feature by the time and resources you spend on it vs. how it increases your revenue.

You also have to include that every further feature is now _more_ expensive than before.




Consider applying for YC's Winter 2026 batch! Applications are open till Nov 10

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: