I’m sorry, but you’ve glossed over far too much.
Richard Kenneth Eng

Hey, I only briefly saw this response a while back and got swept up by a few things, but I wanted to give you a proper response. I’m sorry about the delay.

First of all, I don’t disagree with what you’re saying — I agree that many people are keen to market “code” dishonestly, ie: “Boost your career in 4 easy weeks!” and “15 days to a $20k raise!” The list goes on. There are certainly also those who, for whatever reason, like to call programming “easy.” Maybe to boast, maybe to market some product of theirs, who knows.

But I ask you — is that really what I’m doing?

Note that I openly concede several times to over-simplifying the concepts I’m describing. I admit to making imperfect metaphors/comparisons. I say explicitly more than once that coding is NOT easy, but that it’s *easier* than some people think, and it’s certainly NOT impossible. I stand firmly by this.

To be clear: this was not written for seasoned developers. I was hoping the anecdotal style and review of elementary coding concepts made that clear. The sole purpose of this article is to attempt to encourage those people who view coding as a distant, unobtainable thing. To help them even ask the question, “can I actually do this? Is this something I can actually do?” This was not intended to be an instructional resource and I don’t claim to be an instructor. I’ll leave that to Jeffrey Way!

If my intention with this article wasn’t clear, and if it seemed like I was trying too hard to preach the gospel of code or push some other dishonest agenda, then that is a fault of the article that I’ll acknowledge and work hard to address in any future things I write. But I do not profit from this article. I did not say coding was easy, that programming was easy, and oversimplifications were made cautiously with the intention not to overwhelm. I acknowledge the immense dangers of over-simplification, but considering the target demographic, I made an opinionated decision to cautiously do so. If you have specific revisions in mind, I’d be glad to take your feedback. For example, differentiating between “code” and “programming” is absolutely a worthwhile edit, one that I’ll put on my to-do list!

A single golf clap? Or a long standing ovation?

By clapping more or less, you can signal to us which stories really stand out.