llm/fa6df919-50f4-440a-804d-6a9d3e9721d8/topic-18-1fe0e319-f1d3-4ad2-add0-5b160a222d3c-input.json
The following is content for you to summarize. Do not respond to the comments—summarize them. <topic> Fun Definition Debate # Fundamental disagreement about what makes programming enjoyable - the process of writing code versus seeing results and solving problems </topic> <comments_about_topic> 1. I don't know but to me this all sounds like the antithesis of what makes programming fun. You don't have productivity goals for hobby coding where you'd have to make the most of your half an hour -- that sounds too much like paid work to be fun. If you have a half an hour, you tinker for a half an hour and enjoy it. Then you continue when you have another half an hour again. (Or push into night because you can't make yourself stop.) 2. What you consider fun isn't universal. Some folks don't want to just tinker for half an hour, some folks enjoy getting a particular result that meets specific goals. Some folks don't find the mechanics of putting lines of code together as fun as what the code does when it runs. That might sound like paid work to you, but it can be gratifying for not-you. 3. The difference is whether or not you find computers interesting and enjoy understanding how they work. For the people who just want to solve some problem unrelated to computers but require a computer for some part of the task, yes AI would be more “fun”. 4. I don’t find this to be true. I enjoy computers quite a bit. I enjoy the hardware, scaling problems, theory behind things, operating systems, networking, etc. Most of all I find what computers allow humanity to achieve extremely interesting and motivating. I call them the worlds most complicated robot. I don’t find coding overly fun in itself. What I find fun is the results I get when I program something that has the result I desire. Maybe that’s creating a service for friends to use, maybe it’s a personal IT project, maybe it’s having commercial quality WiFi at home everyone is amazed at when they visit, etc. Sometimes - even often - it’s the understanding that leads to pride in craftsmanship. But programming itself is just a chore for me to get done in service of whatever final outcome I’m attempting to achieve. Could be delivering bits on the internet for work, or automating OS installs to look at the 50 racks of servers humming away with cable porn level work done in the cabinets. I never enjoyed messing around with HTML at that much in the 90s. But I was motivated to learn it just enough to achieve the cool ideas I could come up with as a teenager and share them with my friends. I can appreciate clean maintainable code, which is the only real reason LLMs don’t scratch the itch as much as you’d expect for someone like me. 5. See, I do though. I enjoy the act, the craft of programming. It's intrinsically fun for me, and has been for the 25 years I've been doing it at this point, and it still hasn't stopped being fun! Different strokes I guess 6. Oh I totally agree! I have a lot of fun chatting with friends/coworkers who are super into programming as an art and/or passion. I just was pushing back on the “you aren’t into computers if you don’t get intrinsic joy out of programming itself” bit. 7. This 1000x! I had a bit of an identity crisis with AI first landed and started producing good code. “If I’m not the man who can type quickly, accurately, and build working programs… WHO AM I?” But as you pointed out, I quickly realized I was never that guy. I was the guy who made problems go away, usually with code. Now I can make so many problems go away, it feels like cheating. As it turns out, writing code isn’t super useful. It’s the application of the code, the judgement of which problems to solve and how to solve them, that truly mattered. And that sparks a LOT of joy. 8. Fewer things sound less interesting to me than that. 9. I think, for a lot of people, solving the problem was always the fun part. There is immense pleasure in a nice piece of code - something that is elegant, clever and simple at the same time. Grinding out code to get something finished - less fun… 10. I think this is showing the difference between people who like to /make/ things and those that like to make /things/. People that write software because they see a solution for a problem that can be fixed with software seem to benefit the most of LLM technology. It's almost the inverse for the people that write software because they like the process of writing software. 11. I think you misunderstand the perspective of someone who likes writing code. It's not the pressing of keys on the keyboard. It's figuring out which keys to press. Setting aside for the moment that most loops have a dynamic iteration count, typing out the second loop body is not fun if it's the same as the first. I do code golf for fun. My favorite kind of code to write is code I'll never have to support. LLMs are not sparking joy. I wish I was old enough to retire. 12. I like both the process and the product, and I like using LLMs. You can use LLMs in whatever way works for you. Objections like the ones in this thread seem to assume that the LLM determines the process, but that’s not true at present. Perhaps they’re worrying about what might happen in future, but more likely they’re just resisting change in the usual way of inventing objections against something they haven’t seriously tried. These objections serve more as emotional justifications to avoid changing, than rational positions. 13. I yearn for the mindset where I actively choose to accomplish comparatively little in the brief spells I have to myself, and remain motivated. Part of what makes programming fun for me is actually achieving something. Which is not to say you have to use AI to be productive, or that you aren't achieving anything, but this is not the antithesis of what makes programming fun, only what makes it fun for you. 14. LLMs are really showing how different programmers are from one another i am in your camp, i get 0 satisfaction out of seeing something appear on the screen which i don't deeply understand i want to feel the computer as i type, i've recently been toying with turning off syntax highlighting and LSPs (not for everyone), and i am surprised at the lack of distractions and feeling of craft and joy it brings me 15. I find it interesting how you take your experience and generalize it by saying "you" instead of "I". This is how I read your post: > I don't know but to me this all sounds like the antithesis of what makes programming fun. I don't have productivity goals for hobby coding where I'd have to make the most of your half an hour -- that sounds too much like paid work to be fun. If I have a half an hour, I tinker for a half an hour and enjoy it. Then I continue when I have another half an hour again. (Or push into night because I can't make myself stop.) Reading it like this makes it obvious to me that what you find fun is not necessarily what other people find fun. Which shouldn't come as a surprise. Describing your experience and preferences as something more is where the water starts getting muddy. 16. I enjoy coding for the ability to turn ideas into software. Seeing more rapid feature development, and also more rapid code cleanup and project architecture cleanup is what makes AI assisted coding enjoyable to me 17. Is the manual coding part of programming still fun or not? We have a lot of opinions on either side here. I think the classic division of problems being solved might, for most people, solve this seeming contradiction. For every problem, X% is solving the necessary complexity of the problem. Taming the original problem, in relation to what computers are capable of doing. With the potential of some relevant well implemented libraries or API’s helping to close that gap. Work in that scenario rarely feels like wasted time. But in reality, there is almost always another problem we have to solve, the Y%=(1-X) of the work required for an actual solution that involves wrangling with mismatches in available tools from the problem being solved. This can be relatively benign, just introducing some extra cute little puzzles, that make our brains feel smart as we successfully win wack-a-mole. A side game that can even be refreshing. Or, the stack of tools, and their quirks, that we need to use can be an unbounded (even compounding) generative system of pervasive mismatches and pernicious non-obvious, not immediately recognizable, trenches we must a 1000 little bridges, and maybe a few historic bridges, just to create a path back to the original problem. And it is often evident that all this work is an artifact of 1000 less than perfect choices by others. (No judgement, just a fact of tool creation having its own difficulties.) That stuff can become energy draining to say the list. I think high X problems are fun to solve. Most of our work goes into solving the original problem. Even finding out it was more complex than we thought feels like meaningful drama and increase the joy of resolving. High Y problems involve vast amounts of glue code, library wrappers with exception handling, the list in any code base can be significant. Even overwhelm the actual problem solving code. And all those mismatches often hold us back, to where our final solution inevitable has problems in situations we hope never happen, until we can come back for round N+1, for unbounded N. Any help from AI for the latter is a huge win. Those are not “real” problems. As tool stack change, nobody will port Y-type solutions forward. (I tell myself so I can sleep at night). So that’s it. We are all different. But what type of acceleration AI gives us on type-Y problems is most likely to feel great. Enabling. Letting us harder on things that are more important and lasting. And where AI is less of a boost, but still a potentially welcome one, as an assistant. 18. I derive the majority of my hobby satisfaction from getting stuff done, not enjoying the process of crafting software. We probably enjoy quite different aspects of tinkering! LLMs make me have so much more fun. 19. I do have productivity goals! I want to spend the half hour I have on the part I think is fun. Not on machine configuration, boilerplate, dependency resolution, 100 random errors with new frameworks that are maybe resolved with web searches. 20. Which is fine, because those things are what makes programming fun for you. Not for others. 21. What about the boring parts of fun hobby projects? 22. I enjoy noodling around with pointers and unsafe code in Rust. Claude wrote all the documentation, to Rust standards, with nice examples for every method. I decided to write an app in Rust with a React UI, and Claude wrote almost all the typescript for me. So I’ve used Claude at both ends of the spectrum. I had way more fun in every situation. AI is, fortunately, very bad at the things I find fun, at least for now, and very good at the things I find booooring (read in Scot Pilgrim voice). 23. You just described my experience exactly. Especially the personal side project time as a parent. Now after bed I can tinker and have fun again because I can move so much more quickly and see real progress even with only an hour or two to spend every few days. 24. Yes! I feel like so many people really fail to appreciate this side of things. Heck, Suno has gotten me to the point where I play so much more piano (the recording -> polished track loop is very rewarding) that not only did I publish an album to Spotify in my favorite genre, of music that I’m really happy with, I’ve also started to produce some polished acoustic recordings with NO AI involvement. That’s just because I’ve been spending so much more time at the piano, because of that reward loop. 25. The important difference is the reduction in boilerplate, which allows programs to be written with (often) significantly less code. Hence the time savings (and fun) spoken of in the original article. This isn't really a new phenomenon. Languages have been adding things like arrays and maps as builtins to reduce the boilerplate required around them. The modern languages of which we speak take that same idea to a whole new level, but such is the nature of evolution. 26. I'm sorry, "upskill"? The roles you mentioned don't require any more advanced skills than those required for software development—just a different set of skills. And an IC is not "left behind" if those roles don't interest them. What a ridiculous thing to say. A systems analyst or product manager is not a natural progression for someone who enjoys software development. 27. I was just getting pretty sick and tired of programming, instead now AI can write the code down while I do the fun things of figuring out how shit works and general device hacking + home projects 28. This is why web development stopped being fun: developers that cannot manage or train people and instead hope garbage like jQuery will simply act as a surrogate parent. 29. I still write vanilla PHP with SQL queries. And with all the modern PHP features, things have never been faster or more joyful to work with. I honestly feel bad for people who fall victims to complexity. It burns you out when all you need is to keep things simple and fun. Life is too short for anything else. 30. Don't you enjoy the fact that some staff is actually _done_? 31. In the context of "fun again", debugging slop, finding imaginary dependencies, and discovering unimaginably fragile code isn't fun , even if it's not important. But past bad output, I worry for our creative fulfillment. The old timers are right. That feeling of accomplishment, a keystone of happiness is a product of work. Probably beyond the scope of the thread. 32. Last paragraph resonated so deeply with me. Especially this: ```It’s also not the typing of code that I really enjoy, nor is it the syntax or structure or boilerplate that’s required to build anything. It’s the fact you get to build something out of nothing, writing code was just how you got there. And with today’s tooling, that saves a ton of time.``` I never really related with folks that code for beauty or are put off by how AI does the actual coding. The beauty is actually creating something, solving real problems, shipping, and (hopfully) winning. It might be cliche, but it is incredibly true for me to say that using AI feels like a superpower. 33. The people who love writing code were the ones who created the languages and frameworks that make it even possible for an LLM to cobble something together for you. There is tons of satsifaction in actually creating nuts and bolts frameworks. After you encounter difficulties in creating a real world product you see the need for tools to solve those problems, so crafting those tools and then using them does feel like winning and shipping and solving real problems. 34. A product manager here. Thanks to AI, I was able to create my own website on Astro. I was so fascinated by web technologies, that I didn't realize when I created not just a website, but a blazing fast website with extensive amount of metadata generation (Json-LD, OG, microformats, Dublin Core, PRISM, RSL 1.0, Highwire Press, FAIR singposting, MODS generation) and so on. Thanks to this pet project, I'm now quite capable as a software architect of websites. And it is really fun! 35. Maybe its just me but I enjoy learning how all these systems work. Vibe Coding and LLMs basically take that away from me, so I dont think ill ever be as hyped for AI as other coders 36. Meanwhile, I've been feeling the fun of development sucked away by LLMs. I recently started doing some coding problems where I intentionally turned off all LLM assistance, and THAT was fun. Although I'll be happy to use LLMs for nightmare stuff like dependency management. So I guess it's about figuring out which part of development you enjoy and which part drains you, and refusing to let it take the former from you. 37. I've tried vibe coding and hate it. I guess it's okay for people who are only interested in the result, but for me it takes all the fun out of programming. It doesn't feel like it has anything to do with programming at all. I will continue to "vibe code" out of necessity - saving time and achieving more than I can on my own. But I cannot possibly understand how someone could consider it fun. 38. Strong agree! Forget all those studies that say “but developers are slower” or whatever — I’m actually building way more hobby projects and having way more fun now. And work is way more fun and easier. And my node_modules folder size is dropping like crazy! 39. This sounds like the opposite of fun to me. 40. it is fun again because we can remove ourselves completely from it? seems like web enthusiast are always the first to drop ship huh. "llms good because I no longer have to interface with this steaming pile of shit that web development has become", not because the web ecosystem has improved by any metric. 41. yeah, I think that too - for me the -Ofun comes from HTMX https://htmx.org and the HARC stack https://harcstack.org so I can server side code in a my preferred programming language hint: not JS (with a helping of LLM on the side) 42. AI has increased my productivity in dealing with side tasks in languages/frameworks I'm not familiar with. But it has not made development fun. To the contrary, I enjoy writing code, not reviewing code. 43. Fun is the way, not the destiny 44. I don't get it. What part of the process do you enjoy? Do you also enjoy hiring a taskrabbit to go hiking for you, taking photos along the way? 45. I’m just looking to make pizza not smelt the ore for the oven I’m going to cook it in. 46. Why make pizza when you can order it? As far as I can tell, there's not much enjoyment of making being had. Enjoying having is fine too, but let's at least be honest about it. I enjoy looking at photos people took on hikes, but I don't call it hiking. 47. Is it hiking if I bought my boots on amazon? 48. Not if you sit at home wearing boots and looking at photos of mountains. If you want to have boots, that's cool. But is replacing walking with ordering boots and photos making hiking fun again? Or were you only interested in the photos anyway? What part of the process of hiking do you enjoy? And why is it so hard to hear what part of the process of programming people enjoy? 49. But you’d agree it’s still hiking even if I didn’t tan the leather for the boots myself. 50. Yes, if you go out and walk. The same way I would agree it was programming if you designed the algorithms yourself. 51. This is just obtuse. Some folks have fun building their own pizza oven, curing & slicing their own meat, and mixing their own dough. Some folks like to buy mostly pre-made stuff and just play with a few special ingredients. Some folks want to make 5 different pizzas with different flavors. Some folks just order a pizza. Some folks walk out of their house and start hiking. Some folks drive somewhere and then start walking. Some folks take photos from the car. Some folks take a roadtrip. All of these things ask for different effort & commitment with different experiences & results as the payoff. At least be honest about that. 52. It's interesting that nobody has actually answered what part of the process they enjoy. 53. It's different for everyone, so no one answer would likely satisfy you 54. That's why I used the word "you" and not "I". 55. What is fun? Prompting? </comments_about_topic> Write a concise, engaging paragraph (3-5 sentences) summarizing the key points and perspectives in these comments about the topic. Focus on the most interesting viewpoints. Do not use bullet points—write flowing prose.
Fun Definition Debate # Fundamental disagreement about what makes programming enjoyable - the process of writing code versus seeing results and solving problems
55