Tag Archives: Strategy

Hold your program in your head

I just found this very well written and interesting blog post titled "Holding a program in one's head". To summarize in short the post is based on the following topics:

  1. Avoid distraction.
  2. Work in long stretches.
  3. Use succinct languages.
  4. Keep rewriting your program.
  5. Write re-readable code.
  6. Work in small groups.
  7. Don't have multiple people editing the same piece of code.
  8. Start small.

The post explains much better what the eight points above mean and I suggest you go and read it now.

Comments { 5 }

The rules of successful executions

I love books like "the seven habits of highly effective people" by Steven R. Covey. Personally I think that the world would be a better place if people would follow more the "inner voice" and leave a life of peace and fulfillment then running after wealth and career.

The other day I came upon a post that talks about the 10 rules of execution. I wrote these 10 rules down on a paper and moved on, thus I apologize for not quoting the source.

  • Take a active role with all your actions
  • Always look out for the most challenging task and never settle for less
  • Be in full charge for all your projects
  • Take upon yourself difficult work. When you will master the most difficult tasks you will gain both in know how and in experience
  • Never give up
  • Be a leader and not only a delegator
  • Act reassuring and full of confidence, this will give yourself and your work strength. Others will notice.
  • Force yourself to think creatively and find solutions
  • Don't be to shy for any confrontation. Most of the time confrontation will bring you forward
  • Set new goals every day

Of course, some of the above points are plain simple and some might argue that it can not be so simple. Well, then why do people who follow these (not to close but you get the point) are successful in personal life as well as in the working job?

I urge everybody to try the above for 3 weeks. Write down how you feel before doing this exercise, take notes everyday how you feel and what you have achieved. Then after the 3 weeks compare how you feel and look at your achievements. You have nothing to loose!

 

Comments { 1 }

Keep it small, keep it simple and with less structure

You know 10 years ago you had to be this big company to succeed, especially in the software business. Nowadays with the Internet people can find you and you don't need to shell out big money for advertising campaigns and hire 100 developers just to make your product succeed.

Actually we think that a small team with some key people can make it all happen. Some of the advantages of a small team are:

  • Less overhead. You don't need a big fancy shiny office, a location that fits 4 to 6 people will do.
  • Less structure. Think about how easy it is to come up with a decision without hours of meetings.
  • Less intrusions. A big team also means a lot of disturbances going on in the office. Ask any developer inside a big company. I swear they want to work in a room all by themselves …
  • Less infrastructure. Obviously a smaller team does not require so many special arrangements. Your CFO will thank you.

All of the above leads you to one single thing; that is your product will get done sooner then later, you can act faster to market then big teams (think about how long it takes Microsoft to make its Mac Office 2004 available for the Mac 2 years after Apple made the Intel switch) and all in all your reaction time for your customers will outdo any big team.

 

Comments { 71 }