Picking Your (Tech) Poison Wisely
summary
Start by defining what to build, use Google/ChatGPT/Bing to shortlist candidates, and favor the simplest tool that meets current and near-future requirements over an all‑in‑one framework. For existing projects weigh legacy, transition cost, team familiarity and modularity; follow five planning steps: requirements, re-evaluate business logic, budget, maintenance, scope. Avoid blindly copying big companies, narrow to two or three options, test them yourself, look for pitfalls, and be ready to roll back and iterate.
AI-written summary · about
chapters (11)
- 0:00Introduction and speaker intro
- 1:04About the speaker
- 1:45Choosing tech from scratch
- 3:34Reasons to switch tech stacks
- 6:03Should you change everything
- 8:55Planning the tech switch
- 11:50Common mistakes to avoid
- 17:31Evaluating new technologies
- 20:52Pitfalls of over-optimism
- 22:15Learning from failure
- 22:59Conclusion and final advice
related talks
47mHow To Build Future Proofed Applications
51mHow Not to Break a Simple Idea
26mBe Awesome By Being Boring
29mBuilding What Developers Actually Want: Lessons Learned
36mIf, when and how? - Strategies towards web-based tooling
15mThe AI-Augmented Engineer [...]
09mLeading a team through 0-1 product development
40mBuild Better Software