702

CSS (i.imgur.com)

submitted 8 months ago* (last edited 8 months ago) by nullPointer@programming.dev to c/programmer_humor@programming.dev

34 comments fedilink hide all child comments

easy to get into trouble for sure.

you are viewing a single comment's thread
view the rest of the comments

[-] gofsckyourself@lemmy.world 34 points 8 months ago

It's really not, though. This is only true if you're bad at CSS, which basically can be said about anything.

[-] nullPointer@programming.dev 50 points 8 months ago

unless you inherit a large base written by someone who is bad at it where their approach seemed to be to write new bad rules in attempt to cover up previous bad rules and so on. we all know how supportive employers are at addressing technical debt. (site redesign cant come soon enough)

[-] underisk@lemmy.ml 32 points 8 months ago

Not sure about your particular situation but there’s also the possibility that the bad CSS was good CSS when it was written and over time that got superseded by advancements in both technology and practice.

[-] agressivelyPassive@feddit.de 14 points 8 months ago

Or simply different styles and/or skill levels were mixed. I'm currently sifting through a code base that I know for a fact started out goodish, but through multiple team reorgs and lax standards/tight deadlines it devolved into a hot mess. A major contributor being that most of the devs were inexperienced in the framework and just did what they thought was right.

[-] Aceticon@lemmy.world 1 points 7 months ago

Even supposedly senior devs often have a "I know best" mentality and when they get their hands on a code base do it their way, with the result that after something went through a couple of hands you have a mess of different coding styles and even different software design choices in the same code base, or in other words, and unmaintainable mess.