Centaur vs. Cyborg Being a Fisherman

Back to stories Open in a window
Article news.ycombinator.com

Centaur vs. Cyborg Being a Fisherman

<pre><code>Disclaimer: This was written by a human, no AI was used in this process :)</code></pre><p>The type of AI user you are can vary, just like people. I recently stumbled upon the debate of <strong>Centaur</strong> v <strong>Cyborg</strong> and it inspired me to look in the mirror and ask the question to myself, am I a Centaur or a <strong>Cyborg</strong>? I pondered on this question for a while and came to the conclusion… I am a <strong>Fisherman</strong>… I will explain.</p><p></p><p>Feel free to take this entry with a grain of sale, it is through my own practical experience using AI at Work at an enterprise level. I believe the debate of <strong>Centaur</strong> v <strong>Cyborg</strong> is particularly intriguing because the practices of prompt engineering are so nuanced and depending on the user and how that user learns and works best will entirely depend which side you lean towards.</p><p></p><p>As I begun using AI more and more, my ways of working and the type of user I was certainly leaned to being a <strong>Centaur</strong>. I enjoy writing, and there is nothing like writing a long context-rich bulleted and detailed prompt, hitting enter, walking away, making a coffee and coming back to a fairly close result to what I was expecting. Just as much as I enjoy hitting that enter button and walking away, I also love hopping into a phone booth, closing the door somewhere, going for a walk with my dog… and absolutely rambling into my phone. I am talking a total brain dump of epic proportions, doesn’t even matter if there is 1-2 minute pauses of nothing left to say… there always is! I provide all the context I can think of, to ensure I encapsulate all of my ideas. In fact, this is often how I begin most of my projects and it works wonders.</p><p></p><p>Vice Versa, through my AI journey when my task gets more narrow and I am building out more complex systems, dashboards or even getting meticulous about UX details, the <strong>Cyborg</strong> arises. Making surgical directions also has its benefits, I tend to find my most creative ideas come out of this process. The pressure and narrow scope creates idea, this does have its downsides, I find myself going down unnecessary rabbit holes implementing designs and unnecessary functionalities purely for the woah factor.</p><p></p><p>With all that that being said, what is the goal of a <strong>Centaur</strong> or a <strong>Cyborg</strong>? Well, realistically speaking, neither of them are real and therefore I reflect on my own AI practices, techniques and ways of working and I eventually get to:</p><p></p><p>Why I am a <strong>Fisherman</strong>?</p><p></p><p>AI at work reminds me alot of fishing, the goal is clear → catch fish = success/mission complete. As a real, daily user of AI at work, the goal is clear → ideate, create, iterate (ideally not alot), implement and make impact = success/mission complete.</p><p></p><p>Depending on the project, scope of the objective I tend to always cast an extremely wide net at the beginning of the project, similar to a commercial <strong>Fisherman</strong>. Figuratively speaking, this is me blabbering into my phone or writing out a novel to start a project: casting out a massive net of context, directing the AI to get my fish.</p><p></p><p>Most <strong>Fisherman</strong> aren’t commercial though, they fish for fun, sitting on a dock and throwing out a single cast for one specific fish. Narrowing that cast, seeking a unique fish, going on a hunt, getting exactly what you are looking for → there is nothing like catching that fish, entering that prompt and getting exactly what you are looking for.</p><p>There is no right or wrong answer here, I write this to shift the conversation towards <strong>Fisherman</strong> :)</p>
Discussion 1 comments · 1 points · wwolfson97 · 2026-08-24
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.

    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

    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 a story row's Open in new reader window button to compare articles. 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.

    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 and Open in a window are one-off actions that do not change your saved default. 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.

    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. Pins, hidden stories, filters and layout are kept in this browser only.

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