#063 - I was fired for using HTMX · Backend Banter summary

Key takeaways

Prioritizing developer experience over code quality can lead to long-term issues, including technical debt.
Understanding the frameworks and their implications is essential for maintaining overall performance in software development.
Refactoring should be an integral part of software development to ensure maintainability and adaptability.
Providing necessary mentorship and resources to junior developers can enhance team performance and project outcomes.
Personal experiences in tech can offer valuable lessons for others in the industry to avoid similar pitfalls.

Summary

Introduction to HTMX and Spiro's Dismissal

In this episode, Spiro Floropoulos shares his personal experience of being fired as a result of using HTMX in his development work. The discussion seeks to unravel the events that led to his dismissal, highlighting how an overemphasis on developer experience can lead to pitfalls in software development. The conversation tackles many layers of the tech industry's current state, advocating for knowledgeable approaches to frameworks rather than just focusing on feelings or appealing to developer experience.

The Emphasis on Developer Experience

The podcast debates the industry's fixation on developer experience and how it can often obscure logical decision-making in coding practices. Spiro asserts that while a positive developer experience is crucial, it should not override the importance of performance and stable code. The discussion delves into examples from the industry where prioritizing developer comfort has led to adverse outcomes on overall code quality and stability.

Technical Debt and Its Consequences

Spiro raises concerns about the accumulation of technical debt in software projects, particularly how they escalate due to poor initial decisions rooted in prioritizing speed and developer experience over quality. The conversation emphasizes the need for developers to really understand the implications of their choices, such as adopting frameworks that may initially offer ease of use but ultimately contribute to larger complications and maintenance issues later.

Refactoring and Maintaining Code Quality

The guest recounts his experiences with refactoring, detailing specific instances where he had to rewrite significant portions of the codebase for better maintainability, especially when encountering challenges with legacy code. Spiro illustrates a case with HTMX, pointing out that although the framework helped speed up certain processes, it also presented complex integration issues that required careful consideration, resulting in extended periods of buggy or incomplete features.

Talent Development and Junior Developers

The episode touches upon the challenges of hiring and training junior developers, emphasizing the necessity to provide adequate resources for them to thrive. Spiro advises on the importance of mentoring and maximizing learning opportunities for less experienced team members, ensuring they feel supported and engaged, which is vital for long-term project success.

Conclusion and Future Opportunities

The podcast wraps up with Spiro indicating he is currently seeking work and encourages listeners to connect with him regarding any opportunities. He reiterates the goal behind sharing his story is to provide insights and encourage better practices in the industry.

Show notes

In today’s episode, we bring Spiro Floropoulos, a senior developer and architect with over 20 years of experience. This episode is an unusual one, as Spiro recently got laid off due to a bizarre chain of events that involved HTMX, overworking, and technical debt.

But we’ll learn from this story, as we want to shed some light on how situations that Spiro described could be avoided, namely how the tech industry is obsessing over developer experience and why that’s detrimental, why abstractions should be teaching you the technology as opposed to just doing the work for you, why you should be able to train your junior devs and much more!

Learn back-end development - https://boot.dev

Listen on your favorite podcast player: https://www.backendbanter.fm

Spiro's X/Twitter: https://x.com/spirodonfl

Spiro's Website: https://spirofloropoulos.com/

Timestamps:

00:00 Intro

00:35 Why are we having this conversation

01:33 How was HTMX involved in this?

03:38 Spiro's background

05:58 Why are we focusing so much on developer experience?

13:38 The Tech Industry as a whole is headed down the wrong path

16:17 Abstractions teaching you about the underlying technology rather than hiding it

18:47 What are the long-term consequences of unresolved technical debt?

26:46 There's things you can't blame frameworks for

28:27 We have to slow down

30:46 What happened after the introduction of HTMX into the project?

40:26 Hiring juniors is great, but you should have the resources to train them

47:00 The Technical Debt

50:32 The more complex the feature became, the bigger the struggle with HTMX

53:42 The reasons why Spiro was let go

57:10 Instead of Agile we should treat our programmers like adults

57:31 HTMX was instant and testing ability was better

01:01:21 Is Spiro looking for work?

01:02:00 Where to find Spiro

#063 - I was fired for using HTMX