Products · Product
Chef
Raised as a usability problem by 25 people on Hacker News over 16 years (2010–2025), in 24 threads.
No issue was raised by at least 3 people in 3 threads this year.
No issue was raised by at least 3 people in 3 threads in the last 5 years.
Every issue, all time, most people first
Documentation is hard to learn from, making Chef a struggleUnreviewed
20102026- Chef's terms like cookbook, kitchen and knife make searching hard2021-03-14
- Chef tooling and resources are poorly documented, so users struggle to get things working2020-04-16
- Hard to understand how to write Chef cookbooks2014-08-05
Unreviewed issues were grouped by machine: Claude Haiku labelled each comment as a usability complaint, named what it's about and summed up the problem in a line, and a small model grouped similar problems. Nobody has checked them by hand. Expect mistakes.
The newest 27 complaints
- Chef feels full of weird anti-patterns and buggy, incomplete implementations2025-11-14
- Chef's terms like cookbook, kitchen and knife make searching hard2021-03-14
- Editing user config files needs many permission workarounds because Chef wasn't built for it2020-11-09
- Chef tooling and resources are poorly documented, so users struggle to get things working2020-04-16
- Takes a lot to learn and feels verbose, slow to get configurations right2019-10-30
- Hard to find how to get started amid many products and sales pages2019-04-02
- Ruby code disappears and node state is hard to understand due to evaluation phases2019-03-22
- Unsubscribe link leads to a login screen for an unfamiliar service, with no simple way out2015-11-03
- Same API call creates or updates nodes, so it's easy to make a mess by accident2015-08-31
- Hard to understand how to write Chef cookbooks2014-08-05
- Ruby-based DSL is hard to use unless you already know Ruby2014-08-05
- Steep learning curve that makes the tool hard to pick up2014-06-24
- Hundreds of lines for unused platforms make simple tasks much harder2014-03-15
- Recipes work on one Ubuntu version but break on others, fixing some problems and creating new ones2014-02-02
- Hard to know which override level wins; many confusing precedence options and situations where desired override fails2014-01-24
- No obvious entry point; learning materials jump from trivial examples to huge manuals2014-01-03
- Server is painfully slow and hard to run for small node counts2013-11-22
- Documentation is hard to learn from; you must suffer through it to learn Chef2013-08-14
- Documentation is hard to follow because pages refer back to each other2012-10-30
- Chef server stack is huge and certs/knife setup is a pain2012-10-30
- Opscode's SaaS product is borderline unusable for the commenter2012-05-05
- Chef silently fails after an update with no error message, docs, or clue why2012-04-29
- Needs heavy manual tweaking and upkeep to run, with cookbooks failing to appear or delete2011-10-09
- Takes a long time to set up and needs fixes for basics; frequent crashes early on2011-10-09
- Re-running the setup script after changing values produces errors, and cleaning up a failed install fails2011-09-10
- Chef documentation was not available enough, so the author waited before adopting it2011-02-22
- Steep learning curve when running your own Chef server2010-07-22