Hi Mike,
At 04:05 04-03-2016, Jules Mike Giovanni wrote:
>In my opinion, very soon, there will be no such thing as a "front-end
>developer". This is an endangered title that is held by people who work
>in specific web technologies to create user interfaces (something the
>user can see and interact with on a website) solely. Through, possibly,
>bad understanding, people with that title are expected to not only work
>towards user interfaces but user experiences. Sometimes they are
>expected to work in graphic designing and other times, to have an
>above-beginner understanding of server-side technologies. Is this
>expansion in duty good or bad? Does it reflect, for instance, on the
>salary? Is the above expectation well communicated to them on the job's
>description?
From what I read [1] the full-stack programmer was meant to be a
generalist. An incorrect understanding happens when the person who
hires the programmer/developer does not know what the person is
supposed to do. On the other side, the programmer/developer may list
some web technologies but he/she is unable to show that he/she has an
adequate understanding of those web technologies during a job
interview. It is up to the programmer/developer to discuss about
his/her salary. Some programmers/developers are happy to work in a
code factory.
I was surprised by some of the job descriptions. It's not a problem
I am interested in. :-)
>Front-end and Back-end developers have separate duties but through the
>past few years, these duties have been slowly merged and we saw the rise
>of Full-stack developers. This new role can be a threat to both
>Front-end and Back-end developers. To what extent do companies, in need
>of a website, understand the distinction among those three titles[1] is
>unsure.
The Back-end developer would have experience in the programming
language, framework and SQL.
Regards,
S. Moonesamy
1.
https://www.facebook.com/notes/facebook-engineering/the-full-stack-part-i/461505383919
Received on Fri Mar 04 2016 - 15:05:00 PST