... I'm not even sure what this one means. I gotta jump straight to the book... OK - Users want more. Keep your documentation. Plan your configuration Procedures. I agree with the intent of this. It shows it's age though. With the bandwidth and web centric nature of software - things…
Yes. Again, based on the past few principles; I think I'll be in agreement with the book. This is largely recognized as emergent design; thin vertical slices; tracer bullet; walking skeleton... lots of names witih slight variations in their emphasis. All of these are about producing something that is fully…
I touched on this in Principle 12 - All prototypes should be throwaway, or else you're just doing emergent design. And build them for low effort/cost. It's about quickly integrating feedback. If we spend a long time building the prototype, we'll not get information needed to make decisions. We're…
3 Months ago... That's how long my last post was... bleh... Sorry. Anyway - I burnt out in a few ways. I needed to drop some stuff and the blog got hit. I've got a few posts written that were never scheduled... More of the 201 software series. I'm not…
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 that need clarification as…
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's a good form of…
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 a lot I've heard, and agree with, about…
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 developer tools - I'm gonna go…