Answer the question
In order to leave comments, you need to log in
Should a front-end developer know how to code (css)?
1) Should a front-end developer be able to design (psd-to-css)?
or is it enough to know twitter bootstrap/angular material?
2) if the customer took me as a full-stack, how can I explain to him that I'm not a layout designer?
I'm not a css developer? Please find a css developer in our team. Or let's use angular material
Do you think it's ok?
Thanks for any ideas :)
Answer the question
In order to leave comments, you need to log in
A front-end developer who doesn't know how to code is like a plumber who doesn't know how to fix a faucet. CSS is probably the easiest thing to do front-end, so learn it or you can't claim it. Especially on a full stack.
How can a front-ender do without typesetting?... Yes, I also sat at some point without typesetting anything for about half a year, just pedaling react, and then somehow I had to stupidly typeset again for half a year. In general, this is a necessary skill, I think. Without this, the front is of little use.
Frontend should make up better than a professional layout designer??? Apparently, few people understand what professional layout is.
The layout, for all its seeming simplicity, has a large bunch of pitfalls and nuances, thanks to the variety of browsers and technologies.
Disdainful attitude to layout is most likely due to the attitude towards the result 'and so it will do'.
And if the front does not know how to layout, he will use js and write monstrous markup, if only it works.
For 5 years I was a pure coder, now for the second year I am writing on react (mostly).
And yes - it is better to grow a quality front from a workbench. But this is becoming less and less common.
1. Yes, it’s better than a coder
2. It’s better to discuss all the details before accepting an offer
How to formulate a clarification of the development process depends on how you were given the task
Guys, it looks like you have no understanding of the purpose of the word frontend developer.
A front-end developer should not be able to typeset.
Who wants to argue and write that he is a cool and layout designer and front-end - throw off a link to your plugin that has 10k + downloads or a similar development. There is no such plugin? Then which one of you is a frontend worker?
All your knowledge of gulp and sass is still layout - yes, more advanced tools, but layout tools, and have nothing to do with the frontend.
A frontend developer should be able to write very good abstract OO-js code on classes and prototypes - capable of working outside of any and on any layout.
Frontender - one who writes plugin logic, optimal and fast in accordance with the latest edition of EcmaScript.
Typesetter - the one who typesets: markup + design + some scripts.
The frontender not only should not make up, it should in no case go into the layout.
back-end, front-end and coder are three different specialists, with completely different technology stacks.
You may disagree, but a good specialist does not work 24/24. To take on too much means not to be a specialist. Or let's then put the responsibility on the layout designer - to add the native code of browsers, to write the web server on the front-end, and to develop the DBMS on the back-end developer. Why not? let's also drag in descktop and system development here, and let's hang drivers and operating systems and mobile development on the layout designer, and in general, let the content developer do all this.
Are you a container man? Prick me the Internet, container man!
Definitely should know.
I have never learned to typeset consciously, the skill comes by itself if one encounters it one way or another. Moreover, flex is very easy to learn and covers 90% of tasks.
Spend a week on some kind of layout tasks and you will not sag in this skill.
In place of css, there can be any other technology, it's like "Should a front-end developer be able to write in JS?".
You may not even know js, the main thing is to learn react and nodejs. Sorry, couldn't resist.
And so I don’t pretend to be the truth at all, but my opinion is this: the front must be able to typeset, understand what BEM naming is and be able to use it in practice. Scss pug gulp to taste. There was experience in the company, they connected me to the layout of the front (I'm a layout designer). He wrote, well, just a sufficient amount of disgusting layout, which is not for bam, but for kicks (we’ll hand over everything will be fine), it’s not provided if there will be 2 lines instead of 1. You look in source codes there media requests one continuous. Straight super abusfutsiroval layout. It's been like 6 months already. Most recently, edits to its pages have ceased.
Well, how is it? Nedofrontend or front unworkbench? For me, the first option and unsuitability.
I'm not saying that the front is obliged to typeset, I'm saying that he must be able to typeset and do it well.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question