Stop finger-pointing, and start deep diving. Without designers, fundamentals like CSS wouldn't exist.
Design is not limited to aesthetics.
Just by making statements like the self-appointed "Full Stack" title (which is actually an individual stack, and not the entire gamut of every programming language in existence - which is what a Full Stack is - which was limited to two developers in the entire world, circa 1992, and no longer exists), maybe Developers don't know kuak about programming would be more appropriate.
To take it further, "Architects" are responsible for the backbone, yet most seem to be the laziest people I've ever met - using out of the box solutions, instead of learning how to build something without a generator built by someone else. This makes their projects "pre-fabs" as opposed to "homes", imo.
When it comes down to it, collaboration is key - so, the next time you decide to blame a designer, take a better look at how they are communicated to, killing any roadblocks (like expecting someone else to relay a message for you, via Project Manager). User flow is just as - if not, often more - important than the actual functionality, since it can limit unnecessary transactions and page loads that would normally be included by developers who don't understand the users they are creating the product for.
If you initialize any project by unwrapping a fancy box... you're doing it wrong.