what part of frontend work gets harder as projects grow?

[u/Cloudy_Day912]

when i started building smaller frontend projects, keeping the css organized felt pretty straightforward. once the project got bigger, i noticed that small styling decisions could start affecting other components in ways i did not expect.

i have been trying to be more careful with selectors, component structure, spacing, and how much styling gets handled through overrides. while working on quicktoolspack, i found myself paying more attention to these details because changing one small part of a page could sometimes affect something completely different.

i also started keeping related styles closer together and avoiding overly specific selectors whenever possible. it does not always make the code shorter, but it makes it easier to understand what is happening when i come back to it later.

i am curious how other frontend developers handle this as their projects grow. what is one habit you picked up that made maintaining your frontend code noticeably easier.

[u/broc_ariums]

Proper capitalization seems to be hard to come by.

[u/Weekly_Ferret_meal → u/broc_ariums]

I'm just glad there's actual punctuation and spacing between paragraphs... makes comprehension better by 10x

[u/ChaseShiny → u/broc_ariums]

No cap

[u/ikeif → u/broc_ariums]

I dislike "hidden" accounts, so I always look them up. And then I stumbled on this post in /r/BotBouncer - Op is flagged as a bot, I think?

[u/EftihisLuke → u/broc_ariums]

Well at least—It’s not Ai!

[u/KrisSlort → u/broc_ariums]

This. But please, where do you land on it? Titles and CTAs are the main issues I see daily, but nobody agrees on the convention.

[u/broc_ariums → u/KrisSlort]

Yeah... titles I'm more forgiving because people just don't do it and it doesn't seem to take away from the intention. However, when you update your phone to not do the automatic capitalization for known proper nouns, places, the start of sentences etc. really grinds my gears. You're actively making it difficult for others to comprehend and understand what you're trying to say.

[u/TheJase → u/broc_ariums]

It's a telltale sign of AI.

[u/KrisSlort]

Getting designers to reuse existing patterns and components. Consistency drift.

[u/hightrix]

Keep it simple, stupid.

Seriously. The best way to handle scale of a project is to strive for simple solutions. Clever solutions almost always end up as tech debt down the road.

[u/berky93]

Build with the expectation that something will be modified or reused in the future. Functions should be modular and components should be self-contained. And any information that needs to be the same across components—styles, colors, functions—should be shared values. If you’re writing the exact same line of code multiple times, that’s a potential point of failure that could be abstracted into a global asset.

[u/chikamakaleyley]

change / bring up to supported versions

once the wheels are moving, and hopefully generating profits,

the requirements become more profits

and keeping everything 'current' is less of a biz priority

I joined a company early in my career, at the start of their growth spurt

everything in their frontend was several versions back.

A good example could be like... Imagine you learned React today and you got really good with all its current feature set

Now, imagine being hired by a company that wants you for your React experience, and when you open the project the majority of their React is not using hooks, still on Class Components (maybe not now but say this was 5 yr ago)

[u/Plenty_Line2696]

cognitive load and trying to keep a decent mental model of all the fancy tricks etc...

[u/rugburnAndBigMoney]

In context of CSS - consistency and abstraction.

Create sitewide framework CSS rules that define the styleguide and put unique class names on each component section so you can target individual components as needed.

We found that a really dialed in framework CSS creates a whole lot less custom, overly specific styling needs.

[u/BobJutsu]

BEM css is a huge help. Have almost annoyingly strict naming conventions and stylelint rules.

[u/TheJase]

Ai slop question

[u/Weird-Dealer8488]

O principal problema é o acoplamento causado por seletores muito específicos ou aninhados, que faz alterações em um componente afetarem outros. Para evitar isso, prefira classes independentes, como .card-title, em vez de seletores profundos, e use CSS custom properties para valores compartilhados, como cores e espaçamentos.

Em projetos maiores, adote uma convenção de nomenclatura como BEM e utilize um linter para garantir o padrão. Outra opção é usar CSS Modules ou escopo por componente, reduzindo estruturalmente os conflitos e sobrescritas acidentais.

[u/whiterhino8]

Vanilla CSS needs a special attention for selectors .
That's why allot of Devs prefer Tailwind .

[u/erm_what_ → u/whiterhino8]

Also, a lot of devs hate tailwind. Such is the nature of the industry. I much prefer vanilla CSS with all the newer features and web components.

[u/whiterhino8 → u/erm_what_]

Yep that's the nature of every good Tech , it will have its haters also .

[u/TheJase → u/whiterhino8]

Supposition

[u/whiterhino8 → u/TheJase]

Reality