I feel like, lately, a lot of my blog posts start the same way: I explain that I didn’t particularly like something in the past, then follow that up with how my perception changed. This time its different: I love TDD with my whole being, and did so from the very start.

There were, however, times when Test Driven Development and I didn’t stand on the best of terms. And, being fair with this wonderful software development process: I was wrong in all of them.

TDD wasn’t any less amazing when I didn’t like it. I just didn’t have enough experience to use it to its full potential. And this lack of vision kept me from reaping the full benefits of the approach; which in turn caused me frustration.

But as time went by, and I kept using the approach over and over again, I slowly began to see the light. And once I began to really understand it, TDD showed me a new world I didn’t even know existed, one of certainty and easy refactors.

And I’m here to share that world with you today, if you wish to join me.

Continue Reading "TDD: A story of ups, downs, and ups again."

I was talking with a friend of mine the other day about this one app he’s building for himself. He was really excited pitching me the idea, talking about screens and features and possibilities. You know, all the good stuff.

And I’ll be honest with you, he got me excited about the app too. Why? For starters, he had a pretty good idea that targeted a niche and solved a problem (essential for app development). Second and most important, he was really passionate about his ideas and the good that could come out of his work; and that was what got the little maker in me to fire up.

I asked him to send me the details for the project, and he did the very next day. I read through them carefully and just as I expected, it was really good. It just had one problem: Too many features.

Now now… I know what you’re going to say, how can having too many features be a bad thing? (Or maybe you didn’t say that, but work with me for a second here)

Well, I’m about to propose to you the following:

You can make your application better by having it do less things.

Interested in getting to know how, why or what I’ve been drinking? *cough* coffee *cough* Then buckle up soldier, we’re going for a ride:

Author’s Note: The ideas and tips that are presented in this post are highly influenced by the work done by 37signals (now basecamp) and specially their bestselling books Getting Real and Rework. For a deeper analysis of these methods I highly recommend reading their books and following their blog at Signal v. Noise.

Continue Reading "Improve your App with less features."