🛠️ All DevTools

[Database] Show HN: Rocky – Rust SQL engine with branches, replay, column lineage Hi HN, I&#x27;m Hugo. I&#x27;ve been building Rocky over the past month, shipping fast in the open. The binary is on GitHub Releases, `dagster-rocky` on PyPI, and the VS Code extension on the Marketplace. I held off on a broader announcement until the trust-system surface was coherent enough to talk about as one thing. The governance waveplan — column classification, per-env masking, 8-field audit trail on every run, `rocky compliance` rollup, role-graph reconciliation, retention policies — landed end-to-end last week in engine-v1.16.0 and rounded out in v1.17.4 (tagged 2026-04-26). That&#x27;s the milestone I&#x27;d been waiting for.<p>The pitch: keep Databricks or Snowflake. Bring Rocky for the DAG. Rocky is a Rust-based control plane for warehouse pipelines. Storage and compute stay with your warehouse. Rocky owns the graph — dependencies, compile-time types, drift, incremental logic, cost, lineage, governance. The things your current stack can&#x27;t give you because it doesn&#x27;t own the DAG.<p>A few things I think are interesting:<p>- Branches + replay. `rocky branch create stg` gives you a logical copy of a pipeline&#x27;s tables (schema-prefix today; native Delta SHALLOW CLONE and Snowflake zero-copy are next). `rocky replay &lt;run_id&gt;` reconstructs which SQL ran against which inputs. Git-grade workflow on a warehouse.<p>- Column-level lineage from the compiler, not a post-hoc graph crawl. The type checker traces columns through joins, CTEs, and windows. VS Code surfaces it inline via LSP.<p>- Governance as a first-class surface. Column classification tags plus per-env masking policies, applied to the warehouse via Unity Catalog (Databricks) or masking policies (Snowflake). 8-field audit trail on every run. `rocky compliance` rollup that CI can gate on. Role-graph reconciliation via SCIM + per-catalog GRANT. Retention policies with a warehouse-side drift probe.<p>- Cost attribution. Every run produces per-model cost (bytes, duration). `[budget]` blocks in `rocky.toml`; breaches fire a `budget_breach` hook event.<p>- Compile-time portability + blast radius. Dialect-divergence lint across Databricks &#x2F; Snowflake &#x2F; BigQuery &#x2F; DuckDB (12 constructs). `SELECT *` downstream-impact lint.<p>- Schema-grounded AI. Generated SQL goes through the compiler — AI suggestions type-check before they can land.<p>What Rocky isn&#x27;t:<p>- Not a warehouse — it&#x27;s the control plane on top.<p>- Not a Fivetran replacement. `rocky load` handles files (CSV&#x2F;Parquet&#x2F;JSONL); for SaaS sources use Fivetran, Airbyte, or warehouse-native CDC.<p>- Not dbt Cloud — no hosted UI, no managed scheduler. First-class Dagster integration if you need orchestration.<p>Adapters: Databricks (GA), Snowflake (Beta), BigQuery (Beta), DuckDB (local dev &#x2F; playground). Apache 2.0.<p>I&#x27;d love feedback on the trust-system framing, the governance surface (particularly classification-to-masking resolution in `rocky compile` and the `rocky compliance` CI gate), the branches&#x2F;replay design, the cost-attribution primitives, or anything else that catches your eye. Happy to go deep in the thread.

[Other] GitHub Actions is the weakest link

[Other] Who owns the code Claude Code wrote?

[Other] An Update on GitHub Availability

[Other] GitHub Copilot code review will start consuming GitHub Actions minutes

[Other] Show HN: Devicons, +1300 logos and icons in React, SVG, and icon format After a very long time I&#x27;ve spend a great amount of time revisiting my very first open source project.<p>+1300 logos and icons coming along with a brand new website, high fidelity SVG files, extended documentation and support for all major front end frameworks.<p>GitHub link: <a href="https:&#x2F;&#x2F;github.com&#x2F;vorillaz&#x2F;devicons" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;vorillaz&#x2F;devicons</a>

[Build/Deploy] Show HN: AgentSwift – Open-source iOS builder agent I&#x27;m working on a coding agent for building iOS apps. It&#x27;s built on openspec and xcodebuildmcp. It&#x27;s free and open source.

[Other] Ted Nyman – High Performance Git

[Other] L123: A Lotus 1-2-3–style terminal spreadsheet with modern Excel compatibility

[Other] GitHub is having issues now

[Other] Git-based cache saves 50% on token usage

[Other] GitHub Copilot is moving to usage-based billing

[Other] Show HN: Qumulator – quantum circuit simulator, 1000 qubits, no GPU

[Other] Show HN: Git-agecrypt – transparent file-level encryption for Git Greetings HN! I&#x27;ve forked the excellent work done by [vlaci&#x2F;git-agecrypt](<a href="https:&#x2F;&#x2F;github.com&#x2F;vlaci&#x2F;git-agecrypt" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;vlaci&#x2F;git-agecrypt</a>), looks like the original project has not been maintained for a while, so I decided to pick it up, update all the dependencies and add some thorough testing.<p>I like the ability to store sensitive data in public repositories, it&#x27;s especially useful when bootstrapping new IaC repositories, you don&#x27;t have anything at the beginning of a new project so there is no place yet to store secrets, this is &quot;a way&quot; of doing it.<p>I know you can use tools like SOPS but I think the transparent approach offered by tools like this one or git-crypt really shine for many use cases.<p>Looking forward to hear your feedback!

[Other] Show HN: I made a website to clean up recipe websites Hi hn! It has always annoyed me that recipe websites are so cluttered and have so much (in my opinion) useless fluff, so I made a little website to solve that problem! One good thing about SEO for once is that Google has pretty much forced the internet to adopt JSON-LD for recipes so many recipes are directly extractable and for others I have several fall back parsers including an indieweb parser :)<p>If you do find a website that is broken feel free to click the flag button or share it as I would love to fix any edge cases

[Monitoring/Observability] Show HN: Utilyze – an open source GPU monitoring tool more accurate than nvtop The standard GPU utilization metric reported by nvidia-smi, nvtop, Weights &amp; Biases, Amazon CloudWatch, Google Cloud Monitoring, and Azure Monitor is highly misleading. It reports the fraction of time that any kernel is running on the GPU, which means a GPU can report 100% utilization even if only a small portion of its compute capacity is actually being used. In practice, we&#x27;ve seen workloads with ~1–10% real compute throughput while dashboards show 100%.<p>This becomes a problem when teams rely on that metric for capacity planning or optimization decisions, it can make underutilized systems look saturated.<p>We&#x27;re releasing an open-source (Apache 2.0) tool, Utilyze, to measure GPU utilization differently. It samples hardware performance counters and reports compute and memory throughput relative to the hardware&#x27;s theoretical limits. It also estimates an attainable utilization ceiling for a given workload.<p>GitHub link: <a href="https:&#x2F;&#x2F;github.com&#x2F;systalyze&#x2F;utilyze" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;systalyze&#x2F;utilyze</a><p>We&#x27;d love to hear your thoughts!

[Other] Tendril – a self-extending agent that builds and registers its own tools

[Other] Show HN: OSS Agent I built topped the TerminalBench on Gemini-3-flash-preview Scored 65.2% vs google&#x27;s official 47.8%, and the existing top closed source model Junie CLI&#x27;s 64.3%.<p>Since there are a lot of reports of deliberate cheating on TerminalBench 2.0 lately (<a href="https:&#x2F;&#x2F;debugml.github.io&#x2F;cheating-agents&#x2F;" rel="nofollow">https:&#x2F;&#x2F;debugml.github.io&#x2F;cheating-agents&#x2F;</a>), I would like to also clarify a few things<p>1. Absolutely no {agents&#x2F;skills}.md files were inserted at any point. No cheating mechanisms whatsoever<p>2. The cli agent was run in leaderboard compliant way (no modification of resources or timeouts)<p>3. The full terminal bench run was done using the fully open source version of the agent, no difference between what is on github and what was run.<p>I was originally going to wait for it to land on the leaderboard, but it has been 8 days and the maintainers do not respond unfortunately (there is a large backlog of the pull requests on their HF) so I decided to post anyways.<p>HF PR: <a href="https:&#x2F;&#x2F;huggingface.co&#x2F;datasets&#x2F;harborframework&#x2F;terminal-bench-2-leaderboard&#x2F;discussions&#x2F;145" rel="nofollow">https:&#x2F;&#x2F;huggingface.co&#x2F;datasets&#x2F;harborframework&#x2F;terminal-ben...</a><p>It is astounding how much the harness matters, based on this and other experiments I have done.

[Other] Show HN: A terminal spreadsheet editor with Vim keybindings While speccing out this spreadsheet tool, I realized that I never had to think about the keybindings. It all just came naturally from Vim. Normal&#x2F;insert&#x2F;visual modes, hjkl navigation, dd&#x2F;yy&#x2F;p, :w, :q. The usual muscle memory works.<p>It supports CSV&#x2F;TSV import and export, and a native .cell format that preserves formulas. The formula engine handles SUM, AVERAGE, COUNT, MIN, MAX, and IF with range references.<p>The codebase is a Cargo workspace: a pure cell-sheet-core library (no TUI dependency) and a cell-sheet-tui crate on top of ratatui. Early days, but it&#x27;s usable.<p>To try it out: cargo install cell-sheet-tui<p>Feedback of any kind is greatly appreciated!

[Other] Show HN: I built a reference site for the recurring hard problems in software Hi HN, I&#x27;ve been working on this for a while and it was hard to decide when to stop, either on the way information is presented or when to stop with adding entries. It&#x27;s not meant as a blog, but rather as a reference that keeps growing.<p>Link: <a href="https:&#x2F;&#x2F;thehardparts.dev" rel="nofollow">https:&#x2F;&#x2F;thehardparts.dev</a><p>Currently I&#x27;ve created 4 main section:<p>- Failure Modes: ways project go wrong<p>- Red Flags: early signals that are worth taking seriously<p>- Tech Decisions: common and not so common trade-offs for hard choices<p>- Playbooks - guided approach for situations that repeat<p>I&#x27;ve also focused on creating links between them to show how connected many things are: a red flag usually precedes a failure mode, which might connect to a forced decision, etc.<p>Some entry points to give you an idea:<p>- The Invisible Deadline: a date that exists socially but not explicitly enough to manage honestly<p>- Eveyone Asks The Same Person: when one person becomes the default source of truth<p>- Build a Practical Rollback Strategy: how to build a reliable rollback strategy<p>It has 151 entries across the 4 sections.<p>Curious what you think about the content, format, grouping.