Why I don't want to be a web front-end programmer

Job title does not represent skill set

As a front-end developer, do you think you don't need to know a lot of skills? But that may not be the case.

I did a quick search on the front-end development work in a hot work forum, and found that there was a recurring theme that would be what skills the intermediate/advanced front-end developers needed:

• (X) HTML (5), CSS, sass/scss,less.
• Backbone, Angular, Knockout.
• Responsive web design (e.g. Bootstrap knowledge, Foundation , etc.).
• Adobe Photoshop, Magento.
• Knowledge of source control and some form of client unit testing.

My views on these skills;

• Since the invention of HTML in 1990, its status has remained relatively constant. If you disagree, you might want to take a look at the source code of the first page. The ease of HTML became its biggest advantage, and became a barrier-free channel for novice developers.
• CSS is easy to learn, but it's hard to be very good at it. Thankfully, tools like sass/scss and less can help us. Web developers of any skill level and any degree of experience can learn to use these CSS preprocessor in 60 minutes or less. Simple and effective.
• If you are good at responsive web design, congratulations, you have mastered a valuable skill. If you're like me, and you're not good at designing front ends and frameworks-that's okay, Bootstrap and foundation can also help most developers hide the gap in this skill.
• Photoshop also has a dedicated field of world. Its absurd complexity matches exactly the set of features beyond its imagination. Even installing and running is a selling point.
• Source code control. All you need to know is: git push and Git pull.

Of course there are a lot of jokes and opinions. I would like to say that a full stack developer can be active in all of these areas with minimal exposure and experience. These are not professional skills. This conclusion I think also applies to JavaScript developers. For example, after 3 months of angularjs contact, you will almost be able to know how it works, how to use it, when to use it, and most importantly, when not to use it.

I don't want to be a front-end developer because I have a wider range of skills and I don't want to sell myself at a low price.

From a consulting perspective

Describing yourself as a front-end developer can be meaningful in the short term. Overall, there is still a big demand for developers today. There is even a noticeable shortage of technicians in the UK, so if you show up as an expert or professional, it might help you get better pay.

Rather than being a front-end developer, I found that front-end developers with a significant amount of full stack experience were more gold-content. So, I suggest you try to delve deeper into your skills while choosing a potential employer.

Development of front-end development too fast

To be more dramatic, front-end development has a new dazzling JavaScript framework or a "must-have" tool available every day. Web page as a platform is developing more and more good. Yesterday, we used PHP, ASP,. NET, MVC, Angularjs/knockoutjs/whateverjs. Tomorrow, Reactjs may become the framework's first choice (or Aurelia will be a strong competitor).

In addition, there are countless web development tools: Visual Studio, Code, Sublime, Webstorm, Dreamweaver (joking, who would use this thing?!) ), Eclipse, Netbeans, notepad++, VIM, EMACS ... Wait, countless, endless.

The final result is that I spent hundreds of hours to learn the FRAMEWORKX (and also spent a lot of tuition), just because it is considered dead can only be discarded. (Do you remember Silverlight?) As well as Angularjs 1.x). This gives me the feeling that even though I did my best and invested countless time and energy, my skill level was actually reduced.

I don't want to be a front-end developer because I can't (and won't) be struggling to keep up with trends.

Front-end developers may not be designers

I found that in general, technical staff can be divided into the following two categories (not all cases, of course):

1. Have logical thinkers and like to write code
2. Know how to make things more beautiful.

Often, many programmers do not have excellent design capabilities and vice versa.

Personally, I should count as a programmer. When it comes to design, I use frameworks like Bootstrap and foundation, but I'm not really good at design.

The idea is that front-end developers should both encode and be good at design (see the requirements for skills in a job advertisement, especially when it comes to Adobe Photoshop knowledge). Employers hire front-end developers to write code and design beautiful websites. I think this is wrong, it should be two separate roles.

I don't want to be a front-end developer because I'm not a particularly powerful designer. Employers have unrealistic expectations for so-called front-end developers.

Front-end developers make less money

It's true.

Developer vs Front-end developer

A difference of 10,000 pounds. This is quite a big gap. And that's just one example.

I don't want to be a Web front-end developer because I want to do my best to make money.

Summarize

The reason why I don't want to be a front-end developer is because I don't want to sell myself at a low price and try my best to make money, not to keep up with the trend of the industry.

Either agree or disagree with my point of view ... Please leave a comment.

This paper draws on: Http://www.codeceo.com/article/why-not-front-end-web-developer.html#respond

Link: http://www.codeceo.com/article/why-not-front-end-web-developer.html
Why I don ' t want to be a front-end Web developer

Why I don't want to be a web front-end programmer