unidentified

I'm a software developer with a focus on Apple's platform (iOS, Mac OS X).
More information about me is available at my website. If you're into Twitter, you can follow me.
You can ask me here for personal or professional purpose.


» via rubymotion

What for?

If you’re doing something for ego, recognition, or money, believe me the joy of doing it will not last (that’s if there’s actually a joy in doing that). It is just an activity to fill the void in what we call life.

But, if you do it to get a deeper level of understanding of why you do it, and what is it that you’re doing, then how to be better at it.

It is still an activity to fill the void in what we call life, but…. it lasts forever, until everything is known.

"My pragmatic summary: A large fraction of the flaws in software development are due to programmers not fully understanding all the possible states their code may execute in. In a multithreaded environment, the lack of understanding and the resulting problems are greatly amplified, almost to the point of panic if you are paying attention. Programming in a functional style makes the state presented to your code explicit, which makes it much easier to reason about, and, in a completely pure system, makes thread race conditions impossible." »

John Carmack: Functional Programming in C++ (via Phillip Bowden)

Whenever possible:

  • Avoid mutable strings, arrays, sets, dictionaries, date or data as a property of an object.

  • Avoid creating a method that takes a reference as an input to be modified.

  • Avoid manipulating a global variable.

  • Achieve high cohesion and low coupling.

» via buzz
» via thechangelog
» via onethingwell