Live data from Hacker News

Ask HN: What (other) jobs do you think of doing?

news.ycombinator.com

1–10 of 23 posts

Ask HN: What (other) jobs do you think of doing?

#1
With AI infesting and eating into all kind of crafts--and I being one of those faceless "craftsmen"--I'm rather forced to consider alternative jobs. Setting the monetary rewards aside, I was thinking of jobs that could give me a sense of agency, purpose, and satisfaction (however limited). The few I think of are:

- Parcels delivery driver

- Train driver

- Electrician or plumber

- Mechanic (with auto-mobiles hardly repairable these days, maybe this doesn't qualify)

Surely, I can't be alone in thinking along those lines. What else have you thought of?

Re: Ask HN: What (other) jobs do you think of doing?

#7
In my 25+ years programming, I don't yet think I've met a programmer who hasn't dreamed of "just being a lawnmower" (or some equally equiv, "mundane" job). Just the idea of ending the day having accomplished something and being able to 100% switch off work and just relax. The same is probably true of other professions like lawyers and doctors.

AI is definitely going to change things. It already has, but I don't think what it's done is the real change coming. Right now it's just a new tool in the toolbox. It does great at some things and terrible at others. Note: I'm speaking purely about LLMs/generative AI, because other forms of AI are -incredibly- useful and have been for a while (think DeepFold). I only mention it because it's important people remember there's different types of AI models used for all sorts of different things.

What's important to keep in mind are a few things:

* We all stand on the shoulders (abstractions) of giants. People of the past lamented about C, Java, ... every abstraction that came before. Did those abstractions cause the next batch of programmers to lose knowledge about what was really happening? Sure, but each also enabled an explosion of new ways of thinking and problem solving that brought us to where we are now. If you can recognize that, then that will help.

* You became a programmer/engineer for reasons (what I'll call "itches"). Only you know what those are. Buy, my guess is that - like most of us - there was something about the -problem solving- and logical analyses/thinking taking place, and seeing others gaining benefit from that work. First, if you look to another job, pick something that scratches those same itches, otherwise you'll be bored and depressed again very quickly. More importantly, the reason you're even asking the question is because something about AI feels like it's taken that "scratch" away from you. Keep in mind that your "itch" can be abstracted, too. Instead of solving a (for example) network byzantine problem, go one level higher, which has the same problem at the human-scale. Now AI becomes a tool to help you come up with and solve the problem instead of one that's replacing you. Same itch, different level, different tools.

* The comment mentioning "shadowing someone" is some solid advice. Right now you're succumbing to a "grass is greener" effect. That will disappear quickly if you do switch, and you'll still be in the same place if those itches are not being scratched. Again, identify the itch first.

Finally... and I can't stress this one enough... whenever I've been down due to the "itch" not being scratched at work (for any reason, not just AI), I've personally found the best solution to the problem is to volunteer and help others. This could be anything: food bank, big brother, translation services, helping to teach your native language to someone else, or even teaching something you consider important (i.e., programming) to kids at your local school via an after-school program. Every single time I do this I walk away feeling great. Inevitably there was a single point in the day in which I dramatically affected one person's life positively, and they - in turn - affected me similarly. In a class of 10 kids who want to learn to make games, there was 1 who had no way of being able to do this on their own due to at-home problems. At a food bank it was an elderly woman who couldn't speak English and I happened to be the one person who could speak her language (she was so excited to talk to someone). Or being in the children's ward at the hospital over x-mas, delivering toys. And sometimes I'd even walk away with a new set of ideas where my programming skills could solve a new set of problems I discovered existed and lead me to a whole new career.

Re: Ask HN: What (other) jobs do you think of doing?

#8
If you are an enterprise developer working at a bank, insurance company, airline etc, you have been easily replaceable commodity for well over a decade and comp has stagnated for a decade. Those types of companies are reaching out to me today offering the same comp for the same type of role I was getting in 2016-2018.

If someone hoped to make a career by turning well defined requirements into code forever, the writing was on the wall when it was easy enough for anyone to become a good enough full stack developer/mobile developer/web developer etc.

You are now seeing the same in BigTech where knowing how to reverse a b tree isn’t good enough to get that $225K+ a year mid level job.

AI has just accelerated that trend. The transition I started making a decade ago was not to be just an undifferentiated ticket taker and get closer to dealing with the “business” and taking on projects with larger scope, impact and ambiguity - a true senior developer.

https://www.levels.fyi/blog/swe-level-framework.html

Even though part of my job has been to produce code for 30 years, it’s been well over a decade since I had to interview based on coding tests. I’ve had 7 jobs since then including one at $BigTech.

AI can’t talk to customers. It can’t solve XYProblems. It can’t navigate corporate politics and conflicting priorities.

Re: Ask HN: What (other) jobs do you think of doing?

#10
I think people would do best to retool away from “coder” towards some specilaization where coding is part of the job. Don’t be a coder, be an X that codes.

If we think of coding becoming like writing, then you can see how it might be a ubiquitous skill - but still some differentiation. Some small number of highly skilled people do it full time. Some people do is as a big part of their job (journalists, etc). Still others it’s not core to the job, but it helps (a lot of white collar work).

Post reply on HN