Tanagram is a project idea I've been exploring built around two fundamental hypotheses about modern software.
Documenting Some Thoughts Around Tanagram
Introducing LeetcodeSolutions
I created the study guide I wish I had when I was studying for programming interviews …
Apple Watch: Not-a-Review
There seems to be an inverse correlation between how much I pay for an Apple product and how much I enjoy using it …
An Introduction to jscodeshift
Recently, I had to make a straightforward change over dozens of files spread across our entire frontend codebase. I didn't like the idea of finding all the files and manually make the change; in the spirit of laziness-driven-development, I decided to figure out a way to script it. I'd discovered jscodeshift a few months ago... Continue Reading →
Thoughts on Personalizing Software
Software should be personalized, not prescriptive
Tech Stacks are Overrated
In the process of interviewing dozens of junior and intermediate engineers, the questions candidates ask implicitly say as much about them as the rest of the interview. One question that comes up occasionally is some variation of "what tech stack are you using"? List some of the myriad Javascript libraries-du-jour and I get a murmur... Continue Reading →
Service objects as test fixtures
Service objects can be a great way to improve a number of problems frequently found in Rails application tests
There’s More to Coding than Just Writing Code
Coding is 80% thinking, 20% typing. But many resources do it backwards.
Behavioral Observations from Taking Over SXSW
I just got back from taking over SXSW with Trustwork. We ran a scavenger hunt with multiple stations giving out free stuff in exchange for user signups. This post is the second of two posts on learnings and observations from that week. Part 1 is here. My intent is to present some personal observations. It... Continue Reading →
