Programming, distributed computing| a-nickels-worth.dev
| A Nickel's Worth
Names Considered Useful Software is written for people to understand; variable names should be chosen accordingly. People need to comb through your code and understand its intent in order to extend or fix it. Too often, variable names waste space and hinder comprehension. Even well-intentioned engineers often choose names that are, at best, only superficially useful. This document is meant to help engineers choose good variable names. It artificially focuses on code reviews because they expos...| a-nickels-worth.dev
Hi, I’m Jacob Gabrielson and I’m a developer working on Oracle Cloud Infrastructure. I’m interested in infrastructure, in general, and specifically interested in Kubernetes, Unix, Bash, systems programming, topics related to practical distributed computing, functional programming, and Emacs. This blog replaces my old external blog, which I’ll leave up for the time being. It’s a collection of posts I’ve made over the years (and hopefully a few new ones). Please note this blog is en...| A Nickel's Worth
This content is in snippets/first/index.md pwd| A Nickel's Worth
This content is in snippets/second/index.md ls -la| a-nickels-worth.dev
Note: I originally wrote this on an internal Amazon blog in 2006. This is the original version with a few edits. A newer paper covering the same content can be found on the AWS Builder's Library, Avoiding fallback in distributed systems. More complicated software is more buggy, so programmers try to apply Occam's Razor and code as simply as possible (but no simpler). But how does one define "complexity"?| a-nickels-worth.dev