> Markdown version of [/videos/1916-old-tools-new-tricks?t=68](https://www.wearedevelopers.com/videos/1916-old-tools-new-tricks?t=68). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# Old tools, new tricks

Are shiny new frameworks slowing your team down with unknown failures? Discover why pairing battle-tested legacy tools with modern LLMs provides a massive strategic advantage.

- **Speakers:** [Benjamin Bischoff](https://www.wearedevelopers.com/@benjamin-bischoff)
- **Event:** World Congress 2026 Europe - Virtual Stage
- **Published:** June 30, 2026
- **Duration:** 33:28
- **URL:** https://www.wearedevelopers.com/videos/1916-old-tools-new-tricks

## Summary

In the fast-paced software development landscape, teams are constantly bombarded with new technologies and tools, often falling prey to the assumption that new is always better. This session explores the psychological traps of technology adoption, including the "tutorial dilemma"—where oversimplified happy paths create false confidence—and the sunk cost fallacy that traps teams into ill-fitting architectures. Relying exclusively on cutting-edge software amplifies the risk of "unknown unknowns," whereas choosing boring, established technologies provides the strategic advantage of well-understood failure modes and robust, battle-tested community support.

To demonstrate the enduring value of legacy software, a continuous testing workflow is constructed using progressively older tools. The implementation starts with Selenium for seamless browser automation, layered with Maven for rigid but reliable dependency management, Bash for straightforward cross-platform scripting, and Make to abstract execution commands into universally understood targets like `make test`. This layered architectural approach proves that older tools actively reduce technical overhead; by inherently doing less, they minimize configuration mistakes and serve as universally compatible proxies across diverse project architectures.

Ultimately, deep familiarity with an existing framework should be viewed as a profound asset rather than a limitation, emphasizing the need to decouple true project progress from mere technological novelty. Legacy software consistently benefits from the Lindy effect, meaning tools that have survived for decades usually remain relevant. Furthermore, artificial intelligence accelerates the utility of older frameworks; because LLMs process vast historical repositories like Stack Overflow, they hallucinate far less and function as highly accurate coding assistants when debugging established systems compared to brand-new, niche libraries.

**Keywords:** technology adoption biases, software tutorial dilemma, evaluating unknown unknowns, lindy effect in software, legacy testing frameworks, selenium browser automation, maven dependency management, bash shell scripting basics, make execution targets, unix philosophy patterns, reducing code complexity, sunk cost fallacy engineering, ai coding assistants, llm hallucination risks, software failure modes, automated browser testing

## Chapters

1. **Navigating the influx of new software technologies** (01:08) — The rapid emergence of new tools forces developers into dilemmas around what learning investments are truly worthwhile.
1. **Overcoming cognitive biases in software tool evaluation** (04:08) — Common psychological traps like the tutorial dilemma, sunk cost fallacy, and Maslow's hammer lead to poor technology adoption decisions.
1. **Managing team risk and the bus factor** (07:36) — Adopting single-expert tools introduces critical knowledge bottlenecks and team skepticism based on ambiguity bias.
1. **Comparing unknowns between new and established technologies** (09:20) — While all software contains uncertainties, shiny new technologies possess a significantly larger magnitude of unpredictable edge cases.
1. **Applying the Lindy effect to software reliability** (11:27) — Unexciting older tools are often more reliable and cost-effective because their lifetime expectancy correlates with their age and their failure modes are well-documented.
1. **Selecting Selenium for browser automation and testing** (13:18) — Establishing a basic website test scenario underscores the reality that older libraries like Selenium exist strictly to drive browsers rather than act as full testing frameworks.
1. **Implementing basic website interaction tests with Selenium** (15:53) — Initializing a Chrome driver and sequentially finding and asserting website elements demonstrates typical real-world execution speeds without artificial delays.
1. **Refactoring test code dependencies with Maven and JUnit** (17:58) — Wrapping standalone scripts into structured JUnit test lifecycles managed by Maven standardizes executions and narrows possible configuration errors.
1. **Controlling browser configurations via simple Bash scripts** (22:13) — Extending Java tests with system properties allows basic shell scripts to dynamically allocate driver configurations like Firefox or Edge based on user input.
1. **Abstracting build and test operations with Make** (25:48) — Utilizing Makefiles as top-level proxies standardizes developer commands across differing projects regardless of the underlying language or framework implementations.
1. **Leveraging AI code generation for older software tools** (29:56) — Large language models generate highly accurate code for decades-old tools due to extensive historical training data and resolved edge cases.

## Related Moments

- [Navigating legacy systems and unconventional software testing practices](https://www.wearedevelopers.com/videos/557-iot-the-road-to-sustainability) (from "IoT: The road to sustainability")
- [Diagnosing the persistence of legacy runtime code architectures](https://www.wearedevelopers.com/videos/1863-stop-using-node-js-like-it-s-2020-alfonso-graziano) (from "Stop Using Node.js Like It’s 2020! - Alfonso Graziano")
- [Overcoming the human challenges of software maintenance](https://www.wearedevelopers.com/videos/917-coffee-with-developers-robby-russell) (from "Coffee with Developers - Robby Russell")
- [Evaluating tools and avoiding the sunk cost fallacy](https://www.wearedevelopers.com/videos/100288-why-git-still-matters) (from "Why Git Still Matters")
- [Managing technical debt in legacy web applications](https://www.wearedevelopers.com/videos/917-coffee-with-developers-robby-russell) (from "Coffee with Developers - Robby Russell")
- [Recognizing the symptoms of a broken legacy web project](https://www.wearedevelopers.com/videos/647-defeat-that-legacy-monster-guerilla-refactoring-with-web-standards) (from "Defeat that legacy monster! Guerilla refactoring with web standards")

## Related Articles

- [Ignore the Hype: How to Avoid Being Deceived by Technological Trends](https://www.wearedevelopers.com/magazine/528-ignore-the-hype-how-to-avoid-being-deceived-by-technological-trends)
- [Boring Tech Is What Matters](https://www.wearedevelopers.com/magazine/623-boring-tech-is-what-matters)
- [Exploring AI: Opportunities and Risks for Developers](https://www.wearedevelopers.com/magazine/522-exploring-ai-opportunities-and-risks-for-developers)
- [Dev Digest 137 - AI'm not sure about this](https://www.wearedevelopers.com/magazine/485-dev-digest-137-ai-m-not-sure-about-this)

## Related Jobs

- [Tribe Lead - ( Software) Engineering Centre of Excllence](https://www.wearedevelopers.com/jobs/ext/1475530-tribe-lead-software-engineering-centre-of-excllence) at **SD Worx**
- [Staff Software Engineer, Copilot Experiences](https://www.wearedevelopers.com/jobs/ext/164361-staff-software-engineer-copilot-experiences) at **GitHub**
- [Senior Software Engineer](https://www.wearedevelopers.com/jobs/ext/15942-senior-software-engineer) at **GitHub**
- [Senior Software Engineer, Enterprise Products](https://www.wearedevelopers.com/jobs/ext/1841248-senior-software-engineer-enterprise-products) at **GitHub**
- [Principal Software Engineer, Enterprise AI Platform](https://www.wearedevelopers.com/jobs/ext/1467292-principal-software-engineer-enterprise-ai-platform) at **GitHub**
- [Staff Developer Advocate, GitHub Security Lab](https://www.wearedevelopers.com/jobs/ext/1921051-staff-developer-advocate-github-security-lab) at **GitHub**