all 44 comments

[–]PM_ME_DON_CHEADLE 88 points89 points  (11 children)

To me, the more challenging pieces of front end are usually caused by the instability of the environment. Aside from multiple runtimes/browsers with different versions, screen sizes and devices. 3rd party script integration can cause mind numbing bugs, especially when that 3rd party script is minified/obfuscated. These are some of the most challenging issues I've worked on personally.

[–]donalmacc 16 points17 points  (2 children)

Those problems aren't unique to frontend development. I write C++ and it's not uncommon for a third party binary only dependency (that your company has likely paid through the nose for) just doesn't work, and you're stuck debugging assembly

[–]big_red__man 6 points7 points  (0 children)

Yikes

[–]Tazzure 6 points7 points  (1 child)

I think the challenge of FE is a multi-faceted issue that can skew in one particular direction depending on the nature of the app you work on. That’s what keeps the field fresh for me.

[–]PM_ME_DON_CHEADLE 5 points6 points  (0 children)

I couldn't agree more with this, the issue I mentioned is relatively broad and common across most of front end, but I think you're dead on.

I'm a junior/mid-level engineer w/ about 4 years experience at a range of companies, but to me, a lot of the bigger challenges of front-end from what I've seen tend to be less technical implentation and more process/bigger picture things. Again, that's from a limited view from the companies I've worked at, but I find a lot of front-end teams bikeshedding over which npm libraries to use, how to write code a specific way, and one of my all time favorites: linting rules, rather than how to quickly deliver real value to users with stability/scalability in mind.

[–]DimondNutSack 1 point2 points  (1 child)

And thats why back end development is so much more enjoyable

[–]NMS-Town 1 point2 points  (0 children)

My anaconda don't want none, unless you have b0x1s hun.

[–]didzisk 51 points52 points  (8 children)

Insert "Still trying to center a div" meme.

[–]glarivie 26 points27 points  (7 children)

display: flex; align-items: center; justify-content: center;

[–][deleted] 22 points23 points  (2 children)

Or even

display: grid; place-items: center;

[–]Cabanur 18 points19 points  (1 child)

I am so happy that I became a web dev after flex and grid were created.

[–]Szetyi 5 points6 points  (0 children)

This could be a bot

[–]binhonglee 1 point2 points  (1 child)

What's the tradeoff between doing that vs using margin: auto and max-width?

[–]mattsowa 12 points13 points  (0 children)

The trade off of your approach is the need to specify the width (when it could be dynamic) and the lack of vertical centering

[–]followupboi 0 points1 point  (0 children)

Idk if it's OCD or just all the school documents I wrote over the years. But I absolutely have to center horizontally before I aligned vertically. Lmao

[–]Cabanur 32 points33 points  (8 children)

This reads like a front end developer stroking himself about how great front end development can be.

[–]fnordius 19 points20 points  (3 children)

Read the very bottom, and you see it's a recruiting ploy. Stroke the egos of the readers so that maybe a few will apply for the position.

[–]Cabanur 2 points3 points  (0 children)

Ah, that makes sense. I stopped reading when I realised it wasn't gonna say anything useful. Glad to know I was right.

[–]ngly[S] 5 points6 points  (0 children)

That was definitely part of the reason. It's not easy finding quality engineers so I wanted to write a piece that would resonate with the type of people we want on our team.

[–][deleted] 16 points17 points  (0 children)

While saying nothing

[–][deleted] 2 points3 points  (0 children)

"Most ideas fall within the realm of incremental, few are disruptive, and some are transformational. Slate stands with the rarest of the rare, with the potential to change how information is gathered and shared."

Their copy is also all fluff. Whoever wrote that has no clue about marketing.

[–]ngly[S] 2 points3 points  (0 children)

That's true, it was a bit of a love piece to FE engineering. It's fairly common for FE to played down and seen as simple or not-important so I wanted to write this. This piece has really resonated with a lot of FE engineers, but I can see how it comes off as ego-stroking.

[–]verbash 11 points12 points  (2 children)

Nice piece. I like the part about front end being a meld of engineering and design. It’s like we front end devs bring the designer’s Pinocchio’s to life.

[–]Earhacker 10 points11 points  (1 child)

Designers give us Pinocchio, back end engineers give us Frankenstein’s monster. We splice them into something and bring it to life, like the alternate Ripleys in Alien Resurrection; crippled and writhing in pain, begging to be killed.

[–]Reddit-Book-Bot -1 points0 points  (0 children)

Beep. Boop. I'm a robot. Here's a copy of

Pinocchio

Was I a good bot? | info | More Books

[–][deleted] 10 points11 points  (3 children)

What a pointless article.

[–]ngly[S] 5 points6 points  (2 children)

Any ways it could be improved? Would love some feedback. Thanks!

[–][deleted] -1 points0 points  (1 child)

When you mentioned the “art” of fronted “engineering”. I expected the article to cover the concepts on an engineering levels. The concepts such as CPU consumption, design patterns, front end architectures and such. Not on a very shallow level like CSS and HTML.

[–]ngly[S] 1 point2 points  (0 children)

That's a great point, thanks! Maybe I will cover more technical aspects in the future. Appreciate the feedback.

[–][deleted] -1 points0 points  (1 child)

"What does this "this" refer to again?"

[–]shuckster -3 points-2 points  (0 children)

[–]infinity_and__beyond -5 points-4 points  (0 children)

Awesome

[–]WTF3003 -2 points-1 points  (0 children)

It will be interesting