Over the last few posts, I’ve been sharing some thoughts on why good development takes time. Of course, these are only limited to my own set of experiences, but I do think many of these are shared among developers.
In the first post, I said that we all fall into the category of a producer or a consumer, at some point, and we often want what we want sooner rather than later.
In the second post, I shared two reasons why I think good development takes time:
- The Are Moving Parts
- Problems Within Problems
And in this post, I wanted to share the last three reasons for why that I think good development takes time.
Earlier this week, I wrote a short stating that good development takes time in which I basically laid out the idea that we all fall into the category of a producer or a consumer – at least at some point – and that none of us are immune to wanting something good, and wanting it sooner rather than later.
For some, the post was a bit cliche – which is fine :) – but I was also asked a question via Twitter that I thought was deserving of its own set of posts
And so I know that the answer that I’ll give will obviously be relevant to my experience, but I thought I’d share it anyway, and hope that you guys would also chime in with your own experience and ideas as to why good development takes time.
Since working in software, one of the things that I’ve yet to actually get used to is how quickly people want things delivered.
But I’m not saying this as someone who has built things for others, but also as someone who enjoys using things other people have built, and as someone who cares deeply about trying to get better at what I do for a living.
The bottom line is that development takes time, and good development takes even more time, but neither of the statements are completely one-sided.