What’s a sane, dynamically typed language?

I prefer a hybrid approach. A document explaining some common things to do and generally the idea behind why the API is structured that way (shows me you actually thought about it, and makes it more logical to find different parts of it without necessarily looking it up), and then an API spec showing all the parameters.

Not to rub it in, but in my forties could be read as almost the entirety of the modern web was developed during my adulthood.

We have to work under the assumption that most development is done by inexperienced or, to put it bluntly, bad programmers. I would MUCH rather have bad JS code than bad assembly. One may crash a single tab in my browser, the other may crash my entire computer.

For the uninitiated

Reminds me of my git commit messages!

It’s the quickest way to prove to yourself that you know what you’re doing… Most of the time, anyway…

I’m imagining a scenario where you’re working on a feature that changes the DB state (e.x. introduces a new DB migration that changes some columns) and the bug is on an unrelated part of the code from your feature. In this hypothetical, going back to the state of the upstream branch would make your local environment non functional, and the bug is on an unrelated part of the code. Fairly specific scenario but hey, you can worktree for that. It’s not particularly thorough, though.

I personally go for “wizzywig” but to each their own.

Emacs really can do anything huh

I guess it’s cause they’re on a cruise ship

Strangely enough, Lizard predates Rock significantly but took a long time to be considered competitively fair - around the time Spock was invented.

I use windirstat almost monthly and have never heard of WizTree. Keeping this in mind for next time I use it.

Though at this point, maybe I should just commit honestly

deleted by creator

I know you’re joking, but I just had the realization that S and J are probably the keys you’re likely to hit when alternating two thumbs on a mobile keyboard

Make sure to attend the pre raid Google meet so we can discuss specifics

Even when they do tell you it’s ok, it’s probably not ok. Toilet paper is designed to disintegrate rapidly in water, hence why it’s easily flushable because by the time it’s actually going down the pipes it’s all ripped up already. Wet wipes, even the “flushable” ones stay intact. You can try this at home, take two cups of water, in one put in a few sheets of toilet paper, in the other put it a wet wipe. Stir them both for a minute to simulate flushing them down the toilet. The toilet paper rips up and what clumps are leftover are pretty small. Wet wipes stay completely intact, which is why they cause problems down the line when they’re flushed.

Is it not Rocky Balboa?

It’s probably only ever gonna be used by like, what, a hundred people at most at any given time?

Does that mean on a microkernel you’d essentially have double the amount of code execution for a driver (i.e. driver makes a call to the kernel, kernel verifies and then executes rather than the driver just executing the call) meaning double the latency? Seems like it would cause a lot of problems.