{"id":12188,"date":"2016-04-29T12:11:26","date_gmt":"2016-04-29T09:11:26","guid":{"rendered":"https:\/\/www.webcodegeeks.com\/?p=12188"},"modified":"2016-04-28T09:52:51","modified_gmt":"2016-04-28T06:52:51","slug":"updating-outdated-knowledge-moving-new-web-stack","status":"publish","type":"post","link":"https:\/\/www.webcodegeeks.com\/web-development\/updating-outdated-knowledge-moving-new-web-stack\/","title":{"rendered":"Updating your outdated knowledge by moving to a new web stack"},"content":{"rendered":"

After a few years working with the same framework and language, you have stopped learning new ones. Life got in the way of learning and you let the habit die down, since the knowledge you have is enough to do your job well.<\/p>\n

But now, you\u2019re finding yourself worried about your skills and job prospects: your web stack is outdated and the market has moved on to something else. Change for the sake of change is absurd, but you\u2019ve reached the point where putting some effort into it is warranted if you don\u2019t want to stay stuck maintaining legacy ASP.NET WebForms or ColdFusion applications forever.<\/p>\n

Fortunately, if you need to update your skills, you can pick up things where you left them and learn a new stack in a few months to a year depending on the free time you have<\/a>. Many tools and frameworks have risen and fallen since you stopped learned, but the same patterns and practices are used. The tools are better, but nobody will mind if you missed a few frameworks along the way.<\/p>\n

It\u2019s easy to get overwhelmed by all the choices available, but you don\u2019t need to spend ages evaluating which web stack you\u2019ll pick up: all the popular ones are worth learning. If you don\u2019t have a preference, choose the one that\u2019s most popular for the kind of job you want to do. For example, startups are more likely to use NodeJS and Ruby on Rails on the backend, but in big businesses ASP.NET MVC or Java is common.<\/p>\n

When you start working on a new project, it\u2019s doubtful that the stack is going to be identical, so you don\u2019t worry about the details:. The point is to learn what a modern stack look like and not a specific set of tools: if your knowledge of JavaScript, HTML and CSS is solid, you won\u2019t have trouble adapting.<\/p>\n

I\u2019ve written a lot about learning as a software developer<\/a>, but if you already know what\u2019s your specialty and you only want to update your skills, you can follow this quick and dirty plan:<\/p>\n