11 votes

Software engineering freelancers: how do you survive in the AIpocalypse?

I can definitely feel the crunch. Companies choose to do it poorly and cheaper with AI rather than using humans. I have noticed a sharp drop in new business and conversations with prospects shifted in that direction. I’m not using race to the bottom platforms, and this comes even from customers who used to see the value in quality and “craft” as a way to build a product that users liked.

I’m having serious doubt about the future of freelancing vs salaried. But the rates are so much lower, and it’s so much more restrictive.

Fellow independents, how do you deal with the current state of things? How do you manage to still make a living and make plans for the future? How do you acquire new business in this context?

6 comments

  1. [2]
    delphi
    Link
    Do the thing that AI can't do: Sit down with your clients, talk to them, figure out an exact spec, and then maybe do the visual and UX design by hand? AI's not very good at that currently,...

    Do the thing that AI can't do: Sit down with your clients, talk to them, figure out an exact spec, and then maybe do the visual and UX design by hand? AI's not very good at that currently, compared to a skilled professional. Customer service and design is what makes you stand out these days.

    7 votes
    1. snake_case
      Link Parent
      Its exactly the same elsewhere, Ive become the goto for multiple teams because these people would rather ask me questions even when the Claude that our company pays for would answer it better most...

      Its exactly the same elsewhere, Ive become the goto for multiple teams because these people would rather ask me questions even when the Claude that our company pays for would answer it better most of the time.

      People just dont wanna talk to bots, no matter how good the bot is, when theyre talking to a bot and not a human they feel ignored.

  2. [2]
    post_below
    Link
    There will be lots of work for people who can fix vibecoded messes for some time. You could lean into that market. If you're a coder, learn to use AI effectively, meaning: The end result is...

    There will be lots of work for people who can fix vibecoded messes for some time. You could lean into that market.

    If you're a coder, learn to use AI effectively, meaning: The end result is equivalent quality to a hand written codebase. It's far slower than vibecoding, but still faster than it used to be. Maybe fast enough that you can make the same or better income at lower rates.

    Don't worry you still get to code, agents work best when you show them good quality example code.

    6 votes
    1. marcus-aurelius
      Link Parent
      This is what I'm leaning into, while my coworkers keep creating bigger PRs winch make the codebase worse without understanding what goes it, I took the opposite direction and focus on targeted...

      There will be lots of work for people who can fix vibecoded messes for some time

      This is what I'm leaning into, while my coworkers keep creating bigger PRs winch make the codebase worse without understanding what goes it, I took the opposite direction and focus on targeted cleanups, with proper measurements of improvement.

      AI makes so easy to add metrics to quickly asses if an idea makes sense to implement, that it feels like cheating, sometimes I ask to create components form scratch with the bare minimum data simply to check if it's viable to make the "real" logic faster.

      3 votes
  3. smores
    Link
    Hmmm... I can't really guarantee that this is useful as advice, but I can try my best to answer the question. I'm a member of a 6-person collective (5 engineers + 1 product manager). Being a...

    Hmmm... I can't really guarantee that this is useful as advice, but I can try my best to answer the question. I'm a member of a 6-person collective (5 engineers + 1 product manager). Being a collective is both good and bad — bad, because we need much more work to meet everyone's needs, but good, because if we lose a client, we can almost always shuffle things around so that everyone has at least some work. Also means we can share much of the admin work necessary for running a business, which is nice.

    We've found success within our niches (which are mostly collaborative rich text editing and ebook/audiobook forced alignment). We write about our challenges and successes in these fields as much as we can (we do the writing, not LLMs), and share this writing everywhere we think it might be relevant. The result is that people who find that their LLMs are struggling with these fairly challenging domains are at least somewhat likely to have seen some of our writing, and either reach out to us or are receptive when we reach out to them.

    I will say that we've been trying to get another client for the past couple months and it's definitely been much more challenging than it was, say, two years ago, but we have a few promising leads, still. I think that the pressure will ease up a bit as companies start to see the value that they lost in assuming they could replace domain experts with LLMs (this is happening a bit already).

    But ultimately the way that we're keeping ourselves in the game, so to speak, is doubling down on our areas of expertise. We keep working on our open source projects (we have a rich text editing framework based on ProseMirror and I separately have a self-hosted book alignment platform) and trying to get them some visibility, and keep writing about the things we find interesting.

    1 vote
  4. moonwalker
    Link
    What does this mean?

    I'm not using race to the bottom platforms

    What does this mean?