Sometimes, by trying to achieve more and be a perfectionist, you might actually end up shooting yourself in the foot.
Do you have a habit of over-engineer your projects?
For further actions, you may consider blocking this person and/or reporting abuse
Latest comments (25)
Oof, I'm in this title and I don't like it.
I for sure shoot too high on the first go. I need to be better about focusing small, getting something working then adding onto it later.
Yes 100% I love to over-engineer to learn stuff how it works 😅
Example: In my project, I don't need Memcached to cache the queries we can achieve it only with Redis, but I love to Install Memcached and compare which one is fast 🤣
PS: All happens in production servers 👀
There is a bright side to the coin as well 👍💯
I knew I was not the only one 😀😀
I have also learned the hard way that 'simple' is not 'easy' 😉
This is exactly 💯 how I feel! 😉
Very well put! 👍
I think everyone has. I definitely am guilty. I feel it was not until I decided to take a shot at doing my own startups full time, in 2009 did I realize how much time I was wasting on overengineering vs good enough and still be elegant.
I feel it takes skill to differentiate these two, which only comes by experience once you have gone through it, like you said 😉
For my job, no not really since there's always tight deadlines. But for my personal projects, definitely! It really takes some will power for me not to over spec applications I work on and to eventually decide when its 'complete'.
Set tight deadlines for your personal projects, as well 😀😀 But then again, you remember the only person responsible is you and you overengineer anyway 😀
For the most part, I only over-engineer the model layer of my applications, largely because I'm worried about future-proofing.
The reason I find myself more anxious about M than V and C, is that you can re-write an API/controllers, or re-develop your front-end at any time, but if you try to mess with the data models in a data-driven application in production you'll probably have a rather bad time.
I guess this comes from your personal experience in past, when not putting enough effort into the model layer caused you headaches later on!? 😉
I do that a lot, end up being confused with a lot of open ends , with no solution in hand . Gives a lot of learning but delays the task in hand .
Is the software into the hands of a lot of users, does the servicing side have multiple developers. If some of this is true, over engineering may be good. Otherwise is bad...