Ask HN: How to rediscover the joy of programming?
I wasn&#x27;t 20 years into my career when I did this (more like 10), but at one point I had a serious &quot;lapse of faith&quot; with regard to my career.  I was working for a terrible company with an even worse manager and I was miserable.  I didn&#x27;t know if I wanted to be a programmer any more.  I quit my job and didn&#x27;t look for another one.<p>Instead, I wrote free software -- initially just for a month.  I got up in the morning, had a shower and worked on whatever project seemed interesting to me at the time (which was actually the GNOME Corba ORB -- that&#x27;s how long ago this was ;-) ).  At first I was pretty unproductive (and I&#x27;m not sure I ever actually made a contribution... can&#x27;t even remember).  I watched the stock market go up and down on the TV and occasionally turned the channel for more educational content (I invented the &quot;Teletubbies Drinking Game&quot; -- Drink whenever they say &quot;eh oh&quot; and drink twice whenever they say &quot;again!&quot;... which is to say that I don&#x27;t think I ever lasted an episode).<p>Anyway, one day I was having a shower and I had an idea about programming (I can&#x27;t remember what it was).  I ran out of the shower and started typing away.  Every day after that I had a similar experience.  It took me a week before I realised that I was so preoccupied that I often wasn&#x27;t wearing any clothes. (Actual awkward conversation: I was chatting with a woman who was moving out of the apartment.  She recognised me: &quot;Oh you are that nice man who programs by the window every day.  Such a shame I will miss that from now on&quot;...)<p>After about 6 months of doing this, I realised that I loved programming.  I <i>hated</i> my job.  The hatred of my job so overwhelmed my natural love of programming that I got to hate it too.  But, like a starving man, as soon as I had the time to get back to my passion, I was ravenous.  After that, I was much more careful to take jobs that I liked.  I often worked for incredibly low salaries just because I liked the people or I liked the project.  I was also careful to save enough money so that I could always take a &quot;sabbatical&quot; -- just quit my job and spend half a year writing code that <i>I</i> wanted.  I was single (despite&#x2F;because of my proclivity for exhibitionist programming), so it was easier, but I think it can be made to work in a family setting too.<p>I think the best thing I can say is that when taking a job, it&#x27;s important to find a win-win situation.  I find that when I get in trouble it&#x27;s because I end up doing things that I think are important for the company, but which I don&#x27;t want to do.  Often these are things that my management don&#x27;t want me to do either, which leads to a bad relationship with the management.  I usually think, &quot;Oh this is crap!  They are totally dropping this stuff on the floor.  Someone has to clean up this mess&quot; and then get trapped into doing lots of stuff that saves the company, but destroys my soul (and somehow makes me an enemy of many of the people around me).  So instead, I just try to do the things that <i>both</i> my management and I want me to do.  Usually there is <i>more</i> than enough stuff that I want to do that we can find a mutually beneficial overlap.<p>The most important point: I let the company burn down around me as I play my fiddle.  Um... Maybe not the most apt analogy.  But I hope you get the point.  I only do the non-fun parts of my job, if I really get the impression that somebody wants me to do it!  That makes such a massive difference, it&#x27;s incredible (although I often make the same mistakes of the past, but I try to correct it).  When the company is intent on flying into a wall at 1000 miles an hour, I don&#x27;t stop it.  I just start looking for another job ;-)<p>YMMV.