Is it wrong of me to assume that if the CSS on your project's website is broken in stupid ways, your project itself is probably also broken in stupid ways?

[crell@phpc.social]

Is it wrong of me to assume that if the CSS on your project's website is broken in stupid ways, your project itself is probably also broken in stupid ways?

It's at least a yellow flag, right?

#Programming

[ponchovire@piaille.fr]

@Crell I'm not a front-end developper, but if CSS is broken in a way I can see it, I can tell the project is wrong because people were doing things they're not good at, in that sense it seems that at least project lead was really wrong

[wearwolf@kind.social]

@Crell is it possible for CSS to not be broken?

[crell@phpc.social]

@Wearwolf Hypothetically, yes.

At least I expect text to not overflow out of view at certain common browser sizes...

[bobmagicii@phpc.social]

@Crell young me would have said yes. old me has the wherewithall to realise nobody is a master of all trades, few people even become a jack of more than a few. so no, it is not an immediate "u suck" flag to me upon their entire stack.

[plym@vmst.io]

@bobmagicii @Crell I came here to say this. I've seen people work miracles of architecture with JavaScript only to stumped on centering a div with CSS. And when you get teams and corporate pressure, the reasoning changes. Then there's also the order of highest priorities for a developer, and "good enough" mentality when it comes to visuals.