For every yin, there's a yang, right? When you program, you manage competing logic with ifelse statements. This week, I'm offering that balance, in light of the recent "everyone can code" initiative. The enthusiasm is fantastic and we have a lot of bias to work through to make even the idea of looking behind the screen unscary. And, I'm all in favor of growing citizen developers, a phenomenon that's caught the International Data Corporation's attention in this CIO article. The more we fold in hackers and malware developers for the greater good to the tech industry, the better. But, I do worry about teaching programming separate from its relevance in the tech world. Check out this discussion that sparked as a rebuttal to an e-rant  "Please don't learn to code". I am a professional programmer, and at times, I've felt we can introduce kids to programming at a more sophisticated level, though I'm well aware, even at a professional level, the trend is for integrated development environments that are "push button", driven more by packets of configured code than simple code editors that let you build solutions from the ground up. But teaching kids to program, each and every one, to solve simply self-relevant problems is just the challenge that programming as a profession needs, and will tend to resist. I can attest that it is a pretty insular community used to controlling how things are done. There's plenty of room, as long as we teach kids not just the "how", but the "why" and "hang in there", too.