Use this tool to learn about websites, specifically the one you just entered.
If you find some aspect of it inappropriate it is not our fault.
If you are the owner of this website: yes we are a real search engine, we do have a real web crawler called FyberSpider and you can block it if you feel the urge.
Is It Cataloged?
We are in the process of updating this tool. Until we are done just use our search results to check the inclusion status of your site.
Find out if your site has been cataloged by top search engines for only $8.99.
Below you will see site info taken directly from the URL you entered in real time. This is also known as our URL Breakdown tool and can be used independently of our site info tool.
Page Title
Extreme Programming For One
Stripped Text Content
This is just a sample of the content found on this website. Please visit the website to read the entire page.
"Extreme Programming For One
Scenario
A lone software developer is working on several small to medium scale projects. He needs to increase his productivity and resilience. While his management are amicable and approachable, they tend to frown on "over-designing" a system, since it is "liable to change in the future anyway".
This programmer has been using patterns with Java for a while, but he has no techie colleagues to pair with, and very limited contact with the end users. Requirements tend to "appear" at any time. The management seem to accept that and the resultant geometric increase in effort needed to add to and maintain the design/code.
Can XP help?
See also: ExtremeProgrammingChallenge (source of this discussion) , ExtremeHacking (controversial alternate name for this?)
I hope you all don't mind this rather personal scenario (I admit that I am the programmer in question), but I think that any answers may be applicable to a wide range of loners and lurkers whose interest is piqued by XP. -- DavidMcNicol
We'll be glad to help! Here's a first cut. Other XP masters and observers, please pitch in!
XP does not believe that there is a "resultant geometric increase in effort" as a result of change. XP is built to thrive on change. Requirements appear and change at any time. Here's a short summary of how that happens.
We plan the entire project based on UserStories , using the ReleasePlan to describe the overall plan. We plan our work in (three-week) iterations, using an IterationPlan to say what we're going to do. We build our code using PairProgramming (this one is tricky for one person). The FunctionalTest s, of course, tell us whether we're done.
We DoTheSimplestThingThatCouldPossiblyWork . This means that we do not build for needs we might have in the future: we accept that we can't guess, so we don't waste time doing it.
To allow for future change, we RefactorM"
....
read entire page
