There are two things I’ve tried to include in my morning routine that are gicing me great results. The first is a special way I’m making my coffee. The second is what (on most days) I focus on as my first “work” thing of the day. Here’s a quick description of both.
Sometimes when I talk to other developers about how testing is part of their workflow, I get responses like “Yeah, we have unit tests” or something similar. Most of the time, what these folks are talking about are what I’d consider “verification tests”. But “having tests” isn’t the same as “doing TDD”.
It amazes me how many little commands there are in git that I still keep stumbling across. The latest one I found is a pretty quick way to get a handle on who has committed what, who has made the most commits and other stats from a project’s git repo. It’s a variation of the typical log that you’re probably used to. Read on for the details.
For the most part, the Ruby community is pretty sold on the idea of test-driven development. And I realize that other programming languages have their own take on testing, their own testing frameworks, and so on. However, every so often I come across a developer that isn’t on the TDD bandwagon. For those that fall into this camp, here are just a handful of benefits of adopting a TDD approach.
I recently stubled across what I think is one of the big secrets that separates winners from losers, the successful from the unsuccessful in today’s world. I had come to this conslusion already, then read others talking about this same idea in multiple places, all within about a week of each other. This post is a collection of my thoughts on the idea of being a “producer” vs. a “consumer”.