4
theuser
14d

Junior frontend here, I really fucked up with SCSS nesting. It's a nightmare to go back and maintain or extend the UI. I really should go back and sort this shit out. Some parts of the hierarchy even contains pointers which I phased out long ago, but somehow it still works.

Let this be a lesson. -_-

Comments
  • 0
    Two levels of nesting tops, or you'll create a hellhole.
  • 2
    @norman70688 I won't tell how deep it goes, it just seemed like a good idea at the time..
  • 2
    Have you looked into BEM style?

    It at least mitigates the damage that this sort of thing can do and it makes for a more semantic structure in terms of both naming and file setup.
  • 1
    BEM ftw!
  • 1
    @Charon92 I have never used it no, probably should've used it from the getgo. Large refactoring is not an alternative because of time contraints.
  • 0
    5 levels here, still pretty manageable (putting emphasis on vertical order) u_u
  • 1
    @h4xx3r I'm about in the same ballpark. I found it worked great when I initially laid out the elements according to the mockup. The hierarchy perfectly mirrored the HTML hierarchy, but once the choppin' and the changin' started, the structure started sliding down the shitter.
  • 0
    @theuser yep, that requires extra care
Your Job Suck?
Get a Better Job
Add Comment