m o t i o n l e s s
m o t i o n l se s
m o t i o n sle s
m o t i osn l e s
m o t i so n l e s
m o t si o n l e s
m ost i o n l e s
m so t i o n l e s sm o t i o n l e s s om t i o n l e s s o m t i no l e s s o m t ni o l e s s o m nt i o l e s s o m n t oi l e s s o m n oti l e s s o m n o t lie s s o m n o lt i e s s o m n o l it e s
I've been tracking my listening habits with last.fm since I was in high school. As I'm about to turn 30, it's nice to be able to look back on almost my entire adult life – to see how I've changed and how my tastes have changed with me.
One thing I've been enjoying about working as a technical writer is that the minute-by-minute texture of the work feels right. Something about formatting text, faffing about with SVGs, trying to rewrite a sentence more clearly... it's just enjoyable in itself, and I feel at home with it.
...Working as a programmer was very much not like that. There's something in the rough vicinity of professional dev work that I do like, which I could probably label as 'iterative hobbyist tinkering with websites'. I like working on something with a strong visual component, and I like to be inside of a fast feedback loop, and I'm mostly interested in just somehow bodging through until it works. I'm not very interested in either the computer-sciencey side of programming — data structures, algorithms — or the software-engineerey side of making things run reliably at scale in a maintainable way. So maybe it's not surprising that the minute-by-minute texture of professional programming was just... kind of bad. Occasional fun bits when I got into something, but the background experience was not fun.