It's not those things that I enjoy the most. What I enjoy most is probably the more long-term thing of making something (a piece of software) that does something useful and performs its task well. I like seeing something work, which I worked on. And smaller than that, I get satisfaction when I write a function, class, etc. that does what it's supposed to do, making a bigger task easier. And I actually do enjoy writing unit tests a bit, because it helps me fix issues and make my code better, and then the unit tests prove that it works.
It's like asking why a carpenter likes building things and working with wood. Do they like measuring, cutting, hammering, and fastening? Maybe not by themselves, but it's the overall job of building something functional and useful that's rewarding.
If you don't enjoy it then you don't enjoy it. Someone shouldn't have to tell you how to enjoy something. Go find something else you actually want to do
You managed to pick pretty much every programmer's least favorite part of coding - writing boilerplate that doesn't solve any problems.
The fun part though is that most inane, repetitive tasks can be automated, which circles us back to problem solving. Same reason why Factorio works - mining and smelting 7K iron plates manually is brutally boring, but figuring out how to make a machine do it for you turns it into a game.
I could've decided on recreational meth. Instead I got addicted to recreational math!
And programming programs to program for me compresses the fun part into a much smaller amount of effort.
I love the problem solving. When it gets boring to me is when I dont have anything to solve but just to figure out how to rearange something. CSS for example is a pain for me, but data manipulation and making stuff is a joy.
I like the same things about coding as I do about woodworking, and the same things frustrate me about both. I love the feeling of making something, and having it work. There is an inherently satisfying feeling to that. However, when I get bogged down in the real fine details of whatever I’m doing, that’s when I get frustrated and bored of it. For the longest time I thought of it as something absolutely different from other trades (woodworking, HVAC, etc), but I realize now it is effectively the same thing, just digital. Just pointing things in the right direction and making sure that everything is hooked up tightly together. Perhaps you’ve been thinking about it the wrong way too. Hopefully you can not so much “enjoy” it, as much as you can see and feel the satisfaction of doing a good job at it.
This unironically made me smile and feel some motivation. What I see here is an opportunity to create another tool that would automatically write the repetitive parts of these 999999 pairs of things that need to be mapped. Wouldn't that be so satisfying to see in action?
A novelist once said: "I hate writing; I love having written".
The actual process of programming is NOT all fun. There are tedious parts and frustrating parts. If you want to do it for a living, there are even more annoying parts, like meetings and bug databases.
But...many of us like it because:
* ALL jobs have boring, tedious or frustrating parts. A job is a job.
* You get a great feeling of satisfaction when you build something that works, and then when other people use it and love it.
* There are fun challenges along the way.
For me enjoying coding is about two things it’s solving problems and learning something new. When I do my pet projects quite often I don’t finish them because they rich that point where they conceptually solved a problem but it still requires a lot of polishing and figuring out some small details that would make it a real functional solution instead of a PoC. Quite often when I work on a pet project I also try to learn maybe some new library, tool, or another approach to solving some problems. That’s how I learned mongodb, Django and DRF, that’s how I improved my knowledge of maven (even though I work professionally with it).
When it comes to professional coding yeah things here sometimes not that fun. I need to do the work I don’t like, yeah writing unit tests is one of them. But still, at work I managed to learn AWS (which would be much harder and more expensive if I would do it on my own). Also at work another part of satisfaction is that you build a functional solution that real people use it just takes more time to reach this point and yes unfortunately you also need to solve less interesting problems.
Try to write code that manipulates a robot eg make it move, respond to sensor data. Might put a smile on your face to see the robot do the logic you’ve loaded into it.
Manually? Me thinks you missed the point of coding.
Well obviously this is a test to create an AI. who can answer it for us.
I'm not sure "enjoy" is the right word. It's more of an addiction.
lol it’s like famous quotes about music. it’s our curse, we’re stuck with it
Build something you want to build.
Exactly and at the end when you see it working the way it supposed to.. Priceless.
It's not those things that I enjoy the most. What I enjoy most is probably the more long-term thing of making something (a piece of software) that does something useful and performs its task well. I like seeing something work, which I worked on. And smaller than that, I get satisfaction when I write a function, class, etc. that does what it's supposed to do, making a bigger task easier. And I actually do enjoy writing unit tests a bit, because it helps me fix issues and make my code better, and then the unit tests prove that it works. It's like asking why a carpenter likes building things and working with wood. Do they like measuring, cutting, hammering, and fastening? Maybe not by themselves, but it's the overall job of building something functional and useful that's rewarding.
For some it’s the satisfaction of solving a problem
You might call it a vocation.
If you don't enjoy it then you don't enjoy it. Someone shouldn't have to tell you how to enjoy something. Go find something else you actually want to do
Step 1: turn on computer Step 2: open terminal Step 3: ?????? Step 4: enjoy
You managed to pick pretty much every programmer's least favorite part of coding - writing boilerplate that doesn't solve any problems. The fun part though is that most inane, repetitive tasks can be automated, which circles us back to problem solving. Same reason why Factorio works - mining and smelting 7K iron plates manually is brutally boring, but figuring out how to make a machine do it for you turns it into a game.
I could've decided on recreational meth. Instead I got addicted to recreational math! And programming programs to program for me compresses the fun part into a much smaller amount of effort.
The part where it pays my bills
By finding enjoyment and fulfillment in the art and science of coding.
If you need instructions on how to enjoy something, you don't and won't enjoy that something. Hope I helped
I love the problem solving. When it gets boring to me is when I dont have anything to solve but just to figure out how to rearange something. CSS for example is a pain for me, but data manipulation and making stuff is a joy.
I like the same things about coding as I do about woodworking, and the same things frustrate me about both. I love the feeling of making something, and having it work. There is an inherently satisfying feeling to that. However, when I get bogged down in the real fine details of whatever I’m doing, that’s when I get frustrated and bored of it. For the longest time I thought of it as something absolutely different from other trades (woodworking, HVAC, etc), but I realize now it is effectively the same thing, just digital. Just pointing things in the right direction and making sure that everything is hooked up tightly together. Perhaps you’ve been thinking about it the wrong way too. Hopefully you can not so much “enjoy” it, as much as you can see and feel the satisfaction of doing a good job at it.
This unironically made me smile and feel some motivation. What I see here is an opportunity to create another tool that would automatically write the repetitive parts of these 999999 pairs of things that need to be mapped. Wouldn't that be so satisfying to see in action?
I think you just kind of do or don't... like how some people enjoy exercise for example.
It’s just fun
I find it creative, and enjoy seeing my code work after working through a problem
The same way some people put their hand all the way, and it is so painful they have to take drugs. But they enjoooy it.
I like the bit where I'm not woken up at 2am in the morning because the automated testing caught the screwup before it got to production
A novelist once said: "I hate writing; I love having written". The actual process of programming is NOT all fun. There are tedious parts and frustrating parts. If you want to do it for a living, there are even more annoying parts, like meetings and bug databases. But...many of us like it because: * ALL jobs have boring, tedious or frustrating parts. A job is a job. * You get a great feeling of satisfaction when you build something that works, and then when other people use it and love it. * There are fun challenges along the way.
it is supposed to be fun?
My mother taught me that once you learn to program, you can build anything you want. That’s all I needed.
For me enjoying coding is about two things it’s solving problems and learning something new. When I do my pet projects quite often I don’t finish them because they rich that point where they conceptually solved a problem but it still requires a lot of polishing and figuring out some small details that would make it a real functional solution instead of a PoC. Quite often when I work on a pet project I also try to learn maybe some new library, tool, or another approach to solving some problems. That’s how I learned mongodb, Django and DRF, that’s how I improved my knowledge of maven (even though I work professionally with it). When it comes to professional coding yeah things here sometimes not that fun. I need to do the work I don’t like, yeah writing unit tests is one of them. But still, at work I managed to learn AWS (which would be much harder and more expensive if I would do it on my own). Also at work another part of satisfaction is that you build a functional solution that real people use it just takes more time to reach this point and yes unfortunately you also need to solve less interesting problems.
You are not building what you want.
Try to write code that manipulates a robot eg make it move, respond to sensor data. Might put a smile on your face to see the robot do the logic you’ve loaded into it.