Live data from Hacker News

Programming Sucks and Why I Quit (2014)

deirdre.net

41–50 of 93 posts

Re: Programming Sucks and Why I Quit (2014)

#41
post #18

> Instead, I need to pick projects that I care about and not spend long stretches of time on things I don’t. I'm getting this feeling myself more and more lately. And I've only been doing this for a little over 5 years. Although, I wonder if I'll have this thought regardless of what field I am working in.

After similar lines of thought, my conclusion is that you have to embrace the process of writing code and not get too personally invested in the end product - it doesn't belong to you, and a company can and will sell it, scrap it, or let it decay slowly. Step back and be grateful for the opportunity to apply your skills to help someone else create something they felt they needed, and don't worry about what they do with it after the fact. I've found over and over that caring about a project too much leads to disappointment - the more bleeding edge the project, the more interesting it is, and the more likely it is to die. Embrace the idea that your job is to help someone with a short term goal. It can be fun, but don't let it be your life. Life is about people, not things, and certainly not the code you wrote last week. Help someone by using your skills and move on, it's very rewarding.

Re: Programming Sucks and Why I Quit (2014)

#42
post #28

Earlier quoted context omitted.

Did you? He's not talking about quitting his job, but his (former) passion. That's not retiring.

Deirdre is a woman

Oh, my mistake. Thanks for pointing that out. Not really familiar with less frequent English names.

Re: Programming Sucks and Why I Quit (2014)

#43
I totally get burning out or losing your passion etc. But I'm not sure how other people's web pages being of poor quality affects one's own work -- if anything, it motivates me to do a better job (and gives me a competitive advantage, or at least a reputation which attracts the right kinds of clients/customers).

Re: Programming Sucks and Why I Quit (2014)

#45
post #30
post #23

Earlier quoted context omitted.

> So, after a law professor retires s/he immediately stops thinking about law? The proper analogy would be: "So, after a lawyer retires s/he immediately stops practicing law?" Yes, s/he does.

So, when you retire will you immediately stop practicing programming?

Equivocation; "practicing" law and "practicing" programming are not the same thing.

Re: Programming Sucks and Why I Quit (2014)

#46
post #30
post #23

Earlier quoted context omitted.

> So, after a law professor retires s/he immediately stops thinking about law? The proper analogy would be: "So, after a lawyer retires s/he immediately stops practicing law?" Yes, s/he does.

So, when you retire will you immediately stop practicing programming?

Many people certainly will – because they're already not doing it in their free time. In fact, in most professions you won't find many people who enjoy the same things in their free time as they do in their job.

As for me, I still have >35 years ahead of me, so we'll see.

Re: Programming Sucks and Why I Quit (2014)

#47
I agree with the author that programming sucks pretty bad. Making it suck less is part of the joy I get when programming. Even the highest quality software is at best organized chaos. We all know how to approach problems, that's the boring part that no one really cares about. Diving in and discovering the unknown is where the fun begins. That's where we have the opportunity to optimize, refactor, learn new things, and perfect the art.

Maybe everyone reaches a point where they become jaded, but all of the things causing the author to quit are the exact things that make me want to continue.

Re: Programming Sucks and Why I Quit (2014)

#48
post #42

Earlier quoted context omitted.

Deirdre is a woman

Oh, my mistake. Thanks for pointing that out. Not really familiar with less frequent English names.

It's actually Irish (so is her middle name Saoirse). It's pronounced Deer-dra in case you're wondering

Re: Programming Sucks and Why I Quit (2014)

#49
post #28

Earlier quoted context omitted.

I'm not sure what point you think you're making. When someone takes an action, do they immediately stop thinking about the topic of that action? Did you read the article?

Did you? He's not talking about quitting his job, but his (former) passion. That's not retiring.

Did you really?

She isn't quitting her passion, she's quitting doing it for someone else, i.e. her job.

>"It’s not to say that I have no interest in software. Of course I do...What I mean is that I can’t do it for someone else the way I used to...I have some ideas of what I want to do software-wise, but I’m not ready to announce them yet."

Re: Programming Sucks and Why I Quit (2014)

#50
post #45
post #30

Earlier quoted context omitted.

So, when you retire will you immediately stop practicing programming?

Equivocation; "practicing" law and "practicing" programming are not the same thing.

It can be compared. Both require to mentally navigate certain set of constraints and rules and build up a mental model of the domain problem, after which you produce a concrete result. In programming it's software, in law practice it's mostly a written consultation or a decision.

The point I'm making, is that both are mental endeavours. Programming isn't constantly typing at a desk, hitting TAB, and letting the IDE do the rest, but actually solving the problem in your head.

If I quit a programming job, that doesn't mean I stop thinking on programming problems. Same goes for law.

The problem that the author is describing, is that she has reached the limits of her profession to such an extent, that even thinking on (most) programming problems isn't interesting to her anymore. Which is a sad thing.

Post reply on HN