- 170comments
- 85comments
- 14comments
- 43comments
- 119comments
- 32comments
- 171comments
- 2comments
- 33comments
- 142comments
- 3comments
- 102comments
- 25comments
- —discuss
- 284comments
- 254comments
- —discuss
- 236comments
- 26comments
- 72comments
- 27comments
- 17comments
- 136comments
- 7comments
- 42comments
- 1comments
- 171comments
- —discuss
- 119comments
- 81comments
Yes. Don't succumb to featuritis. Destroy the barnacles.
The one I get constantly is we want "custom reporting". Well what the hell is that really? Why, why, why do you need that? Then I just build a new feature they will actually use and defer "custom reporting" for another month.
I see this all the time... custom reporting, reports... I have seen this so many times in so many places and I wonder why the fuck are people asking about it. Most of the time they have little clue of what they want reported, or how they want the data to look like. Nearly 100% of the time what they mean by reporting is "join all the tables that have a foreign key, force join all the ones that do not have a foreign key by using a union against some arbitrary value picked at most-likely-to-be-the-right-one and dump everything on an "excel spreadsheet". This is the golden standard most people go by.
It’s hard decision, but it has to be made.
I’m not building space elevator.