This will be a very brief post, just as a reminder that we need to give things a good thought, trying to limit our biases (I’ll focus on software development, but it’s applicable to everything really).
A couple of reads and a couple of watches. Articles “Life Beyond Distributed Transactions: An Apostate’s Implementation - A Primer” Nice series of articles (not yet finished) on implementing transactional logic in a distributed system without resorting to the traditional SQL distributed transactions. “Software Testing Anti-patterns” Excellent thorough article on testing anti-patterns, technology stack agnostic, with valuable information to make sure we get the most out of our tests. Videos “GOTO 2018 • Practicalities of Productionizing Distributed Systems • Jeff Hodges” Nice talk on distributed systems, problems that might arise and ways of to figure them out....
Intro This post will be simple and try to act as a discussion starter on unit testing static methods. I’m not the greatest fan of making static stuff, mainly because I’ve been burned by it in the past (the fact is that static was being used badly in those cases, but even so, if I can, I’ll avoid it) but I understand it’s the best way to do things sometimes....