Tap a claim on the ring to put it at the centre.
← Vibe coding is the new product management.
17 connected korrents · 15 moments from 5 Nov 2022 to 19 Sept 2026. Nearly all of them are about vibe coding .
Everything filed under product management
product management
Everything filed under design
design Same subject Same subject Same subject Same subject Same subject Same subject Same subject Same subject Same subject Same subject Same subject Same subject Same subject Same subject Same subject Same subject Same subject Read this korrent: Vibe coding is the new product management. Vibe coding is the new product management. Last stated 8 months ago
19 Feb 2026
NR
Naval Ravikant — holds since 2026-02-19 — tap for who they are
Same subject: Deciding what software should do and why is still a human job: vibe coding changes the implementation phase far more than the planning phase. — tap to centre the map on it Deciding what software should do and why is still a human job: vibe coding changes the implementation phase far more than the planning phase. Last stated 2 years ago
7 Mar 2025
JN
Jakob Nielsen — holds since 2025-03-07 — tap for who they are
Same subject: A person at maximum vibe-coding speed has about three productive hours a day, and a company that will not let them stop there is going to break. — tap to centre the map on it A person at maximum vibe-coding speed has about three productive hours a day, and a company that will not let them stop there is going to break. Last stated 7 months ago
11 Mar 2026
SY
Steve Yegge — holds since 2026-03-11 — tap for who they are
Same subject: A vibe-coded codebase grows heresies: wrong ideas that take root among the agents, keep coming back, and are very hard to weed out. — tap to centre the map on it A vibe-coded codebase grows heresies: wrong ideas that take root among the agents, keep coming back, and are very hard to weed out. Last stated 7 months ago
11 Mar 2026
SY
Steve Yegge — holds since 2026-03-11 — tap for who they are
Same subject: Designers should be designing right at the boundary of the current model, hoping the next one solves it; understanding what is possible and pushing the edges even if you get stuck is probably a good place to be right now. — tap to centre the map on it Designers should be designing right at the boundary of the current model, hoping the next one solves it; understanding what is possible and pushing the edges even if you get stuck is probably a good place to be right now. Last stated 6 months ago
14 Apr 2026
BL
Brian Lovin — holds since 2026-04-14 — tap for who they are
Same subject: Leaving a known production bug unfixed is the right call when the business impact is zero — my vibe-coded service crashes and still has fewer outages than LeetCode. — tap to centre the map on it Leaving a known production bug unfixed is the right call when the business impact is zero — my vibe-coded service crashes and still has fewer outages than LeetCode. Last stated 4 months ago
24 Jun 2026
NE
NeetCode — holds since 2026-06-24 — tap for who they are
Same subject: Letting non-programmers vibe-code features into a large existing product destroys its architecture, even when every individual change looks defensible. — tap to centre the map on it Letting non-programmers vibe-code features into a large existing product destroys its architecture, even when every individual change looks defensible. Last stated a month ago
26 Aug 2026
DH
David Heinemeier Hansson — holds since 2026-08-26 — tap for who they are
Same subject: Making coding easy makes design more critical, not less: when anyone can produce working features, the quality of the experience is what sets products apart. — tap to centre the map on it Making coding easy makes design more critical, not less: when anyone can produce working features, the quality of the experience is what sets products apart. Last stated 2 years ago
7 Mar 2025
JN
Jakob Nielsen — holds since 2025-03-07 — tap for who they are
Same subject: Mockups existed because coding was hard; now designers can skip static mockups and go straight to building a UI that works. — tap to centre the map on it Mockups existed because coding was hard; now designers can skip static mockups and go straight to building a UI that works. Last stated 2 years ago
7 Mar 2025
JN
Jakob Nielsen — holds since 2025-03-07 — tap for who they are
Same subject: "Simplify onboarding" is an action, not a problem, and a roadmap line written that way will not work. — tap to centre the map on it "Simplify onboarding" is an action, not a problem, and a roadmap line written that way will not work. Last stated 2 years ago
19 Jan 2025
EV
Elena Verna — holds since 2025-01-19 — tap for who they are
Same subject: A company needs someone with a product vision to recover — tap to centre the map on it A company needs someone with a product vision to recover Last stated 4 years ago
5 Nov 2022
DH
David Heinemeier Hansson — holds since 2022-11-05 — tap for who they are
Same subject: A company should define what great looks like for its own role rather than borrow another company's definition. — tap to centre the map on it A company should define what great looks like for its own role rather than borrow another company's definition. Last stated 2 months ago
9 Aug 2026
AW
Adam Ward — holds since 2026-08-09 — tap for who they are
Same subject: A first-time founder has an advantage over a repeat winner, because past success makes it too easy to raise money and hire against a big vision before there is product-market fit. — tap to centre the map on it A first-time founder has an advantage over a repeat winner, because past success makes it too easy to raise money and hire against a big vision before there is product-market fit. Last stated 4 months ago
14 Jun 2026
MP
Mark Pincus — holds since 2026-06-14 — tap for who they are
Same subject: A large company should help its existing product managers become AI-native rather than only hiring people who already are. — tap to centre the map on it A large company should help its existing product managers become AI-native rather than only hiring people who already are. Last stated 4 weeks ago
10 Sept 2026
TY
Tamar Yehoshua — holds since 2026-09-10 — tap for who they are
Same subject: A product can be technically impressive yet fail because it launched before a real market for it existed. — tap to centre the map on it A product can be technically impressive yet fail because it launched before a real market for it existed. Last stated 4 weeks ago
11 Sept 2026
MS
M.G. Siegler — holds since 2026-09-11 — tap for who they are
Same subject: A feature shipped in a product's official release is fair to judge, regardless of whether the company labels it a beta. — tap to centre the map on it A feature shipped in a product's official release is fair to judge, regardless of whether the company labels it a beta. Last stated 4 weeks ago
14 Sept 2026
JS
Jason Snell — holds since 2026-09-14 — tap for who they are
Same subject: Getting from a demo to a product is a march of nines, and each additional nine costs the same amount of work as the one before it. — tap to centre the map on it Getting from a demo to a product is a march of nines, and each additional nine costs the same amount of work as the one before it. Last stated 12 months ago
17 Oct 2025
AK
Andrej Karpathy — holds since 2025-10-17 — tap for who they are
Same subject: Most software bugs will not be coding bugs but bugs from asking for the wrong thing. — tap to centre the map on it Most software bugs will not be coding bugs but bugs from asking for the wrong thing. Last stated 3 weeks ago
19 Sept 2026
TB
Thorsten Ball — holds since 2026-09-19 — tap for who they are
At the centre
Vibe coding is the new product management.
Holds Read this korrent →
Deciding what software should do and why is still a human job: vibe coding changes the implementation phase far more than the planning phase.
Holds
A person at maximum vibe-coding speed has about three productive hours a day, and a company that will not let them stop there is going to break.
Holds
A vibe-coded codebase grows heresies: wrong ideas that take root among the agents, keep coming back, and are very hard to weed out.
Holds
Designers should be designing right at the boundary of the current model, hoping the next one solves it; understanding what is possible and pushing the edges even if you get stuck is probably a good place to be right now.
Holds
Leaving a known production bug unfixed is the right call when the business impact is zero — my vibe-coded service crashes and still has fewer outages than LeetCode.
Holds
Letting non-programmers vibe-code features into a large existing product destroys its architecture, even when every individual change looks defensible.
Holds
Making coding easy makes design more critical, not less: when anyone can produce working features, the quality of the experience is what sets products apart.
Holds
Mockups existed because coding was hard; now designers can skip static mockups and go straight to building a UI that works.
Holds
"Simplify onboarding" is an action, not a problem, and a roadmap line written that way will not work.
Holds
A company needs someone with a product vision to recover
Holds
A company should define what great looks like for its own role rather than borrow another company's definition.
Holds
A first-time founder has an advantage over a repeat winner, because past success makes it too easy to raise money and hire against a big vision before there is product-market fit.
Holds
A large company should help its existing product managers become AI-native rather than only hiring people who already are.
Holds
A product can be technically impressive yet fail because it launched before a real market for it existed.
Holds
A feature shipped in a product's official release is fair to judge, regardless of whether the company labels it a beta.
Holds
Getting from a demo to a product is a march of nines, and each additional nine costs the same amount of work as the one before it.
Holds
Most software bugs will not be coding bugs but bugs from asking for the wrong thing.
Holds