4 ms·
An anti-bloat tool for software development. There are plenty of tools that lets you plan, organise and bikeshed over all the things you want to do, like Jira,
by Tabular-Iceberg 4y ago
An anti-bloat tool for software development.
There are plenty of tools that lets you plan, organise and bikeshed over all the things you want to do, like Jira, but I think a much bigger efficiency booster would be one that helps you decide what not to bother doing at all.
- warrenm 4y agoalong those lines ... prioritizing what you don't need to keep (in terms of libraries, unused code, unused features, etc)
- Tabular-Iceberg 4y agoOne problem is that the most important metric of a feature, its ROI, is also the hardest one to measure. Measuring how hot the code paths are may not be much better than measuring programmer productivity in lines of code. How can we quantify the investment without invasive surveillance and micromanagement of developers, and how can we quantify the return without reading the customer’s mind?
- warrenm 4y agoIt shouldn't be that hard to excise unused code blocks, at the very minimum, from a finished product before it goes to prod :)
- Tabular-Iceberg 4y agoNo, excising unused code blocks is a solved problem. The trick is to identify code that is used, but shouldn’t be. I mean identifying features with a negative return on investment, features that you should avoid building. What makes the problem even harder is to consider not only the developer hours, but the opportunity cost of not building a different, more valuable feature.