I got a keyboard.io when they first came out. On staggered layouts i was >85 wpm. But switching to ortholinear knocked me down to 25 wpm with excessive errors. It took several months before I got back up to about 60wpm. I stayed at that speed for a year or two before finally edging back up to 80wpm.
It did hurt my ability to use staggered but only at first. I was able to switch freely after about 3 months.
Those sound like huge trade offs. And they are. But for me carpal tunnel was quickly becoming a problem. Switching to ortholinear completely resolved my carpal tunnel pain. And that is priceless.
I still find the top row reach on my Model 100s a bit much, but I've gotten the hang of lifting my palms forward a little, especially for my pinkies.
In database design typically it recommends giving out opaque natural keys, and keeping your monotonically increasing integer IDs secret and used internally.
On cars without the arrow they often follow the convention where the gas filler handle is depicted on the same side of the gas icon as the filler door is in the car.
I feel like this misses the biggest advantage of Result in rust. You must do something with it. Even if you want to ignore the error with unwrap() what you're really saying is "panic on errors".
But in go you can just _err and never touch it.
Also while not part of std::Result you can use things like anyhow or error_context to add context before returning if theres an error.
Independent thought and personal accountability are sadly lacking in the US. "I see a bunch of unreturned carts. I must follow and fit it. See im justified in not returning it." :-(
Isn't senior leadership choosing languages or core technology, doing things wrong? Shouldn't senior leadership focus on outlining the business opportunities, value case, and requirements for their solution?
For this example id probably accumulate the score total in a local variable. Then once iterating over all the children i would call parent.add_score() with the accumulated total
Even today in my day job I still spend 90% of my time in a No Machine NX session to a remote linux desktop where I do my work.
We do it as an extreme form of access control. Our workstations cannot reach any of our systems. Thus if a laptop is stolen, nothing if real value is lost.
I think a lot of this distinction comes down to individual vs group focus.
Being good at your own work makes you useful.
However being strategic, thinking about the bigger picture, AND being able to effectively communicate that while navigating the complex social interactions of your leadership team, that makes you valued and will lead to a path to leadership (managerial or technical).
So many of is have poor social skills. It pays to focus on them and not just the skills relevant to your tasks at hand.