Yep! I did check out your article last week and dropped a like 😊 it was great! This is a common problem for many organizations that are rigorous enough in their code reviews and don't settle for the first thing that works and also need to ship software in a reasonable time.
A great mental model Akos! It can help decide between over-engineering and under-engineering, though I won't call your second solution over-engineering :) It was a perfectly reasonable thing to do as far as I can see. Sure it took more time but the wizard seems like a pretty basic building block that can come in handy (depending on the system context, of course).
Most of the time I've seen the decision between making something flexible enough for the future boils down to how much time you have. It's always a trade-off.
Thanks, Saurabh! Looking back at this (and after using the component), I think you're right. It might not have been overengineering, but time will tell if we need the flexibility we spent the extra time on.
We definitely had the time for this, so I'd say it was well spent!
Looks like we were thinking about this topic at the same time, the same week I released this article: https://www.leadership-letters.com/p/the-sweet-spot-between-too-much-and, consider checking it out!
Loved your post, btw.
Yep! I did check out your article last week and dropped a like 😊 it was great! This is a common problem for many organizations that are rigorous enough in their code reviews and don't settle for the first thing that works and also need to ship software in a reasonable time.
A great mental model Akos! It can help decide between over-engineering and under-engineering, though I won't call your second solution over-engineering :) It was a perfectly reasonable thing to do as far as I can see. Sure it took more time but the wizard seems like a pretty basic building block that can come in handy (depending on the system context, of course).
Most of the time I've seen the decision between making something flexible enough for the future boils down to how much time you have. It's always a trade-off.
Also, thanks for the mention!
Thanks, Saurabh! Looking back at this (and after using the component), I think you're right. It might not have been overengineering, but time will tell if we need the flexibility we spent the extra time on.
We definitely had the time for this, so I'd say it was well spent!