> I'm pretty sure that the real reason is spam. Nobody is composing e-mail with complex designs to send their colleagues.

There is a use case of using HTML for transactional emails:

- enhance company branding with design - embed call to action items via hrefs

1) Coding clearing in the moment vs (2) coding clearly for future selves is two different mindsets/contexts right there.

(3) Communicating clearly is an orthogonal skill to coding clearly. I think this skill is barely acknowledged in engineering cultures in comparison to the above.

I feel you have to have an engineering culture that values institutional knowledge retention, team education and growth — and not treating engineers as fungible — to get to level (2). Level (3) would be a great place to work.

Are we talking about the book "Souls in the Great Machine" or real history?!

Agree! Came here to give props to EdgeDB. Completely removes the API layer if used with something like SvelteKit. Everything defined in their schema language which then generates typed clients for you.

In my experience the use case is not limited to a single full-stack developer - this approach has turned our entire polyglot team into full-stack devs — no one is afraid of the data layer now. Super refreshing.

For public facing endpoints, "exposing an OpenAPI 3.0+ compliant JSON REST API" would be the first thing I'd reach for.

This is next level cool. Avid mountain biker here and travel all over to ride new trails. Some of which are quite remote and take a bit of planning before setting out solo for the first time.

In my journey I've tried about just every setup imaginable. This app checks all the boxes I've been looking for:

- local data (privacy) - import and store all ride gpx's - can map out new rides - can export routes to gpx for sharing and loading up on Garmin/iWatch/etc - UI/UX clean and simple

Has everything I want and nothing more. I wish I had coded this... :)

EDIT: the meta data cataloging options to be explored. Personal ride journal in one place finally?