@danshipper: Cosign
Summary
The author argues that job roles should be simplified to a single "Shipper" role that focuses on business decisions and prompt engineering, while technical details are handled separately.
View Cached Full Text
Cached at: 09/08/26, 11:27 AM
Cosign
Ravi Ojha (@raviojhax): Every job position should just be Shipper. Gone are the days of just a frontend, backend, devops etc
Real work is now understanding business domain and making right decisions. After that you just plan, prompt and ship.
Tech behind the scenes hardly matters.
Similar Articles
How to Guarantee You Never Ship
This blog post satirically outlines how combining common software development practices like microservices and strict reviews creates multiplicative coordination barriers, hindering product shipping efficiency.
@tbpn: CEO of Every @danshipper says AI increases the demand for human experts because it provides "cheap competence" that onl…
Dan Shipper, CEO of Every, argues that AI increases demand for human experts by providing 'cheap competence' that only humans can transform into valuable, differentiated work, comparing AI to a sandwich where humans frame and evaluate the output.
@lennysan: .@OpenAI's Codex app lead: "A lot of companies are getting rid of the product role, and saying everybody's just going t…
OpenAI's Codex app lead Andrew Ambrosino argues that companies abandoning dedicated product roles in favor of everyone being a 'builder' is a terrible idea, emphasizing the value of product discipline and best practices.
@lennysan: .@danshipper: "The AI jobpocalypse is not a thing. The mass unemployment thing that AI lab CEOs are talking about—that'…
Dan Shipper argues that the AI 'jobpocalypse' is not real, as AI commoditizes past human competence rather than causing mass unemployment. Lenny Rachitsky highlights Shipper's accurate past predictions, including the underappreciated rise of Claude Code.
@bcherny: As engineering, product, design, DS, etc. melt into a new kind of role, I was reflecting on what roles might look like …
Boris Cherny reflects on the convergence of engineering, product, design, and data science roles, proposing five archetypes (Prototyper, Builder, Sweeper, Grower, Maintainer) observed in the Claude Code team and discussing team composition based on product maturity.