Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
It's a 'cognitive bias' to base some decisions on too much information.
gustash24638yYup. I have an almost finished project that I'm gonna redo in React Native now. Lots of work to redo, but it's better for maintainability and code reuse
vultuk418yYes! Which is why my current project already has version 2 and version 3 branches in various states of refactor/reframeworking despite the fact that version 1 isn't complete yet!
Always. But I think we're the cause of this as much as the victims. If you scope something requiring anything more than 3 months, it's just about guaranteed there will be new versions of your components and you'll have read about new ways you could develop some part or other.
A fundamental architectural mistake is a different thing. If it gets to the point where you simply cannot fulfil your obligations using what you have, you need to make changes or alter deliverables. Otherwise, see it through and consider rework for later versions or other projects completely.
If you spend that long questioning yourself on decisions during a project, you didn't spend long enough planning it.
I think it's often not about how long you have spend thinking about it. At some point you have to make a decision and usually you don't know every detail about it at this point.
e.q frameworks: Even if you tried a few small examples in that framework you most probably just scratched the surface. So when the project matures and gets bigger you realize that your framework has also some disadvantages/ "not so nice things". At this point now it's pretty easy to look at other frameworks and questioning your own decision (not knowing that other frameworks have disadvantages too). Yeah it's always the grass that's greener on the other side..