Ask HN: How to get out of Tech and still make a decent living?
I hear you, and hope you can find something that works for you. A cousin of mine, an aeronautic engineer, went on to become a patent agent (editor&#x2F;writer&#x2F;evaluator) at a big patent firm. He needed to do some legal training, but it was less than a year -- not a full law degree. He couldn&#x27;t be happier - he is paid to read and be up-to-date on a lot of interesting stuff, has conversations with interesting people all day and (at least in his firm), has a job that is as 9 to 5 as he wants it to be, no pressure, no crunch time, etc.<p>The down side is that patents are evil.<p>&gt; And no respect for experience, unless you demonstrate on a whiteboard with your implementation of a sorted bubble tree list.<p>I will be a dissenter here: I have interviewed people with 20 years of experience, and who have shipped products, who had gross misunderstanding about the tech stacks they are using -- to the point of taking multiple (2x - 10x) times of both implementation and resources than a reasonable solution -- just reasonable, not compared to an &quot;optimized&quot; (for resources) or &quot;quick and dirty throwaway&quot; (for time) solution. And most of the times, these people were oblivious to their (lack) of knowledge or understanding.<p>Your post reminded me of a specific interview, someone with 20 years of experience, who&#x27;s answer to a question (essentially, a database join, which could have been done inside the select but wasn&#x27;t), which was an O(n^3). Would have worked reasonably well even on an n=1000 table, but our table had n=10,000,000, and this was specified in the requirements. After grilling him a bit about runtime estimates (to which his basic answer &quot;who cares? computers are fast enough nowadays&quot;), he did acknowledge that as written it would take forever, but then added &quot;But it doesn&#x27;t matter, the compiler will optimize this anyway to the best possible O(n) solution, and it will be fast&quot;. This was about a C loop, in 2005.<p>I thanked they guy and declined his job application. I am sure his takeaway was that I was a snotty employer who only wants sorted bubble tree lists and arcane academic stuff, and that I couldn&#x27;t appreciate him shipping products for 20 years. But had I taken him on our team, I am quite sure it would have been a failure: At that place, we had a successful fire-and-almost-forget shipping culture, which required doing back-of-the-envelope runtime estimates (among other things) to make sure things actually satisfy requirements -- and his attitude did not fit.<p>Another similar &quot;20 year experience&quot; story from a friend of mine who worked on a system running a moderately sized financial exchange: In small scale tests everything worked perfectly well, but once real load testing started, it was clear that it can sustain less than 10% of the existing load. (This was a 2nd-generation system, which was to take over existing trading). All measurements pointed to hard drives being the culprit, and a $50,000 SSD (whopping 10GB capacity, IIRC - this was 2002) was bought, and was able to <i>just</i> get the existing load working, with very little room for increased capacity.<p>At this point, my friend was assigned to review that the solution was properly implemented, and he discovered to his horror, that one of the 20-year-experience authors was unable to figure out how to do a &quot;sprintf()&quot; with unknown-in-advance result size, so he instead created a temporary file, used &quot;fprintf&quot; into it, allocated the memory according to the resulting size, read the data, and deleted the file. Changing this to an snprintf-and-if-failed-reallocate-buffer-and-retry scheme sped the system up some 20x (compared to the SSD!), and made the SSD redundant. The original guy&#x27;s response when shown the solution was IIRC, basically a dismissive &quot;oh, yeah - I guess I should have known about snprintf, it wasn&#x27;t there when I learned C, of course the SSD was the right solution given the constraints&quot;.<p>I&#x27;m not saying experience is useless, but it is an appeal to authority, which most of us (especially here on HN) dislike when we are expected to revere it. If one can&#x27;t show competence without referring to (vague, abstract, generally unverifiable[0]) experience, then perhaps one is not as qualified for a job as one thinks.<p>Just to clarify: This is not personally directed at OP - in fact, the vibe I get is that OP can easily pass sorted bubble tree list interviews and just got tired of it.<p>However, I&#x27;m just pointing out that anecdatally, I&#x27;ve seen too many &quot;experienced&quot; developers who are oblivious to the costs&#x2F;benefits of employing them, to the point that I completely disagree with the prevailing (even on HN) sentiment that experienced developers shouldn&#x27;t need to do the kind of interviews that junior devs do.<p>[0] Being a member of a team that did well is not, on its own, proof of anything. the dailywtf is full of &quot;Paula&quot;s and others who have spend months -- even years -- on teams that shipped, and the real world is too.