Home
> Uncategorized > The fallacy of the best tool / framework / library / practice / process
The fallacy of the best tool / framework / library / practice / process
“There is a point in your programming career, when you realise that there isn’t a best tool” – Via https://hackernoon.com/angular-vs-react-the-deal-breaker-7d76c04496bc – Couldn’t agree more.
There was a time when I was thinking
- NHibernate is the best ORM,
- Structure Map is the best IoC Container,
- Angular is the best JavaScript front-end framework,
- Rhino Mocks is the best mocking framework,
- SOAP and WS-* are the best answers to every distributed application problem,
- WPF is the best Rich Client Platform for windows,
- log4net is the best logging library
- DDD is the best design process
- Scrum was the best development & management process
But I have realized that no matter which framework / library / process / tool you choose, You will fall short of your (application’s) requirements.
The most sensible thing to do is,
- Fill the gaps of the frameworks the moment you see infrastructure concerns leaking into the application.
- No matter what you consider best today, you will find something better tomorrow. Write your application in a way that you can migrate to another one easily.
Categories: Uncategorized
Comments (0)
Trackbacks (0)
Leave a comment
Trackback