Posts Tagged ‘software design’

Rule #17: Break it before you build it.

Test-Driven Development (TDD) — the idea that you write tests before you write any code — is one of those killer ideas that we just keep coming back to. At a technical level, most experienced software developers understand the inherent value in TDD: delivering a suite of automated tests alongside your code just feels a [...]

Continue reading »

Rule #16: Small is beautiful.

Let’s take this in baby steps. I find myself saying that phrase to our product team a lot lately. In other words: “let’s think of the smallest possible feature we can build that addresses our customer’s need, and then let’s see if we tighten it up even more.” Working on things one-tiny-nano-step at a time [...]

Continue reading »

Rule #10: Focus on people and pain, not features and functionality.

Writing great software starts with two simple questions: Who am I creating this for? How are they hurting? Focusing on people and pain helps you define why you building what you are. And understanding the why can help answer a lot of questions throughout the development process. However, many discussions in the software industry instead [...]

Continue reading »

Rule #8: Follow the five-minute rule.

When I was five years old, it was a well-known Law of Physics that if you dropped a cookie on the floor, it was “still good” if you picked it up within five seconds. This, appropriately enough, was know as The Five Second Rule and I’m fairly certain a lot of children are aware of [...]

Continue reading »

Follow

Get every new post delivered to your Inbox.