> Mid-level engineers who recently discovered software design patterns tend to fall into this category. A mid-level engineer who only just discovered Design Patterns. So, a first or second year university student is a mid level engineer?
In theory yes, in practice no. Generally speaking university students learn, prove-knowledge-of, then move on to the next course/subject. University projects also tend to be much smaller in scope than any sort of realistic product that a company can be built on. Therefore, the level of technical debt created by under-engineering and the codebase comprehension learning-curve created by over-engineering is not somethin…
Types of Engineers
81–82 of 82 posts
Re: Types of Engineers
#82Earlier quoted context omitted.
Author here. Your point is valid. I do try to make this clear in this portion: > However, an over-engineer can sometimes perform like an under-engineer or an engineer. Underperformance and overperformance could be influenced by a number of factors including work environment, context, intellectual horsepower, and even personal life. I personally continue to write under-engineered and over-engineered code because there…
I encourage you to keep writing, but it seems you need more research into developer patterns if you want to contribute to an already highly discussed topic. For instance, last month this article[1] gave some seriously good insights to developer checkin frequency based on hard data. It provides a lot more value than the anecdotal, muddy definitions of over/under/engineer. [1] - https://blog.gitprime.com/check-in-frequ…