Live data from Hacker News

The Tyranny of Process Worship Within IT

ciopedia.com

21–22 of 22 posts

Re: The Tyranny of Process Worship Within IT

#21
post #14
post #7

I think a distinction needs to be made between actual process and codified process. The former always exists, and the only question is whether it is working or not. The latter is endemic to large organizations with disaffected and mediocre management and employees, which is what Netflix is actively fighting against. However the tone of this piece and the original Netflix manifesto does not acknowledge this distinctio…

Codified process help to increase efficiency by remembering the best way you solved the same problem before. This is extremely useful when you are repeating problems, but it stands in the way when you keep doing new things. The real question is not process and group productivity vs individual productivity, but how fluid your problems are. When a random customer calls the help desk ask "Is it plugged in?" aka say "Ple…

Yes they do that. Additionally I think in a codified process it's probably more important to write down why the process is there and what problem it attempts to mitigate/solve. Then when the problem has been solved in some other way the process should be removed.

(Written) Processes seem to be the same sort of thing as code commenting.

Re: The Tyranny of Process Worship Within IT

#22
post #10

"We should focus on what people get done, not how many hours or days are worked. Just as we don’t have a 9-5 day policy, we don’t need a vacation policy." While I admire the sentiment, it's rather anti-family.

I couldn't disagree more -- what could be more pro-family than being able to come in to the office for face time 10~3, and get shit done on your own schedule?

What could be more pro-family than not having to count vacation days, being able to spend time with your kids instead of reading HN and 'looking busy' when you don't have a pile of work?

Post reply on HN