I'm trying to give the author the benefit of the doubt. The tone of the piece has a definite "buzz off, newbie, unless you're ready to go HARD CORE" tone to it.

I'm trying to give the author the benefit of the doubt. The tone of the piece has a definite "buzz off, newbie, unless you're ready to go HARD CORE" tone to it. He might not realize that because he's not a native English speaker and isn't swimming around in North American culture. Maybe that was his intention, maybe it wasn't. Maybe he thought he was just "telling it like it is". Maybe you disagree that the article has that tone. If so, I'd politely suggest that the way the tone presents to someone used to "programming culture" might be different than it presents to someone outside, someone unsure about their place in that culture. Let me put it this way. I spent a lot of my time and energy finding people of all ages and backgrounds who have decided that programming is for other people and convincing them it doesn't have to be. This article makes my job harder. Compare it to this: > Some people will tell you programming is easy, other people will tell you programming is hard. Most of the time that's a reflection of how they felt or how they think other people should feel, not how it will feel for you. > Forget easy or hard. Will it take a lot of effort to become really good? Yes. The question is whether that effort is worth it for you. The only way you'll find out is if you give it a shot. > With the right effort, you _will_ learn to program. It can be for you if you want it. Let's figure out together whether this is exciting for you. If it is and you put in the work, I'll be there to help you go farther than you thought possible. None of this "gatekeeper" or "diversity card" nonsense. Talk to the person as a person. Don't talk about your favorite abstract bugaboos as it relates to that person.