Neither. There are great resources for learning CSS out there, books blogs posts. I was thinking recently that working effectively with CSS is to work with 'knowing' browser behavior. Knowing the cycles of load, layout, paint. delay etc. We are wrestling with multiple vendor approaches to visualizing content and that is often seen as a kind of war with all kinds of forces. Network speeds, loading sequence, display resolution etc. It's messy and complex and the css rules are "advisory" or hints for the browser.
I suspect that some coders like dry and hard guaranteed outcomes of their code. CSS lives in a messy world of drama and negotiation of forces outside the code.
I think a stick-man cartoon of CSS vs browser might be a better investment of time. :)
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Neither. There are great resources for learning CSS out there, books blogs posts. I was thinking recently that working effectively with CSS is to work with 'knowing' browser behavior. Knowing the cycles of load, layout, paint. delay etc. We are wrestling with multiple vendor approaches to visualizing content and that is often seen as a kind of war with all kinds of forces. Network speeds, loading sequence, display resolution etc. It's messy and complex and the css rules are "advisory" or hints for the browser.
I suspect that some coders like dry and hard guaranteed outcomes of their code. CSS lives in a messy world of drama and negotiation of forces outside the code.
I think a stick-man cartoon of CSS vs browser might be a better investment of time. :)