Ask HN: Novelty addiction is ruining my life and career. What should I do?

You say you write good code in a number of languages but honestly I highly doubt it. If you really haven't stuck it out on any project for the long haul how could you possibly know that your code is any good? In my opinion one of the most important features of good code is long term maintainability.

I can relate I think. Whether you need a cure or not is probably a question for you and a therapist. Ask about sliding fee scales and other options.

My story and maybe something for you to explore. I never held a job longer than 24 months when I was younger. Not being able to figure out a career direction and trying to get some direction in 2000 I sought testing at a great organization called Johnson O'Connor Research Foundation. They do aptitude testing and have been for 70+ years. Lots of data and studies on job satisfaction, aptitudes (which are different from both interests and skills), and success. Check out their web site they have some great info.

I tested high aptitude (80 - 99th percentile I think) on about 1/2 of the 19 or 20 aptitudes they've identified in their research. About 10% of the population tests this way. Most people have 3 or 4 max. The problem is if the aptitudes don't get used they agitate. Deeply. Like having a team of 20 sled dogs all fighting to run and no sled to pull or direction to go.

So I have learned I must use them or suffer the consequences. For example, Argentine Tango exercises my musical and social aspects. Engineering aptitudes, inductive reasoning, rapid idea generation, etc... all need expression. Some more so than others. Ideaphoria is rapid idea generation, handy in marketing or teaching, and a real pain if it is suppressed.

Commonly people with many aptitudes have a lot of difficulty with careers. Some use seasonal work or multiple part-time jobs or many different activities in one job to deal with what can often be conflicting drives.

Whether or not you are in this situation I don't know. What I did learn that may be of help was that I needed to respect the cards I was dealt in life. Gifts or burdens depended on how I looked at things. It's okay to have multiple projects and very diverse abilities and interests. Some may get abandoned quickly while others stick around.

Sharing seems to help. Get a blog up and start writing about all your projects. The ones that work and the ones that don't! For some reason sharing project results seems to help regardless of how they turn out. For example, I just had a surprising and inspiring response from HN readers on a blog post I wrote in November. I didn't realize other people would find what I was doing interesting enough to discuss!

I'm going to be 50 this summer and finally feel like I'm getting a handle on things. Keep at it. I hope some of this was useful. Get the help you need as you find the resources. Take care of your health, physical and emotional,and honor your gifts.

I doubt the affiliate path is a way to actually making a living... it's been fiercely competitive since 2010.

I can relate to your situation. While I have not completely figured it out, one thing I realized is that, even though I shelve many of my side projects, occasionally I come back to some of them, with fresh enthusiasm and move it forward another step or two (before loosing enthusiasm again). I realized that given enough "cycles" at least some of them are bound to be completed.

So a new approach I am trying is the "GPU Pipeline of side projects". First, I choose to trim my list of side projects to a few important ones (4 is a number I like, so four). I work on them in a parallel pipelined fashion. So I have one that's more advanced, one that is being setup, one that is being fleshed out, one still in ideation phase (you get the idea).

Secondly, I realize that when building things, the novelty can come from "recursing down to the details". For example, setup a AWS pipeline for code deployment would mean, learning how to setup an Ec2 deployment, then a Chef or Puppet instance, then easy config management of them, best way to document our setup (gitbook etc) and so on.... So if we use our boundless curiosity, which is both a strength and a weakness, to look a little deeper, we will find enough novelty to keep going even in a "single" project.

What I realized is that one single project is like a LISP S-Expression. (project). You (eval project), and it returns (list sub-project1 sub-project2 interesting-research3 wonderful-idea4) All you have to do is keep eval'uating the sub-expressions till you hit an "atom" of truth to share with the world.