Yes. My take on this is that we're building a prototype to be able to provide users something tangible to get feedback on. Maybe even a proto-prototype to explore internally with the team. "Right Features" is a bit nebulous. It's "Build the features…
Umm... sure? Tracer bullet? Walking Skeleton? I don't know where this one is really going. As a practitioner of Emergent Design and Evolutionary Architecture... I'll just start coding and refactor the hell out of the system as I go. Practically always functional, definitely always deployable. It&…
* It's always better the second time. * If it takes you more than 5-15 minutes git reset -hard and start over. * Don't spend long in red. If you can't quikcly get to green revert back to a green state and start over. There's…
I don't like this phrasing. I don't really even like the idea. I think this is the first one that doesn't have a reference. The problem I have is that the incentives and motivations for developers and customers are going to be different. Excluding…
This is connected to the "Why I hate DI..." post. It was a single post... but got stupid long... so I split it. Let's take a moment to look at what I do... do. HAHAHAHAHAHA... It's my blog, I get to laugh at that…
... frameworks. I have a very strong aversion to Dependency Injection frameworks. Hate... is a little strong; but I'm comfortable saying I hate DI Frameworks. "But why?" I hear you ask. I mean... I actually read it. This post is the answer to that question I was…
Yes. Do that. Not only should we follow Principle 7 of giving products to customers early, but we need to communicate with them. Not just feedback on the product itself; but stay in touch. We need to have raport and a working relationship with our customer. As a product team,…
Yes. Do that. We can't understand what a user is expecting. Most of the time a user doesn't know what they want. They can tell us what they think they want; but is that going to produce the system that will best serve them? No. the…