r/learnprogramming • u/d8gfdu89fdgfdu32432 • Dec 26 '24
How do people not hate programming?
I've been programming as part of my hobby for 6 years. I do it because it's required for my projects not because I enjoy it. After 6 years, I still find it obnoxious. Programming is like 60% fixing bugs and solving annoying problems and 40% actually coding. The best analogy I can think of is your car randomly stopping every few minutes while driving. You just want a smooth experience but it's ruined by constant problems.
35
u/ConfidentCollege5653 Dec 26 '24
Fixing bugs is actual coding. It's the part I like the most.
But you can also reduce the number of bugs with better testing.
6
u/gyroda Dec 26 '24
Also, the better you get the more you don't make "simple" mistakes. Nowadays it's rarely the actual line-by-line code-writing that's the issue for me. .
The analogy I'd use is writing a book - it's much easier if you're not constantly fucking up the basics of writing sentences and paragraphs. Your book can still have issues if you don't have issues with any individual part of the book, and a book can be "functionally correct" while still being dry or confusing or whatever, but you're not struggling with basic literacy.
22
u/boomer1204 Dec 26 '24
> The best analogy I can think of is your car randomly stopping every few minutes while driving. You just want a smooth experience but it's ruined by constant problems.
Ppl who get into programming (and I realize you are doing out of necessity not desire so I really don't think you are the target audience for this) do it for the exact opposite reason. You don't get into programming "because it's a smooth experience" you do it because you are solving tough problems and enjoy solving those problems.
There is nothing wrong with hating programming or not wanting to be a programmer but I think most ppl in this subreddit are not gonna be on your side LOL
-9
u/Internal_Outcome_182 Dec 26 '24
Tough problems? No. Most problems are really easy, we just make mistakes during development process, have not enough testing, some stuff or requrmenets is changing. Problems are not really that tough.
49
u/Ronin-s_Spirit Dec 26 '24
Skill issue.
2
u/Grounds4TheSubstain Dec 26 '24
It really is. You get better at programming over time and -- through experience, good practices such as testing, and choice of coding styles and languages whose features make bugs harder to create -- eventually your experience of programming is that your code generally works.
0
Dec 26 '24
Edit: This is true only to an extent.
Yes, you’ll get better at programming over time & not make as many mistakes. However, this is only true to the extent of you only working on projects that aren’t challenging you to do things that you haven’t done before.
If you’re continually working on projects that are unfamiliar to you & involving new skills, then you’re going to make mistakes. However, these mistakes aren’t necessarily related to programming fundamentals but more so related to the specific domain of the project you’re building.
Note
Depending on the type of projects (and tech used):
The way you create tests & which test cases to include can vary
The coding style can vary a bit, especially depending on who you’re working with on the project
etc…
1
u/Grounds4TheSubstain Dec 26 '24
Source of my post: been programming for 30 years, have written well over a million lines. I stick to my original post. Yeah, there are new mistakes to make in new domains, but the debugging and testing and general programming abilities you learned previously are going to help you write good code, and quickly figure out what's wrong when you make a mistake.
0
Dec 26 '24 edited Dec 26 '24
Edit: Source of my comment - Working at Amazon with varying level of experienced engineers & seeing the mistakes made
Debugging
Debugging skills can vary a bit based on the systems that you have.
You can be experienced debugging software, but based on the different systems, tools, & domain you might have to change your approach.
Plus, things get even more complicated when we throw in other services calling your software.
Testing
Again, your testing approach can vary based on the type of software & domain.
You can have experience testing but make simple mistakes related to that type of software you’re building.
8
u/_ShadowFyre_ Dec 26 '24
By your analogy: there are some people who drive because it’s useful for getting places, and there’s other people who drive because they enjoy it. Considering the first group, it seems obvious that if the car was breaking down constantly, they would get annoyed (imagine if you were trying to get to work and your car broke down every 5 feet). But, in the second group (in this case, really a subset of that group), there are people who genuinely enjoy the process of fixing the vehicle, however that may be.
Programming is like that: some people use it as a means to an end, and therefore will find debugging painful. Other people will genuinely enjoy it and find debugging some or all of the fun. For me, personally, I find that the frustration of getting code to work is greatly offset by the reward of finally having code work, especially when I come up with the solution myself.
7
u/Fyren-1131 Dec 26 '24
To continue your analogy, you should just take the bus if it bothers you that much. Maintaining the car is fun :)
7
u/BDBlaffy Dec 26 '24
Your analogy is extremely flawed. A car is a finished polished product meant to be used. Programming is literally creating something that does exactly what you tell it to do, in the end you create a product that is smooth and that’s really rewarding! In your analogy, programming is more akin to assembling the car in various different stages depending on how low level you get. I’d sure hope you wouldn’t be expecting a hunk of unrefined metals, 4 tires in bags, and a half assembled engine sitting on a pallet all over a garage to somehow provide you with a smooth driving experience
18
u/Cachesmr Dec 26 '24
"as part of my hobby" sounds to me you are either doing arduino stuff, game modding, or some form of scripting, in which case yeah it would make sense why you would hate it.
Programming is much more fun when you deeply understand the tools you are using (and also when you have a statically typed language, and not python...). Expertise is required to have fun in complex problems, otherwise you will simply hit your head against a wall over and over again.
If you understand your tools, whenever you find a bug you usually know exactly where your program is broken, or you are usually almost certain of where it may be coming from, like an experienced mechanic.
1
u/Ronin-s_Spirit Dec 26 '24
True. I don't hate Lua but I absolutely hated trying to mod lua parts of some game.
-3
u/TPO_Ava Dec 26 '24
Disagree on the statically typed bit, the first language I learned was java because I wanted to make Minecraft mods. It took me 10 years to realise that maybe not all programming is awful when I learned python. Now Python is 90%+ or what I use when I script.
1
u/Cachesmr Dec 26 '24
Java is a rough language to start on for static typing. It's too strict. I understand why you wouldn't like it. I usually use Go or Typescript (with deno for direct TS execution) if i need a quick script depending on use case. I just can't use python, it feels like the wild west, lol.
-7
u/Internal_Outcome_182 Dec 26 '24
Now Python is 90%+ or what I use when I script.
You are talking about scripting and not programming.. and python..
12
u/aqua_regis Dec 26 '24
You are talking about scripting and not programming
Scripting is also programming.
You have a completely wrong stance.
3
u/deer_hobbies Dec 26 '24
Scripts do work until you wanna do something big or have a lot to organize or maintain.
Also big structures don’t mean one is “programming” - small codebases do big things and some big codebases do small things.
1
u/aqua_regis Dec 26 '24
Scripts do work until you wanna do something big or have a lot to organize or maintain.
Fun fact: reddit, instagram, youtube and countless other sites use (or used) Python at some time for their back ends.
5
u/throwaway6560192 Dec 26 '24
You are talking about scripting and not programming.. and python..
These distinctions are artificial nonsense
5
u/throwaway6560192 Dec 26 '24
The best analogy I can think of is your car randomly stopping every few minutes while driving. You just want a smooth experience but it's ruined by constant problems.
You know how there are people who spend time fixing and restoring classic cars? Why do they do that when they can just go buy a new one which will just work?
Yeah. Some people enjoy problem-solving.
4
u/Chris_CS_88 Dec 26 '24
It definitely can be a "love hate relationship".
You can bang your head on the desk for hours, because you are stuck with a stupid problem you don't understand or cannot grasp.
Next moment you find the fix and everything is rainbows and unicorns again.
4
u/rizzo891 Dec 26 '24
I like coding for the same reason I like monster hunter and dark souls games. You face a seemingly insurmountable challenge (a bug, or even something simple as a misplaced period/parenthesis) and when you overcome it you feel like a god and the smartest person alive.
That’s just me personally though can’t speak for anyone else
4
u/EdwardElric69 Dec 26 '24
It's because you're not driving a car, it's more like you're building one.
The point is for you to build something so the users have a smooth experience.
4
u/johngh Dec 26 '24
Why do people do jigsaw puzzles? What's the point of getting a puzzle all mixed up with you could just buy it as a picture, ready made.
Or Rubik's cubes... They would be easier if you could just buy them blank with sheets of coloured stickers to put on the faces so you don't have to turn the slices.
Maybe sudoku books with the numbers filled in for you too.
Some people get satisfaction out of using their brains and trying and learning and improving until they get good at something.
3
4
u/Kseniya_ns Dec 26 '24
If you do not enjoy solving problems and fixing bugs you simply will not enjoy programming. A happy programmer enjoys these things.
2
u/spicedcookieman Dec 26 '24
The pros outweigh the cons.
For me there's two things that outweigh the cons of debugging annoying bugs: 1) The sense of accomplishment that solving something difficult gives and 2) the beauty of the working end result. And not just audio/visual beauty but also seeing some good lookin' maintainable code that was produced or knowing the satisfaction of the end-users.
That said, unlike some, I don't like debugging that much either. I'd rather focus on the design and building so if there's a nasty bug that's going to take me many minutes or hours to fix I'd love to press a button that just makes it go away (with some text explaining why it happened in the first place so I can still learn).
2
Dec 26 '24
Sounds like you found the worst part about your "job". I find problem solving the best part. "hmmm why is this not working the way it should" should be an enjoyment, not a chore. It's only a chore when its required and you have NO interest in it.
2
u/Zeikos Dec 26 '24
It's the same question if you swap maths for programming.
The problem doesn't stem from the thing but your understanding of the thing.
If your mental model of what programming is resembles a recipe, a set of rules to follow and a set of independent blocks that need to be shoved in in the right way that's where the frustration comes from.
My advice would be to reflect on what you find frustrating, what fuels your emotional response?
Where does that fuel come from?
Understand why you hate it and you'll likely find that the hatred isn't about programming, but about unrelated things attributed to programming.
2
u/professor_buttstuff Dec 26 '24
Imagine playing a computer game, and you just beat the boss and advance to the next level by just pressing x. Sure, it would be smooth but boring and unpopular af.
Problem solving is quite rewarding, the harder the problem, the more enjoyable it can be to crack. Helps if you're stubborn, too, I think.
2
u/Any_Sense_2263 Dec 26 '24
I code less than 10%. The time before coding is for learning requirements, reasons, happy path, worst-case scenarios, possible ways of developing it in the future, planning, splitting it into smaller chunks, and finally, I can write tests, and then I can write the code.
tbh I love every part of the process... creating test scenarios and writing tests the most
2
u/ffrkAnonymous Dec 26 '24
only 60% bugs? more like 90%!
but seriously, I hate driving. Pedestrians, other cars, traffic lights, looking for parking, gas, tuneups... constant problems.
At least with code, I know it's because I'm an idiot. With driving, I acknowlege I'm an idiot and drive in the slow lane but everyone else is an asshole and it doesn't matter how safely I try to drive.
2
u/illithkid Dec 26 '24
I hate giving up. I hate being defeated by something simple because my ego won't allow it. I would rather go a night without sleep than let a simple bug defeat me. I like the bugs because I hate them. When I finally crush them like I wish I could crush my enemies, I feel powerful. Doing something right after hours of feeling like a moron makes me feel smart. For these reasons. I don't mind bugs much.
As for the 40% of coding? As long as I'm solving genuinely difficult problems and not just making a slightly different button or configuring boilerplate -- when I'm actually engineering -- is when I feel best. When I have to bring out the whiteboard is when I get excited.
It's not all highs. Sometimes it's too difficult and you feel pathetic. Sometimes it's too monotonous and you feel swamped. But when it hits just right? Little else can replace the feeling.
When I'm working on projects that really matter to me, no bugs or lack of skill will get in my way because my ego is too big.
1
u/aqua_regis Dec 26 '24
If your programs produce unexpected errors that you spend more time fixing than actually programming, you are going at this wrong.
You need to start at the other end: plan your programs, make sure to understand every single step you take. Then, develop an algorithmic solution and then, only once you know that it works, start programming it.
Your approach seems to be just glueing stuff together and hoping it will work.
1
u/Esausta Dec 26 '24
I mean...there's people who are bowel surgeons and love their job. I could never, but don't spend time wondering how they don't hate it. To each their own.
1
Dec 26 '24
I like building things. The excitement of my idea helps get past the pain points. I’m a designer by trade but I like the challenge of coding even if it can be frustrating at times. Being a hobby I can also enjoy building my projects at a slow pace. And not ruin my good time by being a job.
1
u/M_Me_Meteo Dec 26 '24
Well it's not for everyone.
An anecdote: I was in bands for most of my young life. I played the drums, but I also know how to play the guitar and bass. I can sing and carry a tune. I can't, however, write perform and record all those parts for a whole song or album. For me, making an album requires collaboration because I don't want to spend the time required to become the guitarist I'd want to be in a band.
To me there's two levels to the conversation the first level is "can I accomplish this part of the project" and the second layer is "should I do this myself or find someone who can do it better/more efficiently".
You have choices; either get better at coding so it doesn't feel like a chore or keep doing the parts you enjoy doing and find a collaborator who enjoys doing the parts you don't like. Congrats: you've just founded a startup.
All that being said, I could just record an album that is only drums and the parts I like doing, but it wouldn't be valuable.
1
u/ghfj53b3sf7 Dec 26 '24
I started programming because I didn't have a plan what else to do in my life. I didn't have any skill I could monetize etc. But after a few years of doing it professionally, I started to love doing this. The key is to understand that programming is a very broad term and you should find out what you are good at and what gives you the most fun. Some people are good at algorithms, some at architecture stuff, some at UI programming. Some people like to stick to one language in their entire career, other want to try many different languages. There is nothing wrong about any of these.
1
1
u/landsforlands Dec 26 '24
like eating spicy, drinking coffee or alchohol, having a relationship. its bad for you but its good.
we are strange species, ( masochism?).
1
1
u/WJC198119 Dec 26 '24
Some people are good at it and people do like and dislike dofferent things you know? If you don't like it maybe it's not for you.
1
1
u/AntranigV Dec 26 '24
I have a feeling that you're using crappy software if you have to fix them every time you use them.
I love programming, and I love the tools that I use. Sure, nothing that I use is mainstream, and yet everything that I use falls into the category of Just Works™
1
u/jakovljevic90 Dec 26 '24
I got into programming for the same reason some others mentioned here—solving problems with it just feels great. Honestly, I was the "worst in my class" back in college, but I still have this weird love for programming, even though I'm not great at it and I don’t work as a programmer.
I think part of why I never became one is because I was never truly skilled at it, plus I kind of flopped during my master’s program. But hey, that’s a story for another time.
The way I see it, you either enjoy programming even if you’re not great at it, or you’re good at it because you have to be—but you don’t really like it since it’s just not your thing.
1
u/RamenJunkie Dec 26 '24
Especially on a hobby level, its just like, art, and like any other art.
You write a book, and thats fun, but then you get to reread it and massage out the grammar tensing and spelling problems, then read it again and fix the plot issue, then you think of a cool extra bit to add in a few places and then you get to do it all over again.
Some people are just really into the creative process and watching their baby take shape.
1
u/gofl-zimbard-37 Dec 26 '24
Because computers are the best toys ever. And if you're spending 60% of your time fixing bugs, you need to up your development skills.
1
u/michiel11069 Dec 26 '24
I like making stuff, I only make mods for minecraft and I just like making stuff
1
u/lilB0bbyTables Dec 26 '24
If your car breaks down every few minutes the creator of that car and/or its maintainer are to blame and are not good at their jobs… you can conclude what follows the rest of that analogy.
1
u/Sshorty4 Dec 26 '24
You’re not DRIVING the car you are BUILDING it and that’s why it breaks down constantly.
If you don’t like building the car buy a prebuilt one and drive that, nobody’s forcing you to write your code, buy a Mac or Windows PC and get some well tested software for it.
And your car breaks down constantly because one: you don’t understand how to build a car. Two: a Lamborghini is not built by one person, it takes several hundreds of people to make a good car
1
u/Fox_gamer001 Dec 26 '24
For me, it's entertaining to solve problems, it makes you think and search for solutions. It's satisfying the part when everything makes "click" in your brain and you say "oooh so that's the problem...", like a boost of adrenaline.
1
u/xrsly Dec 26 '24
If you like tinkering with cars, then a "complicated" and customizable car is more fun than a super reliable off-the-shelf car.
I often feel like I'm being paid to play a puzzle game all day.
1
Dec 26 '24
Programming is not bad per se, it’s the tech industry that is the most soul sucking job I could ever fathom. I did a lot of shitty jobs, but none drained me of the will to live faster than working in tech.
1
1
u/IKoshelev Dec 26 '24
"Programming is like 60% fixing bugs and solving annoying problems and 40% actually coding"
Come to the enterprise. 60% meetings, 30% fixing bugs, 10% actually coding (if you are lucky).
1
1
Dec 26 '24
How do people not hate programming?
The actual coding part is only a small part of it for me. I enjoy the overall process of building projects.
I enjoy solving problems
I enjoy that feeling that I get when I figure out the root cause to a bug & fix it
I enjoy debugging
1
u/Pale_Height_1251 Dec 27 '24
It's much more enjoyable when you're reasonably good at it, or at least not bad at it.
When you're bad you're struggling more than you're creating, when you're good you're creating more than struggling.
0
0
1
126
u/mvr_01 Dec 26 '24
bc every time u solve a problem it feels great