10 Golden Rules

I received this via email, and decided to post it here as a reminder.

1. Steve Jobs said: “Innovation distinguishes between a leader and a follower.”

Innovation has no limits. The only limit is your imagination. It’s time for you to begin thinking out of the box. If you are involved in a growing industry, think of ways to become more efficient; more customer friendly; and easier to do business with. If you are involved in a shrinking industry – get out of it quick and change before you become obsolete; out of work; or out of business. And remember that procrastination is not an option here. Start innovating now!

2. Steve Jobs said: “Be a yardstick of quality. Some people aren’t used to an environment where excellence is expected.” Continue reading “10 Golden Rules”

2010 – My goals

My idea for 2009 was to have no new year’s resolutions, just a keyword for the year, #create.  That didn’t work out too well, I can think of countless excuses, one being the birth of my daughter in Jan, which played havoc with the amount of free time I thought I may have.  But the reality is that without clear goals, you’ll never accomplish much.  So for 2010 I ‘ve decided to set clear goals, and make them public, so that I don’t have any excuses to back down on any of them. Continue reading “2010 – My goals”

Misunderstood keyword

At the beginning of the year, instead of deciding on a stack of new-year’s resolutions, I decided on one keyword for the year. #create. Whether it be more blog posts, some awesome photos, usable applications in the public domain, website that people would actually want to visit/use. That was my motto for the year, to create more and consume less.

But I have to admit, it looks like I misinterpreted my keyword. I went for #procreate instead. Continue reading “Misunderstood keyword”

If only we could all strive towards code perfection

I’ve found two views out there about writing good excellent code, that I absolutely have to agree with.

One is on CodingHorror, by Jeff Atwood, saying that writing code is just like writing, ultimately your co-software developers have to understand what your meaning was, and if they cannot figure it out, you’re doing it wrong.

In Jeff’s post there is reference to this post by Ned Batchelder, which basically gives you THE rule about removing dead code, which I have to admit, I’ve been breaking a big percentage of the time.  From now on, in my quest for personal improvement, I will definitely be following both these guidelines.

What are your thoughts on writing good code?