It’s not just you. My new year’s resolution was to go down from double shots to single shots.
It’s not just you. My new year’s resolution was to go down from double shots to single shots.
Part of the reason this is a great example is you can easily calculate the maximum stress of an I-beam IFF you know where to find the simple formula. Even a dense FEA mesh will always give an answer like 3x4=11.9974, it’s worse. The education is how you know which formula to use.
Ok here’s a question I should have asked like way sooner.
In Ubuntu (and similar distros), is there a hotkey to immediately kill the process? Like CTRL-C but harsher.
I keep telling the stupid thing to stop wasting time and space apologizing, and it won’t.
I’m more of a mechanical engineer than a coder, and for me it’s been super helpful writing the code. The rest of our repo is clear enough that even I can understand what it actually does by just reading it. What I’m unfamiliar with are the syntax, and which nifty things our libraries can do.
So if you kinda understand programs but barely know the language, then it’s awesome. The actual good programmers at my company prefer a minimal working example to fix over a written feature request. Then they replace my crap with something more elegant.
Uh oh, brace yourself for a bunch of whataboutism from blatantly selfish computer nerds. /s
Look, it’s got full disk encryption and I’m very forgetful.
I think they meant call centers in general, for legal sales. No they didn’t I’m wrong
FWIW I’m a shitty coder and still don’t work overtime. And I’ve met brilliant engineers who just put up with everything.
The top priority of any tech professional should be building up a cash reserve so you can afford to play hardball.
How come they don’t count? They’re figuring out how the machines should work, for money. That’s engineering, right? (I’m an American mechanical engineer)