While this sounds right, it is probably a path to depression. At this point I’m pretty much qualified for any web dev job I want, and I know I’d be one of the best hires they ever made, but I also know the interview gods are fickle bastards. I can easily see myself getting a string of rejections and taking a hard hit to my mental health.

An interview is not a fair assessment of your skill and fit, it’s just the best tool we have for the job. Therefore, don’t let the outcome of interviews tell you how good you are or what you’re ready for. Imo you kinda just know these things.

As for OP, sounds like they’re maybe still learning rule 1 of software development; the job is 90% figuring out how to do shit, it’s not actually so much about what you already know, although that certainly helps with the figuring out part. Once you’ve figured out how to figure out most of the problems that come up in your job, you’re more than ready for a new challenge, if you want one.

I feel like this wasn’t even that long ago? I was quite surprised when my content suddenly started being sponsored by them again.

I’ve accidentally opened enormous single line json files more than once. Could be lsp config or treesitter or any number of things but trying to do any operations after opening such a file is not a good time.

Respectfully, no. Rust is great for some things and Python is great for other things. Switching to rust is not a solution to missing exception linting in another language.

That’s way harder to ask for. A docstring solution is fine so long as the linters know to pick it up.

Well at least php has it, which is a JITed scripting language just like Python. Although saying php has it is wrong, it’s just a special doc tag that the linters pick up. Which is exactly what I want for Python. The only other scripting language I’m very comfortable with is typescript, which can also support @throws via jsdoc and eslint.

So to answer your question, I don’t know if it’s common, but from my minimal sample pool it’s at least not unheard of.

You may not know this (just guessing because you commented on the nature of scripting/interpreted languages) but static analysis of dynamic languages has come really far and is an indispensable part of any reasonably sized project written in them these days. That’s another reason why I’m so surprised and frustrated by the lack of this in Python.

Except if it’s a single line file, only god can help you then. (Or running prettier -w on it before opening it or whatever.)

I believe raises is the de facto Python version of throws, but no tools seem to exist to actually handle it.

Day 598 of asking for a way to tell which functions throw exceptions in Python so I can know when to wrap in try catch. Seems to me that every other language has this, but when I’ve asked for at least a linter that can tell me I’m calling a function that throws, the general answer has been “why would you want that?”

How am I supposed to ask for forgiveness if it’s impossible to know that I’m doing something risky in the first place?

Big Giant Circles - The Glory Days

I leave the country for six goddamn months and they pull this shit while I’m away???

I manage computer systems.

• What’s a computer? It’s a fancy calculator that can make moving paintings very quickly
• What’s a calculator? A fancy automatic loom that can do math like an abacus

Guestbook didn’t work, after recaptcha it just said POST failed. Oh and you need a visitor counter!

Don’t you dare come for my Pause key! That’s the one I’ve remapped to launch the screen lock!

Thanks, I love oddly comforting techno theology

I’m using brave mixed with a network wide ad blocker, so while it’s nice that Firefox has UBO I’m fine without. Firefox has been presenting these issues every time I’ve tried switching, so for about a year now, so no not a recent issue.

This is great but I literally can’t use the base app on my S20. Like clicking on Google search hits causes the app to freeze. Trying to scroll up on a page triggers a reload 30% of the time. I want to use Firefox but it’s nowhere near good enough, and adding extensions on top of that state is not going to help.

TTL on all content scales extremely poorly. You touch on this but I don’t think you appreciate just hope big of a SELECT * WHERE TTL ... this would be in just a few months/years. As an alternative, every instance sync should come with a list of newly deleted users. Retrying would not need to be reimplemented. If a user who wishes to be forgotten has had their home instance go dark, there will need to be a way for them to prove ownership over the original account (signup confirmation email perhaps) so a delete can be started from a foreign instance.