List of posts

I'm always reading posts, articles, and papers from various sources on the Internet. In the last 4 years I have developed the habit of collecting the texts that are most relevant to me, and now that I've reached the number of 100 posts collected I think it's a good time to share them with you. I have divided them into some broad categories. The categories are organized in alphabetical order, although the posts themselves do not follow a specific order. Most of the texts are in English and some of them are in Portuguese. Enjoy!

APIs

1. Best Practices for Designing a Pragmatic RESTful API
2. API Gateways are going through an identity crisis
3. API Versioning Has No "Right Way"

Architecture

4. Unifying Mobile Onboarding Experiences at Uber
5. What do you mean by "Event-Driven"?
6. Focusing on Events
7. 11 erros comuns em arquiteturas orientadas a eventos e como evitá-los
8. Event Collaboration
9. ParallelChange
10. The evergreen cache
11. The LMAX Architecture
12. A primer on functional architecture
13. A Brief History of Scaling LinkedIn
14. The Architect Elevator — Visiting the upper floors
15. BLIKI: Arquitetura de Software — EximiaCo.Tech

Blockchain

16. WTF is The Blockchain?
17. Who owns the Blockchain?

Carreer and personal development

18. Programmer Competency Matrix
19. LimitationsOfGeneralAdvice
20. SoftwareDevelopmentAttitude
21. Your obsession with learning might be holding you back
22. How to get experience as a software engineer
23. On Being A Senior Engineer
24. What does sponsorship look like?
25. A forty-year career.
26. Pendulum swings
27. How to Disagree

Development tools

28. How (and Why) to Log Your Entire Bash History
29. Who Needs Git When You Got ZFS?

Documentation

30. Como escrever boas documentações
31. Etsy's experiment with immutable documentation
32. The Golden Rules of Code Documentation
33. Our team broke up with instant-legacy releases and you can too
34. Undervalued Software Engineering Skills: Writing Well

Incident management

35. Introducing Dispatch
36. Blameless PostMortems and a Just Culture
37. Three months, 30x demand: How we scaled Google Meet during COVID-19

Microservices and distributed systems

38. Best Practices for Building a Microservice Architecture
39. Standing on Distributed Shoulders of Giants
40. The rise of non-microservices architectures
41. Thinking about Microservices: The Fiefdom and the Emissaries
42. Where is my cache? Architectural patterns for caching microservices by example
43. Patterns for Microservices — Sync vs. Async
44. The Hardest Part About Microservices: Your Data
45. The Hardest Part of Microservices: Calling Your Services
46. Introducing Domain-Oriented Microservice Architecture
47. Seven Hard-Earned Lessons Learned Migrating a Monolith to Microservices
48. Backend-in-the-frontend: a pattern for cleaner code
49. The Log: What every software engineer should know about real-time data's unifying abstraction

People, teams, and processes

50. The Agile Fluency Model
51. Why Your Employees Are Losing Motivation
52. Our obsession with performance data is killing performance
53. Evidence Based Scheduling
54. 3 Habits of a Highly Effective Growth Engineering Team
55. The epistemology of software quality
56. Building a Platform Team — Laying the Foundations
57. Maximizing Developer Effectiveness
58. front-of-the-front-end and back-of-the-front-end web development
59. Embrace the Grind

Product

60. Design for the Novice, Configure for the Pro
61. Once You’ve Solved for the Novice, You Need to Handle the Pro
62. When a rewrite isn’t: rebuilding Slack on the desktop

Programming languages, design, and implementation

63. Revenge of the Nerds
64. Things You Should Never Do, Part I
65. Python Design Patterns: For Sleek And Fashionable Code
66. The Absolute Minimum Every Software Developer Absolutely, Positively Must Know About Unicode and Character Sets (No Excuses!)
67. Efficiently Exploiting Multiple Cores with Python
68. Python 3 Q & A
69. DRY is about Knowledge
70. Domain-Driven Design is Linguistic
71. GoF Design Patterns — Sobreviveu ao teste do tempo?
72. Design patterns of 1972
73. Ralph Johnson on design patterns
74. "Design Patterns" Aren't
75. Monopólio de linguagens: uma perspectiva além de tecnologia
76. Programming as translation
77. Short Identifier
78. Crash-only software: More than meets the eye
79. Ignore All Web Performance Benchmarks, Including This One
80. Too DRY — The Grep Test
81. The Right Way to Bundle Your Assets for Faster Sites over HTTP/2
82. Collection Pipeline

Security

83. So you want to secure something
84. Up to 20% of your application dependencies may be unmaintained

Technical debts

85. Chernobyl: The True Cost Of Technical Debt
86. Three Tips for Managing Technical Debt: While Maintaining Developer Velocity (and Sanity)
87. When Your Tech Debt Comes Due
88. TechnicalDebtQuadrant

DevOps

89. 5 Lessons Learned From Writing Over 300,000 Lines of Infrastructure Code
90. Monitoring Check Smells
91. The Calculus of Service Availability
92. How to invest in technical infrastructure
93. Why Google Stores Billions of Lines of Code in a Single Repository

Technology and history

94. True Innovation
95. The Secret History of Women in Coding
96. The Yoda of Silicon Valley

Tests and quality

97. Software Testing Anti-patterns
98. Is High Quality Software Worth the Cost?
99. The Rise of Test Impact Analysis
100. I test in prod