Show HN: The Cascade Graph – An interactive map of AI and energy constraints https://ift.tt/O47EcUS

Show HN: The Cascade Graph – An interactive map of AI and energy constraints Hello, I wanted to share with you all a interactive map of the economics and physics constraints of the AI buildout. It has macro drivers, industrial chokepoints, and where that shows up in markets. I've added 393 nodes and 562 edges to capture other supply / physics constraints as well. There's no sign up, and no pay wall, it's all free. Please let me know what you think! https://ift.tt/Wqsz6Dp June 23, 2026 at 08:52PM

Show HN: I created agent skill based on Peter Lynch's books https://ift.tt/p0wT5nA

Show HN: I created agent skill based on Peter Lynch's books For the last few months I have been analysing Peter Lynch’s books on stock picking and doing prompt engineering to check if AI could create useful stock analyses. To my surprise it started making reports that allow me to understand companies much faster with well cited sources. I hope you find it interesting and useful :) Perter Lynch’s books I analyzed: Learn to earn, One up on Wall Street, Beating the street https://ift.tt/OuT2bgJ June 24, 2026 at 12:32AM

Show HN: Loft gives thumb-keys and split-layout on a standard laptop or keyboard https://ift.tt/pc2OxM1

Show HN: Loft gives thumb-keys and split-layout on a standard laptop or keyboard I've put up a homepage for my keyboard layout, LOFT, and thought I'd share in case anyone found it interesting... LOFT is free on macOS and remaps your laptop and standard keyboard into the thumb-keyed, split-layout, ergonomic dream you've been seeking! It positions your hands up and out in a creative way to get you all the goodies you thought you'd need some garage-built, geek-contraption for. All on a standard ANSI keyboard. Maybe of interest is that the site's keyboard graphics are all generated HTML+CSS via Hugo partials. https://ift.tt/bZ5PcIu June 23, 2026 at 08:20AM

Show HN: Durable Agent Sessions API (Preview) https://ift.tt/r7FUYks

Show HN: Durable Agent Sessions API (Preview) https://ift.tt/51rLRt3 June 23, 2026 at 07:07AM

Show HN: Kitcat 2.0 – A Matplotlib back end for terminal plotting https://ift.tt/2Fo34f5

Show HN: Kitcat 2.0 – A Matplotlib back end for terminal plotting https://ift.tt/rMFy7Xa June 22, 2026 at 11:00PM

Show HN: Pure Effect – Reproduce production bugs on your laptop without a DB https://ift.tt/0JPUXjn

Show HN: Pure Effect – Reproduce production bugs on your laptop without a DB Hi HN, I think it's safe to say that the majority of developers don't give a second thought to writing code with I/O tangled in business logic. It's all too common to see code like: const user = findUser(email); if (!user) await saveUser(user); Now, you may ask: what's the big deal? When we write code like this, two things happen: 1. It gets harder to debug production bugs. Unless you have the exact same database and remote API services to connect to, you may fail to reproduce the bug. 2. You have to use mocks and fakes in your tests, or use test containers, which only help somewhat, and they are slow! To solve these issues, I built Pure Effect, a tiny TypeScript/JavaScript effect library. The core idea is simple: if a function performs I/O, it isn't pure. But if it returns a description of the I/O it wants to perform, it is. So instead of await findUser(email), you return a Command object that says, "I would like to call this function, and when it finishes, here's what to do next." Your business logic becomes a pure function. Same input, same output, every time. The database never gets touched until the interpreter (runEffect) runs. When I first started the library, I didn't expect just how far that one idea would stretch. Once your pipelines are just data, a lot of wonderful things become possible: - No need for mocking libraries. You walk the tree in tests and assert on its structure: assert.equal(flow.cmd.name, 'cmdFindUser'). Nothing is executed. - Wrap any effect with Retry(effect, { attempts: 3, delay: 200, backoff: 2 }). The configuration is plain data, so you can assert on it in tests. - Every command's input and output flows through the interpreter, so you get a full execution trace for free. You can write a simple timeTravel() function that replays it locally without touching any I/O. Perfect for debugging complex production bugs. - An onBeforeCommand hook sits between your business logic and the interpreter. Since it sees every intended side effect before it fires, it can be used to enforce runtime guardrails. You can quarantine destructive calls before they happen for example. - You can review AI-generated code before it runs. Since Pure Effect pipelines are plain data, you can inspect what the generated code intends to do before it touches anything. There are just six primitives: Success, Failure, Command, Ask, Retry, and Parallel, plus effectPipe and runEffect. Zero dependencies. Under 1 KB minified and gzipped. How it compares to Effect-TS Effect-TS is the full-featured option in this space and has a large ecosystem. Pure Effect offers a different tradeoff. It covers the 80% case: testable pipelines, dependency injection, retry, and OpenTelemetry hooks, all in under 1 KB with zero dependencies and no new vocabulary to learn. Effect-TS is a framework you build around. Pure Effect, on the other hand, is a pattern you drop into existing code. I've been using Pure Effect in production since December. It's at v0.8.0, not 1.0 yet, but stable enough that I wanted to put it out there and hear what people think. GitHub: https://ift.tt/QSyexEs I wrote five posts that document how Pure Effect evolved. They are tagged at https://ift.tt/TfcXLNw if you want the longer story. https://pure-effect.org June 21, 2026 at 11:06PM

Show HN: DebugBrief – turn debugging sessions into reports, no AI https://ift.tt/F3yUf2V

Show HN: DebugBrief – turn debugging sessions into reports, no AI https://ift.tt/ltmZE45 June 22, 2026 at 01:27AM