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

It goes beyond that. Process is rules that stop people from being able to do things they shouldn't; bureaucracy is process that stops people from being able to do their jobs.


Process is rules that stop people from being able to do things they shouldn't

People tend to disagree on what should or shouldn't be able to do. Should a developer be able to release code to production servers? Should a developer be able to change the database schema? Should a developer be able to access the database tables through an ORM or ad-hoc SQL or must everything go through stored procedures?

A healthier way to look at process is that it's about facilitation, not control.


Bureaucracy is a kind of process group think. It involves adherence to fixed, externally defined, rules. Each contributor is doing things in a way they think are cumbersome and difficult to change.

The alternative to fixed rules, is to discuss issues and tradeoffs, and trust developers to make good decisions based on knowledge.


and trust developers to make good decisions based on knowledge

I would add to that, "give individuals enough room to make mistakes that everyone, especially themselves, can learn from"




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

Search: