Hi Ben. Another cool discussion about a real-world topic. I planned to write a post about over-engineering for a few weeks now.
This discussion reminded me to get back to my draft and finish it.
I published it a few minutes ago. You can find it here:
But to answer your question, I think over-engineering is all about adding additional complexity to code that could be much simpler.
I think most (experienced) developers (including myself) have been guilty of over-engineering. Remember the day when you learned a framework/design pattern/tool that you thought is really cool. That is the same day when you excessively start to look for places where you can use it.
It happened. And it will happen again. We will just have to find a way to deal with it in a solution-oriented way.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Hi Ben. Another cool discussion about a real-world topic. I planned to write a post about over-engineering for a few weeks now.
This discussion reminded me to get back to my draft and finish it.
I published it a few minutes ago. You can find it here:
Over-engineering is real
Lars Richter ・ Jul 15 ・ 4 min read
But to answer your question, I think over-engineering is all about adding additional complexity to code that could be much simpler.
I think most (experienced) developers (including myself) have been guilty of over-engineering. Remember the day when you learned a framework/design pattern/tool that you thought is really cool. That is the same day when you excessively start to look for places where you can use it.
It happened. And it will happen again. We will just have to find a way to deal with it in a solution-oriented way.