Ask HN: Hobby coding that doesn’t feel like work | Hacker News Reader

Ask HN: Hobby coding that doesn’t feel like work

47 points_benj75 comments

Hi HNers!

I’m curious about what practices you do when coding for fun?

For example, I’d use a different desk/space from the one I do my daily work, or work from a coffee shop, or from the sofa with a laptop. I’d also use different tools and languages.

But sometimes I find that even though I want to learn X or play with project Y being on a desk in front of a computer still feels like work.

Do you guys have some practices to make hobby coding fun?

Thx

View on HN

If it's for fun, it shouldn't feel like work. While others have some good suggestion, I'm going to ask the hard question: do you really want to be coding as a hobby?

The fact that you ask that question suggest you already code enough during work hours and you need to do something else after work.

Did you used to code for fun before it was your work? Then maybe it's a good idea to accept that you are not going to find in fun as long as your job is mainly coding (but it might become fun again if you don't mainly code as a job)

Did you drink the kool-aid that a developper is supposed to code for fun after work? Then maybe it's time to question that belief. A lot of professionnal developer that used to do that came to term with the fact that they'd rather do something else from their free time after coding all day.

After 10 years coding professionally, the only times I'm going to consider coding after work is as a mean to an end. There has been some occasions, but I wouldn't consider it "coding for fun". I wanted the results badly enough to dedicate some of my free time to getting that done despite not really enjoying the actual "coding" part.

Most of my free time is now used for anything but coding and I'm cool with that.

I’m still a little drunk off said kool-aid. I have a hard time distinguishing between work and play when it comes to hacking on my work environment.

The ideal fun coding session would emerge as a byproduct from a particularly successful work-related session. In reality, when coding during times I’m not being paid, I find myself with similar headaches to the workplace.

> If it's for fun, it shouldn't feel like work

I would be very careful with this sentiment. Pretty much any creative endeavour consists of parts that are not strictly fun. Coding in particular is filled with difficulty, tediousness, deep and wide thinking, etc. It's also the best creative tool that I know of, deeply engaging, very intelectually stimulating and fulfilling and lets you create things of extreme sophistication with very little limits. It's easy to rationalize your lack of motivation or discipline with a statement like: "I don't feel like doing it so it must not be something that I like" but creating an environment and a mindset to pursue fun, creative projects is not easy.

I could have phrased it more carefully : "If it's for fun and none of it feels fun and all of it feels like work, maybe it's time to consider you don't really want to do that for fun".

Of course any creative endeavour is not only fun, but I know the feeling of trying to do something "for fun" and it ends up feeling like work. Some people like to hustle, and that's fine. But just not doing it and finding something else you find fun instead is something to keep in mind.

I thought the "maybes" and several questions made it clear, but I'll state it regardless: there is no one-size fits all answer, and what I said is just a possibility that should be kept in mind. While it happens to be the one that worked best for me, I'm aware it's not the answer for everyone.

I would agree that the fun/work line is different for everyone, but I would also submit that a really low bar can also lead to an interesting hobby life over the long term.

I would consider that I give up on stuff pretty early when it becomes "not fun [1]." I'm in my 50's and I've been doing it for a long time. Since I'm always obsessed with something and each time I try something I get at least a little better, I have built up a pretty decent background in a lot of different areas and the amount I can accomplish before something becomes "not fun" gets to be more and more. I like to say I have a Metahobby: I collect hobbies.

I know this isn't a viable solution for most, but at least it's an alternative to feeling crappy about not finishing stuff. Also this:https://youtu.be/GHrmKL2XKcE

[1] For hobby projects. In my career, I know it's work, someone's paying me.

> do you really want to be coding as a hobby?

Honestly, most days I wish I had kept it only as that.

I second this. After all these years of programming it's become something I do for work with the exception of the occasional Arduino project (something mentioned more than once in this thread). As a matter of fact, I don't use computers all that much in my free time, that includes smartphones. I prefer to go swimming, cycling, lift weights, bird watching, have a drink down the pub, hang out with friends, than to stare at a screen in my free time.

It's OK to be a programmer for 40 hours a week and be anything else in the remaining hours.

I've started to play with microcontrollers and other embedded systems to create tools for performance artists.

It was a path from a very long soul searching effort. After some 18 years of professional career as a SWE I was really tired of anything related to programming. Finally I got to find something that actually motivates me to learn like it was when I was a young kid and programming was a fun and creative hobby.

I got into it after meeting so many incredible people in circus, dance and other performing arts and watching them struggle to make their dream projects come true due to a lack of technical software/hardware skills and lack of money to hire specialists for their projects. It gives me a lot of joy to get into their creative processes and dream together the possibilities, to push my skills to areas I had never worked with and to actually provide value to a community of artists, to be part of a creative process is also pretty magical to me.

Before this I went through a long lull of motivation to code anything outside of work, to study anything related to programming outside of work needs. I don't get any joy anymore from dreaming about apps and products that I could sell, they all just seem like a boring job on top of my job. Actually creating something related to the arts has been very, very refreshing to my soul.

Brilliant! What’s your tool chain in terms of hardware and libraries and so on look like?

I imagine your skill set is very rare in that community.

So far I've been using a lot of Adafruit components. Their 9-DOF breakout sensor board is really cool to keep track of small movements and I pair it with a WiFi enabled Wemos D1 for wearables.

For my current project I'm creating vests with the 9-DOF sensor + Wemos D1 that connect to a central server and this server is a central dispatch to communicate with other stage parts (similar to the architecture of the Philips Hue Bridge). I have an Adafruit HUZZAH32 to control some stage lights and other equipment (fog machines, etc.).

My idea is to enhance the job of the light designers, instead of them having to choreograph with the artists every movement they can instead select areas of the set that should be reacting to the artists movements and the light FX are triggered by those movements at the points the light designer select as focus for the part.

For programming I'm mainly using CircuitPython or MicroPython as I love Python for the ease of prototyping and iterating over, and there are libraries for all the components I've needed so far :)

Edit: I've also started to look into DMX to integrate these tools into the normal workflow of stage lighting/FX.

The emergence of things like MicroPython and CircuitPython have been an amazing game changer for what people can do in the embedded world. It's amazingly fun and feels different enough from day to day work to be fun.

Wow sounds really interesting, do you have anything online (code, videos, writing etc..) I would love to learn a bit more about this.

Playing with embedded devices (microcontrollers etc) has become my favorite coding-related hobby. The barriers to entry are hilariously low, the parts and tools are cheap and the code and documentation and tutorials are all free. At the end of the day, what you are left with is a physical thing that you can touch and which Does What You Told It To Do.

This - the use cases, end products and way of thinking about Arduino programming is so different that it doesn't feel like work at all.

If something feels like work, don't do it. If you want to do it anyway, do it with a level of detail and attention that you wouldn't be allowed on the clock. Write your code on paper, write assembler, make radical choices and do stupid things just because. Play with microcontrollers and build something physically real. Roll your own crypto and design your own networking protocols. Restrict the length of your functions, don't use the standard library, don't use anything but the standard library. Etc.

“Write your code on paper”

From time to time I write code/pseudocode on paper. It can be lots of fun! And it can help one to think about the concepts/semantics without the immediate stress that the code needs to run/compile ASAP.

I listen to music mostly when working on my own projects. I don't talk much about ongoing projects until I have already progressed very far, and when I do I'm deliberately keeping most of the plans and further ideas out of the conversation - I've realized that it's easy to reward myself too much by talking to someone so that afterwards a lot of motivation is not there anymore. I also try no to listen to suggestions too much since it does create some weird obligations in my mind. And, most of all, I try to not ever fall into the mindset of creating something with a specific goal in mind - I find that it's better to focus on the process itself and not on the final product. This means I often pivot ideas or completely abandon then in favor of something that became more interesting. Also, if you have that option, working in the same room with friends.

I have many hobbies from cars thru music, electronics and various computer-related stuff and I can say with certainty:

There will be always tedious parts, and there will be always unfun parts in anything worth doing. And it will always feel a bit like work.

About the only hobbies without that is passive ones like watching/reading and partially video games.

I did notice that I change what hobbies I engage depending on what I do in work (I work in ops where maybe 30-40% is coding, but I can go weeks coding, or not touching much actual programming at all), if I get some hard stuff to do in work I usualyl engage with other hobbies than programming and vice versa, when I've been stuck in meetings, planning and deploying at work I engage in programming more.

Keeping on one "stack" of libraries can help. I also have a template for new apps so I'm not held in minutia of writing logging again for the next app.

For me, it's game hacking (not online cheating, though!).

Such a diverse topic where you can do a lot of stuff, learn a lot of stuff (x86 assembly, reverse engineering, etc) and you can achieve things like free-cameras, spawning npcs, and understanding how the game actually works at a lower level.

With that, I like to experiment with different languages, I started doing it in C++, moved to Rust, but I also tried Zig and Nim, and since they are all 'system programming languages', and you can interact with FFI, it means you can do fun stuff.

One of my latest projects was to spawn lights in a certain games because I know some folks that likes to take photos inside games, and it was such a fun project to understand how the game manages entities, how to spawn entities and how to control them using an injected imgui.

It feels nothing like work and it's very rewarding.

+1 for game programming. I always wanted to learn ASM, it wasn't until discovering Super Mario World ROM hacking that it became fun and exciting enough to really dig into.

I enjoyed learning Clojure by playing https://spacetraders.io.

It's a game where you use their API to buy/sell ships, food, goods, structures for profit. You write code to plan trade routes, send out scouts, or whatever strategy you think will make the most money.

They reset the game every week and you can see how you're doing on a leaderboard. Good stuff!

That is so cool, great idea for a game and a platform for playing around. I just did a quick reading of an Emacs Lisp client, and I will look for your Clojure client.

I think programming always involves certain amount of frustration and a lot of learning so the problem is do you enjoy the learning?

For example I fimd it interesting to write HDL for the nand2tetris but I absolutely hate writing leetcode. But I also know many people enjoy writing leetcode so it's personal. You have to find something you are willing to learn so the fruatration is overcome by the joy.

It really depends on the nature of hobby coding.

I dedicate considerable time to "hobby coding", including open source, and once a topic - independently of the topic - reaches a certain depth, it becomes "work", and then, the only difference with the daily job, assuming a healthy work environment, is just the choice of the topic.

Documentation, test suites, orderly repository history are not just corporate frills. Once a project reaches a certain size, the developers are, in a way, users themselves. If an open source project is even mildly popular, chores will need to be performed, which includes taking care of the users (this is actually why a sad amount of open source projects ignores PRs and issues).

So if it feels like work, while I can't say with certainly, I believe that you've just experienced how hobby coding of a certain depth, is in real world.

Ultimately, the only answer I can give, is to choose the topic very carefully - one may find that the topic that really tickle them are fewer than one would think.

On this note, contributing to open source was the best "experience" I've ever gotten as it related to my day-to-day job of maintaining a large, but still growing, project.

I've been doing retro (Pico-8) indie game dev for about 2 years now, and I've been having a lot of fun with it. It's great because:

- It exposes me to entirely new classes of problems (pathfinding, graphics math, ai, etc), which are much more interesting than the daily CRUD nonsense.

- It forces me to branch out into adjacent interests and areas, like pixel-art, music composition, storytelling, etc.

- It provides a medium for self-expression.

- There's a well-trodden path for monetization (Steam, etc) if you're interested in that.

- It's fun to share with others! Nobody gives a shit about the Unix-y projects I typically work on, but people have actually been interested to hear about my game :)

This has really reinvigorated me. I do recommend checking it out if it sounds interesting to you at all.

Pico-8: https://www.lexaloffle.com/pico-8.php

This may sound stupid but what helps is:

* jump straight into the implementation * skip writing tests, CI or documentation * do not overthink stuff, write the simplest code that works * do not account for edge cases

This way, I spend most of my time just churning out code, which is different enough from day to day work .

Take up Emacs! You'll always have something you want to tinker with, and programming in lisps is a lot of fun. You get the added benefit that any tinkering you /do/ do benefits your programming UX.

* https://github.com/doomemacs/doomemacs * https://www.masteringemacs.org/book * https://www.gnu.org/software/emacs/download.html

Well, you're in luck, the Advent of Code[1] starts tomorrow night. There's always an interesting challenge, and you get to see how other people solved the problems in the threads on Reddit, etc.

Some people like to challenge themselves to use it to learn a new language, or do a different language each night. Some people write COBOL, assembler, you name it, there's someone trying to use it to solve the problems.

[1] https://adventofcode.com/

Well, that depends on what you mean by "fun!"

I'd like to make a distinction here between "fun" and "easy". For me, the best kind of fun is when I'm working on something really important to me. A better word might be "meaningful". Often, the work is really hard, and sometimes it's very frustrating! At those moments, if someone asked me if I was having "fun", I'd be hard-pressed to say yes, but still there is a kind of deep enjoyment that comes from it.

So I guess my suggestion would be to spend a few minutes figuring out exactly what you mean by fun. What are all the different elements that make it up? You mention "using different tools and languages", which would fall under "novelty". New things are typically a lot more stimulating than something we've been staring at for thousands of hours. (This is why travel is so refreshing!)

Programming definitely is work, whether you're doing it for money or for amusement. Communicating your ideas clearly to a computer is one of the most tedious possible kinds of human activity. But when it all comes together, it's also one of the most satisfying :)

The trick, I think, is to be moving in a direction (ie. a project or language) that is important to you. Then the work won't feel like such a drag. At the best of times, you will be making a tremendous effort, but it will feel effortless.

Well, it has to be fun. I caught the fun side projects bug when I first bought my Apple II (serial number 71, an early one) and wrote a simple Chess program that Apple gave away with their demo software cassette tape. I then wrote a Basic adventure game Valley of the Drawf that I gave away on America Online an a ton of people downloaded.

In another form: for the last 30 years, I have consistently spent about 10 hours a week of my own time (easy to do since I have just worked part time for almost my entire career) researching interesting tech, usually AI related. I write lots of small code experiments and a small percentage of these get cleaned up and used as examples in books I write. Again, this is all a lot of fun for me, and my wife participates by being my editor - something she also enjoys.

When to call it quits on hobby coding projects? When it gets to be what a friend of mine calls “negative fun.” An example: on Sunday I was scratching an itch writing something in Chez Scheme on my M1 Mac. It was a minor hassle getting everything installed but an hour later I hit a road block using bindings to sqlite3 - something that should be easy, but my compiled for M1/ARM Chez Scheme code kept trying to find and load Intel/X86 libraries. Could I have sorted this out? You bet I could but the process devolved into “negative fun” so I stopped.

My advice when coding for fun is to only take projects as far as you want to.

You don't have to do the final 20% if all you're trying to do is learn or prove to yourself that you can do something.

How much polish you apply to side projects is entirely up to you - you are the customer.

As others have suggested, embedded is a really nice area to get into, it is unbelievably easy to get started and it's different enough from day to day work.

Working on my hobby code does feel like work, but it feels like the parts of work that I enjoy.

The drudgery of my job comes from all of the stuff surrounding the code: tickets, meeting, code reviews, meetings, time cards, meetings. When I work on my hobby code, all of that goes away, and I can just code.

Sometimes it's frustrating. Sometimes I'll bang my head against a problem for a few hours, or a few days, then have a sudden "a-ha" that makes everything work. That is agitating in the moment, but the "a-ha" makes it worth it.

It also helps that the domains of my work and hobby code are completely separate. When I write code for fun, there's no enterprisey stuff going on. Right now I'm working on some code that generates character sheets for an RPG. There's no database, no Keycloak, hell, there isn't even a server. It feels a lot more like the toy code I wrote in college than the professional code that pays my bills.

If your hobby code doesn't bring you that kind of joy, you might be better off finding a different hobby? We don't need to chain ourselves to an IDE 24/7.

I can code for fun on my "work" desk, but I need to clear the space of work-related items: any tab, terminal session, Slack/emails (!), IDE window, note, Docker container, VPN,...

For me, what separates work from fun is being able to focus on what makes you happy. When you work, you have constraints on both time and quality so your fun projects should feel liberated from those constraints.

If you like software craftsmanship and elegance, work on a project you can pamper and grow. Make it extensively testable and tested, optimize hot paths, implement a full CI/CD pipeline with blue/green deployment, architecture for extensibility,...

Or if you are like me and have a million things you want to try, pick one topic/use-case and aggressively strip its surroundings to a bare minimum. For example, when I want to play with a frontend framework I emulate the backend by hard-coding JSON responses. (When I can't do that anymore, a FastAPI server with no DB is very good for quick iterations.)

For me it is painting and 3d-modeling. It rarely ends up in finished software, but I like to include some works in little and primitive games. Do something with it.

I often use browsers + javascript because you very quickly get a result. I have some pipelines to convert data formats ready though.

I am not a talented painter, but with some training everyone can put out decent images.

If I want to code something for myself, I just do it. I don't worry about whether it "feels like work" or it's "hobby coding" or whatever. It's a goal-oriented process, and I enjoy it, mostly.

My other hobbies are all basically the same, even if they aren't productive at all. There are parts I enjoy, and, parts I don't. I try not to worry about it too much, and just enjoy the parts I can, and work through the parts I don't to get to more of the good stuff.

I think it's really hard to separate "hobby coding" and "work coding" because they're both coding and I enjoy both. There's more stress for work coding because I'm being told I have to do things I don't agree with, or under a time crunch, but they're still both enjoyable. I don't think sitting at a different desk or location would change that.

I've just moved to two desks. One for work and one for play. Have used different machines for each since starting work but separate desk is new. No regrets.

I stay away from things I associate with frustration. E.g. no cmake. My home stuff used to be written in C and Python, now it's C, Lua, assembly and lisp. Tools that bring me joy that noone seems inclined to pay me to use.

Finally I write things I want as opposed to what anyone else wants. I really like a test framework I built years ago that noone else has any interest in. I like constraint solvers and expect to be the only user of my one. I've also spent days on very precise optimisation with no credible return on investment because perfect brings me more joy than adequate.

Feels just like playing computer games used to. Same feedback loop, same puzzle solving.

Most of my hobby coding is visual somehow. Shader art, procedural graphics, code-based infographics. Laser cutting and 3d printing. Ray tracers. Even microcontroller stuff, most of my projects with those involve blinkenlights.

It's more rewarding to me, and easier to show off to non-coders.

I find hobby coding to be more fun and rewarding when I do it with other junior developers. I used to teach coding and I've kept up with and continue to mentor some former students so if one of them has a project idea or they want to practice algorithms or learn some framework and they want some help I'll pair with them. Recently I went back out on the job market so as I study some more advanced algorithms I'll invite them to code with me.

I love teaching, I always have fun doing it. So the hobby coding ends up being fun and rewarding. Sometimes they'll come up with an idea that I quite like, so the aded outside creativity also makes it fun. Some ideas recently we might even release at some point, this also adds a bit of excitement.

I don't make a huge distinction, at least not in my front-brain.

I just choose a low-pressure project, but hopefully valuable to me or someone. Usually some kind of convenience or automation.

I have some "dashboards" with different key information on them. I like building those, scraping data from various sources, and winding up with this cool spot to look at everything.

I want to get into displaying things in the terminal, maybe the same dashboards. I really like running things on the command line; I've felt that way more than half my life now, hasn't gone away. Not sure why I've done so little programming for it.

Nothing important is purely fun. You'll find the "work" in the thing, and your brain will get testy.

I've found great success in taking my coding skills and applying it to other hobbies. For example:

- I built a nutrition app during the pandemic so I could learn more about nutrition and track my activity.

- I started practicing Qi Gong and Yoga and I hacked together a little handheld controller so that I could learn the movements more efficiently. I used it to rewind/fast forward, A/B repeat sections, speed up/slow down, etc.

- I built a trail companion app for a backpacking trip that helped me plan my hikes.

- I made an app for my grandma to share photos with her on her Kindle device.

I think when you apply coding to other things you're passionate about it brings new life to it.

I choose topics that are deliberately not work-like.

For example, one of my favorite online compos, js13kGames, is about writing small video games really fast. You pretty much have to reject all of the "best practices" from your typical working environment to have a shot at this: can't use established libraries (size restriction), very little time to do proper testing and CI, code compactness is more valuable than CPU cycles... The entire mindset is completely different.

For a person working in gamedev all of this would probably feel like work. Lucky bastards.

I recently made a web app for myself as a hobby coding project. Part of what made it tolerable was not doing any of the stuff that makes the web apps I make at work more tedious, like audit logs or even an account system. It really hammers home the idea that it's _for me_ above all else.

>being on a desk in front of a computer still feels like work

Ultimately I couldn't get past this, even for gaming. I got a Steam Deck instead and mostly just use that and/or a tablet with a holder in my bed now.

I'm in the process of making a digital version of a known dice/board game. Idea is to create a main unit that controls the game state with 5 or more handheld controllers.

Think quiz/reaction time/mario party type minigames

Doing pcb design, soldering, network communication and state management between microcontrollers, 3d-modeling and printing, (to protect the bare pcbs), etc. is new to me. Also creating expansions or twists on existing games keeps my mind going and does not feel like work.

This reminds me of me playing TIS-100, a cool game by Zachtronics where you need to program a small parallel CPU in assembly (see https://zachtronics.com/tis-100/ - btw it's currently on sale at GOG, Steam and HumbleBundle).

At one point in the game i had to implement a sorting function or something like that and i noped out because it very suddenly felt like work.

God the endless struggle of a Zachtronics game. I'm in love with this, but it hurts me to play.

> For example, I’d use a different desk/space from the one I do my daily work, or work from a coffee shop, or from the sofa with a laptop.

If you work at home you should invest in a good office chair set up properly. I did, a bit too late. You should then use it for fun too. My solution was separate logins for each use and have distinctive desktops, which tricks your brain into feeling it's somewhere different.

usually i make silly little games like tetris, 2048, cgol, or attempt simple leetcode challenges, or build userscripts to automate web tediums. To me it feels like solving a sudoku (fun) rather than studying for a math exam (boring). But the real secret sauce to fun programming is to build your own ideas. You might think of an old game you've played, and wonder, can I build that? Yes you can.

We have an open-source React-based framework called "refine" for easily building CRUD apps like Admin panels and Internal tools. It is headless by default and supports Material UI, AntDesign, Chakra UI, and Mantine.

You can build your side CRUD project easily.

Repo: https://s.refine.dev/github-repository

I will get into a free form coding mode to get the thing working as fast as possible, which leaves you with long methods, poorly named variables, and hard coded settings, basically lots of code that would never survive a PR review. Getting out of the "someone else is going to look at this" mindset can make it more creative, faster, and more fun.

I do side projects for myself such as web scraper, etc.. I enjoy hobby coding because I don't do:

1. sprints 2. minimum documentations 3. no test cases 4. only one git branch 5. run on barebone VM

I don't want agile + code review + PRs + git merges + container. I want the least amount of friction between me finishing typing code to running that in prod.

Try to make a CRUD app with API and SPA. Then it's both fun and it's also for real world apps you'll build.

I’m glad that you still find SPA and CRUD apps fun! That is my day job and I’m in the, idk, two figures CRUD app during my career? :)

Yeah, i think it's about what kind of CRUP apps is fun that's more important.

I work from home. I have a separate work computer than my personal computer which are in different rooms. When I code for fun, I make mods for video games. I get to use the mods I make when playing which is a nice bonus. My mods are played online so I also get to see others use them which is satisfying.

No one mentioned it here, but make sure you are using a personal computer for this and not your work computer so you don't get into trouble with your employer. This is well-known advice, but there's always a newbie learning something for the first time.

For me it's easy as programming is only a hobby, not my day job.

Instead of using different tools and setup, try picking different projects or domains you love. For example, if you're a web developer by trade you may write compilers, games, or text editors for fun.

When I code for fun I often go to tinker with a Go project: either a little life simulation, or a library to communicate with a REST API I use, or whatever thing strikes me. Go tends to be the default "fun" language for me.

Hi there! Can you talk about your little life simulations?

I haven't worked on them in a while to be honest, but for many years I worked on a small snail simulation in my spare time and blogged about it[0]. The project had gone through JS, PHP, and later Go iterations. I also spent a few weeks playing around with implementing an approach described in this paper on open ended simulations[1]. Go was not the best language to choose for this project[2], but it definitely counted as fun hobby coding for me.

[0] https://liza.io/categories/snails/

[1] https://www-users.cs.york.ac.uk/susan/bib/ss/nonstd/ecal11-1...

[2] https://liza.io/roee-self-modifying-go-simulation-experiment...

Recreational mathematics - you usually don't end up with large codebases and most is just a single file/single use code to test some number theory hypothesis or find an integer with some properties/find a counterexample.

I have my main TV hooked up to a mac mini and do most of my hobby coding there. None of my work accounts are activated on that mac. I also do most of my HN reading there. Makes a good separation.

I find competitive programming pretty fun. If you want to learn X, you can start solving problems with X instead of a language you know. I use codeforces and used to solve problems on Project Euler as well.

Advent of Code will start in a couple of days.

I built vintage computer 486/MS-DOS and picking up C programming, low level graphics. It's very different from my webdev job. Feels fun and completely useless, just like when I was a teenager!

Sometimes I get a little wild and put ice in my coffee to drink it faster

>I’m curious about what practices you do when coding for fun?

adventofcode.com

Good time to ask this

I don't share my code, so I code however I like, generally not worrying about conventions or what tool is right for the job.

It’s almost time for Advent of Code. That’s always fun!!

Common Lisp is fun!

I’ve been playing with Scheme and I’m loving it!!

You might enjoy some of the little projects in the second Common Lisp book I wrote that you can read on my web site https://markwatson.com/books/lovinglisp-site/

Most of the book is built around fun side projects I have done.

Oh hi! Yes, it was your book in fact that inspired me to work with Common Lisp! Thank you so much! Your book is a work of art.

Thanks! I am releasing an updated version in the next month, and I hope you enjoy the additions.

well do something else than coding, it's fun too

Reply on news.ycombinator.com