5 ms·

I very first got into programming by trying to fix a graphic adventure game that somehow was released with a pretty clear syntax error. This was back in the VIC

I very first got into programming by trying to fix a graphic adventure game that somehow was released with a pretty clear syntax error. This was back in the VIC-20 days. Really, for the first while it was about the games ... tweaking them, altering them, and later writing them. The actual programming was always a means to that gaming end back then and not the end in itself. So in that sense I can completely relate to where you're coming from. Over a couple years of that, it started to dawn on me that the programming itself had a power and interest all its own worth pursuing. But I think if it was dropped in front of me as something I ought to do, no matter how dressed up in "fun" it was, it would have set off my non-conformist predispositions a little too much.

em-bee 16d ago
but even today, don't you write code to solve a problem? to fix a bug in an application? to achieve something? feels to me not that different. just that the targets are no longer games but other kinds of applications.
- sbuttgereit 16d ago
  Of course. But still it's not the same. What's different is that I found the journey can be just as interesting and engaging as the destination. I read papers, books, and even spend time around here... not because the solutions require it, but because I care about the craft and the process itself. So yes, the resulting solution is the prime mover, but the process of finding the solutions is no longer just a means to the end, it's part of the motivation of being involved in the profession at all.