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

Furthermore lots of decisions in enterprises look like the following:

An executive is approached by a vendor. The vendor entices the executive, shows them a good time, gives them a really good assurance their service is worth it.

An engineer hates this service because it sucks. Because the decision was made based on how cool it looks, not by technical needs.

Given that, it is hard for an executive to get approached by a vendor who says "okay, this will cost a crazy amount of time and money but we'll make your systems more modern" which sounds like "hey, I'm going to come in and offer to replace a system that has worked for 30 years with something modern and potentially risky. And it'll cost you a lot." The executive doesn't (usually) realize that the true cost is really high and goes up with time. And of course they don't want to lose their cushy job so hell no they won't take it. Also the executive isn't directly working with the engineers so he doesn't truly know if he can trust them.



This reflects a failure of modern corporate structures to empower engineering to the role it should and (ought) to be having.

Thankfully, this is changing rapidly and the valley is leading the way.




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

Search: