Approximity blog home
839 to 848 of 867 articles

Samizdat - 0.5.2 is out   25 Sep 04
[print link all ]
Samizdat is a generic RDF-based engine for building collaboration and open publishing Web sites. It will let everyone publish, view, comment, edit, and aggregate text and multimedia resources, vote on ratings and classifications, filter resources by flexible sets of criteria, and cooperate and coordinate on all kinds of activities. It intends to promote values of freedom, openness, equality, and cooperation.

Samizdat homepage

Slides Dmitry Borodaenko presented about Samizdat ath the Euruko 2003

Advantages of Extreme Programming   25 Sep 04
[print link all ]
(Source: Kevin Smith post to extremeprogramming@yahoogroups.com) After a couple years of pitching XP, it became very clear to me that XP has different key advantages for different audiences. You’ll have to decide whether to pitch to a single audience, or try to cover several.

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.

Software for your head by Jim and Michelle McCarthy   25 Sep 04
[print link all ]
What Ron Jeffries says: if you read this book, really study and consider it, you will think thoughts you haven’t thought before, and you will likely learn something about yourself, your colleagues, and your projects. I read a lot of books and recommend a lot of books. This one is special. Do yourself a favor: buy it, read it, and give it deep consideration.

fit   25 Sep 04
[print link all ]
Ward Cunningham has released an acceptance testing tool called fit fit is about tests that people can read.

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.

XPlorations: The Humble Yo   25 Sep 04
[print link all ]
(Source: Bill Wake) "The Humble Yo" The humble "Yo!" is a simple convention for getting help. link Nice explanation of why not asking for help can actually hurt the team.

POV-Ray - getting 10 years old   25 Sep 04
[print link all ]

"The Lovers" by Gilles Tran (2001). Find more in the Hall of Fame

I still remember my first ray traced spheres on old XTs 15 years ago :-).

There is a competition and the monthly irtc. See the May-June viewing page and relax.

Computers are a grate time-killer, especially once you get into 3D images and animations. Enjoy it!

What's the Second Directive?   25 Sep 04
[print link all ]
(Source: Ron Jeffries, aka Mr. XP) I’m been struggling for years with notions like having empathy with our mistakes, Kerth’s Prime Directive, and the like. Springing from a couple of notes on the extremeprogramming group, and a blog entry from Dale Emery, here’s my latest rant. xprogramming.com/xpmag/jatPrimeThis.htm

Case stories   25 Sep 04
[print link all ]
Been skimming the XP-ML this morning.

About the $200M Oracle-Ford Desaster: the management did not give them enough power to go fully agile

Chet Hendrickson:

 It was a very frustrating situation.  The team asked Don and me
 to help with preventing the Oracle consutants from making changes
 directly to the production system.  This was about $150 million into the project.

 We tried to sell them on a more agile approach (as you might imagine), but by
 this time they were pretty far gone.

 It was unfortunante that we were not operating at a level in the organization
 that would have allowed us to get the plug pulled sooner.

 chet

Georg Tuparev has a nice case story, too: speak out if you are put on a death march.

 Few years ago I was called to lead a huge team stuck in one and half
 year design phase. The team was supposed to build a control software
 for a network of telecom satellites. Cannot disclosed names and
 resources, but one could imagine ...

 Three days in the project I had a phone conference with the CxO's of
 both companies involved. Told them that the way it is going no
 satellite will ever fly and that I know a better way. After getting
 green line, the design document was burned with a small celebration at
 a BBQ, and 85% of the initial team members were sent to an indefinitely
 long vacation. With the rest (15%) of the team we had the first
 functioning version 2 months ahead of the schedule and 50% lower then
 expected expenses.

 So the lessons:
 - it is never late to change direction of a project in order to save it.
 - I do not agree with Kent that this is a sad story. If you are a good
 programmer put on a death march project you should speak out! If no one
 listens - walk away. There is just one very precious life in front of
 us - do not waste it! And if these folks wasted 2 years of their lives,
 well, it is their business ... but they should not expect my
 sympathies.

 BTW, Philip is right - the project I was telling about had a 9 months x
 40 people "Big Requirements Up Front"!!! Then the design started...

 Just my 0.02

 Georg Tuparev

XP style process and battle-fields   25 Sep 04
[print link all ]
Not that I want to promote war in any way, but these posts in the extremeprogramming-ML made me smile:

Phlip:

 During the planning game, you review last week's
 finished stories, and they inspire you to write some
 new cards, to edit some cards, and to toss some cards.
 Then you (the Onsite Customer) re-sort all the cards,
 and draw off the top batch for the next week.

 But another input into this system that affects the
 planning game - the competition.

 The USA occupied Iraq using an effective new battle
 technique. In traditional advances, you send a
 diversionary force against one of your enemies flanks,
 draw them that way, then send your main force against
 their other flank.

 Modern soldiers, with cell-phones and such, follow a
 more agile approach. You simply send two forks of your
 forces, probing towards both flanks. You use sensitive
 algorithms to detect the defending commander's
 decision which flank to defend. If you can rapidly
 turn one advance into the diversion, and the other
 into the main attack, you will soon collapse the
 opposition's ability to effectively make decisions.

 Agile onsite customers can play this card too. If you
 detect your competition's marching orders, in
 real-time (using either sensitive algorithms,
 good-old-fashioned industrial espionage, or just
 reading their self-congratulatory Web site), you can
 then request iteration features which provide the
 minimum amount of code needed to start your project
 towards blocking the competition's advance. This
 technique will, again, collapse the competition's
 ability to make decisions.

 Or convince them to hire an XP coach or three. So
 either way it's a win-win-win for us! ;-)

Steven’s reply: :-)

 Or you could follow the agile strategy that Microsoft
 pioneered - announcing products with your competitions'
 features before you even start implementing them.

Re: Forth, Befunge, Whitespace, or Malborge: which is hardest to write buggy code in?   25 Sep 04
[print link all ]
(Source: comp.lang.forth)
  >>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/

 

powered by RubLog
839 to 848 of 867 articles Syndicate: full/short
A unique and safe way to buy gold and silver