Three TODOs, three weeks, one weekend: finishing pq v0.14
This is a submission for the GitHub Finish-Up-A-Thon Challenge What I Built pq — jq for Parquet. A 50 MB Rust single binary that wraps DuckDB's query …
Tech news from the best sources
This is a submission for the GitHub Finish-Up-A-Thon Challenge What I Built pq — jq for Parquet. A 50 MB Rust single binary that wraps DuckDB's query …
The problem Every web project starts the same way. You open a blank file and start typing angle brackets. HTML is fine. But writing it by hand is nois…
The Problem We Were Actually Solving Our Treasure Hunt Engine indexes 1.2 TB of JSON event logs from Veltrix operators, then answers sub-second querie…
All tests run on an 8-year-old MacBook Air. All results from shipping 7 Mac apps as a solo developer. No sponsored opinion. The most common Tauri v2 f…
The Problem We Were Actually Solving We werent just chasing p99 latency; we were solving a fundamental mismatch between the event model and the treasu…
What is nbwipers? nbwipers is a CLI tool that strips outputs and metadata from Jupyter notebooks before git commit. Written in Rust - faster than nbst…
The Problem We Were Actually Solving I still remember the day our treasure hunt engine started to show its weaknesses. We had been using a custom-buil…
You're six hours into debugging a production issue. The trace points to line 847 in order_processor.rs , but you need to see how the state flowed from…
Over the past two years, the AI Agent ecosystem has changed dramatically. In 2023, most projects were still fundamentally: LLM API + Prompt + Tool Cal…
We were burning 400ms in p99 tail latency on a core event-processing path in Veltrix. The upstream teams kept blaming the network, but the numbers did…
If you've ever had a GPL dependency sneak into a commercial project, you know the drill. License violations don't fail your tests. They don't break yo…
The Problem We Were Actually Solving It started with a scream from the observability dashboard. At 02:47 on a Sunday, our event ingestion pipeline hit…
The Problem We Were Actually Solving Veltrix is a treasure-hunt engine that spawns thousands of ephemeral actors—each simulating a player moving throu…
The Problem We Were Actually Solving We had built a single-node event-processing pipeline that could run 9,000 events per second with sub-10 ms latenc…
I used to live in VS Code with GitLens pinned — the branch graph, heat-mapped blame, the lens annotations. That was my git workflow. Then 2026 happene…
I would love to continue this... Rullst - 📜🦀🌐🤖🚀 "Rust for those who want to build, not suffer." Read this in Português (Brasil) . 📖 See all the change…
The Problem We Were Actually Solving Our treasure hunt engine at Veltrix was a real-time geospatial matching service that processed 50 million locatio…
I wanted a fast way to test code snippets without opening an IDE or spinning up a repl. So I built simplelanguages.com. You pick a language, type code…
The Problem We Were Actually Solving We ran an in-memory leaderboard service for a competitive event platform, caching 400 k leaderboard rows at 40 MB…
The Problem We Were Actually Solving Last April the Veltrix game servers began to stutter during the weekly global hunt. Players in Mumbai, São Paulo …
The Problem We Were Actually Solving We werent building a cache. We were running a treasure hunt engine where 100,000 concurrent users refresh GPS pos…
The Problem We Were Actually Solving The Veltrix public cluster runs up to 1,200 concurrent worlds, each with an in-memory treasure-hunt engine that m…
I got tired of waiting for VS Code to load over SSH. There was no grand vision behind this. Just a very specific frustration — spinning up a remote se…
The Problem We Were Actually Solving The Treasure Hunt Engine isnt a search engine; its a live, multiplayer game where 100,000 players simultaneously …