CSS: Our best practices are killing us
slideshare.net
CSS: Our best practices are killing us
1–10 of 54 posts
Re: CSS: Our best practices are killing us
#2This seems like it's interesting but could really use some audio. This definitely comes off as a slide deck that someone used in a presentation and wasn't meant to just be read. Does anyone have a video version of this by any chance?
Re: CSS: Our best practices are killing us
#3I wish she'd write a book.
Re: CSS: Our best practices are killing us
#4So the prime example of what not to do is the sidebar/h3 example. Then the example for what to do is a simple example from Facebook.
How about showing us how to actually solve the first problem?
For anyone wanting to know more about this presentation, check out her Object Oriented CSS: https://github.com/stubbornella/oocss
Re: CSS: Our best practices are killing us
#5This seems like it's interesting but could really use some audio. This definitely comes off as a slide deck that someone used in a presentation and wasn't meant to just be read. Does anyone have a video version of this by any chance?
Some slides towards the end, i.e. 5 1 8 unique numbers one match with http://www.youtube.com/watch?v=j6sAm7CLoCQ
Re: CSS: Our best practices are killing us
#6I hate asking to be spoon-fed, but I find it exceptionally difficult to glean anything from context-free slide decks posted to SlideShare. This deck was clearly intended to augment a presentation -- where is that archived?
Re: CSS: Our best practices are killing us
#7The best practice for CSS is to continuously rewrite it. Don't be lazy, just do it.
Re: CSS: Our best practices are killing us
#8The best practice for CSS is to continuously rewrite it. Don't be lazy, just do it.
What if you already have a bunch of custom controls that are common to your app? I'm not suggesting not investigating more efficient selectors or better css practices to target multiple browsers easily, but once you have all the knowledge built up in one place, what do you gain by rewriting it?
When I start a project, if I'm working from scratch I usually rewrite a lot of the css every day, just to achieve the look I'm going for. Once I standardize some things like how text flows, some layouts, and forms, it's time to develop a nice list of css classes you use frequently and tinker with them as needed. Endlessly rewriting css gets you nowhere.
Re: CSS: Our best practices are killing us
#9I hate asking to be spoon-fed, but I find it exceptionally difficult to glean anything from context-free slide decks posted to SlideShare. This deck was clearly intended to augment a presentation -- where is that archived?
Probably this one:
http://www.webstock.org.nz/talks/speakers/nicole-sullivan/cs...
I attended the talk and the workshop. What is interesting is that it genuinely challenges. Some CSS designers who I really respect did not 'buy in' to her theory even after spending a day with her. However, as a programmer, who has since used the OOCSS in a context 'for real' I found that it does live up to its promise in practice (unlike the CSS 'semantic html/best practice' story, which sounds great in theory but so often becomes spaghetti in practice)
Re: CSS: Our best practices are killing us
#10She says we shouldn't blame the language, but how much of this is because CSS eschews Composition for (incomplete) Multiple Inheritance? And how much of the extra code is an effort to avoid bugs because layout properties are non-orthogonal?
At what point do we decide that it's not that "you're doing it wrong", but that there were actually some design choices that, in retrospect, maybe weren't such a good idea? I'd say that when we have other languages that compile into the language just to overcome these issues (CoffeeScript,Less,SASS,etc.), we've about reached that point.