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

Carry your example far enough and the system becomes brittle. We need people who know how to make the machines that make the machines. If you go far enough up the stack components become unique enough that they're unique pieces of engineering.


Correct. Every component made in distant factories all over the world is like micro services model of software development where every function should be its own service.

There is big support of these models from consulting world. If it doesn't work than it just means we need further micro components to make it work but never try back to integrated system.


The problem is that the idiots making their stupid cog in the machine decisions have a financial and ideological incentive not to see themselves, their work and the way they've been trained to approach their work.

Some two bit code monkey screeching "it's not my fault my code shit all over the production database when something upstream of it got a little wonky, I coded to the spec I was given" is no different than some dumbass middle manager or MBA at HQ who's intentionally making the system more shitty for negligible, but measurable, savings so they can fuck off into the sunset with their bonus for hitting KPI before it all comes crashing down.


The meta problem is the present-immaterial nature of risk and possible future consequences. Dollars and time saved are concrete present quantities.

Ergo, any decision which saves dollars and time in the present but increases future risk looks good... in the present.

It's always surprised me that businesses don't attempt to quantify risk in an effort to produce a more balanced decision function.




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

Search: