#063 - I was fired for using HTMX from Backend Banter

#063 - I was fired for using HTMX

1 hour 3 minutes Posted Jul 22, 2024 at 11:00 am.

Intro

Why are we having this conversation

How was HTMX involved in this?

Spiro's background

Why are we focusing so much on developer experience?

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

Abstractions teaching you about the underlying technology rather than hiding it

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

There's things you can't blame frameworks for

We have to slow down

What happened after the introduction of HTMX into the project?

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

The Technical Debt

The more complex the feature became, the bigger the struggle with HTMX

The reasons why Spiro was let go

Instead of Agile we should treat our programmers like adults

HTMX was instant and testing ability was better

Is Spiro looking for work?

Where to find Spiro

0:00

1:03:09

Download MP3

Share at current time

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:

← See all 82 episodes of Backend Banter