I think this is an important bit that a lot of people getting into programming don't realize. Many enjoy the "playing with computers" aspect. Some even enjoy writing new code. But the real test is do you enjoy fixing broken code?
The article ends with:
> Maybe this is what people mean when they tell us to "find our passion", but that phrase seems pretty abstract to me. Maybe instead we should encourage people to find the hard problems they like to work on. Which problems do you want to keep working on, even when they turn out to be harder than you expected? Which kinds of frustration do you enjoy, or at least are willing to endure while you figure things out? Answers to these very practical questions might help you find a place where you can build an interesting and rewarding life.
> I realize that "Find your passion" makes for a more compelling motivational poster than "What hard problems do you enjoy working on?" (and even that's a lot better than "What kind of pain are you willing to endure?"), but it might give some people a more realistic way to approach finding their life's work.
> Every friend I have with a job that involves picking up something heavier than a laptop more than twice a week eventually finds a way to slip something like this into conversation: “Bro, you don’t work hard. I just worked a 4700-hour week digging a tunnel under Mordor with a screwdriver.”
> They have a point. Mordor sucks, and it’s certainly more physically taxing to dig a tunnel than poke at a keyboard unless you’re an ant. But, for the sake of the argument, can we agree that stress and insanity are bad things? Awesome. Welcome to programming.
--
This "What kinds of frustration do you enjoy" I believe is a stumbling block for many people looking to enter the work force. I've encountered people in the past who love writing code but hate debugging.
I didn't realize anyone likes fixing broken code, debugging, or - from reading HN - what seems like what most professional programmers spend most of their time doing, inheriting a huge broken mess of old software and having to come to understand it and clean it up somewhat. I don't remember reading/hearing anyone say they actually like it.
Finding and diagnosing bugs is annoying. Actually fixing them is super satisfying though. Same with cleaning up old crusty code, figuring out wtf it's meant to be doing is painful but turning it into clear clean well-factored efficient code is satisfying.
I do. I love hunting down bugs and leaving the code better than it was. I've done some memorable refactorings of terrible code. It feels weird to say I like it, but I kinda do.
I think this is an important bit that a lot of people getting into programming don't realize. Many enjoy the "playing with computers" aspect. Some even enjoy writing new code. But the real test is do you enjoy fixing broken code?
The article ends with:
> Maybe this is what people mean when they tell us to "find our passion", but that phrase seems pretty abstract to me. Maybe instead we should encourage people to find the hard problems they like to work on. Which problems do you want to keep working on, even when they turn out to be harder than you expected? Which kinds of frustration do you enjoy, or at least are willing to endure while you figure things out? Answers to these very practical questions might help you find a place where you can build an interesting and rewarding life.
> I realize that "Find your passion" makes for a more compelling motivational poster than "What hard problems do you enjoy working on?" (and even that's a lot better than "What kind of pain are you willing to endure?"), but it might give some people a more realistic way to approach finding their life's work.
--
Another article that I love is Programming Sucks ( https://www.stilldrinking.org/programming-sucks )
This one starts with:
> Every friend I have with a job that involves picking up something heavier than a laptop more than twice a week eventually finds a way to slip something like this into conversation: “Bro, you don’t work hard. I just worked a 4700-hour week digging a tunnel under Mordor with a screwdriver.”
> They have a point. Mordor sucks, and it’s certainly more physically taxing to dig a tunnel than poke at a keyboard unless you’re an ant. But, for the sake of the argument, can we agree that stress and insanity are bad things? Awesome. Welcome to programming.
--
This "What kinds of frustration do you enjoy" I believe is a stumbling block for many people looking to enter the work force. I've encountered people in the past who love writing code but hate debugging.