2 ms·
Competency != suggest major changes to architecture. In fact suggesting major changes to architecture is a strong signal of an immature developer. There are ti
by barrkel 9y ago
Competency != suggest major changes to architecture.
In fact suggesting major changes to architecture is a strong signal of an immature developer. There are times when major changes in architecture are warranted, but they are suggested far more often than that. The implications of the suggestions usually mean rewriting lots of code just to stand still.
- mercutio2 9y agoPrecisely this, thanks!
- nitely 9y agoWhy would it be ok to suggest changes after a year then (which is fairly arbitrary btw), according to that logic? TBH, I'd only suggest changes when they are really required (i.e scalability issues, maintenance issues, etc) but that has nothing to do with how long I've been working in a project. Requiring a year of knowledge about the domain is nonsense to me.