If you study web development now, will you need to change your code a lot in 10 years time?
Hi :)
I was just curious whether if you study web development now (and aim to master the core/essentials of HTML, CSS, JS, PHP, and MYSQL, namely) and create websites with those technologies combined, how much will you have to change re the code structure and design, in about a decade's time?
In other words, with programming being something that changes ever so often, I would like to invest my time in something that I am passionate about as well as something that won't be a great loss if I leave it off for some time.
For example, if you were to master the core principals of any one of those techs I mentioned up there within the next few months/years, what would it take to pick it up again if you left it off for some years and found that the language has changed plenty?
My father was once a PHP & MySQL expert around 14 years ago, and coming back to it now he finds the changes absolutely frustrating.
Write your answer…
You are in the wrong business if you don't want to tackle changes. The only constant in this industry is change.
I've been in the industry for 13 years. I used to be gung-ho about writing code, but the experiences taught me to focus more on tools and less on trivia. Once you get past a certain point, it becomes more about tools that you can leverage and tools that other people want you to use. All languages are just the same principles with different syntax styles. You learn just one, and the rest is easy-peasy. It doesn't matter which one or right one or wrong one. Just learn one and the rest follows without much effort. Whatever your employer/client wants you to use, you need to use it for them. So, in my case, I just have to learn ultrafast on the spot, use it to meet the requirements as fast as I can, and BAAM!!! There is a stash of money on the table for me to grab. That's how it's been for me.
That said, I would grab the following to get started if I were you:
- PHP/MySQL in WordPress context
- React/React Native
- Laravel (PHP)
- Django (Python)
- NodeJS (JavaScript)
Angular and Rails are on their way out. Therefore, I wouldn't even bother learning at this point.
Reply to this…
No one says a website, an app, a whatever needs to be on the bleeding edge framework.
I repeat - unless there is a need to, no one says you need to upgrade to anything new because it's new.
People still write in Fortran and Cobol. Companies still need those skillsets and companies still hire those people.
Your Javascript frameworks will come and go, every year. I "mastered" AngularJS just to have it replaced by Angular 2+. Does it piss me off that Google basically abandoned a framework and rewrote it from the ground up? Yep. Is it my job as a programmer to keep myself relevant and learn new things as they come along? If I want to pay the bills and have a good job - you bet.
And I still write in PHP - daily. I have old projects just like the next with clients that don't want to upgrade, yet. Is it hard to work on code I wrote 5 years ago? Sure, sometimes - but it pays the bills.
If you're worried about learning new things and having to learn new things - daily - I suggest a different trade. Perhaps masonry or plumbing - but even then - new techniques are learned all the time, too.
You would also possibly be like "Oh boy, what the hell is this? Oh wait I wrote that x years ago".
Reply to this…
After ten years a lot of things will change, if you write a code now you should do a refactoring because the syntax will change like Javascript changing ES06, 07 and 08. But you are growing together with the technology as well.
For example, an architect builds some home modern for days today, but after 10 years new ideas, new concepts appear. So, it occurs in all areas of jobs, software development is very frequency, but it doesn't the thing for demotivating and be frustrated, the changes are important, nowadays is very nice and motivated to write an app with React instead only HTML, CSS, JS.
Keep study is the best way! Don't give up!
The most important stuff to keep in mind is the concepts, patterns, software engineer, how I said, syntax change, technology as well, but yourself mindset about how to do something, it is not.
The most important stuff to keep in mind is the concepts, patterns, software engineering, how I said syntax change, technology changes as well, but yourself mindset about how to do something not will change, though.
Another point is if you are a backend and you want to be frontend, so, you have learned a punch news stuff.
I suggest focused in one are and to be specialist them. But if you want to change of area, keep it in your mind.
I have a lot of experience in Java Platform, I'm migrating to Javascript platform for work with a bit about backend but with focused in Front End with React, HTML, CSS. So, I have a punch thing to learn and to practice.
Reply to this…
I've been doing web stuff for about ~15 years, and I was in college for graphic design from 2006-2009, so that was exactly 10 years ago!
As for the web technology we were taught:
- Flash: non-viable by 2010, totally dead now
- HTML/CSS: very viable, have become easier to use since then
- WordPress: very viable, has now grown to power 1/3 of all websites on the internet
I've been building websites during this whole time, and consider myself luck with WordPress getting better over time, but some things, like Flash, which were huge weren't built well, and didn't survive.
There are tons of things you could go out and learn today that would be totally dead, like Flash, in 5 or 10 years, but I know for a fact that HTML, and CSS, and JavaScript will be used, so if you look at core 'foundational' technologies, those are more likely to be 'safe' things to invest time in learning and mastering.
It's also nice that PHP is still king :D Thought your dad might be frustrated, it is also nice that he can keep building on top of knowledge he already has!
Reply to this…
Well just one side-note about the ever changing technologies ... most of the now modern concepts are around 30+ years old. actor principles, futures / promises, functional programming is even older.
So I read the current academic papers plus some archives :) and switching a lot of languages over time (~ 1 per year) so I am not stuck with 1 set of problem solutions. It makes a lot of things easier if you at least heard them once.
The core problem will always remain the same information persistence, information transfer, information transformation/mutation.
but N != NP seems to stick at the moment and we have millions of solutions for the same problem.
You have got the right idea. I think that's a pretty clever method you have undertaken :)
Reply to this…
The Dev Community
(Free, friendly and inclusive)
A network for software developers to learn new things and get insight into the world of programming
