2 ms·
> find columns that are near enough totally unused. This is a strong signal that the feature which relied on the column is not valuable, and the column along wi
by drewcoo 4y ago
> find columns that are near enough totally unused. This is a strong signal that the feature which relied on the column is not valuable, and the column along with the feature can and should be deleted.
The actual article's title should have been "Delete Unused Code."
There's also a partial rant about what ORMs do to schema in there. Second article?
- rileymat2 4y agoOften "unused" is tricky too, although customers may not 'actually' use it, sales uses it as a selling point. Sometimes it is easier for sales to check the box, by saying yes we have that feature, than go into a detailed explanation of why it is not necessary in the particular product.
- Closi 4y ago> Often "unused" is tricky too, although customers may not 'actually' use it, sales uses it as a selling point. I think there is a semi-truism in enterprise software too, which is that 90% of customers will only use 10% of extended functionality, but they all use a different 10%. Let's say you have a shopping basket software and only 10% of customers are using your 'expiry-date-tracking' flag (lets say it allows you to track quantities of expiry dates), you can either argue that this is useless to 90% of customers or that it's absolutely critical to 10% of your customers. You don't sell enterprise software by convincing a supermarket that they don't need expiry date tracking - if you want to operate in that sector, you have to sell it by understanding and matching what the customers needs.