Shameless self-promoting Twats… “I Just Shipped Something”, A Love Letter to the Most Insufferable People on the Internet.
There is a specific type of person who has colonized LinkedIn, Twitter/X, and every startup Discord in existence. You know who they are. You’ve seen them. You may have accidentally followed one. They don’t write software. They don’t really build anything, exactly. But they are, at all times, shipping.
They are the Ship Bros. And we need to talk about them.
What Is a Ship Bro?
A Ship Bro is not a software engineer. This is important. A software engineer writes code, debugs systems, thinks about architecture, and does not post about it constantly because they’re too busy actually doing it.
A Ship Bro is someone who has discovered that talking about building things generates more engagement than building things, and has fully committed to this as a lifestyle. They use Claude or Cursor or Replit to generate a landing page, add a Stripe link, and announce to the world that they have “shipped a product.” They have not written a function. They have never written a function. The closest they have come to a function is typing “make me a SaaS” into a chatbox.
This is fine! AI tools are great! But something has gone terribly wrong when the word “shipping”, a term that used to mean “deploying working software built by engineers after weeks of effort”, has been repurposed to mean “I saved a Notion template to Gumroad.”
The Lingo That Haunts Us
Ship Bros communicate in a dialect that sounds like someone fed a Y Combinator blog post into a blender:
“We just shipped.” Shipped what? To whom? What does it do? These are irrelevant questions. The shipping is the point. The shipping is the product.
“Building in public.” This means posting about a product instead of building it. The audience becomes the accountability mechanism. The accountability mechanism becomes the content. The content becomes the product. No actual product exists.
“Vibe coding.” Ah yes. This one. This is when you describe what you want to an AI, it generates code you don’t understand, you deploy it, and you tell people you “coded” something. Look, this is genuinely useful! But calling it “coding” is like calling GPS “navigation.” You didn’t navigate. You sat in a car.
“0 to 1.” This phrase means “I started something.” Every human who has ever done anything has gone from 0 to 1. Your dog learned to sit. That was 0 to 1.
“We’re a small team moving fast.” It’s one guy in an Airbnb.
The LinkedIn Bio: A Crime Scene
Nothing reveals the Ship Bro more completely than their LinkedIn bio. It reads like a personality disorder formatted as bullet points:
Serial Founder | Builder | Maker | Shipper | 0→1 | Former [startup with 11 employees that pivoted twice and died] | Currently building something big | Ex-YC (attended an info session)
“Serial founder” used to mean someone who had founded multiple companies. It now means someone who has had multiple ideas they announced on the internet. The bar for “founder” has collapsed so completely that you can found something by buying a domain name and then abandoning it.
“Maker” is particularly rich. A maker! Like a craftsperson! A blacksmith! A cobbler! Someone who makes things with their hands! Except in this context it means “person who used Webflow.”
The Comparison to “Serial Entrepreneur”
Here’s the thing: “serial entrepreneur” used to be the cringiest phrase in startup culture. It was what people called themselves when they wanted to sound important without specifying what any of their companies actually did. We all agreed, quietly, that it was embarrassing.
But “I ship” has lapped it. It has sprinted past “serial entrepreneur” and is now somewhere in the distance, getting smaller. At least a serial entrepreneur implied some economic activity, however vague. The Ship Bro has dispensed with even that pretense. They have distilled self-promotion to its purest form: a verb, applied to nothing in particular, repeated indefinitely.
Who Gets Hurt?
Let’s be clear: no one is getting hurt. This is all pretty harmless. The Ship Bros are, at worst, annoying. Most of them are earnest people who genuinely want to build things and have gotten slightly intoxicated on startup culture’s dopamine loop of announcement → applause → announcement.
The real victims are the words. “Ship.” “Build.” “Founder.” “Engineer.” Each of these once described something specific and has been stretched into meaninglessness. Every person who has actually spent three years learning to write production software has to share the word “builder” with someone who made a Carrd website in an afternoon.
That’s the genuine complaint here. Not that AI tools exist, they’re incredible. Not that non-technical people start businesses, please do. But that an entire culture has formed around performing the act of building rather than the act itself, and has colonized the vocabulary of people who actually do the work.
How to Spot One in the Wild
- Posts the phrase “excited to share” more than twice a month
- Their product’s landing page has more social proof logos than features
- References “the community” they’re building, which has 40 members, 38 of whom are also Ship Bros
- Has a newsletter about building a newsletter
- Calls a ChatGPT wrapper their “AI company”
- Uses the word “momentum” to describe the experience of having posted something yesterday
- Their GitHub is either empty or has one repository called
my-saas-templatewith zero stars
The Builder: Ship Bro’s Philosophical Cousin
If the Ship Bro is annoying in a loud, caffeinated, Product Hunt kind of way, the Builder is annoying in a quieter, more spiritual sense. They have transcended the need to ship. They have gone beyond. They simply… build.
“I build things.”
That’s it. That’s the bio. No further context. What things? For whom? With what tools? These are questions for lesser minds. The Builder builds. The building is self-evident. To ask for specifics is to reveal that you don’t understand the building.
The Builder posts differently from the Ship Bro. Where the Ship Bro announces, the Builder reflects. Where the Ship Bro says “we just shipped,” the Builder says something like:
“Most people want the result. Builders fall in love with the process.”
Two thousand likes. Seventeen comments saying “this.” Three comments saying “so true, keep building brother.” One comment from someone asking what they’re actually building, which gets no reply.
The Builder’s relationship with completion is, let’s say, flexible. Things are always being built. The building is perpetual. To finish something would be to stop being a builder, and then who are you? The Builder’s identity is load-bearing. If the product shipped, the builder would dissolve.
The Crucial Difference (There Isn’t One)
Here is where it gets philosophically interesting: the Ship Bro and the Builder are, at the infrastructure level, identical. Both have Cursor open. Both have a half-finished Carrd site. Both have a Discord server with 40 members who are also Ship Bros and Builders. Both have not written a function.
The difference is purely aesthetic. The Ship Bro is optimistic and loud. The Builder is pensive and vague. The Ship Bro says “we shipped v2 🚀.” The Builder says “iteration is the builder’s meditation.” They’re describing the same Notion page update.
What truly unites them — what makes them a distinct and coherent category of internet person — is the performance of technical identity without the technical part. They have discovered that the social rewards of being someone who builds things are available without the inconvenience of building things, provided you post about it confidently enough.
| Feature | Software Engineer | “Shipper” |
| Primary Skill | Problem-solving, algorithm design, understanding computer science principles | Using low-code/no-code platforms, copying and pasting templates |
| Focus | Building robust, scalable, and maintainable systems | Getting something, anything, live as quickly as possible |
| Vocabulary | Algorithms, data structures, complexity analysis, design patterns, testing frameworks | “Shipping,” “building in public,” “vibe coding,” “stack,” “product-market fit” (without understanding what it actually means) |
| Response to Bugs | Methodical debugging, root cause analysis, implementing robust fixes | Panic, blaming the platform, “shipping” a quick-and-dirty patch that probably breaks something else |
| Understanding of Technology | Deep understanding of how the underlying systems work | Superficial understanding of how to use a specific tool or platform |
| Motivation | Creating elegant and effective solutions to complex problems | Looking cool on social media, getting “likes” and “retweets,” being seen as a “tech visionary” |
| Weekend Plans | Reading a book on a new programming paradigm, working on a personal project that will never see the light of day | Attending a hackathon (where they will mostly just network and use low-code tools), posting pictures of their “workspace” (which is probably just a coffee shop) |
| Reaction to the word “Shipper” | A deep sigh, followed by a sudden urge to explain the difference between a for loop and a foreach loop again | Immediate excitement, accompanied by a lengthy explanation of all the products they have “shipped” that month |
| Reality Check | Knows that software development is hard work, requiring patience, discipline, and a constant willingness to learn | Believes that software development is easy and that anyone can do it (as long as they have the right “vibes” and are comfortable with a low-code platform) |
A Handy Self-Test
Not sure if you’re a Builder? Ask yourself:
- Have you described something as “the build” in the last 30 days?
- Do you have a newsletter about your creative process that predates having a creative output?
- Have you used the phrase “I build in public” and then posted exclusively about building in public, creating a closed loop with no external product?
- Do you refer to asking ChatGPT to write your backend as “engineering”?
- Is your company name a single lowercase word with no vowels?
If you answered yes to three or more: welcome. You’re one of us now. You’re a Builder.
In Conclusion
Ship Bros: we see you. We know you. Some of us have become you briefly, at 11pm after too much coffee, when we posted “Day 1 of building in public!” and then never posted again because we got busy actually living our lives.
The antidote is simple. If you want to build things: build things. If you want to learn to code: learn to code. If you want to use AI to make stuff: make stuff, and call it what it is.
And if you ship something, truly ship it, in the sense that real humans use it and pay for it and it does something useful, you are allowed to tell people. Once. Without a thread.