{"id":307322,"date":"2020-04-24T11:35:55","date_gmt":"2020-04-24T18:35:55","guid":{"rendered":"https:\/\/css-tricks.com\/?p=307322"},"modified":"2020-04-24T11:41:21","modified_gmt":"2020-04-24T18:41:21","slug":"the-title-front-end-developer-is-obsolete","status":"publish","type":"post","link":"https:\/\/css-tricks.com\/the-title-front-end-developer-is-obsolete\/","title":{"rendered":"\u201cThe title \u2018Front-End Developer\u2019 is obsolete.\u201d"},"content":{"rendered":"\n

That title is from the opening tweet of a thread from Benjamin De Cock<\/a>. I wouldn’t go that far, myself. What I like<\/em> about the term is that \u2018Front-End\u2019 literally means the browser<\/em>, and while the job has been changing quite a lot \u2014 and is perhaps fracturing before our eyes \u2014 the fact that the job is about doing browser work is still true. We’re browser people. This was a point I tried to make in my “Ooooops I guess we’re full-stack developers now”<\/a> talk.<\/p>\n\n\n\n

I really like Benjamin’s sentiment though. There is a scourge of implementations of things on the web that are both heavier<\/em> and worse<\/em> because they re-implement something that the browser offers better and “for free.” Think sliders: scrolling behavior, snap points, fixed\/sticky positioning, form controls, animation, etc.<\/p>\n\n\n\n\n\n\n\n

Our industry seems to have acknowledged that backend and frontend developers require very different skills (even though they often use the exact same language), and yet it’s struggling to see there’s too much bundled into the term “front-end developer”.<\/p><\/blockquote>\n\n\n\n

That’s the tricky part. That’s at the heart of The Great Divide<\/a>. There’s an awful lot of front-end developers where their job solely focuses on JavaScript. You could call them “JavaScript Engineers” or “JavaScript Developers,” and that feels OK. However, I’m not sure what you call someone who’s a great front-end developer, not particularly focused on JavaScript, but is on other aspects of the front end. <\/p>\n\n\n\n

The modern frontend developer is most often than not a “Jack of all trades” mastering JS (or even just a framework) and barely tolerating HTML\/CSS as a necessary evil. That’s understandable. I strongly think it’s a different specialization, and it’s too much for a single person.<\/p><\/blockquote>\n\n\n\n

Yep, it’s OK! The divide isn’t a bad thing; it’s just a thing. Front-end teams need JavaScript specialists and<\/em> CSS specialists and<\/em> accessibility specialists and<\/em> performance specialists and<\/em> animation specialists and<\/em> internationalization specialists and, and, and, and. They don’t have to all be separate people. People can be good at multiple things. It’s just exceptionally rare that people are good at everything, even when scoped only to front-end skills.<\/p>\n","protected":false},"excerpt":{"rendered":"

That title is from the opening tweet of a thread from Benjamin De Cock. I wouldn’t go that far, myself. What I like about the term is that \u2018Front-End\u2019 literally means the browser, and while the job has been changing quite a lot \u2014 and is perhaps fracturing before our eyes \u2014 the fact that […]<\/p>\n","protected":false},"author":3,"featured_media":307383,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_bbp_topic_count":0,"_bbp_reply_count":0,"_bbp_total_topic_count":0,"_bbp_total_reply_count":0,"_bbp_voice_count":0,"_bbp_anonymous_reply_count":0,"_bbp_topic_count_hidden":0,"_bbp_reply_count_hidden":0,"_bbp_forum_subforum_count":0,"sig_custom_text":"","sig_image_type":"featured-image","sig_custom_image":0,"sig_is_disabled":false,"inline_featured_image":false,"c2c_always_allow_admin_comments":false,"footnotes":"","jetpack_publicize_message":"","jetpack_is_tweetstorm":false,"jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":[]},"categories":[4],"tags":[1142],"jetpack_publicize_connections":[],"acf":[],"jetpack_featured_media_url":"https:\/\/i0.wp.com\/css-tricks.com\/wp-content\/uploads\/2020\/04\/cogs-pattern.png?fit=1200%2C600&ssl=1","jetpack-related-posts":[{"id":339046,"url":"https:\/\/css-tricks.com\/eliminating-five-top-compatibility-pain-points-on-the-web\/","url_meta":{"origin":307322,"position":0},"title":"Eliminating five top compatibility pain points on the web","date":"April 23, 2021","format":false,"excerpt":"Robert Nyman and Philip J\u00e4genstedt: Google is working with other browser vendors and industry partners to fix the top five browser compatibility pain points for web developers. The areas of focus are CSS Flexbox, CSS Grid,\u00a0position: sticky,\u00a0aspect-ratio, and CSS transforms.[...] The goal in 2021 is to eliminate browser compatibility problems\u2026","rel":"","context":"In "Link"","img":{"alt_text":"","src":"https:\/\/i0.wp.com\/css-tricks.com\/wp-content\/uploads\/2021\/04\/sticky-header-compatibility.png?fit=1200%2C601&ssl=1&resize=350%2C200","width":350,"height":200},"classes":[]},{"id":273936,"url":"https:\/\/css-tricks.com\/sometimes-sizes-is-quite-important\/","url_meta":{"origin":307322,"position":1},"title":"Sometimes `sizes` is quite important.","date":"July 27, 2018","format":false,"excerpt":"Paraphrased question from email: I just read your article Responsive Images: If you\u2019re just changing resolutions, use srcset. In the age of \"responsive websites,\" srcset does not help in certain situations. For example, I have a popular products slider. On mobile, I have one image per slide where the images\u2026","rel":"","context":"In "Article"","img":{"alt_text":"","src":"https:\/\/i0.wp.com\/css-tricks.com\/wp-content\/uploads\/2018\/07\/srcset-sizes.jpg?fit=1200%2C600&ssl=1&resize=350%2C200","width":350,"height":200},"classes":[]},{"id":269127,"url":"https:\/\/css-tricks.com\/w-descriptors-and-sizes-under-the-hood\/","url_meta":{"origin":307322,"position":2},"title":"w descriptors and sizes: Under the hood","date":"April 1, 2018","format":false,"excerpt":"Eric Portis digs into how the browser decides which image to downloads when you give it . Notably, a browser can do whatever it wants: Intentionally un-specified behavior lets browsers provide innovative answers to an open-ended question. Still, calculations happen based on what you give it and you can still\u2026","rel":"","context":"In "Link"","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":257120,"url":"https:\/\/css-tricks.com\/browser-statistics-matter\/","url_meta":{"origin":307322,"position":3},"title":"The Browser Statistics That Matter","date":"July 27, 2017","format":false,"excerpt":"Have you ever had a web development related conversation discussion where someone brought up global browser usage statistics? I might be a little weird, but I\u2019d say I at least overhear a conversation like just about every day: I\u2019d love to use FANCY NEW FEATURE, but it\u2019s not supported SOME\u2026","rel":"","context":"In "Article"","img":{"alt_text":"","src":"https:\/\/i0.wp.com\/css-tricks.com\/wp-content\/uploads\/2017\/07\/1080x0180.jpg?fit=1080%2C1080&ssl=1&resize=350%2C200","width":350,"height":200},"classes":[]},{"id":279705,"url":"https:\/\/css-tricks.com\/blue-beanie-day-2018\/","url_meta":{"origin":307322,"position":4},"title":"Blue Beanie Day 2018","date":"November 30, 2018","format":false,"excerpt":"Another year! You better not cry, you better not shout, I\u2019m telling you why: @BlueBeanieDay is coming Nov. 30! Start sharing your #bbd photos, links, articles, and videos now: https:\/\/t.co\/3US4vHBsDR#a11y #WebStandards #InclusiveDesign #ProgressiveEnhancement pic.twitter.com\/AiV3ktRqka\u2014 zeldman (@zeldman) October 24, 2018 I feel the same this year as I have in the\u2026","rel":"","context":"In "Link"","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":316421,"url":"https:\/\/css-tricks.com\/improving-chromiums-browser-compatibility-in-2020\/","url_meta":{"origin":307322,"position":5},"title":"Improving Chromium’s browser compatibility in 2020","date":"July 7, 2020","format":false,"excerpt":"This is exactly what I love to hear from any browser vendor: When it comes to browser compatibility, there are still too many missing features and edge-case bugs. But it doesn't have to be this way. Things can and will get better, if browser vendors can understand what is causing\u2026","rel":"","context":"In "Link"","img":{"alt_text":"","src":"https:\/\/i0.wp.com\/css-tricks.com\/wp-content\/uploads\/2018\/07\/div-different-browser.jpg?fit=1200%2C600&ssl=1&resize=350%2C200","width":350,"height":200},"classes":[]}],"_links":{"self":[{"href":"https:\/\/css-tricks.com\/wp-json\/wp\/v2\/posts\/307322"}],"collection":[{"href":"https:\/\/css-tricks.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/css-tricks.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/css-tricks.com\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/css-tricks.com\/wp-json\/wp\/v2\/comments?post=307322"}],"version-history":[{"count":5,"href":"https:\/\/css-tricks.com\/wp-json\/wp\/v2\/posts\/307322\/revisions"}],"predecessor-version":[{"id":307538,"href":"https:\/\/css-tricks.com\/wp-json\/wp\/v2\/posts\/307322\/revisions\/307538"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/css-tricks.com\/wp-json\/wp\/v2\/media\/307383"}],"wp:attachment":[{"href":"https:\/\/css-tricks.com\/wp-json\/wp\/v2\/media?parent=307322"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/css-tricks.com\/wp-json\/wp\/v2\/categories?post=307322"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/css-tricks.com\/wp-json\/wp\/v2\/tags?post=307322"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}