Re:On over-engineering; finding the right balance
by CharlieDigital on Monday September 16, 2024 @09:05AM
(#41555675)
It doesn't really matter if the domain is the same.
If you're building a regulated document management system for life sciences, the big picture aspects of what it has to do, how it has to scale, and how it has to be packaged (process, testing, documentation) doesn't have much variance.
> I'd counter that this is subjective based on experience.
> If I've built a similar system before, it's in the same domain, and the customer/userbase has a similar profile, then it makes sense that an engineer that's "been there, done that" can foresee the needs of the system, domain, and customer and can more accurately extrapolate how the system will need to evolve.
Don't just ignore the first part of their comment:
> > The problem is people stay at a job for 2 years.
You can't "been there, done that" if you haven't "been there" in the first place.