Agreed sort of. Especially when the solution is often easily searchable.

I’ve hired interns and junior folks who have trouble with the command line (special circumstances for FT hire). I offer help, but also tell them that it’s their responsibility to understand any extant skill gap and learn. I’ve worked with at least one older boot camper who threw fits when they had to learn something new on their own to debug a problem. I’ve worked with much older career programmers who’ve done the same.

I don’t think it’s a matter of being a coder or not, rather some people aren’t problem solvers, and some people are lazy, and some people dumb, and some people want to be somewhere else. If I had my pick, I’d never work with these people. However, sometimes the people doing the hiring shouldn’t be managers, you could say, and sometimes the people making the decisions have incentives to hire bad people. Then you end with experienced newbies, and have to fill a position eventually.

A better articulated post would posit the problem is not inherit to people not knowing things, but people not having to.