The longer I’ve worked in developer – and the more developers with whom I’ve interacted – the more I recognize that we all share a single trait:
We want to get our project right the first time.
Of course, this looks different depending on the type of project, but the point remains: We want to make sure that we nail not only the larger details, but the smaller details correct for the first release.
- Have we detailed all the features?
- Have we tested across every single device?
- Did we select the right font size?
- Should this feature automatically work, or should it have an element exposed to control it?
- …and so on
And even though this is true, I think that deep down we know it’s not really possible to achieve.
In fact, I’ve talked numerous times about what I call a strong 1.0 which is essentially the idea that you focus very hard on an MVP – trim the features, nail down the specifics for the first release, and then iterate.
And when it comes to that compulsive need that we – as developers (and probably designers, as well) – have, this can go along way in helping to make a better product.