Those sound like proposed solutions, not the underlying concerns. Motivating concerns here might be things like "our wiki will be full of inaccurate info", "people will unknowingly install spyware".
The stated concern embedded in the first example is "anyone would be able to edit the wiki".
> Motivating concerns here might be things like "our wiki will be full of inaccurate info", "people will unknowingly install spyware".
Right. That's the point. The concern that "anyone would be able to edit the wiki" is not a valid concern. The concern that "our wiki will be full of inaccurate info [if just allow anyone to edit it]" has to be determined through empiricism. Avoiding locking down the wiki and seeing whether it fills up with junk will reveal whether the concern was valid. It's possible that it's an invalid concern and therefore requires no solution.
I don't think this means "most concerns aren't valid", it's more "people aren't always good at vocalizing their underlying concerns, and instead treat a proposed solution as the concern".
Your distinction between stated concerns and underlying concerns is a red herring.
If their underlying concern is "our wiki will be full of inaccurate info because the wiki is open", and if that's empirically shown that opening the wiki doesn't produce a wiki full of inaccurate info, then it's an invalid concern. Neither it (the "underlying concern") nor the stated concern are valid.
You're not engaging with the premise. There is no problem involving a wiki that is full of junk and that locking it down is a way to solve that. The concern is that it would be filled with junk if flipped from closed to open.
Yeah I think the lesson is that specific suggestions for what to do aren't as helpful as just hearing how someone else experienced your work, and then drawing your own conclusions about how to fix that.
Bug reports should describe the problem but often shouldn't try to prescribe a solution.
> if enough people want to willing vote in a corrupt president
Why do people do this though? Maybe it's inevitable, but I think there was a lot of pent up frustration with the government that led a lot of people to just say "fuck it". Not really excusing it (especially for his second term), but I feel like we're reaping years and years of a dysfunctional and ineffectual congress. Not that that's an especially easy problem to solve either.
I think this also explains a lot of the frustration with SCOTUS. In-theory, SCOTUS is supposed to just interpret and flesh out the policies decided on by congress. In practice, congress doesn't really do anything, and people started depending on SCOTUS's ability and willingness to make far-reaching and impactful decisions. Now a more conservative SCOTUS isn't doing that.
It's worth noting that an ineffective and gridlocked congress is specifically a problem of presidential-style democracies. Parliamentary systems with a prime minister have some of their own shortcomings (notably a weak executive), but the government is actually controlled by the legislature.
Countries that follow the presidential model regularly succumb to strong man type leaders. Ironically, in the modern era when the US had a hand in helping other countries establish their governments, we specifically helped them establish parliaments.
I agree there is a lot of pent up frustration in the U.S. and the GOP did a bang-up job of cultivating this frustration. And now that they have their chance at bat they seem to be striking out.
At the risk of my analogy making something serious sound like a game, I'd like to see another team have a chance at bat.
> Although [touch typing] refers to typing without using the sense of sight to find the keys ... the term is often used to refer to a specific form of touch typing that involves placing the eight fingers in a horizontal row along the middle of the keyboard (the home row) and having them reach for specific other keys.
The strict definition of touch typing reminds me of how when I was a kid, my parents would always tell me that there’s a specific way of holding chopsticks. You gotta hold the top one like a pencil, and rest the bottom one between the crook of your fingers and your ring finger, and make sure they’re the same length and the bottom one isn’t moving and you’re just using it as a base to press against.
And then I became an adult and visited China and met actual Chinese immigrants and married a native chopstick holder. And half of them don’t hold chopsticks “the real way”. Somehow it all works out. As long as you can eat a peanut with them, you pass.
As an adult I learned that there’s also a whole lot of prescriptive bullshit that basically nobody pays attention to. The strict definition of touch typing seems like one of those. If you can type without looking at the keys, you can touch type.
I will say you are far faster touch typing proper. I never fully learned it in school. I kind of half do it. Left hand is pretty religously touch typing byt right doesnt' stay on its home row.
Just never cared to get perfect at it in school. I would get absolutely crushed on typing tests though with the kids who actually learned touch typing. They all had piano experience and could reach the modifiers while holding on to the home row still. I still can't really do that on my right hand, its like my pinky doesn't reach.
I use a Dvorak keyboard, so usually outpace the touch typers. By the strict definition, it's not technically touch typing. By any colloquial definition, it absolutely is, if I looked at the keys I'd be touching the wrong letters. I just have the Dvorak layout burned into my brain so it's what I type regardless of what the keys say.
With such a strict definition the OP’s comment becomes basically meaningless. They could be referring to using index fingers only. They could be using an alternative keyboard layout. They could mostly be using left-hand only. Pretty much any WPM between 1 and 200 seems possible with the statement: “I don’t keep my fingers on home row in between key presses.”
Craft, in coding or anything else, exists for a reason. It can bleed over into vain frivolity, but craft helps keep the quality of things high.
Craft often inspires a quasi-religious adherence to fight the ever-present temptation to just cut this one corner here real quick, because is anything really going to go wrong? The problems that come from ignoring craft are often very far-removed from the decisions that cause them, and because of this craft instills a sense of always doing the right thing all the time.
This can definitely go too far, but I think it's a complete misunderstanding to think that craft exists for reasons other than ensuring you produce high-quality products for users. Adherents to craft will often end up caring about the code as end-goal, but that's because this ends up producing better products, in aggregate.
A "deep" tool that fully automates fairly specific tasks works this way. LLMs are more of a "shallow", general tool that can partially help with lots of different things, but none so completely that they alleviate the need for human involvement in them.
A car that can self-drive 100% of the time is a new tool that could make driving an obsolete skill. A car that can self-drive successfully 99% of the time is dangerous because it trains people to not be ready to take over for the 1% they need to.
What actually happens is that the 1% is ignored or outlawed. The shovel doesn't do 100% of human excavating tasks better than hands, but we rightly realized that the space of possibilities involving a shovel was much greater than the 1% of hand powered excavation.
Sure -- I think articles like this are a warning that the skills we're losing are likely _not_ so completely supplanted by AI that they'll soon be irrelevant.
reply