unwiredcouch.com on unwiredcouch.com

Post breakfast quick sketch this morning.

This has come up in various discussions again and again so I finally decided to read it.

Usually I tend to shy away from longer (i.e. over 300 pages) books because I feel like I’m a somewhat slow reader.

I really liked especially the first part of the book that focuses on the science and research of motivation.

This book was just plain amazing.

I also found this one by accident while looking through the book store.

I decided to give this book a try after poking around at the local book store.

This was another purchase while rummaging at the book store.

It took me quite a while after buying this book to find the excitement to actually read it.

This book gives a thorough introduction into logic and how to apply it.

A while into learning how to draw I realized that watercolor is a lot more fun and versatile than I thought it was from my experience using it in art class in school.

One of the things I’ve come across most in my career in technology (and one that still persists) is the belief that as an engineer, your manager (or coach) needs to be fairly technical as well.

I decided to read this new edition of “A Brief History of Time”, which I had started but never finished.

I absolutely loved this book.

Batwoman!

Really enjoyed the book.

I was pretty excited about this book.

I didn’t much enjoy the book which might be due to expecting something different.

I really enjoyed this book.

It’s really short, more of an essay really, so there’s no reason not to read it.

This is a fantastic book.

I’ve known Lara for years and have also been part of her organization for a bit when we worked at Etsy together.

This book blew my mind (pun intended).

A couple of years ago I went from working in an office to working remote mostly from home.

Ben Grimm.

Reed Richards.

“Kept you waiting, huh?”

Finally done with this teen Jean Grey piece I’ve tried to finish for a while now.

I’ve been having a lot of discussions about delivery of software lately and especially about the deployment part of it.

Very nice and easy read.

Young Hank McCoy.

John Constantine.

I wrote about how we do capacity planning for our web and API clusters on Etsy’s engineering blog.

I wasn’t quite sure what to expect from this book.

Saying that the last 18 months or so were stressful and full of changes would be a colossal understatement.

I read this book during a fairly busy time of my life (both personally and professionally) and it provided a very welcome perspective on slowing down, dialing down distractions, and focusing on what Newport calls “deep work”.

This book provides a great overview of how to run good retrospectives and meetings in general.

I’ve been somewhat interested in Go for quite a while now.

I recently read John Vincent’s very interesting and honest blog post about being paralyzed because of seeing all the flaws in systems.

In the last couple of months I’ve done a foray into unit testing the shell scripts I write.

I don’t like breaking things.

I really enjoyed reading this book and the author’s argument with the fact that not everybody is perfect and that not everyone needs to be perfect to strive for feminist ideas to become reality.

If you’re working as a software engineer, you have very likely already heard about ’egoless programming’.

I was really looking forward to this book as I’ve heard good things about it and thought it would round up what I already knew about the topic.

This was an interesting read about the author’s perspective on the issues of objectification and discrimination of women and their bodies.

This is a really great introduction to systems thinking.

This year has been really good for reading for me.

Some years ago I wrote about how to use Heroku and a set of hosted solutions for getting started with monitoring for your personal infrastructure.

In this book Sarah Jeong - a journalist trained as a lawyer at Harvard Law School - talks about the problem of online harassment.

I’m one of those engineers who used to happily claim to not have any frontend skills and just not be good at design.