🛠️ All DevTools

Subquadratic – Introducing SubQ 1.1 Small

Show HN: git-lrc – Free, Micro AI Code Reviews That Run on Git Commit Hi HN, I&#x27;m the author of git-lrc, would appreciate some feedback from the community<p>Last year my team started using AI coding tools more heavily, and we found ourselves generating tons of code, but spending less time looking at the stuff that&#x27;s been generated.<p>We felt like we were losing a bit of grip&#x2F;understanding of what we were building. Regressions occasionally slipped through. Sometimes changes made it all the way to production only to be reverted later.<p>We tried several AI code review tools, but most operate at PR time. That felt too late. I wanted review to happen while the implementation was still fresh in the developer&#x27;s mind at a team level (soft enforcement). I also wanted to emphasize responsibility for keeping prod stable with each individual engineer.<p>So I built git-lrc.<p>When you commit, git-lrc opens a review UI with your diff. It summarizes what changed, points out things that deserve a second look, and lets you quickly jump through the important parts of the change.<p>Over time, git-lrc has grown to check for around 100 common risk patterns across 10 categories, including security, reliability, performance, maintainability, etc.<p>Note that this is far from a formal review. It&#x27;s a quick 60 seconds spent looking at your own work before it gets recorded in git.<p>It also generates a short &quot;summary deck&quot; that highlights the main changes, with special emphasis on potential risks. With git-lrc you can quickly sanity-check what you&#x27;re about to ship and obtain greater confidence in what&#x27;s been generated.<p>In my mind it is less of an AI reviewer and more as a habit for AI-assisted development: a small pause to make sure we understand and stand behind the code we&#x27;re shipping.<p>Developers can review the change, vouch for it, or consciously skip the review. Those decisions get recorded in git history, creating a trail of how code was reviewed before it shipped.<p>It&#x27;d be great if you could take a look, give it a try in your projects or teams and let me know what you think.<p>Happy to take feedback from the HN community and improve it over time!<p>GitHub: <a href="https:&#x2F;&#x2F;github.com&#x2F;HexmosTech&#x2F;git-lrc" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;HexmosTech&#x2F;git-lrc</a>

'Wow, it really worked ': 70s TV show causing worldwide panic today

A lightweight, lightning-fast, in-process vector database

SpaceX to buy Cursor AI coding agent operator Anysphere for $60B

Feds freaked over Fable 5 after simple 'fix this code' prompt, not jailbreak

Understanding the rationale behind a rule when trying to circumvent it

The time the x86 emulator team found code so bad they fixed it during emulation

Show HN: Garden of Flowers – an archive of pictorial typography before ASCII art Hey all, I made this. The archive started with my 2015 BA thesis on Amiga ASCII art when I was curious about the history of ASCII art but found very little on text art that came before it. The historical precursors are often attributed to typewriter art and shaped&#x2F;visual poetry, but I think letterpress is overlooked. So, I got slightly obsessed and started a personal database of pictures built entirely from metal type, ornaments, and rule, some going back to the 1600s. After eight years, I&#x27;ve managed to find ~2500 images. My friend Adel Faure built the website so it&#x27;s now browseable by anyone!<p>I would like to note that most images are from public digital collections (Internet Archive, national libraries, etc.) and displayed without permission (for educational purposes). I&#x27;ve tried to source every image, but check the original source and its license before reusing anything. I&#x27;d be happy to take down or correct anything.<p>It&#x27;s also incomplete and surely has errors and misattributions. Corrections to anything are very welcome.<p>If anyone has leads on works I haven&#x27;t catalogued, I&#x27;d love to hear them! The practice and pictures are scattered across languages and keywords (type picture, typosignet, typotectur, Bildsatz, stigmatypie, stunt typography...), so things hide in odd corners of archives. If you&#x27;ve seen something like this, please point me at it.<p>There&#x27;s also a longer essay on how it began: <a href="https:&#x2F;&#x2F;garden-of-flowers.heikkilotvonen.com&#x2F;?essay" rel="nofollow">https:&#x2F;&#x2F;garden-of-flowers.heikkilotvonen.com&#x2F;?essay</a>

Microsoft turns to AWS as GitHub faces AI capacity crunch

Show HN: Claude Code for Visual Studio (native diff with accept/reject) VS Code and JetBrains have official Claude Code IDE integration, but Visual Studio doesn&#x27;t. There&#x27;s an open GitHub issue with a lot of +1s so I built it myself (check out the gif in the GitHub repo for a visual example).<p>It implements the same protocol the official plugins use, so the Claude CLI connects to it automatically. You don&#x27;t configure anything, just install the extension and click Launch.<p>The main thing it adds over running Claude in a terminal is that edits open in Visual Studio&#x27;s native diff viewer instead of auto-applying or prompting you in the terminal. You click Accept or Reject right there. You can also reject with a reason, and Claude will take another pass.<p>It also shares your compiler errors (C# and C++) and your current selection with the CLI automatically, so Claude has context without you having to copy-paste anything.<p>A few other things: - There&#x27;s a dockable panel with connection status and token&#x2F;cost stats for the session - A &quot;run wild&quot; toggle to auto-accept edits without opening the diff Works with the existing claude CLI, no model calls of its own<p>Marketplace: <a href="https:&#x2F;&#x2F;marketplace.visualstudio.com&#x2F;items?itemName=firish.bridgev1" rel="nofollow">https:&#x2F;&#x2F;marketplace.visualstudio.com&#x2F;items?itemName=firish.b...</a><p>GitHub: <a href="https:&#x2F;&#x2F;github.com&#x2F;firish&#x2F;claude_code_vs" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;firish&#x2F;claude_code_vs</a>

San Francisco Weighs PG&E Takeover Amid Soaring Utility Costs

Show HN: Transpilatron – an AI tool that converts Python code into C binaries

Show HN: We built an 8-bit CPU as 2nd year EE students Hi! me and my friends together built an 8 bit CPU implemented in Logisim purely from scratch. The control unit of this system does not implement the generic microcode ROM or any kind of RAM. This was made purely from discrete logic gates and coded the system to run different programs.<p>key features: Custom 16-instruction Harvard ISA, 8-bit fixed format, 4 general purpose registers<p>Hardwired control unit built entirely from AND&#x2F;OR gate logic matrix<p>Dual-phase clocking to eliminate race conditions<p>Bootstrap Control Unit that cold-boots via ROM-to-RAM transfer Early-exit conditional branching that saves upto 25% cycles when conditions aren&#x27;t met<p>Full design specification document with version control<p>Since this was our first time doing such teamwork and a new thing we used RISC based system that fetches an 8-bit instruction from Instruction memory 4 bits of which translate to an instruction the last two bits are for source and destination registers. There are a total of 4 registers in the system with two memory units namely Data SRAM and I SRAM, the system follows a Harvard architecture.<p>There are design discrepancies too since it was our first time designing such a system and on top of that completely hardwired too.<p>To solve the problem of cold booting a bootloader is present too that copies the contents of a temporary ROM into instruction RAM and then hands over the reins to the CPU.<p>We also implemented conditional branching as well as early exit branching too that only checks for zero or carry flag and branches without wasting cycles, if the conditions are not met the Program counter increments.<p>Moreover we also created a complete documentation with version control describing each necessary part assuming prior knowledge.<p>Please take a look at it at <a href="https:&#x2F;&#x2F;github.com&#x2F;c0rRupT9&#x2F;STEPLA-1" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;c0rRupT9&#x2F;STEPLA-1</a><p>For future development I want to implement a RISC CPU using FPGA&#x27;s and connect it to an actual DRAM. We are also selling the full spec document and Logisim files for $5 to fund our passion <a href="https:&#x2F;&#x2F;tcfdiq.gumroad.com&#x2F;l&#x2F;zyyux" rel="nofollow">https:&#x2F;&#x2F;tcfdiq.gumroad.com&#x2F;l&#x2F;zyyux</a> Thankyou!

What job interviews taught me about Kubernetes

Show HN: StarScope – Free astronomy dashboard for observers outside the US/UK

Show HN: A pure-Ruby X11 terminal I use this as my regular xterm replacement... Why? Because I can.<p>It&#x27;s pure-Ruby down to the font-renderer, and the X11-bindings.<p>(I also run a Ruby WM, a Ruby editor, file manager, and more, so this is just par for the course of my descent into madness)<p>It supports double-width and double-height text, unicode (but double-width characters may currently be rescaled down), layering fonts, special rendering of box-drawing characters (to ensure they seamlessly scale and connect, and has reasonably complete vt-100&#x2F;vt-102 emulation. The whole thing is available as a Rubygem and comes with an ANSI text backend, so you can run your terminal in your terminal. The bulk was written manually, but the last few days I had Claude write a test harness to shake out a bunch of bugs, and start refactoring and cleaning up the code base (it&#x27;s still full of warts).

Show HN: Vet turned founder, AI lawn diagnosis I know, it&#x27;s kind of weird. What is a veterinarian doing creating an analysis tool for lawn problems?<p>Frankly, the idea was born of my own lawn care struggles. Endless lawn care company fees without any actual improvement. Googling problems and finding generic solutions without regional considerations. One time I overseeded my grass not realizing I had to actually put soil down too.<p>One day, I decided to run lawn pictures through AI and found some pretty helpful information. So I decided with my clinical background (the idea of treating the cause, not just the symptoms), as well as tech savvy, I would create an AI tool where homeowners can upload pictures of their lawn, enter their ZIP code, and get a diagnosis tailored to their location with actionable next steps in just 15 seconds.<p>Completely free. The platform is monetized with affiliate sales (if a user elects to purchase through one of our Amazon or other links) and by selling exclusive rights to individual ZIP codes to lawn care companies seeking warm leads. Users can pursue their own DIY plan, purchase a lawn care subscription service, or contact a local lawn care system.<p>I&#x27;d love if you&#x27;d test it out, toy with it, try to break it, and give me your feedback. Any feature requests would be super helpful.<p>Thanks! Excited to hear your thoughts.<p>Andrew

PRC-linked spies hid inside medical and military networks for more than a year

Show HN: machine0 – Persistent NixOS VMs You Control from the CLI Hi HN! Excited to launch machine0, a CLI that makes it easy to create, provision and snapshot persistent NixOS (&amp; Ubuntu) VMs.<p>You can think of machine0 as a modern VPS provider. VMs stay on unless switched-off (with 99.99% uptime), they have static IPs and HTTPS endpoints, 1-60 vCPU, up to 240GB RAM and optionally GPUs. The CLI provides commands to manage lifecycle, snapshots and also provision the VMs using Nix flakes or Ansible playbooks. VMs are priced by the minute of usage.<p>What makes machine0 unique is that it has first class support for NixOS! In a nutshell, NixOS lets you define your entire OS as code (think Terraform but for your Linux). A flake declares your system state (packages, services, firewall rules, users...) and pins all dependencies via a lockfile. Given the same flake.nix and flake.lock, `nixos-rebuild switch` always produces the exact same system.<p>The NixOS ecosystem is mature, and flakes are expressive: at the system level you can define packages, what&#x27;s in &#x2F;etc, firewall rules, users &amp; groups etc. At the user level, you can define your shell, aliases, tmux and vim config. Having your entire environment defined as code makes it easy to audit what&#x27;s installed and how things are set up. You can rollback by reverting the last commit. And agents can write the code for you and test it against disposable machine0 VMs.<p>If you&#x27;d like to dive right in, these commands will get you started:<p><pre><code> npm install -g @machine0&#x2F;cli machine0 new my-vm --image nixos-25-11 # create a new nixos VM machine0 provision my-vm .&#x2F;flake#my-profile # provision it using a nix flake machine0 ssh my-vm # ssh in machine0 stop my-vm # stop the VM machine0 images new my-vm my-snapshot # create a snapshot machine0 new my-clone --image my-snapshot # create a new VM from the snapshot </code></pre> - Demo of installation + NixOS provisioning via Claude Code: <a href="https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=RT8N0_e3Vfg" rel="nofollow">https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=RT8N0_e3Vfg</a><p>- Documentation: <a href="https:&#x2F;&#x2F;docs.machine0.io&#x2F;introduction&#x2F;overview">https:&#x2F;&#x2F;docs.machine0.io&#x2F;introduction&#x2F;overview</a><p>- machine0 NixOS flakes: <a href="https:&#x2F;&#x2F;github.com&#x2F;fdmtl&#x2F;machine0-nixos" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;fdmtl&#x2F;machine0-nixos</a><p>If you&#x27;re in the habit of using VMs, or want to know what the NixOS fuss is about, would love for you to give machine0 a try!