Even without AI, Web Development was destined to be a short lived industry.

Sure, it will be around in some form, but a lot of that space has been taken over by mobile app development. Another portion of the market has been taken over by social media (your business doesn’t need a website anymore; it needs an Instagram/twitter/etc). And yet another portion has been taken over by products like Wix that allow non-experts to make good enough websites themselves (even without AI).

Really, thinking of “web dev” as a profession is a category error. You are a graphical designer and programmer that was working in the web industry. There are plenty of other industries that hire your profession.

• /ram - tmpfs filesystem
• ~/.local/bin - added to my path
• ~/.local/software - any user-local program more complicated than a binary gets a directory here. Generally a binary would be symlinked to ~/.local/bin
• ~/.local/venv - shared python venv to use for one liners and small scripts
• ~/repo - local filesystem backed package repository for which the host system is configured to install from
• ~/.local/repo - local filesystem backed package repository for which the host system is not configured to install from (used for mock, VMs, and external systems).
• /overflow - Used to point to a large secondary hard drive (back when having a small ssd was the economical thing to do. Nowadays, it is just where my large directories go cause I can’t be bothered to get used to a more sane setup

If it’s not a backend error, you shouldn’t be throwing a 5xx error code. Since you are throwing a 500, you have a server bug; even if that bug is simply “sends incorrect error code”

I would argue that in your application, a wrong URL is a sever error. That error being improper handling of a client error.

I’m not a web dev, but had a similar problem with a niche compiler I used to develop.

We were pretty good at validating invariants at the mid and back-end. This meant that most user errors got reported as internal errors. Generally, these errors were good enough that users were able to get used to reading them and fix their code.

It was next to impossible to actually get users to file bugs about this. Our internal error messages started with a banner that read “THIS IS A BUG IN <compiler name>. PLEASE REPORT TO <support email address>”. Despite that, whenever we actually got a bug report, it would inevitably start with “I’m pretty sure this isn’t actually a bug in the compiler, but I can’t figure out what I am doing wrong in my code”.