Software devs in general seem to have a hard time with balance. No comments or too many comments. Not enough abstraction or too much, overly rigid or loose coding standards, overoptimizing or underoptimizing. To be fair it is difficult to get there.

Interesting, yeah. I inherited a Blazor project though and have nothing positive to say about it really. Some of it is probably implementation, but it’s a shining example of how much better it is to choose the right tool for the job, rather than reinventing the wheel. For a while I was joking about setting the whole project “ablazor” until we finally decided to go back to a React/C# ASP.NET stack. If you’re thinking of using Blazor still, though, I think two fun things to look into are “linting issues with Blazor” and “Blazor slow”. I’ve heard people praise it, but they tend to be those who consider themselves backend devs that occasionally get stuck making frontends.

Depending on the software, you still get to think about garbage collection!

Nothing wrong with being an EMT who does all those things as hobbies, unless the capitalist pigs to whom you sell your hours demand more than their fair share…

The problem with modern UI design in a nutshell…

I unironically use this one all the time, because it captures both sentimental and practical value for me. I just compare the thing itself with the joy of having that much more clean empty space.

E plumbus unum

I wrote a json prettifier a couple months ago with just a couple lines of code. I thought it would take a while but ended up taking like 10 minutes.

Shout out to the yt channel Ahoy for making some of the most sleepable video game videos, like this one: https://youtu.be/9F9ahZQ7oP0?si=AzP9X_vq-o96gPD_ Also great when you’re not sleeping!

It’s my birthday too! Happy bday!