Partial Contents- Tricks That Ignore Those Who Come AfterFailing to Clean Up Temporary Code - Creating Cryptic or Cute Variable Names - Building Monolithic Code- Tricks That Destroy PortabilityInventing Your Own Programming Language - Depending on Internal Compiler Details - Ignoring Compiler Warnings- Stupid Design TricksFailing to Design Your Program Before You Code It - Failing to Consider at Least Three Design Alternatives- Stupid Design Document TricksLeaving No Design Artifacts and No Garbage - Mistaking Documents for ...
Read More
Partial Contents- Tricks That Ignore Those Who Come AfterFailing to Clean Up Temporary Code - Creating Cryptic or Cute Variable Names - Building Monolithic Code- Tricks That Destroy PortabilityInventing Your Own Programming Language - Depending on Internal Compiler Details - Ignoring Compiler Warnings- Stupid Design TricksFailing to Design Your Program Before You Code It - Failing to Consider at Least Three Design Alternatives- Stupid Design Document TricksLeaving No Design Artifacts and No Garbage - Mistaking Documents for Documentation - Mistaking Documents for the Design- Tricks Arising from Social InadequacyUsing Technical Tricks to Avoid Social Situations - Not Asking for Help- Experts and Gurus as Leaders"Guru" As a Degrading Term - Be an Expert Who Can Teach Expertness- The Leader as LearnerHave Personal Experience - Be Able to Communicate Your Expertise - Remember That There Are Some Things Even a Guru Can't Do- The Expert as TeacherProvide a Discovery Trail - Teach on a "Pay as You Go" Plan - Provide the Questions, Not the Answers- The Courage to Teach in Any DirectionGive Your Boss Some Credit - Balance Self-Worth and Safety - Don't Confuse Courageous with Dumb- The Courage to Be YourselfIf It's Not a Good Fit, Don't Do It - Is It the Hair, or Is It the Arrogance? - Who You Are Is More Important Than What You Wear
Read Less
