Sewing for sure, especially machine sewing. I feel like I've got as much time invested in fighting and maintaining our sewing machines as in our Windows machines. π
And then there's that whole transition between pattern (spec) and outcome that is oddly reminiscent of far too many of my software projects!
Knowing how a switch works in a circuit and how it's typically represented in schematics, I would guess that moving the switch toward the body of the gun should be off.
But if actually placing a bet, I'd put my money on it being the other way.
I haven't yet started blacksmithing, but it's the next logical progression. Other than a (very!) occasional boat and the odd bit of furniture or cabinetry, I seem to spend most of my time making tools, jigs, and fixtures.
If you might be looking at more general mucking about, Oracle's "always free" tier is pretty good. Yes, you might have to set aside decades of hate for Oracle like I did, but it's not like I'm ever giving them any money.
#5? (Me): pronounced S.Q.L. except for Microsoft's product which is pronounced "sequel server".
I call that the "nerd equivalency problem". I think it's the source of much (most? all?) of the problems with software that comes out of organizations that are not programming shops by nature.
"We're not moving fast enough (or, "I have this great idea!"), hire another nerd!"
The problem also exists within individual programmers ("sure, I can do that UX/UI thingy, just let me finish building this ray-tracing thingy"), but that's just an ordinary cognitive weakness that affects us all (thinking that being expert in one field makes one expert in all). It's the job of proper leadership to resist that, not act as though it's true.
Every time I see a set of instructions like this, I can't help thinking that someone forgot that we're using computers.
Unless, of course, that programmer has any number of mobility issues that limit their use of the keyboard, in which case something like cursorless might be the only option.
I urge you to take a look at it. Some even claim that it's more productive than the keyboard. I don't know how the VSCode voice feature works, but if it makes integration of cursorless easier or better, then I'm all for it.
I'm only just embarking on my git journey as a hobbyist. When programming was my career, I was a solo programmer and subversion was almost overkill.
When I look at the diagram of "merge" I see what I would have thought to be perfection itself, not something pain inducing.
As I said, I'm just getting started. Is there no tooling to make this graph painless and useful or is it left to mental visualisations?
I'd be very interested in learning more about how Canada manages "software engineer." Because whatever is being done certainly doesn't seem to include mandating where regulated professionals must be employed or punishing failures.
Saskatchewan's electronic health records system (eHealth) has had a couple of egregious failures that it shouldn't have taken a "software engineer" to prevent.
Several 911 services became unavailable during an outage that happened to also disrupt point of sale payment systems nationwide.
Both of the relevant companies are telecommunications companies (Telus and Rogers, respectively), where one would expect "software engineering" to be conducted by "software engineers" regardless of regulation.
A quick search for breaches in critical personal information will show that Canada is performing about as well as the US. Which is to say, abysmally.
No problem, thanks for reading!
Hey, me too! Although I took a transition job in between as public works foreman for a small village. (Single person doing everything from water treatment to sewer cleanouts, snow clearing to cutting grass.)