Days in the Life of Mo

Let’s be honest: every developer remembers their first heartbreak.
Mine wasn’t a person, it was CSS centering.

I still remember that moment in my early dev days: sitting in front of my screen, refreshing the page like the browser owed me answers, whispering “please just… move a little to the left?” as if the div could hear me. Spoiler: it couldn’t. It never does.

And yet, here we are in 2025, building neural networks, sending robots to sew tiny stents inside human arteries, and using AI to suggest what we should eat for lunch… but centering a div? A global crisis.

You would think, after 28 years of CSS (yes, it was introduced in 1996, meaning CSS is older than Google), we’d have figured this out by now. But no. No, we did not.
Google, born later in 1998, grew up, became a billionaire, built maps of the entire earth… and CSS is still like “margin: auto? I could center this… but I choose violence today.”

Even the Mozilla Developer Network, the scriptures of our people, explains centering with paragraphs that look like ancient runes. MDN literally has entire sections dedicated to different types of centering, because apparently “center the thing” was too much for one method to handle (real source, look it up: MDN Web Docs → CSS Layout → Centering).

So… why is centering still chaos?

Because CSS wasn’t originally designed for modern layouts. According to the W3C archives, in the early web, designers were basically just throwing content onto static pages and hoping for the best. Nobody told the early CSS creators that one day we’d be building responsive grids, fluid layouts, and animated elements that behave like they’re auditioning for a Marvel movie.

Flexbox tried to save us in 2012.
Grid said, “hold my beer” in 2017.
And yet… I still find myself adding:

display: flex;
justify-content: center;
align-items: center;

…and saying a small prayer. Because sometimes it works. Other times? It decides the alignment you think you chose isn’t the alignment your div spiritually needs.

Maybe the real issue is this…

CSS centering isn’t just a property, it’s a metaphor for life.
Think about it:

• We’re all trying to stay centered.
• We’re all trying to balance chaos and structure.
• We’re all positioning ourselves in relation to things we cannot control; parents, deadlines, layout containers.

And sometimes, like a stubborn div, we drift.

Centering forces you to pause, re-evaluate, rewrite, try again, and ask questions. Lots of questions. Questions like:

• “Why won’t this thing move?”
• “What have I done to deserve this?”
• “Is this truly my calling or should I become a farmer?”

It makes you reflect.
It makes you learn.
It makes you painfully, humbly human.

And in a weird way, I kind of like that about CSS.
It refuses to let you autopilot your way through. It makes you think.
It makes you aware.

CSS centering forces dialogue.
Between you and your code.
Between you and your layouts.
Between you and that one junior dev who still believes text-align: center will fix everything.

So… what’s the point?

The point is: CSS centering is hard because the web is alive.
It has rules that contradict each other, structures that shift, and behaviour that only makes sense after you understand 17 hours of layout theory.

And that’s okay.

Because if there’s one thing that makes you a stronger developer, it’s not getting everything right — it’s wrestling with the tiny things that refuse to cooperate, and learning to laugh through it.

So here’s my question for you, the one that’s going to expose your soul:
What is the pettiest CSS problem that has nearly broken your spirit?
Drop it in the comments so I don’t feel alone in these Flexbox streets.

Like posts like this?

Stay close, I write the kind of tech stories you read at 10PM when your code decides it no longer wants to compile.
Subscribe to get more dev-girl chaos, calm, and casually educational thoughts delivered straight to your inbox.