Pages that link to 97 Things Every Programmer Should Know
From WikiContent
(List of links)
< 97 Things Every Programmer Should KnowThe following pages link to 97 Things Every Programmer Should Know:
View (previous 500) (next 500) (20 | 50 | 100 | 250 | 500)- 97 Things (← links)
- Encapsulate Behavior, not Just State (← links)
- Inter-Process Communication Affects Application Response Time (← links)
- Fulfill Your Ambitions with Open Source (← links)
- Please Read this Guideline before Making Your Own Contribution (← links)
- Comment Only What the Code Cannot Say (← links)
- Restrict Mutability of State (← links)
- The best way to clean things up is to avoid them getting dirty in the first place (← links)
- Speed Kills (← links)
- Never ever break encapsulation (← links)
- Useful software is used longer than ever intended (← links)
- Beware the Share (← links)
- Reuse Implies Coupling (← links)
- Learn Foreign Languages (← links)
- Understand Principles behind Practices (← links)
- Own (and Refactor) the Build (← links)
- Acknowledge (and Learn from) Failures (← links)
- The Road to Performance Is Littered with Dirty Code Bombs (← links)
- How to Get Started (← links)
- Only the Code Tells the Truth (← links)
- You Gotta Care about the Code (← links)
- Interfaces Should Reveal Intention (← links)
- Use the Aggregate Design Pattern to Reduce Coupling (← links)
- Test for Required Behavior, not Incidental Behavior (← links)
- Test Precisely and Concretely (← links)
- Simple Is not Simplistic (← links)
- Choose Your Tools with Care (← links)
- Two hours of thinking can save two months of coding (← links)
- Verbose Logging Will Disturb your Sleep (← links)
- Keep the Build Clean (← links)
- Two Wrongs Can Make a Right (and Are Difficult to Fix) (← links)
- WET Dilutes Performance Bottlenecks (← links)
- Don't Just Learn the Language, Understand its Culture (← links)
- Testing Is the Engineering Rigor of Software Development (← links)
- Make Interfaces Easy to Use Correctly and Hard to Use Incorrectly (← links)
- Know Your IDE (← links)
- Programmers Who Write Tests Get More Time to Program (← links)
- Small! (← links)
- Don't Nail Your Program into the Upright Position (← links)
- The Boy Scout Rule (← links)
- The Professional Programmer (← links)
- The Linker Is not a Magical Program (← links)
- Hands on in All Phases (← links)
- Prefer Domain-Specific Types to Primitive Types (← links)
- Code Layout Matters (← links)
- Know Your Next Commit (← links)
- One Binary (← links)
- The Longevity of Interim Solutions (← links)
- Implicit Dependencies Are also Dependencies (← links)
- Distinguish Business Exceptions from Technical (← links)
- Learn reading and judging code, especially your own (← links)
- The Three Laws of Test-Driven Development (← links)
- The Single Responsibility Principle (← links)
- Ask "What Would the User Do?" (You Are not the User) (← links)
- Prevent Errors (← links)
- Make Progress Visible (← links)
- Deploy Early and Often (← links)
- Understand SCM (← links)
- Structure over Function (← links)
- Don't Ignore that Error! (← links)
- Beauty Is in Simplicity (← links)
- Comments!=Evil (← links)
- Missing Opportunities for Polymorphism (← links)
- Don't Touch that Code! (← links)
- Collection of Collections Is a Code Smell (← links)
- A Comment on Comments (← links)
- Hard Work Does not Pay off (← links)
- Continuous Refactoring (← links)
- Scoping Methods (← links)
- Improve Code by Removing It (← links)
- Don't reinvent the wheel (← links)
- Use the same tools in a team (← links)
- Learn to Estimate (← links)
- Domain-Specific Languages (← links)
- Check Your Code First before Looking to Blame Others (← links)
- From Requirements to Tables to Code and Tests (← links)
- Message Passing Leads to Better Scalability in Parallel Systems (← links)
- How to Access Patterns (← links)
- Balance Duplication, Disruption, and Paralysis (← links)
- Don't Rely on "Magic Happens Here" (← links)
- Consider the Hardware (← links)
- Data Type Tips (← links)
- Reinvent the Wheel Often (← links)
- Improved Testability Leads to Better Design (← links)
- Decouple that UI (← links)
- Put the Mouse Down and Step Away from the Keyboard (← links)
- Expect the Unexpected (← links)
- Continuous Learning (← links)
- Clint Shank (← links)
- Methods Matter (← links)
- Do Lots of Deliberate Practice (← links)
- Code Is Hard to Read (← links)
- Dave Anderson (← links)
- The Golden Rule of API Design (← links)
- Make the Invisible More Visible (← links)
- Code in the Language of the Domain (← links)
- Write Small Functions Using Examples (← links)
- Integrate Early and Often (← links)
- Write Tests for People (← links)
- Read the Humanities (← links)
- Know Well More than Two Programming Languages (← links)
- Apply Functional Programming Principles (← links)
