https://www.quora.com/What-are-the-growth-stages-of-a-programmer/answer/Andreas-Blixt https://www.quora.com/What-are-the-growth-stages-of-a-progra... Second ph

https://www.quora.com/What-are-the-growth-stages-of-a-programmer/answer/Andreas-Blixt https://www.quora.com/What-are-the-growth-stages-of-a-progra... Second phase of a developer: 2. The philosophizing abstracter "This code works for now, but if I move this part into a factory, and create an interface for these methods, it'll also support all these future cases I can think of!" They've read all the articles on how to structure code. There's a lot of patterns out there for object-oriented (or functional!) code. Their code has all sorts of useful interfaces, abstraction layers, factories, extension methods, data structures. Things break down when the project needs to move in an unexpected direction and it turns out that implementing the change requires changing a lot of the codebase because there were a bit too many abstractions that ended up creating hidden dependencies across the code.