最新

There’s a point where growth stops feeling like momentum and starts feeling like an anchor.<p>It’s not a lack of effort. It’s the complexity threshold.<p>We just ran the first Vision diagnostics for real companies. From tech startups to 50-person firms, and the data is clinical:<p>By the time you hit 25 people, decision latency spikes by 30–50%.<p>On the surface, you look fine. Underneath, the system is opaque. You aren&#x27;t scaling leverage; you’re scaling chaos.<p>What this looks like in the trenches:<p>- The Manual Glue: Teams compensate for broken workflows with manual workarounds. We call it the friction tax. - The Artisan Trap: You’re in &quot;craft mode&quot; (bespoke tasks) rather than &quot;platform mode&quot; (scalable systems). - The Insight Gap: Simple questions take three days and four spreadsheets to answer.<p>In one Vision report, revenue was up 18%, but costs ballooned 27%. They were paying a premium to grow slower.<p>The reality…<p>Most leaders optimize nodes (hiring, new tools). But the bottleneck is the constraint.<p>True transformation follows one law.<p>Intelligence precedes action.<p>Once these companies saw their diagnostic, the fix was simple: Solidify the data spine and prune low-leverage work. This unlocked 12–20% operating leverage without one new hire.<p>When a system finally sees itself, the weight lifts.<p>Decisions compress.<p>Waste becomes visible.<p>If your org feels heavy, you don&#x27;t need more ambition. You need a cognitive core.<p>Vision by Cultivation was built to be that core.<p>Run the diagnostic. Name the thing you’ve been feeling.<p>→ heycultivation.com<p>It takes 60 seconds. It might save your next two years.

I am a big fan of apps like Tricount, but yesterday, I was with some friends and found that creating a group and adding everyone was a burden for a simple calculation.<p>I thought that a simple website to add people and expenses with no sign-ups&#x2F;ads (or downloading another app) to calculate payments automatically would be helpful.<p>So I created and published it. It is very simple but I think nice-to-have for one-day trips&#x2F;activities.<p>https:&#x2F;&#x2F;splitcostonline.com<p>Let me know your thoughts :)<p>Jaime

Inspired by TAWS. Built as a learning exercise.

I’m an independent researcher proposing State Discrepancy, a public-domain metric to quantify how much an AI system changes a user’s intent (“the Ghost”).<p>The goal: replace vague legal and philosophical notions of “manipulation” with a concrete engineering variable. Without clear boundaries, AI faces regulatory fog, social distrust, and the risk of being rejected entirely.<p>Algorithm 1 (on pp.16–17 of the linked white paper) formally defines the metric:<p>1. D = CalculateDistance(VisualState, LogicalState)<p>2. IF D &lt; α : optimization (Reduce Update Rate)<p>3. ELSE IF α ≤ D &lt; β : warning (Apply Visual&#x2F;Haptic Modifier proportional to D)<p>4. ELSE IF β ≤ D &lt; γ : intervention (Modulate Input &#x2F; Synchronization)<p>5. ELSE : security (Execute Defensive Protocol)<p>The full paper is available on Zenodo: <a href="https:&#x2F;&#x2F;doi.org&#x2F;10.5281&#x2F;zenodo.18206943" rel="nofollow">https:&#x2F;&#x2F;doi.org&#x2F;10.5281&#x2F;zenodo.18206943</a>

I have been mostly anti AI. I did experiment a bit with aider and free models, but my results were inconsistent, and nothing to worry about.<p>However, recently I have purchased the max plan from anthropic and have been vibing with Claude code since then. And wow, the results are very good. With a good enough prompt, and planning step, it could generate full features in a project with 20k LOC, with very little modifications needed by me after review.<p>I heard even more success stories from friends who gave Claude 3-4 different features that Claude would develop in parallel.<p>On top of that, everyone seems to produce side project at an astronomical rate, both among my friends, and here on HN where fully complete project that would take months to develop, seem to appear after few hours with Claude code.<p>So, my questions is, is programming as a profession cooked? Are most of us going to be replaced with a “supervisor” who runs coding agents all day?

Hi HN,<p>When production breaks, writing a clear and honest incident report is stressful and slow — especially while customers and teammates are waiting.<p>I built IncidentPost to solve that. You paste a raw outage timeline (alerts, Slack logs, timestamps) and it generates a professional, shareable postmortem with an executive summary, timeline, root cause, mitigations, and action items.<p>You can see a full demo output here: <a href="https:&#x2F;&#x2F;incidentpost.vect.pro&#x2F;demo" rel="nofollow">https:&#x2F;&#x2F;incidentpost.vect.pro&#x2F;demo</a><p>Live app: <a href="https:&#x2F;&#x2F;incidentpost.vect.pro" rel="nofollow">https:&#x2F;&#x2F;incidentpost.vect.pro</a><p>It’s a one-time purchase per incident — no accounts, no subscriptions.<p>I’d love feedback from engineers, SREs, and founders who’ve had to write postmortems under pressure.