performance
Sometimes I feel developers think that performance is a dark art. It is not. In my experience, well performing systems come down to this: fewer and faster. If you are doing something a lot, do it fewer times. If you are doing something that is slow, make it faster. It
randoms
The Error Model [http://joeduffyblog.com/2016/02/07/the-error-model/]. I’ve been doing a lot of resiliency related things lately and that means dealing with errors. This post is one of the longest (and also best) summary of error handling on the planet. Write code that is
randoms
Fail at Scale [http://queue.acm.org/detail.cfm?id=2839461] Great post about failure at Facebook. My favorite parts were controlled delay and adaptive LIFO. > These two data points seem to suggest that when Facebook employees are not actively making changes to infrastructure because they are busy with
performance
de•cay noun - the state or process of rotting or decomposition. Let us kick off the new year with a lovely post on decay. All systems decay. Even when you continually work on improving the system, it decays. That said, in my experience, not all decay is equal with regards
performance
A general model (or guidelines to live by) that won’t solve all your problems, but will keep you from getting into trouble overly quickly.
performance
The norm for rate limiting these days seems to be based on the number of requests a consumer can make in a given time window. The problem with this is that all requests are not equal. Some requests are more expensive than other requests and should be treated as such.
randoms
Previously [https://jnunemaker.ghost.io/monday-randoms-2015-11-02/]. Quotes > The true purpose of testing, just like the true purpose of design, is to reduce costs. Sandi Metz in Practical Object-Oriented Design in Ruby. Motivational Want to Create Things That Matter? Be Lazy. [http://99u.com/articles/
randoms
Previously [https://jnunemaker.ghost.io/wednesday-randoms-2015-09-30/]. Resiliency Resiliency checklist [http://monkey.org/~marius/checklist.pdf] A fantastic checklist broken up into 4 categories: fault tolerance, scalability, operability and efficiency. > What happens when a dependency starts failing? What if it begins failing slowly? How can the
randoms
Previously [https://jnunemaker.ghost.io/saturday-randoms-2015-09-19/]. Data Building DistributedLog: Twitter’s high-performance replicated log service [https://blog.twitter.com/2015/building-distributedlog-twitter-s-high-performance-replicated-log-service] How Twitter build a distributed log on top of Apache BookKeeper [http://bookkeeper.apache.org]. Great
programming
I enjoy reading papers and try to on a regular basis. I actually read them old school style. I print them and then use a pen to underline the quoteables that I liked. Sometimes I annotate them with thoughts, and rarely, I have even put a grade at the top,
randoms
I read a lot. I curate what I read into likes in instapaper [https://instapaper.com] and bookmarks in pinboard [https://pinboard.in]. It hit me the other day, as I was reading one of the many email newsletters I subscribe to for dev tips, that there is value in
flipper
Nearly three years ago, I started work on Flipper. Even though there were other feature flipping libraries out there at the time, most notably rollout, I decided to whip up my own. Repeating others is, after all, one of the better ways to level up your game.