Earlier quoted context omitted.
protip: Be a very picky freelancer and only work on projects that interest you.
I'm having a mid-career crisis much like OP and the notion of freelancing is enticing. Can you tell me more about how it is more fulfilling, lees frustrating and how you find quality gigs?
Programming is a Terrible Job
221–230 of 296 posts
Re: Programming is a Terrible Job
#222I've felt this way before. Dejected that the my new job wasn't an exciting candy land of save-the-day hacks and movie montage of elegant code spanning the screen. My expectations were too high. I thought we would always do the right thing to kick out software all grown up ready to take on the world. When the realization set in I got angry. First at the job then at myself. I held it tight knowing someone was to blame.…
If you know a trick for maintaining a sense of satori in such conditions, you would oblige me enormously by describing it.
Re: Programming is a Terrible Job
#223Re: Programming is a Terrible Job
#224Of course the day job isn't always fun. That's why it's a job and that's what we get paid for. But: I f'ing love my job as a programmer. There is nothing in this world that I'd rather do. There's nothing that constantly fills me with as much joy as programming does. I admit that I might be a bit lucky here, having founded the company I'm working for; that allows me to pick my battles and find a good balance between s…
I think, as a founder you are missing the point that 99 out of 100 times you are told - explicitly or by work schedule "do not do it in an interesting, performant or elegant way, just get it working somehow and move on"
Sure, we're in businesses (well, most of us), and there's little room for gilding the lilly or perfectionists who can't deliver.
That said, I've always found that elegant code is easier to maintain, thus reducing technical debt. If your employer doesn't want to reduce technical debt, you're either working for a start-up that's in a mad rush to 1.0, or you're working for someone who doesn't understand or care about the interest you pay on technical debt, and it may be time to move on.
Re: Programming is a Terrible Job
#225Re: Programming is a Terrible Job
#226There's a reason it is called work and not play. If work was always enjoyable, then they wouldn't need to pay you to do it. I think the author is delusional if he thinks any programming anywhere doesn't have large swaths of time that are a bit mind numbing. And my experience has been the programmers who think themselves 'above that' are the ones that provide the least value. Our job is not to program, our job is to c…
There' a difference between having "large swaths of time that are a bit mind numbing", and having those swaths taking most, possibly all your working time. OP said: > I don't think I ever caught myself writing code for my employer and thinking "hey, I really enjoy this" ----- > Our job is not to program, our job is to create value. It's supposed to be the job of every worker out there. Even janitors (believe me, clea…
Poor guy. I write stuff I enjoy for my employer all the time.
Re: Programming is a Terrible Job
#227Just take a step back and ask, "what is the company I work for trying to do?" And if you don't like it, or don't think it's cool enough, move along. Again, it's all your choice.
Re: Programming is a Terrible Job
#228Sure, programming is a job, like working on cars is a job. You can be mechanic in a small town, or work for an F1 team. It's your call. Just take a step back and ask, "what is the company I work for trying to do?" And if you don't like it, or don't think it's cool enough, move along. Again, it's all your choice.
Re: Programming is a Terrible Job
#229I don't think that means much of anything, and I don't identify with the rest of the post, but I find it interesting that someone from another time and place has a nearly identical programming origin story.