This is one of my all time favorite web pages.
I first read it back in 2002 while managing my first big web project at Project for Public Spaces.
I still think about it a lot, to this day, and try to email it around to people who are new to bug tracking as often as I can.
I can’t exactly put my finger on why I like it so much, but I think it’s that the writing and examples are so crisp and clear (thanks Joel!). And I feel like reading it embedded some really good work habits deep into my brain.
I still, to this day, feel proud every time I submit a bug report in the format suggested here:
* steps to repeat
* what you expected to happen
* what happened instead
I know that’s geeky and weird, but it honestly does fill my heart with warm happiness to think about those steps and use them.
The best explanation yet if how utterly out of date my skills are. LAMP generation.
Processing seeks to ruin the careers of talented designers by tempting them away from their usual tools and into the world of programming and computation. Similarly, the project is designed to turn engineers and computer scientists to less gainful employment as artists and designers.
Variables and loops.
At the early stages of teaching programming for this semester…thinking of how the basic metaphors can be extended.
What are the variables in my life?
How does one explain loops…what are they?
Perhaps my answer to the second
1. Where to start.
2. Where to finish.
3. How to get there.
Practical stuff for programming…but also powerful outside of that context.