Slashdot Mirror

However skeptical the ads make you, it's hard to deny that what used to be considered supercomputing power keeps showing up in consumer-priced boxes, and the threshold of what really is extreme has crept steadily upward. If you're planning a project of more than average size, though, the review that chromatic contributed below of Planning Extreme Programming could be a valuable read, and the ideas in the book itself could save you a lot of money and time. Even if you have no plans to desire to install a beowulf in your broomcloset, it's interesting to consider what sort of thought must go into any large-scale programming project.

Planning Extreme Programming author Kent Beck & Martin Fowler pages 139 publisher Addison-Wesley rating 9 reviewer chromatic ISBN 0-210-71091-9 summary Guidelines, anecdotes, and tested techniques to plan and track your Extreme Programming projects.

The Scoop Last year's Extreme Programming Explained argued that all of the good activities of software engineering (planning, designing, testing, refactoring, estimating, reviewing, and releasing) ought to be done all the time. Dividing the technical and management tasks, forcing each group to work to its strengths, the technique has gathered several proponents. Until now, there's been no general presentation of the HOW of XP, suitable for management and customers.

Planning Extreme Programming covers the practice of XP, the techniques other groups have used while applying its principles. Data and anecdotes from XP practitioners contribute to this collection of lessons.

What's to Like? The book fits the XP philosophy handily, with short, simple chapters hitting a single point apiece. This is a book suitable for busy managers (weaned on slide presentations) and customers (who don't want to learn any more about programming than necessary). Without the support of both, projects will fail. An afternoon invested reading this thin tome will pay off handsomely, whether or not you use XP.

It's hard to pin down the main emphasis in the face of the gestalt. The strongest lesson relates a simple driving anecdote. Reaching your destination requires a successful combination of small steps and course corrections. You can't just point the car at Boston and accelerate. Back out of the garage first. Ready, fire, aim aim aim aim aim.

Instead, the authors suggest breaking a project into self-contained, testable components (stories). The customer creates the stories. The programmers estimate the time it will take to complete each. The customer selects the stories for the next iteration (period of time between release dates, generally three to six weeks). The programmers write their tests, write their code, ask the customer to postpone a story instead of slipping a release date. Finally, the customer runs the test and selects the stories for the next iteration.

It's a powerful concept, and just might work. The text examines each step of the process, with a consistently simple emphasis on the big picture. Of particular note are the sections on estimates (you can do as much work as you did in the last iteration) and the role of customers. The big benefit of XP is that it minimizes risk over the long term by producing working software as soon as possible, continually revising the overall plan with fresh data.

What's to Consider? This book really assumes readers already have some understanding of the part they play in Extreme Programming. (One might argue that there's no reason to read this book without having read Beck's first XP book.) The more open-minded in the audience may jump right in, while the cautious and practical will want proof to go with the manifesto. Invest in reading this and Extreme Programming Explained.

Related to the previous point, XP is not free of jargon itself. Readers unfamiliar with the role of 'stories' or the duties of the customer will have some difficulty with the first few chapters. A short glossary of terms and duties would alleviate this.

A criticism of Extreme Programming Explained also applies here -- there's still too little data about which projects and software types fit XP best. This book does present some criteria: projects running on Internet time, outsourced projects, and projects with medium-sized teams (six to twelve developers) are possible candidates. Only experience and more data can provide hard answers.

The Summary More practical and less controversial than its predecessor, Planning Extreme Programming makes the XP manifesto workable. Better for people already sold on the practice, the book is also appropriate for people considering Extreme Programming, whether programmer, manager, or customer. Improve software quality and your quality of life by embracing change. Table of Contents

1. Why Plan?
2. Fear
3. Driving Software
4. Balancing Power
5. Overviews
6. Too Much to Do
7. Four Variables
8. Yesterday's Weather
9. Scoping a Project
10. Release Planning
11. Writing Stories
12. Estimation
13. Ordering the Stories
14. Release Planning Events
15. The First Plan
16. Release Planning Variations
17. Iteration Planning
18. Iteration Planning Meeting
19. Tracking an Iteration
20. Stand-up Meetings
21. Visible Graphs
22. Dealing with Bugs
23. Changes to the Team
24. Tools
25. Business Contracts
26. Red Flags
27. Your Own Process

You can purchase this book at ThinkGeek.

You thought the ban on violent video games from public display was a little off-putting? Well, try it on for size in Lotusland, USA. If that's not taxing enough, consider working some more on an allegedly cracked Poe cipher (but which you can't see yet). And then, it's primary source time on the MP3 brouhaha with Esther Dyson, Hilary Rosen, Orrin Hatch, Kevin Smith and Some Guy. All in this episode of Slashback.

A 17-year-old can join the real army, remember ... If you thought that the Indianapolis ordinance restricting video games with violent content from storefront display was either an anomaly or a strictly Middle-American move, read on. An unnamed correspondent writes: "GameFan reports in an article that yet another city is creating an ordinance that '...would restrict minors from playing arcade games with graphic violence or sexually explicit content.' The ordinance also covers the positioning and clear marking of the 'bad' machines. 'Currently, the bill states that such violent arcade machines must be marked and situated more than 10 feet from non-violent video titles.'"

Yes, at this point, it's just the proposal of a city council member, not a done deal. The city is (gulp!) sunny San Diego. Bother anyone? Perhaps they'll move all the games with punching into buildings like NYC has for Off Track Betting?

A long long time ago, I can still remember ... And for those into games that with a bit less gore ("We didn't have gore when I was small -- we were too poor!"), Kevin writes " Futurelooks has started a new feature called Retrolooks, which looks back at technology of the past and puts it up against the technology of today." Go read 'Atari 2600 VCS VS. Sega Dreamcast: FIGHT!' and try not to weep with nostalgia, at least if you are -- errrrr -- mature enough to have developed nostalgia. Here's a sample:

"Ah Atari, the granddaddy of all gaming platforms, the editio princep, the grail upon which all future gaming developed. In 1976 the Saturday Night Fever crowd was tired of just Staying Alive and craved something new. One Nolan Bushnell gave them that new fix with the invention of the first Atari console. Bushnell created the first unit with $250 and a desire for something new. Within four years the company of one had grown considerably and was worth over $28 million."

Plus, the grail is in the Castle ... [Aaaaggghhhh ....] AssFace writes: "As previously covered there is/was a contest of which the main goal was to break a cipher that had stood 154 years. At least two people have now solved it (separately) and we are now waiting on word (from the Bokler site) as to what will come next - apparently once one part is broken there is more? - I had created a list a while back on which a group has been discussing the cipher and at least one of the members is one of the people that came up with a solution of sorts and he posted a note regarding it here.
Frustrating for me personally because the code I was writing was just starting to evolve pretty nicely - but it will be fun to see what is next."

Proof positive, though? No word yet on the contest Web site; I think Edgar is cackling merrily in his grave.

If I share some love with you, do I have less left afterward? StoryMan writes "There's an interesting (and long) article at the NYTimes about file sharing, peer-to-peer networks, and the future of digital music.

It merits a read, if only because its participants are both important and interestingly diverse. Participating the round-table were: Hilary "I Speak for Artists, Hear me Roar" Rosen (complete with a very scary picture), Kevin "Chasing Amy" Smith, Esther Dyson, David Boies, a software developer, and your average 17-year old dude."

So long as you label it accurately, OK, fellas? For all their possible nefarious uses, cookies on your hard drive simply don't track you as well as certain companies would prefer. That's why devices like the Cue Cat, which exchange some convenience for information on your buying habits, will only get more common.

For instance, jgilm writes: "A 'new' product/company called Qode (marketese for "code") (www.qode.com) has a device reminicent of the Cue:Cat. Informationweek had a brief on it with items like '... a small wireless device called a Qoder ... scan UPC bar codes ... to search for better deals online.' and 'The scanned data is then downloaded to a personalized Web site.... Companies will then offer special deals on the personalized sites.'

The Qode site, which has a penchant for Flash movies, has info for businesses like '...a new and far more efficient way to deliver promotions. Plus you get a real-time heads up on consumer product interests.'

They claim that they are a 'wall' and 'walls are strong. And silent.' No joke. This is in relation to their privacy policy. Their idea of privacy is that they don't give out personal information to their business partners.

One aspect they don't address is the fact the the company still keeps track of your buying habits. Another is the probable lack of Linux software for the device (though no mention is made anywhere of system requirements)."

OK, so the world will soon be (or is already?) awash in free barcode readers. However, that's not all -- japhar81 writes: "Saw this over at GeekNews: netcity is offering a free smart-card reader. I'm personally planning to use it for an unintended purpose, like a certain other freebie. Off the top of my head, perhaps using my creditcard as the key to my pc ... Hardware hackers go wild:)"

A few bits and pieces on the BSD front in the recent past. Scott Bartram announced that JDK 1.1.8 is now available for NetBSD-current/i386. Over at LinuxWorld, Jonathan Bresler sent in this e-mail about BSD related activities. Sun are releasing source code for NFS under the SISSL (and boosting funding for a Linux only effort to implement v4, sigh). Anti Basic wants you to know that you can now pre-order FreeBSD 4.0 from the FreeBSD Mall. And finally, this month's edition of DaemonNews hit the stands a few days ago, including a particularly interesting article by Greg Lehey, outlining his work on software RAID, Vinum.

An anonymous reader sent us a bit where Rick Moen speaks about the recent Linux Myths thing that has raise MS once again to the top of everyone's "People We Love" list. Its a good summary piece that pretty much explains how valid the Gartner Report was.

Joachim Achtzehnter writes "The next release of Xerox PARC's ILU system will have a modified license which clarifies that ILU is free software. Last year the GNOME project decided not to use ILU because of its ambiguous license. The old license already allowed unlimited use, the new license is more explicit by stating that derivative works are permitted as well. ILU is a CORBA compatible distributed object system supporting many programming languages and platforms. "