LinkedIn Larpmaxxing
- ID
- 30843
- Status
- summarized
- Published
- 30 Sep 2026, 12:19 PM
- Fetched
- 02 Oct 2026, 12:26 AM
- Provider
- Hacker News
- Category
- dev-community
- Original URL
- https://hereticpleb.vercel.app/blog/linkedin-larpmaxxing/
- Source URL
- https://hnrss.org/best
Summary
- Score
- 5.5
- Created
- 02 Oct 2026, 12:28 AM
- Tags
- Audience
- developersvibe_codersai_ml_learnersstartup_founders
What happened
A satirical blog post (dated Sept 28, 2026, ~6 min read) argues LinkedIn's feed is dominated by near-identical computer-vision demo posts — hand-tracking webcam tricks and a pothole-detection project — which the author says are either tutorial-derived or vibecoded, and which in the pothole case 'is not sending it to anything.' As a counter-move, the author describes building a 'YOLO Post Detector' aimed at the '🚀 Excited to announce...' style of post. The Hacker News thread drew 270 points and 222 comments.
Why it matters
If you are building a portfolio or launch demo to post publicly, this piece gives a concrete differentiation test rather than a vibe check: does the output go somewhere? The author singles out the pothole detector because it only displays a detection locally instead of feeding an API or downstream action — the same criticism would apply to any hand-tracking or object-detection demo that ends at a bounding box on screen. Decide now whether your next demo has a consumer of its output (an alert, a ticket, a dashboard, a dataset) or is just a webcam effect, because the audience this piece represents can no longer tell them apart. Note: the text contains no Malaysian or Southeast Asian angle, so there is no local policy, funding, or infrastructure impact to draw from it.
Discussion angle
Run your last public demo through the author's test — does the detection go anywhere after the bounding box appears? If not, what is the smallest downstream action (a webhook, a stored record, an alert) that would make it defensible?