Pitfalls in Technology Selection
summary
Budget and licensing drive choices: vendor audits and sudden per‑seat or per‑core price jumps (Salesforce, Oracle examples) can triple costs and block virtualization plans. Customizing ERP often costs more to maintain than to accept process change. DIY projects hinge on hiring and keeping engineers; complexity doubles failure rate as components double. Notable wins: a DUKPT implementation runs five weeks late but ultimately succeeds; switching from SAS to R and NumPy replaces costly licenses. Beware free gifts that save $100k and later cost $1M.
AI-written summary · about
chapters (19)
- 0:00Start
- 1:48DISCLAIMER
- 4:39CODE SMELLS
- 7:26You can do things without a budget. Just not well. Or fast.
- 9:01KNOW YOUR TCO
- 10:49LICENSING
- 13:49ORACLE ON VSPHERE
- 14:48COTS CAN CYA
- 16:18DIY: KNOW YOUR LIFT
- 17:11IS THIS REALLY YOUR CORE BUSINESS?
- 20:51AREAS TO LOOK INTO
- 21:51DATA IMPORT/EXPORT
- 31:53COMPLEXITY
- 32:30MASSIVE THROUGHPUT
- 33:28DISTRIBUTED SYSTEMS
- 34:57PINNING HOPES ON THE FUTURE
- 38:53GETTING EATEN BY YOUR ECOSYSTEM
- 40:34WHAT'S HOT, WHAT'S NOT
- 41:20BUT BE CAREFUL OF THE NEW, HIP, UNTESTED
related talks
47mBuild vs Buy: Software Systems at Jurassic Park
48mAgility in Large Transformation Programs – An oxymoron?
18mAchieving Innovation and Stability for Enterprises
20mRethinking technology at large enterprises
11mMaking better build vs buy decisions
25mMaking smart investments: A framework for maximizing your ROI in technical decisions
21mSelling your Company on Chaos Engineering
57mStrategic Decision-Making for Tech Leaders and Developers