Peter Friese

Developer Advocate / Mobile Developer / Public Speaker

Annotated Links for Week 32

| Comments

This week, we’ll have a look at Apple’s new system status page and another, more serious issue in a rather well-known computer-driven system. Other topics in this post: a very high-level view on programming (and why we failed so far) as well as a very detailed look at programming (and what you can do to excel at it). Finally, some spying.

Apple System Status Page

As an iOS developer, you rely on a surprisingly high number of Apple systems. Until recently, there wasn’t a way to find out if a system was offline or if it was just you, “holding it wrong”. As an immediate response to the (alleged) hack of their developer support systems, Apple shut down pretty much all of their developer support systems and set up this system status page. As of now, all systems are back to normal, but this page might come in handy for future outages.

The Explosion of Ariane 5

Due to popular belief, Ariane 5 exploded because a programmer mixed up a comma with a period, but it’s not that easy,

In fact, the problem was someone used a 16 bit unsigned integer variable to hold the result of converting a 64 bit floating point value. I guess this is strong point for using type safe languages in safety-critical systems as well as clearly stating the pre- and post conditions of library functions. Some unit tests might also be in good order.

The Future of Programming

A talk Bret Victor gave at the DropBox conference in 1973 2013 on how he thinks the future of programming could have looked like if developers had been more courageous in embracing new ideas instead. Instead, we often see people rejecting new ideas, stating “that’s not real programming”. Thankfully, every now and then new ideas are strong enough to gain enough traction. Otherwise, we’d still be writing code in binary. Recently, we’ve seen a growing interest in programming languages and programming paradigms other than the well-known object-oriented / procedural approaches. I think this is a good sign, however, we need to be more open minded and think more about other, new ways of programming. If you haven’t done so in this year, you should set aside some time to learn a new programming language. Why not try Xtend?

The NYTimes Objective-C Styleguide

If you develop software for a living, you know that following a coding style guide makes sense. Sometimes, people do get religious about how to format their code – try to steer clear of this by using a widely-regarded style guide. The NYTimes Objective-C Styleguide is well-written, has the right amount of concise examples and can be forked in case you feel you need to adjust something to your liking. The fact that the New York Times mobile team welcomes contributions will probably make this styleguide one of the more popular ones.


Whether you just want to quantify yourself, something which Stephen Wolfram seems to be doing to quite some extent or you’re curious what secret services might know about you if they installed a keylogger on your system: SelfSpy is a good tool to get started: it runs on Linux, Windows and Mac OSX. Besides, it’s open source – so you can see what it does and you can extend it if needed.

Chains image by Haya Bernitez