Search Results

• AbstractModelsAnswerQuestions
• AbstractionsInProjectManagement
• AcompanyIsProsecutedForBeingAmonopoly
• AdoptUnitTestsFirst
• AgileMaturityModel
• AgileModeling
• AllDevelopersShouldBeMethodologists
• ArchitectsDontCode
• AreBusinessAppsBoring
• ArtificialDeadline
• AsFastAsCee
• AssemblyLanguage
• BackSideOfAnInterface
• BackwardsCompatibility
• BadCodingStandards
• BadEngineeringPropertiesOfOoLanguages
• BadProvenPractice
• BelievingAbstractions
• BenefitsOfOoOriginalDiscussion
• BetterForLoopConstruct
• BeyondExtremeProgramming
• BigAnalysisUpFront
• BigBlocksOfAsterisks
• BigDesignUpFront
• BigRequirementsUpFront
• BinaryPortabilityWithTweakingDiscussion
• BlameYourselfFirst
• BracesAreGood
• BreakLongLines
• BrutalSarcasm
• BugFreeDoesntSell
• BugFreeSoftware
• BuyDontBuild
• ByRefConsideredHarmful
• CanAnArchitectureEmerge
• CapabilityMaturityModel
• CategorizedChanges
• CeePlusPlus
• CeePlusPlusInlining
• ChartsOnExtremeProgrammingProject
• CodeOwnership
• CodeUnitTestThird
• CodeWithoutExceptions
• CodingConvention
• CodingStandard
• CoffeeFlavoredCoffee
• CollectiveCodeOwnership
• CommentCostsAndBenefits
• CommentTheWhy
• CommitmentToQuality
• CommonLanguageRuntime
• CompareConstantsFromTheLeft
• ComplexityInComPlus
• ComplexityIsBugs
• ComponentOrientedProgrammingLanguage
• ConflictingRequirements
• ConstCorrectness
• ConstIsaVirus
• ConstructiveCriticism
• CoreXpDependencies
• CorrectInsteadOfCriticize
• CostOfFutureChange
• CriticalSpirit
• CriticizeHelpfully
• CthreeProjectTerminated
• CustomizationViaProgramming
• CyclomaticComplexityMetric
• DatabaseIsRepresenterOfFacts
• DebuggingAndTheScientificMethod
• DesignBeforeCoding
• DeveloperTurnedManager
• DoBothUnitAndAcceptanceTests
• DoItRightTheFirstTime
• DoNotUseAssertions
• DoTheSimplestThingThatCouldPossiblyWork
• DocumentationBeyondTheSourceCode
• DoesSoftwareQualityMeanNoBugs
• DontDistinguishBetweenClassesAndInterfaces
• DontThrowGenericExceptions
• DontUseExceptionsForFlowControl
• DotNetWillKillJava
• ElicitingRequirements
• EmptyCatchClause
• EncapsulationIsHierarchical
• EnforcingMethods
• EnoughVerification
• EveryoneShouldBeaMethodologist
• EvolutionaryDesignIsWasteful
• ExpressiveLoopCondition
• ExtractMethod
• ExtremeGuidelinesForCeePlusPlusDiscussion
• ExtremeProgrammingMultipleVoices
• ExtremeProgrammingWithTypes
• ExtremeQuality
• FactoryMethod
• FaganDefectFreeProcess
• FirstLanguageLearned
• FirstLawOfProgramming
• FixedPriceContract
• FixedPriceContractsWithChangeControl
• FixmeComment
• FocusOnCode
• ForgetToFixItLater
• FormalStandards
• FourVariables
• FundamentalFlawsInProceduralDesigns
• FuzzyLogic
• GenericProgrammingIsBetter
• GenericVsObjectOrientedProgramming
• GetRidOfIndispensableProgrammerAsQuicklyAsPossible
• GiveMeEstimatesNow
• GoodEnoughIsNotGoodEnough
• GoodVariableNames
• GrandMasterProgrammer
• GrandRefactoringDay
• GreatFailureOfXp
• GuardClause
• HandleErrorsInContext
• HeroicProgramming
• HighPerformanceWithGoodDesign
• HomogenizeExceptions
• HowCanYouCodeWithoutTesting
• HowDoYouMeasureMaintenance
• HowiLearnedToLoveObjects
• HundredPersonProject
• IdealPageSize
• IdentifiersAreComments
• IfXpIsntWorkingYoureNotDoingXp
• IncoherentRewardStructures
• IncrementalDelivery
• InformalHistoryDiscussion
• InheritStlContainersPublicly
• InlineAllMethodsWhereverPossible
• InterfacesForDefiningConstants
• InterfacesShouldBeAdjectives
• InternalLoopExitsAreOk
• IsBreakStatementArchaic
• IsThereEverGoingToBeSufficientEconomicIncentiveToDoSoftwareRight
• IsWaterFallDiscredited
• IsXpUnitTestingBest
• IsYourRudenessNecessary
• IssuesForLanguageDesigners
• ItsTimeToDumpCeeSyntax
• JavaIoClassesAreImpossibleToUnderstand
• LanguagePissingMatch
• LargeExtremeProgramming
• LimitConstructorArguments
• LimitsOfUserStories
• LinksDestroyFlow
• LoggingDiscussion
• LongFunctionsDiscussion
• LookBeforeYouLeap
• MakeItWorkMakeItRightMakeItFast
• MassiveFunctionHeaders
• MaybeProcessesArentThatBad
• MeaningfulComment
• MethodologiesAndScale
• MethodsShouldBePublic
• MicrosoftIncompatibleDependencySuite
• MicrosoftWayOrNoWay
• MisUsingMultipleInheritance
• MisunderstandingHungarianNotation
• ModelOfQuality
• MvcIsNotImplementable
• MyersBriggsDiscussion
• NamedConstants
• NoConcreteBaseClasses
• NoPointers
• NobodyAgreesOnWhatOoIs
• NumberOfKeystrokes
• ObjectOrientedPurity
• OnceAndOnlyOnceForRequirementsDocuments
• OneUnitTestAtaTime
• OoIsPragmatic
• OperatorPrecedenceConsideredHarmful
• OtherLanguagesForTheJavaVm
• OurWordsNotYours
• PairProgrammingCostsBenefits
• PairProgrammingGoneBad
• PeopleVsProcess
• PeopleWhoDontGetOo
• PerformanceOfConditionalLogic
• PerformanceTests
• PointersAndReferencesAreTheSameThing
• PolymorphismAndInheritance
• PoorCppProgrammers
• PowerOfPlainText
• PowerVersusAuthority
• PraiseBasedLeadership
• PrematureGeneralization
• PrematureOptimization
• PrematureStandardization
• ProblemsWithOnSiteCustomer
• ProcessImprovementTools
• ProductivityRant
• ProfessionalPerfectionism
• ProfessionalSoftwareDevelopment
• ProfileBeforeOptimizing
• ProgrammingExtremes
• ProgrammingIsMoreThanCoding
• ProgrammingValueSystem
• ProjectManagementInstitute
• ProjectSaboteur
• QualityAssuranceIsNotResponsibleForQuality
• QualityIsFree
• QualityIsNotFree
• QuestionsAndAnswersAboutUserStories
• QuestionsThatMakeYourHeadHurt
• RefactorLowHangingFruit
• RefactorReplaceCommentWithTestCase
• RefactoringCppToReduceDependencies
• RefactoringWithCeePlusPlus
• RenamingUnitTests
• ReplaceConditionalWithPolymorphism
• ReplaceDocumentationOriginal
• ReturnEnumerationsNotCollections
• ReuseHasFailed
• ReviewBeforeCheckin
• ScalingExtremeProgramming
• SelfDocumentingCode
• SeparateDomainFromPresentation
• SeparateInterfacesFromImplementation
• SetsAndPolymorphism
• ShipWithAssertionsOn
• ShouldMemberVariablesBeAccessibleToDerivedClasses
• ShouldUnitTestsTestInternalFunctions
• ShouldUnitTestsTestInteroperations
• SimplicityIsOverRated
• SimulatingKeywordArguments
• SingleFunctionExitPoint
• SixSigmaDiscussion
• SkewedBellCurve
• SmallFunctionHeaders
• SmallIterationsSmell
• SoftwareArchitecture
• SoftwareCannotBeModeled
• SoftwareDesignForTesting
• SoftwareDevelopmentImprovementParadigmShift
• SoftwareManagementManifestoDiscussion
• SoftwareMetrics
• SoftwareVsBuildings
• StaticTypingRepelsElephants
• StopUsingMetaphors
• StrictTypingIsaTest
• StructuredProgramming
• SuccessOrientedApproach
• SyntaxMeansLittleWithTypedef
• SystemOfNames
• TableOrientedProgramming
• TestDrivenDesignPhaseShift
• TestDrivenDevelopmentForAggregateMethods
• TestDrivenProgramming
• TestFirstDesign
• TestsAreAnExecutableSpecification
• TestsCantProveTheAbsenceOfBugs
• TheCustomerNeedsItRightAway
• TheProcessIsTheProblem
• TheSourceCodeIsTheDesign
• TheTroubleWithConsensus
• TheoryOfConstraints
• ThinClientHasFailed
• ThinkObjectsButWriteAssembler
• ThoughtfulReactionsPairProgramming
• ThoughtfulReactionsRefactorMercilessly
• ThrowDontCatch
• TimeForaParadigmShift
• TooMuchGuiCode
• TwoPointersInOneWord
• TypesAreRedundant
• UnUnitTestableUnits
• UncleBobsNamingConventions
• UniformlySlowCode
• UnitTestToCodeRatio
• UnitTestingDynamicBehavior
• UnitTestingLegacyCode
• UnitTestingNetworkFunctionality
• UnitTestingNonPublicMemberFunctions
• UnitTestingRandomness
• UnitTestsRequirePerfectDevelopers
• UnixFunctionalityVsWindowsFunctionalityDiscussion
• UseExceptionsInsteadOfErrorValues
• VbClassicDateConversions
• VbClassicLanguageIssues
• VbIsBadForNewbies
• VbScript
• VbTeachesBadHabits
• VelocityVsLoadFactor
• WashingtonDcExtremeHour
• WaterfallModel
• WayneMack
• WellFactoredCode
• WellFactoredProgramsCannotBeUnderstoodStatically
• WellWrittenCode
• WhatIsAnalysisContinued
• WhatIsIntegrity
• WhatIsRefactoring
• WhatIsReworking
• WhatIsSoftwareDesign
• WhatIsSuccess
• WhatIsaSpecificationAnyway
• WhenToStopRefactoring
• WhenXpIsUnpopular
• WhereDoTheBracesGo
• WhoOwnsYourMind
• WhyDoPeopleMakeSoManyMistakes
• WhyIsLeadershipImportant
• WhyWorryAboutArchitecture
• WikiObjectionsToWorkingTestFirst
• WilliamEdwardsDeming
• XpTeamVsIndividualCodeOwnership
• XpVsStandardDefinitionOfUnitTest
• YagniAndDeleting
• YagniIsBologna
• YouAreGonnaNeedIt