Though it’s Unity-specific, this post does a great job of explaining Metal in iOS 8.
Software engineer Sam Soffes gives us his hands-on first impression of Swift and why it’s better than Objective-C.
Interesting thoughts on this. I feel similar actually. It’s quite fun to write Swift compared to Obj-C. So far, at least.
Don’t forget you’re writing code for other people to read. This is the single most important thing you can learn as a programmer. “Does it run?” is the minimum requirement for a good program. After it runs, spend the time needed to clean it up so it’s presentable and well-factored.
Even if you are coding by yourself, future you will thank you.
Coding, like any other form of writing, has an audience. Consider that audience when you write. Everything else about being a great programmer flows from this one simple idea.
The Internet is full of articles like this one which advise (implicitly novice) game programmers to use UDP as a first step in designing their game’s network protocol. […] I’m here to tell you that this advice is wrong (the data on performance notwithstanding).
Fantastic post from glyph explaining why what you think you know about UDP is wrong.
I’m finding this true of programming generally in lots of ways lately. There’s all this advice inexperienced programmers find on the Interwebs that is grounded in some truth, but it begins to break down pretty rapidly when put to real use.
An interview with a Victoria’s Secret model with a passion for coding.
Bjarne Stroustrup (via raducu-filip)
There are just two kinds of programming languages: the ones everybody complains about and the ones nobody uses.
Great truth in this: “think about what you want to code.”
Ever since PyCon 2013, the interest in the Young Coders class has been intensifying. Practically every Python conference since then has asked about doing one, and several have run their own. Classe…
Nevertheless, a single code base fixes pretty much all the problems and it actually is fun to use Python again.
Thinking about how to port a Python 2.x codebase to 3? This post advocates staying with a single codebase supporting both versions.