<\/td><\/tr><\/table><\/p>\nHere is a question<\/a> from reader cody:<\/p>\n Me and my brother got into an argument recently and I figured you could help us settle it. It started when an update for Minecraft was released that caused the game to crash when shift clicking items into a full inventory. He thought this was incompetent coding on behalf of the developers and that any problem like that would be obvious and easy to fix. I told him that it's a lot more subtle than that and any number of seemingly insignificant bits of code could break the game in major ways. In the end we both agreed that computers only do exactly what you tell them to, our opinions on what that means are different though. He thinks that it means if you tell them to do something that breaks the game you're bad at making games.<\/p><\/blockquote>\n There’s an old saying among writers: Writing is re-writing<\/em>. The real work isn’t having an idea or putting the words down, the real work is when you’re done with that and you have to go back and polish, cut, and expand until the work flows.<\/p>\n There’s a parallel saying for software engineers: Programming is debugging<\/em>. Yes, a terrible programmer will write bad code. But a normal programmer and an exceptional programmer will write good code. The difference between the two appears when it comes time to locate an obscure bug or intuit the source of a problem based on the non-technical ramblings of an end user. A task like that can take a day or five minutes, and it all comes down to how deeply the programmer understands the discipline. <\/p>\n The thing is, ALL programmers write bugs. John Carmack<\/a> is one of the most brilliant software engineers alive today. He’s a visionary, an inventor, a member of Mensa and yes, he’s also a rocket scientist<\/a>. Yet he writes bugs just like the rest of us. It’s unavoidable. Saying a programmer should never make bugs is like saying writers should never make typos. A good one will make fewer than a bad one, but they happen to everyone. (In fact, it’s probably pretty even between great coders and average coders, because we all seek our own level. If you’re able to write something completely bug-free, then you’re under-utilizing your abilities and you’re probably bored at your job. We all want to hit that sweet spot where the work is challenging enough to be interesting and rewarding, but still easy enough to avoid frustration.)<\/p>\n But this Minecraft bug isn’t about programming skill. That’s a playtesting problem. Writing the bug was a trivial mistake. Releasing the bug was less so. This began as a one-man hobby project with low expectations and is now a multi-million dollar project with a team and an immense base of customers with the usual consumer demands. Mojang is going to go through some growing pains as they develop a production pipeline and company policy regarding releases. <\/p>\n
<\/td><\/tr><\/table><\/p>\n