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

The first part of the essay was a very interesting view into bureaucracy and overcoming it via personal connections. The second part seemed to be very hand-wavy armchair-psychologist-esque. The thesis seems to be that:

- Some/many workers care more about job stability, as opposed to making a difference at work

- Such workers are suffering from "real psychological damage"

- They are constantly hounded by imposter syndrome, because they aren't respected by anyone else, and they know it

- They often end up as senior bureaucrats/leaders, because of their risk aversion, and because they are trying to overcompensate for their low self-esteem and psychological damage

- They also "end up in startups more often than you might expect" (which seems ironic since startups are far more risky than being at a BigCorp)

At the risk of putting myself out there, I suspect the above conclusions are quite a reach.



The part that they "end up in startups more often than you might expect" was a fascinating line for me and one that resonates with me quite well based on my experience.


I've often been shocked by how conservative an unprofitable/stagnant growth startups will be with engineering time. I've seen growing teams locked in incremental product/platform investment with no major new customer features in the roadmap.

I wondered where the conservatism came from given that at a business level the status quo was failure. This seems like a plausible explanation.


Yeah, I've been quite puzzled too, and figured perhaps they were anecdotal but perhaps they are not. I really like this definition of engineering process as "a decision making process (often iterative) in which the basic sciences, mathematics, and engineering sciences are applied to convert resources optimally to meet a stated objective" (https://en.wikipedia.org/wiki/Engineering_design_process) and have met too many, by their unwillingness to commit and take ownership of a decision, pretty much stall the entire engineering development progress.




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

Search: