strategy

• 1411689600 » Apply agile concepts to your career
• 1411516800 » Deliver value, not hours
• 1411430400 » DIY
• 1371686400 » When (not) to use your programmer's black belt
• 1360713600 » Learning to focus
• 1349568000 » Go to the source

tech

• 1416960000 » Refactoring the three laws of TDD
• 1416787200 » Behavior Patterns
• 1416355200 » Introduction to Smalltalk Best Practice Patterns
• 1414713600 » The Theory of Constraints
• 1414454400 » Extreme Programming Corollary Practices
• 1414368000 » Extreme Programming Primary Practices
• 1414022400 » Extreme Programming Principles
• 1413936000 » Extreme Programming Values
• 1413331200 » Mental models for concurrency
• 1412640000 » The "Law" of Demeter
• 1391731200 » Gollum on Heroku
• 1378339200 » New blog
• 1367193600 » Pagination with ActiveResource

personal values

• 1441756800 » Becoming a better software developer
• 1418860800 » The Craftsman Toolbelt
• 1411603200 » The Humble Programmer
• 1411344000 » Software Development Intermission

clean code

• 1413763200 » The Boy Scout Rule
• 1413417600 » Your code is working? Great, you're not done yet
• 1412812800 » Third-party code boundaries
• 1412553600 » The Coding Style Guide
• 1412294400 » Avoid comments
• 1412208000 » Better functions
• 1412121600 » Communicate through meaningful names
• 1412035200 » Dealing with spaghetti code
• 1411948800 » Keep your tests clean

examples

• 1425772800 » Named Pipes
• 1421884800 » Loose coupling in Go lang
• 1415577600 » Build and validate your own web server
• 1412899200 » Reusable code through separation of concerns
• 1412726400 » Use `nil` when you mean it

design

• 1417478400 » Formatting Patterns Picks: Cascade
• 1417392000 » Behavior Patterns Picks: Reversing Method
• 1415145600 » Incremental Design
• 1413849600 » Code Heuristics
• 1413244800 » Four rules for emerging simple design
• 1413158400 » Test drive your system architecture