from a bussy
I assume that word also means something else than what I’m thinking…
from a bussy
I assume that word also means something else than what I’m thinking…
But it’s good that viable alternatives exist in case Microsoft ever considers shutting down the Java edition.
I had never even considered that as a possibility but now it seems all too possible and I’m gonna have to sit with that for a while…
I’ve actually used this to my advantage. I bought some cheap speaker/light combos which basically made the lights dance to the music. The only power connector was a wire that comes straight out of the device and into an outlet. But it did have a USB port for loading music from a USB stick. So naturally I plugged one side of a USB A into the port and the other side into a power bank and it just straight up worked.
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.
From the stories I’ve heard from corporate software employees, this does sound like exactly the kind of thing you gotta do to show some manager the guy is buddy-buddy with that they’re actually not doing their job. And even then they didn’t listen.
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.
This level of effort is probably geared more towards those who create the torrents, not those who consume them.
Assuming you put everything important in home, that is…
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.
I mean, it’s just like collecting baseball cards. Just because I enjoy collecting them, doesn’t mean I inherently have to jerk off to them more than the next guy
Emacs really can do anything huh
Strangely enough, Lizard predates Rock significantly but took a long time to be considered competitively fair - around the time Spock was invented.
You can’t leave purgatory at will
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
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
And then their non standard file format turns out to just be a zip file or gzipped JSON data 😂