2作者: JaimeAlonsoHN27 天前原帖
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
6作者: daikikadowaki27 天前原帖
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>
3作者: fnoef27 天前原帖
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?
1作者: tasssmaal27 天前原帖
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.
1作者: jjdev815727 天前原帖
I kept running into the same problem in large codebases: “temporary” code almost never gets removed. People add TODOs, FIXMEs, or quick hacks to hit a deadline, and six months later nobody remembers why they’re there or who owns them. They quietly turn into production bugs. I built a small CLI that treats those comments as time-bounded instead of permanent. You can attach an expiry date to a TODO in the code, and when the date passes, CI fails and points to exactly where the expired code lives. It works by: scanning comments across any language parsing structured annotations and optionally using git blame to infer who added them and when I tried to keep it simple and CI-friendly rather than tied to any particular language or linter. Here’s the repo if anyone wants to look at the implementation: <a href="https:&#x2F;&#x2F;github.com&#x2F;jobin-404&#x2F;debtbomb" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;jobin-404&#x2F;debtbomb</a> I’d love feedback from people who’ve dealt with long-lived “temporary” code in production.