Amongst other things this article tells you when best to have children :-). groups.yahoo.com/group/extremeprogramming/files/when%20should%20we%20test.pdf

  >>Here is a version of Forth that runs under Windows, written in Whitespace:
  >
  >>
  >>I can't get it to run.  Do you think my browser has clobbered the code?
  Hmmm. I did exactly as the web page[1] suggests: "What do you do? Simply
  print it out and delete the file, ready to type in at a later date.
  Nobody will know that your blank piece of paper is actually vital
  computer code!"  I sure hope that I didn't mistake my only copy of the
  source code for an ordinary blank page!

  Perhaps writing my Befunge[2] compiler in Malborge[3] and then making it
  to a Forth[4] compiler written in Whitespace[1] wasn't such a good idea...

 References:
 1 http://compsoc.dur.ac.uk/whitespace/
 2 http://dmoz.org/Computers/Programming/Languages/Befunge/
 3 http://www.freebsd.org/cgi/query-pr.cgi?pr=28147
 4 http://www.cbel.com/forth_programming_language/

 >>Which brings me to an excellent 'forthism' I once read in a
 >> newsletter.  It stated:
 >>
 >>     "You can do anything in Forth - but you must be prepared
 >>     to do it yourself."
 In a recent discussion in c.l.functional, about why popular languages
 are popular, I summarized the relationship between Lisp and Forth
 more-or-less as follows:
 "From the Lisper's perspective, every other language is a cute subset
 of lisp; whereas from the Forther's perspective, every other language
 is a cute extension of Forth."

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

   --Albert Einstei

The organisation will next week show off a Wi-Fi enabled bus at the Paris-hosted Public Transport Exhibition 2004. It will also launch a public trial of the technology, on the number 38 bus, which runs between North and South Paris. Buses on the route have already been equipped with Wi-Fi, RATP said. Travellers will be able to connect their (suitably equipped) PDAs and notebooks with the bus’ on-board access point. However, Internet connectivity is only provided at Wi-Fi speeds when the vehicle passes within range of a fixed hotspot - at a major terminus, for example. For the rest of the journey, connectivity is maintained through a GPRS link. link

"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.

For developers, XP allows you to focus on coding and avoid needless paperwork and meetings. It provides a more social atmosphere, more opportunities to learn new skills, and a chance to go home at a decent hour each night. It gives you very frequent feelings of achievement, and generally allows you to produce code that you feel good about.

For the Customer, XP creates working software faster, and that software tends to have very few defects. It allows you to change your mind whenever you need to, with minimal cost and almost no complaining from the developers. It produces reliable estimates so you can coordinate your schedule easier.

For management, XP delivers working software for less money, and the software is more likely to do what the end users actually want. It cuts risk in a couple ways: 1) It allows you to "pull the plug" on development at almost any time, and still have highly valuable code, and probably even a valuable working (if incomplete) application. 2) It reduces your dependence on individual superstars, and at the same time can improve employee satisfaction and retention.

The biggest disadvantage: It’s hard. It’s difficult to get many developers to accept the practices, and it takes a lot of discipline to keep doing them all. Customers may not like the idea of having to be so involved. Management may expect fixed-cost, fixed-scope estimates, which XP teams often refuse to create (because they are usually incorrect with any methodology).

Also, certain people may feel their jobs are being threatened, particularly architects, testers, and project managers. "Cowboy" coding "superstars" may dislike the reduction in fame, attention, and adreneline from "saving" the project at the last minute.

Both of these images are wrong. Hacking and painting have a lot in common. In fact, of all the different types of people I’ve known, hackers and painters are among the most alike. www.paulgraham.com/hp.html

Amongst other things this article tells you when best to have children :-). [groups.yahoo.com/group/extremeprogramming/files/when%20should%20we%20test.pdf]