CodingWithJesse

Exactly my point. Learning stuff is fun. But if you're going to introduce new technologies or programming languages into a system, you need to make sure it suits the skills and experience of the rest of the team. Rewriting the company's admin dashboard in Elm, not letting anyone else work on it, and then quitting - that's just cruel. (Elm's cool, but you know what I mean..)

100% wasn't. I use Derek Sivers' approach, search "writing a sentence per line", and I try to keep my sentences short intentionally. If you view source on the HTML you can see the line breaks.

Exactly right.

Simple in the sense that it would have been quick to do, yes, and I almost did that instead. But I felt it would have been more duct tape on an increasingly fragile and outdated system, and I decided the best path forward for the project was to modernize the whole system instead.

I got an email today from one of my clients, letting me know that one of his web apps was down. He said he was getting an error and asked me to take a look.

In the end, I was able to fix it and get it running faster than ever. What caused it turned out to be a huge surprise to me. I thought I'd outline the steps I went through here, to try to help others trying to solve similar problems in the future.

Yeah I think so too. It'll be a lot simpler to refer to all of it as "Svelte" instead of having a separate framework or package.