But there are similarities: software is developed in stages, it is created in a process amenable to change, and it’s developed in a team. Lean manufacturing is a different approach than a traditional assembly line, and offers some lessons for software development. xp123.com/xplor/xp0312/index.shtml

Summertime .. so all we do is to ski-roller. High time for the snow to come back and cool it down a bit. I found that pic a long time ago on I have forgotten what website.

• Skolelinux is a network architecture tailored for use in schools.
• Skolelinux is designed to be easy and cheap to maintain.
• Skolelinux gives the students their own usernames, home directories and services.
• Skolelinux includes OpenOffice.org

link

"The Linux Incompatibility list is a wiki project that attempts to document hardware that is incompatible with Linux rather than list what is compatible. In the wiki, it is possible to add alternitives so as to push hardware manufacturers to make good binary drivers, publish specifications, or even better, publish open drivers."

Example isn’t another way to teach, it is the only way to teach.

   --Albert Einstei

Are you a slacker? So am I. Do you browse the Web, read the news, and write email all day in stead of working? So do I. Does it make you feel miserable and apathetic? Do you tell yourself to stop browsing the fucking Web and get some bloody work done? Do you have absolutely no discipline? I know your pain.

But recent technological advancements have made it possible… There is a cure for your disease!

Years of slacking at the renowned Massachusetts Institute of Technology have resulted in a brilliant 461-line Perl script (which includes 130 lines of comments for free!) that makes it all possible! Your productivity will dramatically increase!

Today, I present Lockout: The Self-imposed, Computer-aided Work Enforcer. This program will help you get some work done by not allowing you to browse the Web. It won’t allow you to do anything but work. It’s a miracle! Your colleagues will respect you, your Ph.D. adviser will compliment you, and your boss, if you have one, will probably not notice the difference! It’s amazing! Scroll down! Read more!

Get the program

I’ve started work on a book, tentatively titled _Driving Projects with Examples: a Handbook for Agile Teams_. All that’s done to date is the Preface.

Two years ago, this would have been about driving projects with tests, but I think the role of examples in projects is larger than that. Also, examples fit more obviously into the whole "individuals and interactions over processes and tools" thing. Examples are something people use to explain themselves to each other. Conversations and learning are more obviously part of the picture.

Because I’m so hot on examples, I’ve put the draft book on a new site, exampler.com. Here’s the book: <www.exampler.com/book/>

(And, rather than "QA", "tester", or even "ECaBian", "exampler" might be a good name for those people on an Agile project that exhibit certain traits more strongly than other team members.)

Some of you practice the style of development I’m documenting - or variants of it. If you do, I want to talk to you, be it on the phone, or via emai, or in person. (I am budgeting travel money to visit worthy sites.) I’m serious about the "handbook" in the title: I want to fill it with tricks, tips, techniques, and stories. The more people I gather them from, the better the book will be.

In this document we show you the Ruby version of the Smalltalk code published in the pink book.

• Both ssh or telnet into the same (remote) Unix machine and account.
• One enters screen, then starts vim, then the other enters screen -x.
• ctrl-d to exit screen)

Linux Gazette article about screen

"The quantity of meaning compressed into a small space by algebraic signs, is another circumstance that facilitates the reasonings we are accustomed to carry on by their aid."

• Charles Babbage, quoted in Iverson’s Turing Award Lecture

paulgraham.com/power.html

The first person to write about these issues, as far as I know, was Fred Brooks in the Mythical Man Month. He wrote that programmers seemed to generate about the same amount of code per day regardless of the language. When I first read this in my early twenties, it was a big surprise to me and seemed to have huge implications. It meant that (a) the only way to get software written faster was to use a more succinct language, and (b) someone who took the trouble to do this could leave competitors who didn’t in the dust.

Brooks’ hypothesis, if it’s true, seems to be at the very heart of hacking. In the years since, I’ve paid close attention to any evidence I could get on the question, from formal studies to anecdotes about individual projects. I have seen nothing to contradict him.

The Cook’s Tour offers an excellent howto to get yourself and your customers into the test-writing mode.

An intro article by Bill Wake.

…I arrived at the classroom ten minutes before the lecture began. I was worried that there wouldn’t be any seats left, but I discovered one at the fourth row from the front so I hurried over and sat down. The classroom, which can hold around 200 people, filled up almost instantly. By the time I entered the room, Mr. Miyamoto was already sitting in a chair next to the blackboard.

Since Miyamoto was apparently too busy to make any special preparations for the event, it was decided to move from a traditional lecture format to a more informal discussion. To start off things, the instructor in charge discussed CERO [the Japanese game rating system], age restrictions, GTA, Kakuto Chojin, and other topics related to game regulation.

And then Miyamoto stepped up to the mike. Applause…

www.video-fenky.com/features/miyamoto.html