[lbill]

I agree with the author : start simple, then use more complex tools when and if you need to.

I believe it is true about infrastructure, and about features and code as well.

When my team needs to release a functionality for the "product"[1] that we maintain, we have a very simple strategy : we go step by step. The users tell us what they need, and we start to deliver as soon as we can. Our first release only solves a portion of the user's problem, but the second release solves more, and so does the next, and so on. I devised this strategy with the users to make sure they are fine with it: they expect a perfect product... eventually. But in the mean time, they having only some portions of their needs met, and we avoid the feeling of being overwhelmed by a great apparent complexity.

[1] The context is a bit complicated... and irrelevant. We don't exactly maintain a product, but it's close enough for the argument here.

[lbill]

Oops! Sorry for the huge typo in my comment. "they having only some portions of their needs met" should be read "they are fine with having only some portions of their needs met".

(It is a bit more than a typo)