> Isn't programming a skill that can be learned alone in a fairly straightforward manner?
No?
Stuff like pointers, for loops, threads, interface design, data structures, idempotency, source control, working on a linux command line, etc. all present reasonably challenging roadblocks for a burgeoning developer, and I think many of us benefited from having someone around to help walk us through this the first time.
That's an interesting example. Sure, I was initiated to the Unix command line at the University, but it was just that : an initiation. I got hooked quickly though so I was driven to learn the rest all by myself (or rather, with the help of the linux community online). I'm sure it's more or less the same for most linux nerds. I may have bought one or two books about linux though, but buying a book about a subject you're passionate about is something normal.
You're right that once you want to get into the important technical details, free documentation on the web may be insufficient and you may need to invest in proper textbooks. I still think my point stands, though.
I was introduced to Linux in college and I thought, "Neat. Now please put me back into Visual Studio where the real coding happens." I was not hooked.
It wasn't until I used Linux professionally that I started to really respect (and enjoy) using the environment. And even then it wasn't until I saw another human using it efficiently. It's one thing to read about how useful it is, it's another thing to struggle with a problem and have someone show you how you could solve your exact problem.
Once I had that connection with another human/mentor, seeing my specific problem solved, that's what hooked me. I don't think I could have gotten there with toy/educational examples online/in books.
> I don't think I could have gotten there with toy/educational examples online/in books.
For programming, the available documentation is not just ludo-educational, it's also the official references, like the RFCs and specifications. There is literally no better source of knowledge for computer science. I haven't delved into technical specs very often in my life, but I have at times and I bet most good programmers do it often.
I learned programming on my own. Sure there is a lot to learn in programming. Often you are stuck with a problem for long and there is simply nobody, except online forums, to help you out. Nobody around me is into programming. I am married and have 2 kids. My regular job has nothing to do with programming. I have to spend 3 hours in daily commute. Saturdays are working day. But I still manage to learn programming.
I don't understand why women in general need special help or guidance.
I didn't really start programming until I took an intro to programming class in university. I had been taught programming languages multiple times before, but that was the first time anyone explained the underlying systems the language was built upon. It was the first time I felt like I understood what I was doing.
A good instructor will also guide you to good learning materials. There's lots of terrible books out there, but I found good books through my classes. Though, it's probably easier to find learning materials today than when I began.
No?
Stuff like pointers, for loops, threads, interface design, data structures, idempotency, source control, working on a linux command line, etc. all present reasonably challenging roadblocks for a burgeoning developer, and I think many of us benefited from having someone around to help walk us through this the first time.