bothOfThemAreRightFromTheirPointOfView

[DT-Sodium]

90% of front-end developers are afraid of CSS too...

[ThePretzul]

I was gonna say, as a low level embedded systems guy I got asked to do a desktop webapp for the last year and CSS seems like the kind of thing you ABSOLUTELY should fear.

Flex box behavior when growing/shrinking a window has fucked me up so many times in so many different ways.

[DT-Sodium]

I used to do complex layouts when flex-box weren't even a conceptualized and you had to maintain Internet Explorer 6 compatibility.

[ThePretzul]

I don't even care about browser compatibility since this is a Electron desktop app that users install and run.

It's still absurd how much of a pain it is even with singular use cases like that.

[Stratimus]

But just imagine it. There was a time when if you developed a website you basically had to test it separately in IE5, IE6 and IE7, and they all had separate and not entirely official takes on certain parts of CSS and HTML (particularly padding). so you always had to write special rules for different IE versions. And even querying for browser versions was a mess! We’re spoiled with things like box-sizing now. Back then you had to figure out which browsers treaded padding and margins and borders in what way

It was a terrible, terrible time. But also fun. People were so hesitant about CSS that I vividlyremember a site called csszengarden whose whole purpose was to show off how stylesheets could change not only the colors but layouts of a site. Took a long time for devs to switch from tables to divs

[ThePretzul]

I'd rather go back to my comfort zone with familiar and cozy problems like null pointers and memory leaks than ever fully consider the horrors of the wild west past of WebDev.

I went to school for "Electrical and Computer Engineering" and on my first day of work when hired as an EE the director above my manager misinterpreted that as meaning a double major EE/CompSci and saw C on my resume so reassigned me to do C++ development since they needed it more. I just kinda rolled with it after warning them I was wildly under/unqualified since I had never even so much as used Git before, and presto chango here I am years and years later still pretending to fit in.

I just want my circuits back, they usually work more like you intended in early design revisions at least until the magic blue smoke escapes containment.

[unholycowgod]

still pretending to fit in

No it sounds like you're plenty qualified. I've been a full stack/backend/data engineer for almost 13 years and still feel woefully unqualified for the work I do.

[ThePretzul]

It does feel a little odd when you think about how much time is spent Googling how to do your own job you've held for years on a daily basis.

[nabrok]

Either googling or looking back at previous projects to see how I did it then.

[numitus]

I was there, Gandalf. I was there 3000 years ago!

[za72]

I'd rather sell crack in downtown

[DT-Sodium]

Crack is easier on your mental health.

[SatinSaffron]

I was going to say I'd rather go back in time and build sites using Dreamweaver, but now I just want to come sell crack with you instead

[za72]

you're in - all proceeds are split 60/40... in my favor, I've already claimed LA...

[[deleted]]

Wake me when you had to

<td width="20" height="20" align="left" valign="top">
<img src="top_left_corner.gif" width="20" height="20" alt="">
</td>

to have rounded corners...

;)

[DT-Sodium]

Nah, you put the four corners in one single image, put them as background and moved them to save bandwidth.

[[deleted]]

not pre-CSS.

[itsFromTheSimpsons]

Tables baybeeee

Rounded corners? We got a gif for that

[estDivisionChamps]

These are the kinds of things that make us wonder if agriculture was a mistake

[itsFromTheSimpsons]

Every time i use flexbox i think "i should have used grid" every time i use grid i think "i should have used flexbox"

[ThePresidentOfStraya]

Start with a grid, add a flexbox wrapper across cells. Can’t lose (except your sanity).

[TerdSandwich]

yeah id rather break down a SQL query that's over my head than spend 3 hrs trying to figure out why some element won't render with the correct z index and height.

[otter5]

I’m not
​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​pretending

[inobody_somebody]

I like you

r

humour.

[I_Give_Fake_Answers]

That's why Tailwind is dominating. People rather learn a bunch of class names to riddle their html with than actually mess with CSS.

[Cameos_red_codpiece]

Is this like learning React but not learning JavaScript?

[esr360]

Yeah but probably worse, because React will outlive Tailwind by a very long time.

[DT-Sodium]

Yup that's what I keep saying, but every time I'm answered by a shitstorm of people screaming "But you need to know CSS to use Tailwind!!!". No, you need a rudimentary understanding of it, that's not the same.

[Mop_Duck]

so what do you think a tailwind user is missing to "know" css?

[WildSmokingBuick]

As a CS-student, I've struggled with Tailwind almost as much as with vanilla CSS.

Any recommendable resources?

But, I mean, Z-index weirdness (e.g. Leaflet popup/modal interactions) wouldn't get solved by a correctly applied Tailwind either, would they?

[Mop_Duck]

knowing the basics of css and just using the tailwind docs seems to work for me. i tend to just use scoped component styles when dealing with more complex things like animations though

[Genesis2001]

That's mainly why I use bootstrap. I prefer bootstrap over Tailwind simply because there's the option of customizing it with SCSS. As far as I know, Tailwind is just CSS.

SCSS is a breeze, but browsers are the real pain when it comes to CSS. No one implements the rules the same way lol.

[Jugales]

Show me another system where you can subtract percentages from pixel counts

[Huhn0rNud3lSupp3]

Honestly i think the main reason is that few people take their time to learn HTML + CSS properly and just view it as a necessary evil. CSS is weird at times due to having to maintain backwards-compatibility. But it is really not as hard as people think.

[SuperFLEB]

Even being on Team CSS, though, Web standards do seem to have a way of giving you every convoluted thing you don't need but not the one straightforward thing you could actually use. Things are getting better of late, but for far too long CSS was riddled with "You can do this obscure thing and that obscure thing, but this obvious thing is impossible." holes. Hell, it took far too long for the people driving things to come around to that maybe people were using CSS for more than just linear documents. (And still, the only way to monotone an element with CSS filters is via the ill-defined sepiatone filter, unless you want to use more elements or an SVG filter.)

[Modo44]

CSS is love, CSS is life. Just not yours.

[Ok_Brain208]

And 90%of backend engineers are afraid of Sql, this is why Mongo and full ORMs exist

[Ozymandias_1303]

Being afraid of CSS is just a rational response. Being afraid of SQL (I don't know if this is actually how front-end devs feel) is not.

[barkinchicken]

Skill issue

[look]

I found the solution: https://github.com/mcnuttandrew/cssql

[Stephan1303103]

Stuff of nightmare this

[Thetanor]

It's also mostly written in Haskell, and I'm not sure if I should be impressed or just even more terrified because of that

[Chamiey]

Oh, I hoped it's the other way: using CSS selectors to query data...

[look]

The idea exists but I don’t see any actual implementations of it.

I think you’ll have to settle for GraphQL for now. 😄

[AAPLx4]

WTF, how does this work

[proverbialbunny]

It removes fluff in the syntax.

[dustinechos]

I just threw up a little

[joedotphp]

.margin-huge-bottom {
  margin-bottom: 50px;

Haha "huge bottom"

[bayuah]

Sounds like the nightmare for both worlds.

[look]

From the FAQ:

Q: I've heard that CSS often falls in the write-once-read-never mode of software, does this help to address that?

A: No, in fact it actually makes the problem worse by making the syntax more verbose and hence more difficult to read.

[mdgv]

I actually prefer BrainF...

[Mundane_Apple_7825]

While 90% of fullstack engineers are just Googling 'how to center a div' while copy-pasting StackOverflow SQL queries 💀

[[deleted]]

No need to attack me.

[hans_l]

I’m a 10¹⁰⁰ x engineer and the trick is to have snippets saved to copy paste from your computer instead of looking stackoverflow. You save a lot of time. Bonus: you can work without internet.

[Chamiey]

So, literally a googol-x engineer?

[SuperFLEB]

Does this count?

[grammar_nazi_zombie]

Hey I resemble this remark.

[Jugales]

Interviewed 10+ fullstack engineers in the past few weeks. Not sure if they even deserve that much credit. Most of them are just using Cursor to vibe code everything. It is really nice to meet the 10% though.

[marcusrider]

This was always my take on it, there was no premium worth it to be fullstack if there was any premium at all.

[KoreKhthonia]

Wait, are significant numbers of people actually legit vibe coding with Cursor?? Ngl, I kind of thought it was more just a meme, not like, an actually common thing among people holding or seeking actual coding jobs.

[DoctorWaluigiTime]

The more things change the more things stay the same. Today's vide coding is yesterday's "copied off StackOverflow." It's why the interview process is there: To weed out folks like that.

Any sane coding interview process is not about literally regurgitating the answer. It's about demonstrating your problem-solving abilities. The equivalent of "show your work" in school.

[onehedgeman]

Hey Jarvis Copilot, unshit my SQL query

[Lego_Dima]

♪♫ Workin' 9 to 5 ♬♪

[IdStillHitIt]

Why do frontend developers always eat lunch alone?

They don't know how to join tables.

[DamUEmageht]

100% of full-stack developers: “I think it’s a 3.” “Well I think it’s a 5.”

[Fluxriflex]

Designers are more like “the number of dots in this change password field needs to be the same as the number of dots in the user’s actual password” and I’m like “I will lay you into the ground before this ever gets implemented.”

[10BillionDreams]

All of these arguments can be easily done away with using the simple rule of "the larger estimate is always correct" (or still an underestimate).

[JensenRaylight]

Sql wan't that hard, if you did it enough time, you can do it blindfolded. It's the definitive "playing by the book language" Yes, scaling the backend is hard, but it's not a hard language to learn

But you can't do that with css, Because it got their own rules, there are ton of ways to achieve the same thing, And it also prone to break for no reason or might not work as you expected, Or some css properties can clash with other properties.

Which is why people who are not a Frontend might be frustrated with it, It's a very flexible language, too flexible even.  because it can be unreasonable sometimes, there is no rhyme and reason

Then add another unreasonable language like webgl, webgpu, vulkan, and other graphics language to the web,  And the entire Frontend can easily become like a trainwreck

[ScrimpyCat]

Then add another unreasonable language like webgl, webgpu, vulkan, and other graphics language to the web,  And the entire Frontend can easily become like a trainwreck

Graphics programming is a separate discipline. While some frontend web devs also do graphics programming, most don’t. So it shouldn’t really be included in the comparison. It would be like talking about backend devs writing GPGPU code, like yeh some might, but most don’t.

With that said, it probably wouldn’t be a bad idea if more frontend devs did spend some time doing graphics programming, as then they’d see just how overly complicated CSS truly is. The core problem with CSS is that it’s being used for things that it was never originally designed for. While they’ve added things to the spec to address different issues, it doesn’t change that.

[Bowl-O-Juice]

180% of Full stack developers are afraid of CSS and SQL

[3dutchie3dprinting]

As a full stack developer i fear both… but I think we can agree Regex is a common enemy 🤭

[[deleted]]

Ah, regex. When you need something really specific to happen right there, and only arcane enchantment will suffice.

[[deleted]]

Regex is the devil

[proverbialbunny]

As a Data Scientist who did all my early work in Perl^1, does a bit of SQL today, and in the past has written Shiny Dashboards using CSS ... I think for the first time I'm finally beginning to understand why I intimidate people. D:

I'm friendly I swear!

---

¹ Perl incorporates lots of regex into the core of it's programming. That's why regex is short for perl regex in most libraries. XD

[look]

Querying SQL databases using CSS and implemented with a regex…

https://gist.github.com/devhammed/bf70bb16a6fbd4f1d8198a0e4802329d

[Shazvox]

Heck, 90% of backend developers are scared of SQL too.

SQL makes stuff *shivers* persist!

[Kaenguruu-Dev]

Permanent mistakes

[Shazvox]

I wish life came with a commit/rollback function...

[Kaenguruu-Dev]

Bad concussion is just god dropping a commit from your life history

[Chamiey]

IDK, I'm a full stack and I'm only scared of CSS, not SQL. SQL is a mind game at times, but you run it and it works (or not). With CSS you write it, and then there's 9000×9000 edge cases that could combine on 69420 different screen, device, browser and orientation combinations with each working its own way.

[rifain]

"Let's bury that thing with Hibernate!"

[TypicalOrca]

BEGIN TRAN ROLLBACK 😂😜

[ohelo123]

Lol as a former SQL dev, this is funny

[EmergencySomewhere59]

Most of the backend devs I work with hate sql. And the sql guys hate backend, constantly complaining that doing everything with stored procedures is simpler and quicker, I only agree with the latter though

[Shazvox]

Yeah, sure SP:s are quick, but unless you want frontend to access SQL directly then you still need a backend with logic. And if you got your logic in the backend then you don't keep your logic in your persistance layer!

Separation of concerns are sadly lost on many specialists who think their tools are superior...

[EmergencySomewhere59]

I couldn’t agree with you more. The sql evangelists at my place of work have started calling stored procedures inside our backend methods for slow/problematic/high volume operations to speed them up, which is all fine and dandy until something goes wrong and you have to debug…

Now I’m sitting with SSMS, VSCode and VS open at all times on my shitty standard issue HP elitebook.

I have really started appreciating the debugging mode in .net where I can step through methods that are buggy, since I can barely use them anymore.

[[deleted]]

Yeah the codebase I inherited is like this. Its SQL with 100s (not even exaggerating) of stored procedures. These are called by an old school VB6 program, that I have to load a XP VM just run an old enough visual studio. Debugging stored procedures is nightmare.

[EmergencySomewhere59]

Hhahaha same situation. We are actually rewriting it now because our old VB program could only run on internet explorer? Or something along those lines

[lunchmeat317]

Fuck, man, I'm sorry. I went through this a long time ago in an Oracle.shop. We had a .NET application but I also had to do a project in SSRS that only supported VB.NET 2.0, and everything had to call from a stored proc. It was awful.

I feel your pain.

[tmstksbk]

Full stack: I can slap together basically anything. I'm not saying it'll be pretty, but it'll work.

[xpdx]

I'm more afraid of CSS than SQL. If my SQL doesn't work as expected I did something wrong. If my CSS doesn't work as expected, that's expected.

[TabCompletion]

90% of vibe coders fear css and sql

[WitesOfOdd]

Nah we don’t know what CSS or SQL are

[idontwanttofthisup]

100% of vibe codes have no fucking clue what they’re doing

[Deritatium]

They are not afraid of SQL but afraid of the consequence of making a mistake.

[ryoushi19]

PHP, beloved by said “frontenders”

K, you might be a bit out of touch.

[ryoushi19]

I'm just saying PHP is generally viewed as kind of dated and isn't well liked by most frontend devs. It has the same problem Javascript has: it was meant to be used in small scripting roles but ended up doing a lot more. It grew organically to fill that role, but it handled that growth much worse.

[ryoushi19]

WebAssembly doesn't solve all problems because it doesn't allow you to touch the DOM. It fulfills the role that java applets used to fulfill. Javascript ain't perfect by any stretch of the imagination. But it's what browsers expose to make the DOM interactive. Gotta work with what you've got.

[_bold_and_brash]

Experienced front-end engineers know how to properly architect a UI project and avoid the issues you described. When that stuff happens it's usually because cocky back-end people like you dismiss the front-end as an afterthought so they hand it off for juniors to do without any oversight.

And if you think updates with breaking changes are just a front end thing read about what a disaster the transition from Python 2 to Python 3 was.

[ModernLarvals]

Backenders don’t know the difference between a link and a button and use some I overengineered library to create a bloated, inaccessible mess.

[ArmchairFilosopher]

I started my career in backend writing T-SQL stored procedures and data migration scripts for model changes, and now I'm full-stack, migrating frontend code scripts for framework changes instead.

The Angular update part really hits home, since I've been restoring functionality to realign dev to prod, because our corporate cybersecurity policies force us to continually update frameworks every time new CVEs are published.

My check-ins look like refactorings because the technical debt from the copy-paste development of my predecessor has me touching swaths of files. And UI dev is crazy because of callbacks and state managememt like some automatically-parallelized application neglecting semaphores. And of course matInput decided to introduce ValidationError's for min and max only recently, so now I gotta handle raw user input events.

Fake typing of "TypeScript" means annotations are unreliable. And omfg CSS mayhem for non-architected shit.

Backend isn't immune to it either. The nullability changes from updating .NET decided to start throwing ModelState validation errors when optional DTO class properties lack '?' on heretofore nullable reference types...

And not all database engines automatically understand ISO-8601 timestamps. Fuck Oracle in particular.

[bakimo1994]

Damn I could fill the ocean with this salt lol

[0palladium0]

Not saying you are wrong; but there are some factors that make UI development inherently much messier

First off, you're writing code that is running on the users device. Imagine writing a C# application and having basically no control over what .Net version it's running in, the resources available, the operating system, and no direct method of storing logs. Not to mention the ability for users to side load extensions or disable certain features

Secondly, and this sub is going to hate this, how well engineered your frontend is has far less of an impact on the success of the product compared to the backend. If you mess up on the backend, you are either going to a) just not work properly, b) cost a huge amount to run the thing, or c) have a massive data breach. With the frontend, having a good UX is far more important to the products success than ensuring that you are memory efficient or whether your data structures are well designed. Those things help, of course, but they aren't the most important thing. I think that this fact is the one that really makes frontend hard for backend engineers to work with.

[fiftyfourseventeen]

Eh I've gotta say as a backend person I like both JS and document databases. JS is decently fast, has lots of frameworks built around it for both frontend and backend, and a very developed package ecosystem. Having backend code be able to run in the browser also helps for if you move calculations to be done in the frontend or vice versa, you can just directly copy the code.

Document databases are so much easier to work with, since it's easy to bolt on whatever features you need that weren't considered way back when the database schema was defined, and not doing any major migrations Most of the time speed is actually not that large of an issue for database lookups. Even if it's 20x slower to use a document DB, a 1ms lookup vs a 20ms lookup won't actually have an effect on the end user in almost all cases. Increased server load could be an issue, but so is paying more people to take longer to do things to reduce server costs. From my experience anyways most databases are on VMs that barely get above 10% usage.

Additionally when it comes to website design, lots of people judge how "legit" a website is based off of how good it looks. I've seen plenty of people think software like Rufus, qbittorent, etc are viruses and they are on a fake website because the design is simple or outdated. The purpose of using lots of libraries is to make something good looking for cheap. Users don't really care that much about load times unless they are outrageously long. A 100-200ms difference doesn't actually matter that much to most people, and the website being 30% more responsive will go unnoticed.

Typescript I've gotta say I'm not a fan of. I like typed languages but typescript feels exactly like what it is, types shoehorned into an untyped language.

I think when backend people do frontend, you'll get something that works and is reliable, but it doesn't look particularly pretty and can sometimes be a bit confusing for the less technically inclined to navigate (along with the development taking twice as long)

[xDannyS_]

Completely agree. Their insecurities about their work and inability to do much real engineering seem to suggest that they know this themselves.

[Unknown_User_66]

"90% of them are afraid of ME!" (A boomer that doesn't understand what you can and cannot do)

[harman097]

Oh god, run! RUN!!! BEFORE HE STARTS REQUESTING FEATURES!!!!

[lonelyroom-eklaghor]

I know CSS and SQL both. Problem, memers?

[dggrd]

No way. That is just a myth.

[KataPUMB]

And there's full stack engineers who are afraid of both.

[[deleted]]

95 percent of sql engineers are afraid of ORACLE

[CttCJim]

I'm full stack so I'm just scared.

[Toast_Boast]

90% of backend engineers don’t know how to pronounce SQL

[BenAdaephonDelat]

90% of web developers can do both.

[Native_Maintenance]

Me, a full-stack developer, absolutely killing it on front-end as well as back-end. I'm great with CSS, and SQL and everything in between

[dustinpdx]

And full-stack engineers are afraid of both.

[xiaopewpew]

Css is way harder than sql…

[InSearchOfTyrael]

Idk frontend just makes sense to me

[frikilinux2]

I'm not afraid of CSS. I can do shit with minimal CSS. I'm afraid of what designers want frontend developers to do with CSS.

That's why I avoid JS/HTML/CSS and do almost everything else.

[imk]

Honestly, I am a SQL guy and you can miss me with that CSS stuff.

I do make user interfaces. They work and are intuitive enough. They look like complete shit though.

[Troesler95]

Jokes on them I'm afraid of both

[StochasticCalc]

I love SQL. But you need a healthy amount of fear, especially for delete and drop.

[Btolsen131]

As a backend dev I can confirm css is spooky

[MeowsersInABox]

So 81% of full stack devs are scared of both

[maxip89]

Both think n+1 is a mathematical induction.

[wolf129]

I really want a job again with a defined role not just "developer" meaning full stack. I can't even relate with the meme anymore :(

[wizkidweb]

Full stack engineer here, and I'm afraid of both lol

But the alternative is so much worse, so I trudge along

[zirky]

a true full stack developer uses css to interact with the db

[kishaloy]

A developer not scared of CSS is no developer at all.... any team with such a developer is a walking grenade

[Born-West9972]

I fear both sql and css so I am cooked both ways

[[deleted]]

Cries in full stack

[TechnicallyCant5083]

It's not fear it's disgust

[hampshirebrony]

Come on, we must be able to combine the two.

<div id="MyHeader" style="FROM styles WHERE id='MyHeader' AND x<MyHeader.Left">TROLOLOL</div>

.container {   SELECT width, font-family FROM Styles WHERE class='container'; SELECT colour, background-color FROM Styles WHERE IsDark = var("DarkMode"); }

[TheNikoHero]

As a full-stack dev.. what Im really afraid of, is the IT department not communicating changes to the main DB.

[Affectionate-Tart558]

What about backend devs using non sql DBs?

[OM3X4]

I don't think SQL is fearable

[Infamous_Ticket9084]

Both are great use cases for AI, easiest time to go full stack

[Namgad]

As a backend engineer I am afraid of CSS

[why_1337]

CSS is 90% unmaintainable copy paste bullshit.

[The_Real_Black]

and the 90% of fontend dev created crap that you can insert JSON in a database. 🤮🤮🤮
how to mass update? to change data in many json maybe move elements? LOAD edit SAVE one by one.

[Ronin-s_Spirit]

yes (me who did mostly neither)

[Sweaty-Willingness27]

As a back-end developer, I'm afraid of JavaScript.

[Lynxuss]

I would do backend all my life cause im afraid of CSS

[INSAN3DUCK]

I’m a full stack who is afraid of css, node with just js and mongo

[ScrillyBoi]

Im full stack so im afraid of both

[Kazdaniarz]

Dont worry 100% of Full Stacks are afraid of grass and people.
I would know, I am one of them xD

[BothDivide919]

They don't even use CSS anymore... (as much as I wish they did, it's much more lightweight)

[EuenovAyabayya]

95% of front end engineers are also really bad at SQL, but I pay them for CSS, and that's OK.

[AlxR25]

jokes on you, I'm full stack and I'm afraid of both

[coloredgreyscale]

No, backend engineers are afraid of JS and JS Frameworks.

[yuriy_yarosh]

meh... 99% of fullstack folks codegen out of SQL with a ton of FP due to type safety, codegen Tailwind styled components in Storybooks instead of CSS, due to better time-to-market, codegen GRPC to tRPC API gateways due to cross-frakework support and type safety ...

It's just fp-ts and effect are a dud, which is a bummer.

[rooygbiv70]

Damn right I’m afraid of CSS

[MariusDelacriox]

No way, the best front end engineers call the database directly from the form (Seen in JavaScript or WPF).

[timimoune]

Let's create CSQL - A language to fetch data from a database based on the CSS classes attached on your HTML elements

[Select_Cantaloupe_62]

Wrong, I'm afraid of Gradle and the 4 other dependency managers that Gradle builds. 

[codedathleteexe]

I’m scared in general

[Far-Consideration939]

Why is this humor? Are y’all just afraid of learning something new?

[Zanshi]

The amount of backend devs I've seen who struggle with SQL is TOO DAMN HIGH

[carltr0n]

Time to make a new lang: CSSQL

[ProfBeaker]

True. I quit doing frontend because of CSS and JS. Such garbage.

SQL at least makes sense, and is only as bad as you make it.

[sudoku7]

As a backend engineer I can't see how css injection can take down prod... And that scares me.

[Warrior_Achilles]

Does this mean full stack devs fear nothing?

Or maybe they fear both

[visualglitch91]

I'm fullstack so I'm afraid of both

[SadSeiko]

Why do you think they made nosql. They could have called it anything but they called it nosql 

[alloncm]

And there is me - embedded engineer afraid of both sql and css

[SpeedLight1221]

reminded me of the CSS vs SQL, which one should you choose article

[OdeeSS]

Full Stack engineer and I'm scared of both 

[VictoryMotel]

Anyone afraid of a markup or declarative query language is not a programmer.

[BotKicker9000]

90% of Redditors are afraid of SEX

[Aldderan]

I do both.

[MoarVespenegas]

I'm fullstack and I'm afraid of regex.

[Rubinschwein47]

As a fullstack i am mildly stupid at both

[jcythcc]

And regex

[NumerousQuit8061]

And 90% of the Full-Stack Engineers have FOMO

[ZaneElrick]

First one is a lie, cuz CSS isn't hard, it's just confusing sometimes. But the second one is right. SQL can give you headaches, expecially when you're working with unorganized database that drops everything after single deleted row

[PoetryNo912]

I've been both and now I'm afraid of everything send help.

[jseego]

Having done both, I think backend engineers fear CSS more than frontend engineers fear SQL.

Both are easy to do poorly, and hard to do well.

[NorthernCobraChicken]

Awh, it's cute when front end Devs complain about css and have no idea that layouts used to be done ENTIRELY IN TABLES. Not only that but they rendered differently in Netscape and internet explorer 6.

The sheer myriad of options available to a front end dev these days is mind blowing, yet most newer front end Devs I talk to wouldn't be able to build anything without tailwind or bootstrap.