software development
January
- 02
- Almost Always Unsigned
- 12
- Data-Oriented Programming is dope
- 13
- How I build a feature
- 25
- The truth about starting with microservices
- 27
- Three kinds of memory leaks
February
March
- 04
- How to design better APIs
- 06
- Pair Programming Antipatterns
- 08
- Still No Consensus On Testing Private Methods
- 14
- Storing UTC is not a silver bullet
- 22
- My key takeaways from The Pragmatic Programmer
April
May
June
- 12
- Best practices for inclusive CLIs
- 12
- The hard problem: naming functions and other gizmos
- 15
- Why Duck Typing Is Safe
July
- 08
- Why DRY is the most over-rated programming principle
- 13
- The Top 10 Tips to Write Clean Code
- 24
- Is keeping dates in UTC really the best solution?
- 25
- A Guide to Naming Variables
August
- 01
- Print based debugging and infrequent developers
- 05
- Use One Big Server
- 14
- Avoid Spaghetti Code with Scope Minimization
September
- 05
- Top 10 skills every programmer should know
- 12
- Write Your Own Task Queue
- 24
- Want cleaner code? Use the rule of six
October
- 01
- Signals in prod: dangers and pitfalls
- 03
- Software engineering practices
- 11
- 12 Factor App Revisited
- 15
- Avoiding Featurism
- 19
- When life gives you lemons, write better error messages
- 31
- 7 Estimation Anti-Patterns
November
- 15
- 80/20 Refactoring
- 23
- The case for dynamic, functional programming
- 25
- Feature Switch Best Practices
- 26
- I/O is no longer the bottleneck
- 30
- I am disappointed by dynamic typing