(Replying to PARENT post)

The idea about microservices is that they are small and self-contained. This makes them easy to rewrite completely. Now I wouldn't say it is the goal to rewrite them all the time, but it is not a bad sign if some of them get rewritten occasionally. Microservices are somewhat new and a lot of architecture and infrastructure is being built around it. Companies like Netflix and Uber take the lead in this. Susan Fowler wrote a book about this during her time at Uber, you can find it here:

http://shop.oreilly.com/product/0636920053675.do

👤rejschaap🕑8y🔼0🗨️0

(Replying to PARENT post)

I've been programming a while now and it definitely is a bad sign if you're rewriting any code often.

Firstly, it takes a lot longer than just making the necessary change. It's a waste of time.

But more fundamentally, I can understand getting it wrong the first time. Throwing what should have been a prototype up without rewriting it. Whatever.

But how the hell did you get it so wrong the 2nd time? And the third time? And the 4th, etc., etc.

Now I'm not afraid to do refactors, massive ones if needed. But there's a big cost to doing it. The big problem with constantly rewriting stuff is that you almost always introduce new bugs. Or you misunderstand the reason behind some of the edge cases and cut them out.

Sounds like the actual problem here is classic NIH syndrome with new programmers coming in, not liking the old programmer's style and rewriting the whole thing.

👤mattmanser🕑8y🔼0🗨️0