A big theme in the keynotes and conversation during Velocity Conf in NYC a few weeks ago was the role of ops in an "ops-less" and "server-less" world. It's also been a big feature in discussions on twitter and in conversations I've had with coworkers and friends in the industry. There are several things that stand out to me in these conversations: first, that some ops engineers (sysadmins, techops, devops, and SREs) are worried that they will be phased out if developers and software engineers are responsible for the operational tasks in their systems; second, that developers and software engineers do not have the skills needed to take over responsibility for operational tasks; and third, that building reliable systems is impossible without an operations organization.
Over the past few years, ever since writing "If Susan Can Learn Physics, So Can You", I've been contacted by people from all backgrounds who are inspired and want to learn physics, but don't know where to start, what to learn, what to read, and how to structure their studies...this post is a condensed version of what I've sent to people who have contacted me over the years, outlining what everyone needs to learn in order to really understand physics.
After reading Philip K. Dick's Do Androids Dream of Electric Sheepover the Thanksgiving holiday and watching the very first few episodes of The Man in the High Castle TV series on Amazon, I just had to read The Man in the High Castle, and I'm so glad that I did. Neither book is exactly pleasant to read: PKD's writing is extremely choppy, and the surface plots don't quite come together or make much sense. It was only after I read both that I realized why the plots were so strange: they aren't quite the stories that the books are telling.
In this post, I cover the four layers of microservice architecture - the hardware layer, the communication layer, the application platform layer, and the microservice layer - and what each of them contains.
One of my goals this year was to read a total of 52 books - one book every week. There were no restrictions on which books would qualify, as long as each book was something that I actually wanted to read, read carefully, and took notes on while reading...here are the 52 books of 2016:
The crux of reproducibility when it comes to bugs is this: being able to reproduce a bug requires that the state of the system be nearly identical at the time of reproduction as it was at the time the bug originally occurred - something that is impossible to guarantee in large production systems...
This week's BART book of the week is Charles Petzold's Code: The Hidden Language of Computer Hardware and Software, recommended to me by my awesome coworker Dan Tsui. Oh how I love this book. This is the book that every computer science student should read during their first few weeks of undergraduate (seriously, they should just hand out copies of Code to all incoming computer science freshmen). It's the book that everyone who wants to understand how computers really work should read. This is the book that I'm going to buy a pile of copies of just so I can give them away. It's perfect.
Every week I read at least one book during my commute to San Francisco while I'm riding BART. Since I'm doing all that reading, and I love writing about what I read, I'm starting a new feature here on my blog where I'll write up little informal reviews of the books that I read, focusing on what I liked about each book and the lessons I learned from it. I'm excited to kick off this series with one of the most amazing books ever written, by one of my favorite writers of all time!