Why "Enterprise Tools" Are Bad for the Enterprise
summary
Argument: big expensive vendor stacks hurt agility because they force slow context switches, create support silos, and lock in one brittle API. Evidence: a Verizon engagement yields a causal model built in Flying Logic showing license-driven tool groups and inertia; experiments use run code run CI, RSpec, Cucumber, ActiveRecord and small services (nginx thin redis solr) to stitch solutions; rules engine pilots mostly treat symptoms and fail to speed change. Conclusion: human-scale tools with escape-hatch APIs enable fast feedback and pragmatic hacks.
AI-written summary · about
chapters (10)
- 0:00Start
- 2:56Is Ruby Ready for the Enterprise
- 4:11Enterprise Tool Market
- 4:32The Challenges of Enterprise Software Are about the Enterprise
- 13:59Agile Manifesto
- 16:36Context Switching Costs
- 22:10Typical Enterprise Tools
- 32:48Model of Incentives
- 37:41Rules Engines
- 42:32Preventing People from Making Mistakes
related talks
30mThree value inhibiting dysfunctions of enterprise software development
29mFrom big to small and back again
29mThe Experimental Enterprise
26mNot-So-Greenfeld Agile Implementations
40mPlatform Wars: The Battle Between Golden Paths and Spaghetti Pipelines
01h 03mBeyond the innovator’s dilemma
44mLies we tell ourselves about developer infrastructure
01h 02mThe Enterprise DevOps Challenge