Writing contextual CSS ->
Organization and structure of CSS might be one of the largest difficulties for beginners as for professionals in web design. It is hard writing good CSS. It is somewhat easer with pre-processors (SCSS, LESS, Stylus), but they'll only give you the tools: it's up to you how to use them (what I can't do without is the
Changing perspectives and doing the crazy thing ->
Like it or not, but tech people often have their way of doing things. Together we've drunk the same drink telling us that "this is the way of doing things", and we repeatedly create products where we incorporate this way of thinking, which go generations back (slight over-exaggeration).
A symbol for sex ->
"What is an appropriate symbol for sex?". The question I asked myself some time ago might seem somewhat trivial at first, but when you dig deeper, it reveals a bunch of sub-questions and scenarios.
I don't like counting hours ->
In the freelance and consultancy business, you often charge per work hour. It's the rate, and then you estimate the total number of hours for a project. The estimate is ... an estimate. Estimates are seldom correct, even for senior consultants. I'm not ashamed to say that I often do an initial estimate, then almost doubling it when responding to the client. One thing I've learnt is that it's immensely better to land a project below the estimate than above.
On Scala ->
A friend and colleague of mine is boasting a lot about Clojure and it's productive capabilities. But I really can't wrap my head around the LISP syntax. Perhaps it's a matter of putting in time.
Tags and class names – on building flexible markup ->
It is said your markup should be clean and semantic. What does that mean, exactly? As few tags as possible? The correct tags for the job? Few or no ID and class attributes? At least that's been the main formula for a while now. Littering ID and class attributes over your markup has been frowned upon. But what does the alternative mean?