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.
I explore the classic monty hall problem and use a little bit of ruby to help understand it.
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.
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 don’t know why I didn’t do this sooner.
An issue I ran into when using the
pjax_rails gem, and useful advice if you need additional content delivered besides the
A great tool for git users
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.
Perhaps obvious advice, but still struck me.