AlexMcP
Joined 15 years ago
Joined 15 years ago
tr
tr td
tr td a
could be LESS unrolling a nested bit: tr {
td {
a {
OR... could just be how people write CSS.I mostly ignored by-domain grouping in my queries, but there is a host of analysis you could do that would get into the modeling portion of data science, teasing our correlation and trying to find 'groups' or styles' of CSS that is written on a site. I had only so much time ;-)
I also did a web perf report that is not fully edited or ready for consumption, but does not that 54% of sites I ran Google Page Speed Insights against didn't compress all of their CSS assets. (Same sample of domains)
select count(*) from property
where value similar to '%!important%'
=> 177119Immediate reactions from me include "Should my company get on board with something like this?", "I wonder what the equity split is like", "Could there be a platform for voting up ideas to work on based on customer validation?", "Should I build that platform to bubble up ideas with a verifiable userbase?"
The payoff, however, is if more features or behaviors were in the pipeline (and when aren't they?). This really sets you up to gracefully manage more complexity by having sensical places to put more code, instead of writing a few more $(document).ready callbacks to ship something on time.
Backbone.js might not be the right tool for the contrived example, but I've come to expect a sacrifice of real-world applicability for smaller, digestible chunks. That the synthesis is up to you is ok, I think.