View high resolution
rain north of las vegas, nm.
got poached. so good on you, L., for poaching someone to a university position. not sure who the unicorn is in this case.
the summer has been marked by all of these questions about coding and craftsmanship and science, from different people and different places. some of them want an easy answer - craftsmanship is kanban or agile or whatever. it’s just wanting to write elegant code. it’s picking the buzzword of the day and hoping you’ve picked the one they like. and, man, you better say how passionate you are about coding.
but i don’t come out of that place. my background comes from languages, design, printmaking and ceramics, watershed modeling. and some of those things have an understanding of craftsmanship that is different.
i had a thought, unfinished, about process and markmaking and code north of las vegas. one of my favorite projects is still a little bit of fortran that generated an irregular landcover raster using fractals. i always come back to that when i think about code and craft. it was iteration, sure, but more about refinement. simplification. using the tools effectively. making a useful thing. the markmaking isn’t always so clear with code - you pull that piece of paper off the block and you know what have. good run, bad run, you know it as soon as you see it. and those fractal glitches were pretty good.
i don’t know.
i know i don’t like having the conversation about code and craft and science dominated by cs folks. there are research coders that do good work. there are cs coders that really don’t. way of the world, right.
i’m going to have a think, possibly while headed north again, probably while hiking up a mountain.