News for hackers. Stuff that matters.

A comment on The top bug predictor is not technical, it's organizational complexity. Parent comment

Re:The top bug predictor is not technical, it's organization... by silveroriole on Wednesday December 18, 2019 @09:22AM (#21825087)
What actually happens in a “business purpose focused” company: You tell the boss you need to double the estimate they gave to the customer, so that you can pay the tech debt and add those layers we need. Boss refuses, we need that change now so get it done without fixing the debt, why is the team so incompetent that they didn’t add layers to start with, why didn’t you just fix the tech debt on your own time in quiet periods, we can’t have a ticket for that since it doesn’t add business value, blah blah...

;)

[ Parent | on HN ]
Re:The top bug predictor is not technical, it's organization... by _def on Wednesday December 18, 2019 @09:50AM (#21825368)
That's why there's no final answer to "layer: yes or no?". It depends. And as a developer it's your job to guess which decision is more likely to save you time (= money) in the future. There's no way to know the right answer for sure because it depends on further (business) decisions that aren't made yet.
[ Parent | on HN ]
Re:The top bug predictor is not technical, it's organization... by jressey on Wednesday December 18, 2019 @11:19AM (#21826367)
What you're describing sounds to me like poor departmental relationships and the typical challenges of lots of people with lots of goals working together.

I sure hope all of y'all's companies are 'business purpose focused' or you're gonna be looking for a new job pretty soon.

[ Parent | on HN ]
Re:The top bug predictor is not technical, it's organization... by celticmusic on Wednesday December 18, 2019 @11:33AM (#21826527)
are you claiming this same boss would have given you the time to do it at some other point, thereby delaying something else?
[ Parent | on HN ]
Re:The top bug predictor is not technical, it's organization... by silveroriole on Wednesday December 18, 2019 @12:53PM (#21827372)
Ironically yeah ime - when doing it upfront. These places sometimes expect so much business value from Cool New App that they let it spiral out of the agreed timespan and you get lots of time to ‘add layers’ (i.e. plan for the future or overcomplicate, however you see it). Once Cool New Thing is live and expectations have cooled, they just want to make some ‘small’ changes, nobody wants to let you restructure the architecture.
[ Parent | on HN ]