4 ms·

I don't remember wanting to "be the best programmer I could be" - I just wanted to build stuff and it made me feel smart/good when I solved complex problems. N

I don't remember wanting to "be the best programmer I could be" - I just wanted to build stuff and it made me feel smart/good when I solved complex problems. Nowadays I get paid to solve trivial problems, self-inflicted complexity, and work in problem domains I have no interest in. But it gets me a nice living.

sircastor 4y ago
Me too. And in danger of being "found out", I don't think I've ever wanted to be a "ninja coder" or someone who dives deep into solving hard problems. I like computing, and I like programming a lot, but the thing that I really enjoy about it is (as you said) building something that makes me feel smart, or accomplished. Incidentally, I feel like this is why I gave up on running OpenWRT on my routers, or FreeNAS on my NAS, and why I don't end up sticking with Linux on my personal computers. I enjoy computing, but it's not my hobby. My hobbies are things that I do with my computer.
- foobar_______ 4y ago
  Refreshing to hear opinions like this on HN. I feel similarly but often times feel alone with that feeling.
xupybd 4y ago
I solve trivial software problems but get to help solve interesting business problems. I still code but have moved into a role where I get input on the business processes that my software helps run. It's awesome and I love it. My input is directly aligned with business outcomes and it feels amazing.
nkozyra 4y ago
Most problems are trivial, particularly to people with domain expertise. I think getting really pulpy, difficult problems is a rarity even at the top of the field. I don't think that should be the goal and particularly not most of your time (it would probably drive us insane) What we can do is solve trivial (or easy) problems in ways that are elegant and robust and easy for other developers to understand. That in itself is a challenge.

4 ms·

I don't remember wanting to "be the best programmer I could be" - I just wanted to build stuff and it made me feel smart/good when I solved complex problems. N

by moonchrome 4y ago

sircastor 4y ago
Me too. And in danger of being "found out", I don't think I've ever wanted to be a "ninja coder" or someone who dives deep into solving hard problems. I like computing, and I like programming a lot, but the thing that I really enjoy about it is (as you said) building something that makes me feel smart, or accomplished. Incidentally, I feel like this is why I gave up on running OpenWRT on my routers, or FreeNAS on my NAS, and why I don't end up sticking with Linux on my personal computers. I enjoy computing, but it's not my hobby. My hobbies are things that I do with my computer.
- foobar_______ 4y ago
  Refreshing to hear opinions like this on HN. I feel similarly but often times feel alone with that feeling.
xupybd 4y ago
I solve trivial software problems but get to help solve interesting business problems. I still code but have moved into a role where I get input on the business processes that my software helps run. It's awesome and I love it. My input is directly aligned with business outcomes and it feels amazing.
nkozyra 4y ago
Most problems are trivial, particularly to people with domain expertise. I think getting really pulpy, difficult problems is a rarity even at the top of the field. I don't think that should be the goal and particularly not most of your time (it would probably drive us insane) What we can do is solve trivial (or easy) problems in ways that are elegant and robust and easy for other developers to understand. That in itself is a challenge.