I'm Drew Town a web developer and systems engineer in Colorado. Always learning, traveling and exploring. Sharing updates, trials and tribulations in tech and life.
Framework traveling is another form of procrastination. You get stuck in a learning loop, chasing the new shiny, like you said.
It's one thing if you actually can't get something done with your current toolset. It's another if you see a 5% improvement in a new framework and need to start from 0 and tackle the easy parts of your project...again.
Agree 100% with you. What frustrates me even more is when we choose a framework because it is popular for a, b, c reasons but we are blind when choosing the right framework for the right job, used by the right people (people who are experienced enough to work on it AND/OR can adapt quickly)
Framework traveling is another form of procrastination. You get stuck in a learning loop, chasing the new shiny, like you said.
It's one thing if you actually can't get something done with your current toolset. It's another if you see a 5% improvement in a new framework and need to start from 0 and tackle the easy parts of your project...again.
Agree 100% with you. What frustrates me even more is when we choose a framework because it is popular for a, b, c reasons but we are blind when choosing the right framework for the right job, used by the right people (people who are experienced enough to work on it AND/OR can adapt quickly)
Exactly!
The thing is do you really need the (maybe) 5%?
Maybe getting things done is more important then looping through frameworks!
Couldn't have said it better!