Software is quickly born, but is slowly grown. Knowing how to raise software properly ensures continued return of investment, and prevents costly rewrites that can bankrupt you.
Understanding the Monty Hall Problem
I explore the classic monty hall problem and use a little bit of ruby to help understand it.
The Story Behind Creating Cloudspeq
How I got my 5 minute test suite down to 20 seconds, and made my first gem from my efforts.
Get it here:rubygems.org and github.com
Understanding Rspec Test Doubles
For a while, I have not understood what rspec test doubles do, or why you’d use them. I recently came to understand their usage and function, and thought I’d share.
11 Lessons From a Codebase
I’ve been fixing up the codebase of a rails app for a few months now. It was written by some smart folks, so I wanted to share some of the philosophies and design patterns they utilized.
I Quit Reddit for Music
I don’t know why I didn’t do this sooner.
Pjax_rails and Layout Rendering
An issue I ran into when using the pjax_rails
gem, and useful advice if you need additional content delivered besides the yield
result.
Tip: Order Git Branches by Last Commit Age
A great tool for git users
The Difference Between Savant and Opinionated
Steve didn’t like the status bar and didn’t see the need for it. “Who looks at URLs when you hover your mouse over a link?” He thought it was just too geeky.
Important to remember that how you approach something is not the same way others approach it. Good software has an adjustable grip, whereas poor software assumes all users are the same.
If You’re Not Doing Something Different You Can’t Make a Difference →
Perhaps obvious advice, but still struck me.