Search Results
AcronymsOnTheWiki
AdoptingXpPatternLanguageDiscussion
AlanChristiansen
AllOfXp
AlwaysUseBracesOnIfThen
AntiCreation
ArgueAgreeIdiomArgue
ArraySumInManyProgrammingLanguages
AtsDiary
AtsDiaryWeekThree
AtsGoesExtreme
AutoTracker
AvoidConstCompletely
AvoidExceptionsWheneverPossible
BeRationalAboutNumericalAnalysis
BeforeYouDoAnything
BellsWhistlesAndGongs
BestPractice
BigBallOfMud
BigDesignUpFrontMyths
BigModelsAreUseless
BiggerRefactoringThoughts
BillKelly
BookTestUnit
BottomUpProgramming
BracesAreGood
BruceAtherton
BusinessObject
BusinessRulesBelongInFiles
ButUnless
BuyDontBuild
BuyNowAndSave
CanOnceAndOnlyOnceLoop
CategorizedChanges
CategoryJargon
ChangeBrainstorm
ChangesInAugustFourteen
ChangesInAugustThirteen
ChangesInDecemberThirteen
ChangesInJanuaryTwelve
ChangesInJulyTwelve
ChangesInJuneTen
ChangesInMayFourteen
ChangesInNovemberFourteen
ChangesInNovemberZeroNine
ChangesInOctoberThirteen
ChangesInSeptemberZeroNine
ChartsOnExtremeProgrammingProject
ChronicProcrastination
CodeAndFix
CodeChangeResistance
CodeSmell
CodeUnitTestFirst
CodeWithoutExceptions
CoffeeFlavoredCoffee
ColinDeVilbiss
CombiningOpenSourceAndXp
ConsiderationOfAlternatives
ContrivedInterfaces
ConvertExceptions
CostOfFutureChange
CouldIsntWill
CouplingAndCohesion
CreatePrivatelyPublishLater
CriticalSpirit
CyclomaticComplexityMetric
DanielMunoz
DatabasesAreMoreThanJustStorage
DavesRealExampleWhereThinkingAheadWouldHaveHelped
DbasGoneBad
DecisionMathAndYagni
DecisionsAlwaysChange
DeletingBrokenUnitTests
DeletionDiscussion
DesignBeforeCoding
DesignDebt
DesignForNecessity
DesignInIdl
DesignPatternsConsideredHarmful
DevelopersWithHighProductivityTenxHundredxThousandx
DevelopmentTools
DijkstraPairProgramming
DisciplineInXp
DistributedMind
DistributionIsOptimization
DoIt
DoItOverAllTheTime
DoItRightTheFirstTime
DoItRightThisTime
DoNotUseAssertions
DoNt
DoOrDoNot
DoTheMostComplexThingThatCouldPossiblyWork
DoTheMostComplicatedThingThatCouldPossiblyWork
DoThePartTwo
DoTheSimplestThingThatCouldPossiblyWork
DocumentationBeyondTheSourceCode
DoesYagniInterruptFlow
DoingThingsRightvsDoingRightThings
DontDistinguishBetweenClassesAndInterfaces
DontLimitYourOptions
DontLoseGoodIdeas
DontRepeatYourself
DontThrowGenericExceptions
DontUseGetAndSet
DuplicatedCode
EconomicsOfXp
EconomicsOfYagni
EliminateDesignDebt
EmbraceChange
EncapsulationIsaWasteOfTime
EngineeringVsMarketing
EnterpriseJavaBeans
ErrorsBecomeFeatures
EstablishYourCredibility
EvaluatePreconditions
EvolutionaryArchitecture
ExampleLoggingFramework
ExponentialCostCurve
ExtendToImplementInterfaces
ExtensibleMarkupLanguage
ExtremeAlignment
ExtremeCooking
ExtremeDating
ExtremeDimSum
ExtremeGuidelinesForCeePlusPlus
ExtremeGuidelinesForCeePlusPlusDiscussion
ExtremeHacking
ExtremeHumility
ExtremeManagement
ExtremeMarketing
ExtremeNeed
ExtremeNormalFormCommentary
ExtremeNormalFormDefined
ExtremePayoff
ExtremeProactivity
ExtremeProductsWontSell
ExtremeProgramming
ExtremeProgrammingAndPatterns
ExtremeProgrammingBareMachine
ExtremeProgrammingBoundaryConditions
ExtremeProgrammingChallenge
ExtremeProgrammingChallengeFourteen
ExtremeProgrammingChallengeThirteen
ExtremeProgrammingCorePractices
ExtremeProgrammingInContext
ExtremeProgrammingIsNotTheOneTrueFaith
ExtremeProgrammingPractices
ExtremeProgrammingRoadmap
ExtremeProgrammingSystem
ExtremePspExperience
ExtremeRules
ExtremeSurgery
FactoryMethod
FlimsyAndBarelyFunctional
FoosLaw
ForFree
ForgetAboutWritingAccessors
ForgetToFixItLater
FormAndFunctionAreOne
FormValidation
ForthIsDeadFlames
ForthValues
FourVariables
FrameworksConsideredHarmful
GameOfBackgammon
GenericVsObjectOrientedProgramming
GetTheRightAbstraction
GoldPlating
GoldenToolbelt
GoodQuotes
HandleErrorsInContext
HankStuck
HeroicProgramming
HighDisciplineMethodology
HintsForComputerSystemDesign
HouseConstructionMetaphor
HowToBecomeaSkilledProgrammer
HowToDoCodeGenerationWell
IfItIsWorkingDontChange
IfXpIsntWorkingYoureNotDoingXp
IfdefComments
InfiniteAmountOfTransactionalMemory
InsertionSort
IntegrationMachine
InternalLoopExitsAreOk
InventorsParadox
InvisibleExceptionHandlers
IrrevocableThreadMode
IsTheOriginalProgrammerResponsibleForMaintainableCode
IsXpBorgDevelopment
IsXpReallyTheSimplestThingThatCouldPossiblyWork
IsXpUnitTestingBest
IsYourCodeThatImportant
ItAintBroke
JakartaStruts
JeraWorks
JosephTurian
JustInTime
JustInTimeProgramming
JustSufficientImplementation
KanbanInSoftwareDevelopment
KeepItSimpleMinimalization
KillYourDarlings
KkOoPuristRant
KnowledgePattern
LarsAronsson
LawOfDemeterAndCoupling
LawOfDemeterExample
LazyBastard
LazyEvaluationOverhead
LazyInheritance
LazyObject
LeanProgramming
LeonardoBueno
LifeAsaDevelopmentEnvironment
LimitsOfUserStories
LinksToCurrentPageViolateYagni
LittleSimulatorInJava
LoadAccessor
LoggingDiscussion
LongTitlesSmell
LotsOfShortMethods
MakeParameterizationPossible
ManagingCards
ManagingEvolutionaryDesign
MethodsShouldBePublic
MightPayoff
MinimalMethodologies
MorePainMoreGainSolution
MozillaBrowser
MsWindowsResourceLint
MuddyDecomposition
MvcIsYagni
NanoIncrements
NanoRefactorization
NecessaryAbstraction
NeedIt
NetscapeComposer
NoMoreDatabases
NoRoadArchitecture
NoStrings
OaooBalancesYagni
ObjectRelationalImpedanceMismatchDoesNotExist
OccamsDebugger
OnceAndOnlyOnceNameParadox
OnceAndOnlyOnceOriginal
OnceOrLess
OneRealWorldLoggingSystem
OoIsJustGoodEngineering
OpenClosedPrinciple
OpenClosedPrincipleAndXp
OpportunityCost
OppositeOfYagni
OptimizeLater
OrganizingTestCases
OverDesign
OverGeneralizing
PairProgrammingIsDoneByPeers
ParseUsingGrammars
PatternsForTeaching
PerFlock
PerformanceExperiment
PermissiblySimple
PleasePleaseDontCategorizeEveryPageOnWiki
PrematureAbstraction
PrematureGeneralization
PrematureGeneralizationIsEvil
PrematureOptimization
PrevalenceLayer
PrincipleOfParsimony
ProductSight
ProductivityRant
ProgrammersNotebook
ProgrammingTeamSize
ProofsCantProveTheAbsenceOfBugs
PropertyFieldTransparency
QuestionsAboutXpStoriesAndTasks
RavioliCode
ReadWhatYouNeed
ReduceHiddenScope
ReduceUnimportantInformation
RefactorNegateIf
RefactoringClassToBePolymorphic
RefactoringGovernment
RefactoringHouses
RefactoringImprovingTheDesignOfExistingCode
RefactoringIsaRequirement
RefactoringIteration
RefactoringMercilesslyHidesTheForest
RefactoringTrumpsYagni
RefactoringYtwok
ReferDontDelete
ReinventingTheDatabaseInApplication
ResponsibilitiesSubsumeOtherRules
ResponsibilityDrivenDesignConflictsWithYagni
ReturnBooleanEvaluations
RightThing
RoleAndPlayer
RollYourOwnFilesystem
RonDagostino
SafariTechBooksOnline
SavasAlparslan
ScrumProcess
SecondSystemEffect
SelectorGeneratingVisitor
SeparateDomainFromPresentation
SevenPrinciplesOfSoftwareDevelopment
SharingDataIsImportant
SharpenTheSaw
ShieldPattern
ShortBooks
ShouldPageTitlesBeQuestionsOrAssertions
ShunTheLight
SimpleDesign
SimpleIsntEasy
SimpleSuperclassName
SimplestThingReplyFromRonJeffries
SimplestVersusRight
SingletonPattern
SingletonsAreEvilPageRefactoringNotes
SmalltalkFrameworkIsOk
SoftwareDesignForTestingViolatesYagni
SoftwareNormalForms
SolutionOfTheWikiNamePluralProblem
SometimesYourGuessWasWrong
SpecificTestimonyOnCategories
SpeculativeGenerality
StarWars
SteerWithYourEyes
StepwiseRefinement
StopTryingToCodeMeAndCodeMe
StressFreeProgramming
TechnicalFutures
TechnicalMemo
TestDrivenDesignPhaseShift
TestFirstUserInterfacesPrinciples
TestPrintedOutput
TestsCantProveTheAbsenceOfBugs
TetrisAnalogy
ThatsNotReallyAnIssue
TheBestIsTheEnemyOfTheGood
TheElementsOfStyle
TheSimplestCode
TheValueOfResearch
ThereAintNoSuchThingAsPrematureGeneralization
ThinkingForthTips
ThirtyPersonProject
ThoughtfulReactionsRefactorMercilessly
TimeToDoItOver
ToDeleteIsHarderThanToAdd
TodoCommentsConsideredHarmful
ToleranceForAmbiguity
TooDeepIntoTheBagOfTricks
TossIt
TowerOfVoodoo
TragedyOfTheCommonsCantHappenHere
TreatTheCauseNotTheSymptoms
TwoIsAnImpossibleNumber
TwoYearItch
TypesAreContracts
UnderscoreVersusCapitalAndLowerCaseVariableNaming
UnitTestIsolation
UnitTestTutorial
UnitTestingFutureStories
UnitTestingQuestion
UseBeforeReuse
UseCompositionAndInterfacesWithoutClassInheritance
UseFactoriesToBuildObjects
VbClassicRefactorTypeToClass
VerifyOutputWithGrammar
VeryCoolBuilding
VeryMildXpOkay
VeryOldPerson
VlissidesOnBeck
VoluntarySimplicity
WaterFall
WdNiy
WeAlreadyKnowWeWillNeedItButJustDidntPutInJiraYet
WeDontNeedItYet
WhatIfInheritance
WhatIsSimplest
WhatMakesSoftwareFlexible
WhatWillThisBecome
WhenAreWeGonnaNeedIt
WhenInDoubtLeaveItOut
WhenToStopRefactoring
WhenXpIsUnpopular
WhyBotherToStructure
WhyDoPeopleMakeSoManyMistakes
WhyDoesntWikiDoHtml
WikiBlackmailNote
WikiInterchangeFormat
WikiIsForGrowingConsciousness
WillardsXpDiary
WorkingCodeTrumpsEverything
WorkingOnTheWrongThingAltogether
WorseIsBetter
WorstThingsFirst
WouldntItBeNiceIf
WriteInterfacesBeforeClasses
WritingApplicationsThatRunWell
WritingPortableApplications
WyattMatthews
XpAndEncapsulation
XpAsReligion
XpAsp
XpChallengeCeePlusPlus
XpChallengeCompilers
XpChallengeGraphicsPackages
XpDesignFaq
XpGlossary
XpGuilt
XpInPolitics
XpIsForBabies
XpLite
XpProductivityMeasurementProblem
XpQuestions
XpScheduleFaq
XpSimplicityRules
XpVsStandardDefinitionOfUnitTest
YagNi
YagniAndCompanyAssets
YagniAndCostOfChange
YagniAndCpp
YagniAndDatabases
YagniAndFrameworks
YagniAndLogging
YagniAndReuse
YagniAndSpikeSolutions
YagniAndTeamDynamics
YagniExceptions
YagniIsBologna
YagniPrinciple
YouAintGonnaNeedIt
YouAreGonnaNeedIt
YouArentGoingToNeedIt
YouArentGonnaNeedIt
YouArentGonnaNeedItAndYtwok
YouDontNeedItAnymore
YouMightNeedIt
YouNeedCleanCode
YouReallyArentGonnaNeedThis
YouShouldntaDecidedIt
YtwokParanoia
ZeroOneInfinityRule
ZitfacePattern