#400 Write code. Not too much. Mostly functions.

this week's favorite

Write code. Not too much. Mostly functions.

Code, like food, has value. I think those of us who write it can (hopefully) agree on that. Some, though, are so afraid of writing/eating too much that they avoid writing/eating what they should.

Consistent Disaster Recovery for Microservices: the CAB Theorem

How do you backup a Microservice? You dump its database. How do you backup an entire application decomposed into microservices? In this paper we discuss the tradeoff between the availability and consistency of a microservice-based architecture, when the backup of the entire system is being performed.

Command Line Interface Guidelines

An open-source guide to help you write better command-line programs, taking traditional UNIX principles and updating them for the modern day.

My Engineering Axioms

In any case, I thought it would be fun to share the list here, with a few brief clarifications. Some things are pretty unsurprising, but hopefully others will generate some provocative thoughts and/or interesting disagreements.

Statistical approaches for performance analysis

Software performance is a complex discipline that requires knowledge in different areas from benchmarking to the internals of modern runtimes, operating systems, and hardware. Surprisingly, the most difficult challenges in performance analysis are not about programming, they are about mathematical statistics!

newsletters

Would you like to become a sponsor and advertise in one of the issues? Check out our media kit and get in touch.