Sneak preview of latest development build of OpenLoopz over at the old website.
In the end, much of the challenge of programming is in identifying and holding tight to every invariant you can find, those things in your algorithms, applications, or business rules that do not change. The more invariants you can identify, the more you can focus on the local effects of a particular piece of code, and the more risk you can drive out of whatever system you are building.
Clojure Programming, p59
The Android Design Guidelines should be treated as you would a GPS in your car—it’s there to navigate you along logical paths but it is still you who must do the driving
42 doesn’t change. June 29th 2008 doesn’t change. Points don’t move, dates don’t change, no matter what some bad class libraries may cause you to believe. Even aggregates are values. The set of my favourite foods doesn’t change, i.e. if I prefer different foods in the future, that will be a different set.
I’m now convinced that choosing a language based on how easy it is to read or write is a very bad idea. What if we chose musical instruments based on how easy they are to play? Everyone would playing kazoos. You can’t think deeply about music if all you know is a kazoo. Skill at reading and writing code is learned. We should choose languages based on how accurately they allow us to think about the problems we are trying to solve.
If you are developing a Qt app for Symbian and it reports “Memory Full” errors when running on a device then…
Just a quick post to explain a problem that has had me pulling my hair out for days!