I don't think so. I am a full stack developer I learned backend first and then frontend it wasn't that hard for me. But some people do.

Jim Coplien suggests that we should get rid of developers who do not have clear understanding of UI/UX (let alone CSS). Moreover, Finding it hard to work with other developers is a clear sign of lack of people skills which is a must have quality for senior level posts.

No developer should ever think it is cool not to understand CSS, given that it is the second most popular (after HTML), Turing complete, domain specific programming language.

That's a resounding, "Maybe."

I know developers who dislike all UI work whether browser-based or not. Some of these are primarily Back Ends guys - others (surprisingly to me) not.

I know developers that find ONLY browser-based UIs painful, because browser UIs are, well, you know - browser-based, i.e., not fully compliant with specifications for HTML, JS, and CSS and differently implemented from one browser to the next. These are mostly EVERYBODY. It's gotten better as libraries have stepped in to provide Facade pattern abstractions to shield us from the vagaries of the underlying primitives across most browsers.

IMO these attitudes are not so much Back vs. Front as they are personality-driven preferences. I know people who find project analysis and design painful but love debugging crashes of live production system. I am the opposite. I know others who enjoy all facets of architecture and development. I'm one of those.

The world of IT is wide enough to justify specialization in any number of ways. A priori, it's not unreasonable to postulate a higher probability that Back End specialists might find Front End work more painful than a Front End specialist. However, good IT folks have to be pretty smart and flexible in general. I'm bettin' smart wins out as needed.

Role and personality-driven issues aside, I think Brandon got it rightest: people find stuff outside their areas of expertise difficult (at least at first).

Reverse is also true.. because backend is not just about CRUD

I think it's good to have a wide range of knowledge, having full stack experience broadens your job market as well as being able to create pretty much any type of application. I have created and administered databases, web servers, written thousands of stored procs, written front ends and backends in numerous different languages and platforms. Having a wide array of knowledge is very empowering.

It is difficult for [ person ] to work with [ unfamiliar thing ] without learning more about it.

As backend developer, it is hard to think about the many little details that make the UI the UI. It is a different context and style of development compared to backend development. CSS (classes) can be re-used in a different way than backend classes and functions. But coming from a background where always both was needed: back and front-end work, I cannot really tell what feels easier. I think both sides have their own quirks.

Complete bull, it's not painful haha It's just that do you need to think differently. Coming from front-end, completely throw me until I learned how to do it all. I think if you're dedicated to enough to learn it, soon enough you'll work it out quick as anything ;)