How I learned frontend as a backend developer

[@jonathanjohnson2785]

Slow and incremental steps at the beginning makes learning so much more manageable. Thanks 👍

[@neugey]

I'm a backend dev who had "old" HTML/CSS skills, and learning the ways of responsive web design (RWD) on my side project really opened things up. I resisted it at first, but it was worth it.

[@TheDeathknight23]

I'll apply this advice to learning backend development.

[@PerryCodes]

I wouldn't describe my avoidance of frontend due to it being "confusing". My personal struggles with it, and the main reason why I gravitated more towards backend work, had to do with the state of browsers at the time. The JavaScript framework explosion hadn't happened yet, so a large part of frontend development had to do with hacks so that an application would behave similarly on all major browsers -- Netscape Navigator, Internet Explorer, and Mozilla Firefox. The other side of the hack coin was using HTML Tables for page layout. CSS was just around the corner, but by then I was happily working side-by-side with a graphic designer and a frontend dev. Today, component-based JavaScript frameworks, CSS, and tools like Figma and XD make the experience A MILLION TIMES more enjoyable!

[@TomGregoryTech]

Oh boy, I forgot about all that. Damn table layouts!

[@TheCodeTinkerer]

I always found fronted easier to internalize rather than backend. I would read once, build and make it work fast. I always thought of this as "frontend is easier, thats why I accellerate faster in this scope". Backend always seemed more "unnatural, non-tangible" maybe because backends scope is focused on streams/IO. And I work backend only 🤣

[@rajeshthecoder]

Always thought people starts from frontend since it's easy

[@dig8195]

The css part and layout is the frustrating part. 10years of exp in meshmash java/nodejs/rails and if you'll give me task to create a sidebar I'll probably resign(kidding). But yeah, I don't even know how and where to start

[@rflx3608]

@@dig8195 I am definitely the opposite i am only like 4 years in frontend, first year layout is confusing until you kept experimenting with how each and every css works, and not only that i really like doing UI/UX designs as well (in which i do and code them too) and i can pretty much code anything you give me a design even if its animated yet i struggle in the backend side since i lack knowledge on pretty much everything about it cause i feel like there is too much to learn than the frontend (which is just a basic route from html css js to react, angular, vue, css frameworks and semantics) i only know the basics, so if you tell me to make a simple api of this and that i just cant. So i guess it's all preference.

[@dig8195]

@@rflx3608 it's like we're already too wired to only think of BE or FE due to years of exp. Haha but I'm grinding on reactjs now. The more senior I get the more companies are trying to hire fullstack devs - at least in my country.

[@dig8195]

@@rflx3608 Sounds exactly like my colleague who's in FE for years. It's like we're already too wired to think only in BE or in FE Haha but hey, started grinding my way with reactjs now and hopefully someday soon can do both FE and BE.

[@FiazItik]

Naah man! Frontend is soo hard for my brain to wrap around it! No logic there

[@not_a_cool_handle]

As a HTML engineer, I would recommend you to just do it.

[@jmg9509]

Html “engineer”? Is that an actual role nowadays? Or was it an older term that used to be used ?

[@adnan7698]

Can you also make the opposite of this video?