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.
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.
Assuming you put everything important in home, that is…
Heh nice try but we don’t write textbooks or exams for the outliers.
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.
Especially the last one!
I personally go for “wizzywig” but to each their own.
Right, if all you talk about is the shit Elon is doing, you’re really no better than a fanboy of his.
🎵 gigging on your dock cause I’m gay 🎶
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
Why do you run nginx as a server on your phone? Not judging just wondering
Save for a brief period in 2001 when I was off my bullshit I have been on my bullshit since '93
Katakana (one of the two phonetic alphabets) is for foreign words and it’s not exactly the same - Katakana has more variations to represent different sounds basically unused in actual Japanese-origin words. For example there’s the ヴ character pronounced like “vu” but no such sound is used in Japanese words. It gives an immediate visual indicator that the word is taken from another language so it’s not like they made it just because.
If Mr Pooh was personally overseeing my day to day I’d feel pretty special
Them: “my favourite political party will stay in power forever”
She can’t “own” people, don’t be ridiculous now. She can only compel them with violence into servitude and extract the fruits of their labor. But ownership? That’s messed up.
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.