Approximity blog home
372 to 381 of 910 articles

Everyday Scripting with Ruby   11 Feb 07
[print link all ]

Brian Marick wrote this great book. Brian is a well known testing guru, but this books appeals to a much wider audience. Through a few simple scripts he teaches people how to code every day tasks in ruby.

It’s a short and easy read of nearly 300 pages and requires no previous ruby knowledge. If you already know ruby, this book is probably too slow, but if you come from any other language, it’s a great book.

htop - interactive process-viewer for linux   07 Feb 07
[print link all ]
Are you also sick of good old top? Especially if your tasks run for 20 days and more? You might want to have a look at htop.

Ceramics for Breakfast   04 Feb 07
[print link all ]
Designboom has a bunch of interesting ideas on design.

Dragons of Design   04 Feb 07
[print link all ]
David Buck compares software subsystems with dragons.

In the end, it’s better to avoid creating stubborn dragons in the first place and to slay them early if they start to turn bad. Young dragons are easier to slay than old ones. You may even slay several dragons before you are happy that you have one you can live with.

Image source

The last 5 Euruko 2006 T-Shirts   27 Jan 07
[print link all ]
My wife sells the last 5 Euruko T-Shirts. Better be quick :-).

Sven's new blog with the euruko06 videos   27 Jan 07
[print link all ]
Sven C. Koehler has started a new blog and what is best, he posted the euruko06 videos.

The rumor mill says, that we will soonish see tons of interesting Javascript and Ruby stuff there .. thanks to one project in winter country :-).

NeXT and NeXTStep   26 Jan 07
[print link all ]
A very long read about my old love :-).

Beating a dead horse   25 Jan 07
[print link all ]
Victor posted this to the XP-list

Dakota tribal wisdom says that when you discover you are riding a dead horse, the best strategy is to dismount. However, in business we often try other strategies with dead horses, including the following:

  • Buying a stronger whip.
  • Changing riders.
  • Say things like, "This is the way we have always ridden this horse."
  • Appointing a committee to study the horse.
  • Arranging to visit other sites to see how they ride dead horses.
  • Increasing the standards to ride dead horses.
  • Appointing a tiger team to revive the dead horse.
  • Creating a training session to increase our riding ability.
  • Comparing the state of dead horses in todays environment.
  • Change the requirements declaring that "This horse is not dead."
  • Hire contractors to ride the dead horse.
  • Harnessing several dead horses together for increased speed.
  • Declaring that "No horse is too dead to beat."
  • Providing additional funding to increase the horse’s performance.
  • Do a Cost Analysis study to see if contractors can ride it cheaper.
  • Purchase a product to make dead horses run faster.
  • Declare the horse is "better, faster and cheaper" dead.
  • Form a quality circle to find uses for dead horses.
  • Revisit the performance requirements for horses.
  • Say this horse was procured with cost as an independent variable.
  • Promote the dead horse to a supervisory position.

Nice thread int he extremeprogramming-ML

MC Escher   25 Jan 07
[print link all ]
Google Earth community MC Escher’s world

Flatland, the movie :-)   23 Jan 07
[print link all ]
Flatland, the 1884 novella by Edwin Abbott finally as movie

You can get the entire book at Projet Gutenberg for free.

 

powered by RubLog
372 to 381 of 910 articles Syndicate: full/short