Dice

The Algorithms recently flung this article my way which crystallized the idea of "serious leisure" for me. It brought to mind Dungeons & Dragons and Role-Playing Games, but it also made me think about my experience with Software Engineering. The study's hypothesis is that involving yourself in an intense hobby over the course of years/decades has benefits beyond simply relaxing and having fun. It's about skill development and mastery, a sense of accomplishment, and a sense of community.

I played D&D intensely throughout my teenage years. I get what the article is saying.

Game Controller

It also occurred to me that I've been doing "Software Engineering" for much longer: almost 40 years now. Of course back then, as a kid, I just called it "coding" and on the surface it was usually about creating video games. But as I look back, I see that where I really got the satisfaction was learning how to tell the computer to do something complicated. I'm sure self-esteem and dopamine also had something to do with it.

I'm lucky that Software Engineering as "serious leisure" eventually led me to a successful career. There are not a lot of professional D&Ders out there.

Read the rest of this entry ...
§1446 · February 9, 2026 · Life, Software, Technology, Tips · 1 comment · Tags: , , , ,


[clipart]When I started programming it was on the Commodore 64 (uh oh, you know this is going to be a long story - go take a piss first). I started with Basic and then eventually moved to assembly language to try and write a Bard's Tale clone with a friend. We got pretty far. I just came across the notebooks where I had scribbled all those assembly routines too - great times! But by the time we got close to having something we could call a game, Commodore had lost the battle and the IBM PC clone market was taking off. Different instruction set, different hardware and capabilities. Doh! Read the rest of this entry ...

§850 · May 7, 2010 · Software, Technology, Web · 4 comments · Tags: ,


Why don't Comp.Sci professors give out extra credit to students who submit patches to open source projects? I'm sure profs could come up with some scoring system based on the complexity of the patch and the amount of effort involved (size of code base, subject matter, etc). This would get the student out of pure theoretical assignments and give them real-world experience with software problems. About the only challenge I see with this idea is that a student may get 90% of the way through working on a patch and someone else (outside the school) comes in and scoops them. For this, a prof could still give some points for 'trying' if there was proof of the work.

§488 · August 15, 2008 · Software, Technology · Comments Off on Patches For Credits · Tags: ,