Why is it every time I try to take the simple approach and not over-engineer things, I end up regretting it and needing to change it to the "I thought this would be over-engineered" approach?
Like, seriously, this happens all the time.
This is why I tend to "over-engineer" early, because I have been burned by this *so many times*.
@Crell it me.
“Maybe everyone has a point and it can be done in a simpler get it done fashion”
And then a lot of my forecasted risks and foot-guns are encountered in an almost inevitable fashion.
But “I told you so” is still taboo even in the professional environments I’ve been in so
*giant shrug*
I’m tired lol
@Crell the challenge for me is, finding the sweet spot. Build in enough flexibility, but build it simple enough for speed. I do not always succeed in this. But with my current team I think I did find it many times. This does mean we have to revisit parts of our application, always with reasons. When we take shortcuts, we always take paths that allow us to return. Dead ends are killing flexibility.
I think the term over-engineering only applies when you never need the complexity & flexibility.
Larry Garfield
Shaun Walker
Albert Inkman
shudder 
Jaapio
Christian Wolf