r/javascript • u/kamranahmed_se • Mar 26 '18
Modern Frontend Developer in 2018
https://medium.com/tajawal-engineering/modern-frontend-developer-in-2018-4c2072fa2b9c83
u/mariusg Mar 26 '18
"Typescript can be mastered in a few hours"
I call bullshit on this. TS supports generics and weak types (just writing 2 features for example). Someone who never used those in a different language will not be able to grok the concept in a few hours.
29
49
u/nwsm Mar 26 '18
Nothing can be mastered in a few hours, except maybe tic tac toe
9
u/senocular Mar 26 '18
And yet I still never win :(
14
Mar 27 '18
TBF if you are playing against someone else who has mastered it, neither one of you will ever win.
12
Mar 26 '18
I've used statically typed languages before. Used typescript for a while, read a few books on the subject, how to pull types in via NPM and other admin type work, even spoke to some guys at microsoft regarding details of their choice of keywords when dealing with inheritance (compiler should throw a warning instead of mislead developers). Yet I still can't get my head around creating definition files for existing JS projects!! The &$* do you even put them lmao. So I'm with you on this one.
3
Mar 26 '18
Yeah nothing in web development can be mastered in a few hours. Maybe you can get the hang of it but you'll still get caught up on trickier stuff and will need to google constantly.
-1
u/turkish_gold Mar 26 '18
I agree, but it's problematic to always separate out developers without any experience from the rest of the herd. Most developers ought to have more than 5 years experience, and thus have been at least once exposed to a static and dynamic typed language. But if your only experience is bootcamp, you will struggle here... And struggle in a lot of other places people simply take things for granted.
I don't say this to look down on people, but I remember in my first 5 years I was full of energy but utterly ignorant to many things.
1
u/thilehoffer Mar 26 '18
I don't say this to look down on people, but I remember in my first 5 years I was full of energy but utterly ignorant to many things.
I agree completely. You don't even know what you don't know in the beginning. I have been working as a developer professionally since 2000. I am still getting better.
5
3
u/maci01 Mar 26 '18
Cool info graphic. I enjoyed reading it and figuring out where I'm at.
I wouldn't want your English mistakes to have others dismiss the content. Just a couple I noticed:
It's "many different hats". Also under the frameworks, you wrote "much more simpler/easier". It should be "much easier" . I'm sure there are more but just a few. Sorry that this comes off as a grammar nazi.
1
18
u/thilehoffer Mar 26 '18
Quick question about package managers. Does it make sense to use more than a few packages and always be keeping them up to date? Why not just add a package to your site and leave it? Wouldn’t updating multiple packages to a new version increase your risk of issues / bugs with each deployment?
11
u/vinnl Mar 26 '18
There's always potential security issues and bugs in the versions you're already using, which means it's good for you to update. Furthermore, there's going to be new features that, if not you yourself, other packages you are or will be using might want to use. For example, if you're still on React 0.13, you won't be able to introduce react-redux to your project without also upgrading React, which makes the cost of introducing that a lot larger.
6
u/thilehoffer Mar 26 '18
Sure, but do you need to always be current? Wouldn’t be better to update all your packages once per year. Then do a build with no other changes, QA that release and deploy? Seems like that would be much less risk, and a lot easier then always updating.
18
u/vinnl Mar 26 '18
That's a philosophy that some people (sometimes implicitly) entertain. However, the trend appears to be to move to a "release early, release often" strategy (see: continuous integration/delivery and devops). The idea is that when you do a lot of small changes continuously, you will run into potential problems early and are able to fix them while they are still small. Updates can and do have side effects that may be difficult to track down, and if you batch a lot of them together, it can be far more work to find the source of problems. Also, it's going to be more work to do in a single go, which makes you more prone to postponing.
(Obviously you will always have to keep an eye on pressing security concerns, and being able to fix them quickly is an advantage as well.)
To provide a real-world example from my work: dependencies.io regularly and automatically clones my repository, checks which dependencies are out-of-date, and submits separate pull requests for every dependency that needs updating (usually no more than three, and most of the times fewer). Each of those pull requests than automatically runs a CI pipeline that builds the code with the new dependencies, runs the tests, deploys it to a separate environment, and starts a browser that performs a few actions on that environment as if a user were controlling it.
Keeping the project up-to-date is then usually a simple click to accept the pull request, sometimes after a manual check of the environment if I suspect the update to have some risk of breaking. And rarely, but still a few times a year, something will have broken that I can then address on short notice, and it's still relatively clear what will then have broken it.
As you can see, the risk of something breaking and making it into the mainline code is relatively low, and it's still low effort to keep things up-to-date. It's pretty sweet. (The project is open source, so if you want to see this in action, see this pull request from last week.)
That said: it's dependency management is a notoriously difficult problem and there are different schools of thought, so unfortunately there's no quick and definite answer to your quick question :)
1
u/BirdToTheWise Mar 26 '18
Is there any alternative services to dependencies.io?
2
u/variegatedEncyclopod Mar 27 '18
Greenkeeper is the one I use (https://greenkeeper.io/). Incredibly useful to get PRs automatically to update dependencies. +1 for a tool like this.
0
u/vinnl Mar 27 '18
There are quite a few - Greenkeeper, Gemnasium are two I can think of off the top of my head. As GitHub, GitLab and the likes integrate this functionality, some of them are bound to disappear though.
1
u/plafoucr Mar 28 '18
Gemnasium has been acquired by gitlab, and the later is now proposing a lot of similar features with the security products.
8
u/firelitother Mar 26 '18
Think of it like version control.
Do you just do one giant commit per feature? Or do you do many small commits which cumulatively result in the feature you want?
2
1
u/planetary_pelt Mar 26 '18
It's just that it can become harder to update the larger the gulf become between you and latest. And you need to update eventually, else you're on unsupported software. So regular updates just become a way to pay off technical debt.
1
u/thilehoffer Mar 26 '18
es, QA that release and deploy? Seems like that would be much less risk, and a lot easier then always updating.
True. There probably is no correct path for every scenario. Some site probably put a premium on staying current while others put a premium on stability.
1
u/worldDev Mar 27 '18
I would say the best is to keep your current version up to date, and plan full version releases when you have the time for whatever migration. So far with angular since v2, it's not taken me more than 10 minutes to update a current version, and maybe 30m-1hr to upgrade to the next version.
0
Mar 26 '18
[deleted]
5
u/thilehoffer Mar 26 '18
Management does not care what tech we use. They just want it too work.
0
Mar 26 '18
[deleted]
5
u/thilehoffer Mar 26 '18
Management does not know what client side framework is used. Newer isn’t always better. Some new SPA applications remind of Flash applications back in the day.
0
Mar 26 '18
[deleted]
3
u/thilehoffer Mar 26 '18
Lol. Please, I reached the top already, I am already at architect level and I make bank. Of course I keep learning. I switched from TFS to GIT and switched to TypeScript. But when you are a full stack coder and client side is only 20% of your work, you have to reduce complexity and keep it simple. Can’t jump on every hot new framework when your application has to last forever. Do you know how many front end frameworks have come and gone since I started coding...
2
u/rorrr Mar 27 '18
I agree. There's also an issue of finding developers who understand your stack. The more shit you pile on, the harder it is to find a developer. The older I get, the simpler I try to code and architect.
→ More replies (0)0
2
u/estacks Mar 26 '18
Management that pushes for rapid adoption over stability is doomed to fail. I think it would take brain damage to push "learning new skills" over using stable, proven tech, especially when it's as prolific as PHP.
0
Mar 26 '18
[deleted]
-4
u/estacks Mar 26 '18
You're ridiculously out of touch, it's amazing that this company would hire you at all, especially as you feel fit to shit talk them. PHP is used by 83% of websites with a known backend, jQuery is used by 96% of all sites that use a JS framework. Get perspective.
2
u/coyote_of_the_month Mar 26 '18
I think those numbers are probably a little skewed by widespread adoption of WordPress etc. Not saying you're wrong, but those numbers probably aren't the best indication of where the jobs are today.
1
u/thilehoffer Mar 26 '18
It varies by location but I think PHP is the most in demand web dev skill. Front end only frameworks are good, but Java, PHP and ASP.Net are the most popular job skills I would think.
1
u/coyote_of_the_month Mar 26 '18
Around here, there are plenty of PHP jobs but also a ton of Java and Python. There are also a handful of Go and Node jobs.
Ultimately though, there are more frontend jobs than backend.
2
u/Sito187 Mar 26 '18
Sounds like jQuery isn’t really optional then, correct?
2
u/Kumagor0 Mar 28 '18
As someone who started working as a fullstack webdev 2,5 years ago and never used jQuery single time, I'd say the only reason you might need jQuery in 2018 is if you are previous generation developer who has been using jQuery for years when it was best (and only) option available, and too lazy to learn new frameworks that make development and maintenance so much easier and faster. Since you are asking this question, it's probably not your case, so you should of course be able to recognize jQuery when you see it and look up something in the docs, but other than that, don't bother.
That's, of course, just my opinion from personal experience.
1
u/Sito187 Mar 28 '18
Thanks for your input. I’ve been working on personal projects using react and react native and see jQuery come up often for job requirements. I don’t feel like learning jQuery not out of laziness but because I rather learn other things.
0
u/vinnl Mar 26 '18
We've automated most of the maintenance, that allows you to move quickly with the ecosystem :)
1
u/thilehoffer Mar 26 '18
I am a .net full stack dev. Our main application was started 15 years ago. I don’t move quickly on the front end. Too much change. We have moved to GIT for source control and adopted TypeScript. But for the web we use KendoUI, JQuery and Twitter Bootstrap, no other libraries. Our team of six full stack devs evaluated Angular 2 but hated the complexity. We loved TypeScript though. It’s good for me to learn what the web developers are up to. Thanks for the information. Nice article too. It’s a balancing act trying to keep up with the ecosystem especially for full stack devs who may only spend 20% of their time on client side development. We also have to keep updating legacy code in web forms, server side MVC and webAPI too...
0
u/uptownjimmy Mar 26 '18
I cut my teeth on my boss' custom Web Forms + jQuery preferences: he thinks that stuff is as good as it will ever get. I was about 1.5 years into my career when I started to suspect that there might be better ways. jQuery gets pretty nasty when the business logic is sufficiently complex. That's the working definition of spaghetti code, if you ask me.
Then 2 years ago we all sub-contracted out to a firm using .NET MVC, Web API, and Angular, and it has been (mostly) amazing. The Angular stuff, in particular, just felt so much better, so much cleaner, so much easier to reason about. I hope to never go back to day-to-day jQuery again...
-1
u/thilehoffer Mar 26 '18
For a new project, webApi + Angular would be fine. But we have to maintain the old stuff too...
1
Mar 27 '18
Of course it would but there's reasons the packages are updated. Bugs are found, vulnerabilities are reported, optimizations to the code are made.
9
Mar 26 '18
CSS framework - pick bootstrap
Fuckin' lol
1
u/wizardwusa Mar 27 '18
What's a better alternative?
0
Mar 27 '18
Not saying there is one, just that it's ironically funny that the flowchart showing progress / decisions is just like no really though pick this one
I've used materialize before and I like it but it's not on the same level
5
Mar 26 '18
This is awesome thanks a lot. Very helpful in getting the big picture of the innumerable frameworks/things to learn out there. It would be amazing to have the same direction and guidance for backend development. Thanks again!
4
u/JabawaJackson Mar 26 '18
As a semi-beginner, thank you! I've been stuck at which libraries I should be prioritizing and haven't even thought ahead of that. Lots of new stuff for me to try.
2
u/CorduroyJonez Mar 27 '18
I wish I had seen this a year ago. I sat down a couple weeks ago to write a broad roadmap/guide similar to this for a few friends, and this is nearly identical to the order I wish I would have learned front end
4
u/golangJord Mar 26 '18
Too many frameworks not enough actual work!
5
Mar 26 '18
There are only three that matter: http://www.npmtrends.com/angular-vs-react-vs-vue-vs-@angular/core-vs-polymer-cli-vs-svelte-vs-lit-html-vs-ember-source
And of those three, two are essentially the same internally. The rest either fulfil a niche or are derivatives, often with shared semantics or even the ability to swap components. Isn't this what you want when you say "too much"? Otherwise i don't understand the sentiment.
4
u/golangJord Mar 26 '18 edited Mar 26 '18
Too many unneccessary derivatives. (Although the same could be said for programming languages)
3
3
Mar 26 '18
I would add Selenium to the list. It is useful for unit- and integrationtests of the UI aswell.
E.g.: Imagine an input form that should convert all text inputs to upper-case. It has an attached event handler: cvtToLower(input:string).
Test the event handler the traditional way.
Use Selenium to make sure the converted test actually ends up in the correct input.
Thats basically an integration test of the markup and UI code (i.e. are the ids set correctly?). Integrating Selenium in a unittest runner(like mocha), still allows mocking and makes the test run fast (compared to the typical end-to-end use case of selenium). Granted, this is a very basic example and not worth the effort, but having perfectly tested code and still ending up fixing a malfunctioning UI is something people are spending way too much time on.
2
2
Mar 26 '18
Great if real-time (think websockets/socket.io) and mobile development (react-native/ionic) were included. Seems it's a tad behind already ;)
2
u/itsthenewdan Mar 26 '18
I started using Cypress lately for end-to-end tests, and while I haven't mastered it yet, I can say that it feels like a huge improvement over Protractor. Test code is far simpler, and you get to generally avoid arbitrary timeouts while waiting for requests or DOM elements to load. The test code reads more like a concise description of what you're exercising. I'll be interested to see if it gains popularity.
1
u/xxSINxx Mar 26 '18
No database stuff?
3
u/wh33t Mar 27 '18
"Front End"
1
u/xxSINxx Mar 27 '18
I see, that makes sense I guess. Are there really front end developers that never touch a database though?
2
u/wh33t Mar 27 '18
Well, Front End development never includes database work as there is no client side databases, however its possible that some front end devs can also work on the back end. I could see wordpress devs being like this.
Also, people who know javascript are finding they can take their skills to the backend now with node.js
1
1
u/UnrealNL Mar 26 '18
Thank you so much for this, I saved this and will come handy in the near future!
1
1
0
u/mcmouse2k Mar 26 '18
Bummer that Ember isn't mentioned anywhere - it's a fantastic way to get started with web-apps and covers the majority of the "focus areas" with minimal setup and configuration.
As an alternative to most front-end boilerplates and interminable Webpack configuration work, it's really nice. Plenty of large tech company employers as well.
I'm not saying it's perfect, or that it doesn't have warts, or that it's the most popular framework - I just think it's a great resource for web beginners.
-3
u/jaman4dbz Mar 26 '18
I disagree with a lot of choices in the chart, including even mentioning Angular... Or using_bem__with_css shudder
However the order and flow of the chart is great, and the graphics are clear and their is enough rationalization to appease any beginner, so thank you for this great resource! :)
0
Mar 26 '18
[deleted]
1
Mar 27 '18 edited Mar 27 '18
Me right now. This is the reason why I don't know any of this shit. Our company prefers ASP.NET C#, and Native JS. We use libraries/frameworks to an absolute minimum, only when absolutely necessary. Currently we use Vue to create multiple UI modules, but then integrated it on a vanilla JS project.
And I'm not motivated enough to learn this on my free time kek
-2
u/jWalwyn Mar 27 '18
Don't hope for any decent career progression related to programming then
3
Mar 27 '18 edited Mar 27 '18
Pretty subjective, since it wouldn't be that difficult to adapt to various technologies when needed. News flash, you don't need to use all your time just to have a "decent" career progression trying to study endless number of technologies. Especially in
programmingweb development, where a lot of various frameworks/libraries/tools change quite fast. Should I study Framework X, Y and Z right now when I wouldn't need it at work? Sure, I can study it, then something else comes along and it gets obsolete before I have the chance to use it professionally and in my career. Sure.I'm not a freelancer such that I can use all the extravagant technologies that I want to use. No matter how I want to use toolX, if management says I can only use toolY then I have no choice.
1
u/jWalwyn Mar 27 '18
I just meant in terms of improving your companies tech. Often companies will stay with an old stack, but its not often hard to explain the benefits of newer tool for a project that you yourself have found - its, in my opinion, the way to lead/pm/architecture roles
0
26
u/kamranahmed_se Mar 26 '18
Hey Guys,
You might have seen this "developer-roadmap" shared in this subreddit at the beginning of this year. There was still a lot of room for improvement, so I started updating it this weekend. I am still working on improving the Backend and DevOps ones but the frontend one is ready. To give you an idea about the updates, I have written a detailed article on medium. Here is the summary of what has been updated
Updated some suggestions here and there
Added details on how to follow – more beginner friendly
Added tips to practice and get better
Removed the "obsolete" parts
Have a look at the article on medium if it may help anyone :)
Thanks.