How will a web developers job change over the next five years?
First off, If you’re a dev, a programmer, employed or freelance, or someone who generally doesn’t get to see the ‘light of day’ (or is a shut-in), you’re welcome… We are out and about today!! Also, if you were in the mood for Dim Sum and talked yourself out of it…sorry.
Today we’re contemplating how the web-stack will change over the next 5 years. What devs and programmers should expect in terms of changes to their jobs, and delicious Dim Sum…sorry, I’m really hungry now…
Web Frameworks: Re: front-end frameworks, “…that’s more difficult to predict because web frameworks are more volatile. …My best guess -barring any new framework coming into the game/ some new disruptive technology- …I think you’re going to see React and Vue are going to be the dominant players, followed by Angular (but you can’t lose with any of them). This is a prime exmaple of why I always tell people to learn your fundamentals: frameworks change, libraries change, but the fundamentals don’t change.”
Complexities of Web Development: “Another thing you’re going to see …is the move more and more to the server. You’re seeing more and more sophisticated server tools that are pretty mind-blowing (from an old nerd’s prospective), [for example] virtualized database management: …instead of having to worry about charting your database and database optimizations, the advanced hosting companies -they provide that for you. They take care of that; scaling, auto-backups, all this kind of stuff that normally you would have to do yourself -you’d have to work it into the development cycle- not anymore! And you’re going to see more and more of this offloading of complexity in terms of application design and architecture…onto sophisticated hosting solutions. …So that’s another you’re going to see, that obfuscation of the complexity -and that’s a good thing.”
Closing Thoughts: “I think it’s going to shift from day to day ‘nuts and bolts’ type of coding, and going to go more towards architectural. Now what people use is a content management system; the most popular being WordPress. Which has given rise to the ‘WordPress Professional’, …[they] know how to install, configure WordPress, know the environment -the ecosystem around WordPress: know what the good themes are, the bad themes, the good plugins, the bad plugins, how to install and debug, how to lockdown and secure WordPress -there’s a whole skill set. Now you don’t necessarily need to be a coder, but having coding skills does help…and you can’t discount these type of skills… It’s very little about code but you gotta really know your stuff. …And this is a trend that been going on for awhile; this move away from nuts and bolts’ coding, to being someone who leverages different libraries and frameworks and understands how to use them/when to use them, and what circumstances to use them.”
So there you have it. The VLOG really goes into a much deeper and detailed dive, you should check it out. Also, speaking of fundamentals -SHAMELESSS PROMO- check out our links (below) to various courses we offer, particularly web development. It’s super effective. As for your job; it doesn’t mean coding is going to go away, just that there will be a shift. Again, know your fundamentals and you can’t go wrong. “A little less code, a little more architecture…and Dim Sum…always leave room for Dim Sum…so hungry!!! -Enjoy!
Young developers are hyper concerned about learning the newest programming languages and frameworks only … but the most popular languages today are 20+ years old!
Alright yung’uns, gather ’round the fire… I know, everyone has indoor heating and there’s no need for fires anymore but this is gonna help with the over all ‘flavor’ for this blog…
Many you young devs are focusing on the shiniest, newest programming languages and frameworks, and while I salute your moxi, your gusto, heck; even your gumption… I’m here to tell ya, that there’s a difference between new and popular. I know when you’re listening to your CardiB’s and your Lizzo’s, you may not see a distinction but in the programming world, lemme tell ya, bucko, there is definitely a difference…
“…For a long, long time -like 10/20 years- especially when it came to the web stack, the technology changed so often…websites and web apps…it has changed so radically.” Now, as I understand with you yung’uns, 10 or 20 years ago might as well be 100 years ago but, “…when it comes to the actual programming languages (the popular ones that are used to date), …they are pretty much entrenched. I think you’re not going to see a big move away from the major players over the next long time. Why? There’s just no need to. Now in the past you would create a programming language because there was a particular need that was very important, but it was not addressed by current languages.”
Also, over the years as computers have become markedly faster (CPUs and memory both have become faster and cheaper), the need for highly optimized programming languages have become arguably less and less important, because a human eyeball won’t necessarily notice execution speed on most modern computers because they process that information much more efficiently than a computer from 10 or 20 years ago.
The VLOG goes into waayyy more detail, we’re talking SQLs, Bootstrap, even RUBY (and only an inkling of an insult too). But, “when it comes to the major programming [and coding] languages of today, not much has changed in many years. …On the advanced stuff yeah, but in terms of language, not much has changed. …When you’re looking at the languages, at the technology, it’s not as critical to have stuff that was created in the last two minutes. The big ones [programming languages] they’re not going anywhere because they’re good, they’re good at what they do and the problems they may have can be addressed with some small updates, and they just keep getting more performance with the updates…”. Now, it’s almost 4pm so you better git gone and think about what I’ve said while I get ready to sit down to my dinner… -Enjoy!
Before we get started, this is the article we are …framing?… our references around, and full transparency: we use Vue.js (henceforth called ‘Vue’) for our needs with StudioWeb. Here we go:
Angular: Developed by Google in 2010 (making it easily the most mature), this behemoth (500kb) is more in the realm of big projects with ‘advanced developers’. “Angular is basically positioned for larger projects. There’s a much steeper learning curve with Angular, …it’s a very powerful framework.” Another feature of Angular is that, “it separates out the logic from the application/the behavior of an element and the element itself is separate.” So while you would be gaining flexibility with Angular, you might be sacrificing a certain amount of simplicity that you would get with the other frameworks..
React: Developed by Facebook in 2013 this slimmer framework (100kb), offer way more simplicity than Angular (at the cost of some flexibility) and has an equal market share with Angular. This Framework tends to be adopted by more flexible small-medium sized companies.
Vue: Open source-developed, holding approximately 20% of the market share (and growing), weighing in at about 80kb (soaking wet), we have the staple of most start-up/small businesses: Vue. Boasting an easy, practically non-existent learning curve, Vue is the compromise between flexibility and simplicity.
So what’s the best option for you? Well, all these frameworks have their strengths and weaknesses, and they’re all used by many companies, businesses, and corporations, so they’re not going to vanish anytime soon… I guess it all comes down to what you want to do… Want to work for a big corporation? Angular. Spunky start-up with a can do attitude? Probably Vue. We really want to stress that one framework is not better than the other, they just offer different options, benefits, and drawbacks.
Check out the VLOG for a deeper dive into the pros/cons and features of all three frameworks, and remember, “…your choice of framework -of any technology- largely depends on the type of work you wanna do, the job market, a personal choice… there’s no language that is ultimately best, …no framework that is ultimately worse; it really depends on what you want to do.” -Enjoy!
The face of native mobile development is changing indeed … and fast!
Okay, so a couple of months ago we talked about SWIFT and how we felt it was going to “lose market share” because frameworks like FLUTTER, React, etc. were going to put more pressure on native development (like SWIFT) with their sheer versatility… it did not go over well with the SWIFT OG’s… but if we could just have a moment of your time, I’m sure we can make things worse… 🙂
“Flutter allows you to write cross-platform mobile applications (iOS & Android) using one language: DART, one framework: FLUTTER framework, and it’s created by google; and what interesting about FLUTTER -it compiles down to native so you don’t have a ‘performance hit'”.
Now, traditionally when you use frameworks, you don’t have access to certain things that you would with native but the major concern when creating FLUTTER was to give developers the ability to customize and have access to everything…in other words: flexibility. Writing and maintaining one code base which is responsive, compiles down to native is gives you a lot of control over UX and UI is pretty attractive and while no framework is perfect, it’s pretty close…
In the video we go into more detail and hit on a few interesting points. Check it out, it’s worth a look. Enjoy!