Stories

Ask HN: AI writes better code than me. How to keep my identity?

Article news.ycombinator.com

Ask HN: AI writes better code than me. How to keep my identity?

Nowadays, almost everyone codes with AI, right? I am a freelancer, and the entire market is now setting deadlines based on AI-assisted coding speeds. If you don't use AI, you simply cannot meet the deadlines. Because of this, I completely transitioned to AI-driven coding at the beginning of this year (starting around GPT-5.3).

It's not that AI coding isn't fun. It is. But in the beginning, there were still many things AI couldn't do well. The community focus was on "Harness Engineering," attaching MCPs, or deep Prompt Engineering. I actually built and used quite a few custom AI tools during that phase.

In the past, you had to provide not just your intent and direction, but also detailed, step-by-step instructions to reach that goal. Lately, though, even if you skip the detailed instructions, both Claude and GPT-5.6 handle it perfectly. You don't even have to agonize over which model to use. "Graph engineering" is currently trending, but it seems the models have already learned those patterns natively—if you establish a high-level plan with them, they automatically embed the execution policies into it. Whenever I try to learn and apply a new AI engineering technique, the next model update already does it out of the box, making the effort feel pointless.

The real problem is that AI is now too good. It applies ADT patterns, immutability, Option/Maybe, Result patterns, functional programming patterns, monadic chaining, and architectural structures like MVC, MVVM, MVI, and Hexagonal architectures far better than I can. It's heavily demotivating.

All those years I spent memorizing GoF patterns, slowly applying them to my work, and tweaking them into my own style—it all feels meaningless now.

Honestly, the vast majority of freelance work revolves around simple CRUD apps. Sure, there is domain knowledge to memorize, but when it comes to structuring CRUD, using functional techniques for error and value handling, or writing boundary tests, AI is just far more meticulous and capable than I am.

It even feels like AI is better at domain modeling. I try to hypnotize myself into believing I'm still necessary, but realistically, I don't work in Big Tech. I'm a programmer who mostly assembles business logic on top of existing frameworks, and the truth is, AI does my job better. And faster. I don't think I can deny it anymore.

Top-tier developers might still outperform AI, but for the vast majority of us, including myself, that is no longer the reality. To write the kind of code AI generates, I used to have to keep documentation open on a second monitor, think deeply, and constantly Google better approaches. AI just generates it instantly, making my past efforts feel obsolete.

When AI writes better code than I do, how am I supposed to maintain my motivation and identity? I would especially love to hear from other freelance developers. With market deadlines getting tighter and tighter because of AI, how are you handling this transition?

Again, it's not that AI "vibe coding" isn't fun. It is. But entirely separate from that, the stark realization that I am losing my competitive edge is making me increasingly depressed.

Discussion 25 comments · 15 points · jdw64 · 2026-08-28
Open on HN
Loading the discussion…

Domain filters

Stories from these domains are hidden from every list. Subdomains match too: blocking substack.com also hides danluu.substack.com.

    New collection

    Delete this collection?

    About YAVCHN

    YAVCHN is a reader for Hacker News and Lobsters, with articles and discussions in separate windows or Classic pages.

    Created by Paul Parks and built with PUDL.

    YAVCHN source code on GitHub

    Privacy policy · Terms of use

    Help

    Keyboard

    j / k
    Move down and up the story list. The arrow keys scroll whatever has focus.
    Enter
    Read the marked story in the article reader.
    ]
    Read the next story in the same article-reader applet. Back returns to the previous story.
    p
    Pin or unpin the marked story, which keeps it in Pinned.
    n / N
    Move to the next or previous top-level comment in the window in front.
    c
    Collapse or expand that comment.
    f
    Hide or show the story list.
    Esc
    Close a menu or this help.
    Access key m
    Go to the menu bar. Most browsers take it with Alt on Windows and Linux, and Safari with Control and Option.
    ?
    Show this help.

    Windows

    Each story opens in a window holding its article above its discussion; drag the bar between them to share the room differently. A window can be moved by its title bar, resized from any edge, snapped to a half or a corner by dragging it there, maximised, or minimised to the bar at the foot of the page. Use Window > New reader window to open an empty reader, or Story > Open in new reader window to open another reader for the current article. Docked readers keep their articles when you select another story from the sidebar. Minimized readers can be restored and reused for their site. A window's Next story link reads on down the list in the same window.

    A link in a comment or an article to another Hacker News or Lobsters thread opens that thread in a window too. A link to a single HN comment opens the comment above its replies.

    While a story's window is in front, the Story and Discussion menus in the menu bar hold its commands: pinning, Next story, sorting, collapsing every thread, jumping to the first new comment. Each window also remembers where you were in its article and discussion, so a reload, or Back to a story that Next took you past, finds your place again. Closing a window forgets it.

    The whole arrangement lives in the address, so a bookmark or a shared link brings it back, and Back undoes the last change. Moving between Hacker News, Lobsters, their lists, Pinned and Find changes only the list, and leaves the windows open.

    The list

    The pin at the start of a row keeps the story in Pinned, and the cross at its end hides it. Pinned can be narrowed by words in the title, site or author, by source, and to the stories you haven't opened yet, and ordered by when you pinned them, by points or by comments; the filters are part of the address, so a filtered view can be bookmarked. Scroll past the end of the list to load more. Domain filters, in the View menu, hide every story from a site.

    Collections are named lists of stories. Story > Add to collection files the story in front into one or more of them, and the Collections feed shows them all or one at a time; the menu that chooses collections also creates, renames, and deletes them. A note is your own text on a story. Choose Add note in a story's toolbar to write one; it saves as you type. Rows with a note carry the note mark, and the Notes feed lists every noted story and searches the text of your notes.

    Browsing view

    View > Windowed and View > Classic select the browsing view and save your default in this browser. Window view reuses a reader for each feed. Classic view opens stories and applets as pages. Open as a page is a one-off action that does not change your saved default. Use the Windowed selector to return an article to a window. Direct page links always open as pages.

    Applets

    The Applets menu in the menu bar holds three tools, each a window of its own. Replies to me takes your Hacker News user name and lists the replies to your last thirty comments and stories, checking again every three minutes while it is open, and marking what is new since you last marked them read. Look up a user opens a profile on Hacker News or Lobsters, with their submissions and recent comments, as a commenter's name in any discussion does; the bar at the top of a profile looks up someone else in the same window, and Back returns to the one before. Who is hiring? filters the posts of HN's monthly hiring threads by the words you type.

    They read only what the sites publish to everyone, so none of them asks for a login, and your user name stays in this browser anonymously and is included in retained applet state when signed in.

    Find

    Find takes any link and lists every time it was submitted to Hacker News and Lobsters, so you can read each discussion of it.

    About

    YAVCHN never sees your Hacker News or Lobsters login. The discussion is fetched from each site's public API; to vote or reply, follow the link above the discussion, or the arrow beside a comment, to the source's own site. Without a YAVCHN account, your data stays in this browser. When signed in, pins, collections, notes, blocked domains, and retained reading state are stored with your account and synchronized across devices. Hidden stories and layout stay in this browser. The privacy policy has the details.

    Open source: github.com/paulmooreparks/yavchn. Built with PUDL.