sketching

One idea I've considered, as a means of sharpening my imagination, is getting into sketching or painting.

The features of a Lisp make sketching and exploring easier, and that's part of understanding the problem.

By drawing/sketching you make it easier for you to visualise all the points and then make a solid counter argument.

There is an article by the Public Domain Review[1] where they present an old book about sketching on a blackboard.

You do it as a way of sketching the depth of a problem I think, not much more.

With all due respect, I just looked at your pictures and it doesn't look like you're sketching right.

We've already began the planning and sketching stages, but we want to get our hands dirty soon.

The reason people don't like interviews is simple: We're trying to figure out a skill (programming) by proxy (simple exercises and whiteboard sketching).

If you have no knowledge right now, start by sketching in English.

It's good enough for varying my pen strokes in a sketching app.

At the moment I'm sketching a trip that includes Etihad's new first class apartment, Qatar business class and Singapore's first class suite.

It's a collaborative sketching tool; not a collaborative mockup tool.

And, really, enabling sketching extensions is one of the most important features of any "scalable realtime processing" tool, in my opinion.

"Mockups" isn't really the right term here as far as I'm concerned – it implies high fidelity, whereas this is a tool for rapid, low-fidelity idea sketching.

I'm not exaggerating at all, it took me literally one day of sketching with Betty Edwards' book to go from "I can't draw, it must be genetic" to "I can draw anything right if I look hard enough".

Sketching allows you to learn that skill quickly and easily, while pixeling has so many distractions that IMO it's almost impossible to learn from pixeling alone.