Shmungus
I think roguelikes should steal Noita's philosophy
I think printable objects are an underrated way to test physical products
So I built something that will.
Paste a link. Get a number out of 100.
Mine said 54%. Yours will be worse.
Link in comments. Don't cry.
Shorter, dumber:
Paste your website.
Get a number.
Cry.
Nobody is going to tell you your website is bad
Competitors have more analysts. They should not know more than you
Your niche is too specific for the analyst firms and too small to staff a research team. Tensorust finds the exact public record your question lives in, connects it, and hands you the answer your larger competitor pays a department to produce.https://tensorust-site.vercel.app/
An undo layer for coding agents that ship too fast
The SharePoint zero-day panic this week is a marketing event
That's why I wrote this handmade Python script.
It validates whether this script has been executed prior to the current execution context being instantiated.
It is Enterprise-grade and runs with 0 dependencies.
I really wanted to show the world just how valuable handwritten code really is.
Link -> https://github.com/Mattbusel/pre_execution_validator
Humans are better at coding than AI
Show HN: Three backtested quant strategies as Jupyter notebooks
https://mattitude8861.gumroad.com/l/QuantStrategyTemplatesBundle
I've spent a few years building quant strategies and most of the work isn't the math — it's the plumbing: getting clean data, structuring the backtest so it doesn't look at the future, generating a readable tearsheet. I packaged three of my working strategies as self-contained notebooks so someone can go from zero to a proper backtest in an afternoon.The three strategies:1. Funding Rate Carry —...
Every surface is a continuous matter field held together by spring-force physics. When something takes damage it doesn't play an animation, the forces holding it together get overcome and it physically falls apart. Destruction resolution is infinite because particles don't have polygon limits.
Cloth, fluid, soft-body, volumetric light, they all come from the same particle substrate. Different spring constants, not different systems. Every other engine fakes these as separate modules. This one doesn't fake any of them.
Geometry is SDF. That means analytical normals, mathematically exact ambient occlusion from the SDF gradient, and subsurface scattering from thickness probes. No baked textures. No approximations.
Current demo runs 50 million particles in real time. 650k lines of Rust. OpenGL 3.3 renderer with 23 post-processing passes. Full visual editor with a compiled Windows .exe on the releases page.
Proof Engine: Rust renderer where the math is the visual, no meshes, no polygons
Proof-engine A mathematical rendering engine for Rust
Proof Engine renders mathematics, not graphics. A Lorenz attractor looks like a Lorenz attractor because particles follow the actual differential equations in real time. Entities are held together by force fields and dissolve into strange attractors when they die. Audio is synthesized from music theory, not audio files.This is not a traditional game engine. It is a system where the math IS the...
Show HN: Fin-primitives Zero-panic, decimal-precise trading types for Rust
https://crates.io/crates/fin-primitives
I couldn't find a Rust crate that gave me validated financial types backed by decimal arithmetic. Everything I found either used f64 (unacceptable for order books), panicked on bad input, or was a thin wrapper around a single indicator.fin-primitives provides:- Price and Quantity newtypes over rust_decimal::Decimal, validated at construction — an invalid Price literally can't exist at runtime -...
Show HN: Rust primitives for AI agents, LLM infrastructure, and financial data
https://github.com/Mattbusel/rust-crates
I've been building the substrate layer for production AI systems in Rust. This is the index repo for 10 crates I shipped this week. The AI side covers agent memory (episodic, semantic, working with decay and multi-agent bus), cost governance with hard budget enforcement and automatic model downgrade cascade, CRDT state sync for distributed agent fleets, output versioning with full lineage...
LLM-cpp: 26 single-header C++17 libraries for LLM integration
26 libraries across four categories — Core, Data, Ops, App. Each one is a single .hpp file. Drop in what you need, define one implementation macro, ship. No Python runtime, no package manager, no build system changes beyond linking libcurl where needed.
llm-stream has 83 unique clones already with zero promotion. Figured the rest of the suite was ready to share. Happy to answer questions on design decisions, the single-header pattern, or anything else.
Show HN: Single-header C++ libraries for LLM APIs – zero deps beyond libcurl
- llm-stream — streaming from OpenAI + Anthropic, callback-based - llm-cache — file-backed semantic cache, LRU eviction - llm-cost — offline token counting + cost estimation - llm-retry — exponential backoff + circuit breaker + provider failover - llm-format — structured output enforcer with hand-rolled JSON parserDrop in one .hpp, link libcurl, done. No nlohmann, no boost, no...
Show HN: Tokio-prompt-orchestrator – LLM pipeline orchestration in Rust
https://github.com/Mattbusel/tokio-prompt-orchestrator
I built this after getting frustrated with "multi-agent" frameworks that claim parallelism but are really just one fat async task with no resource bounds.tokio-prompt-orchestrator breaks LLM inference into 5 physical stages (RAG → Assemble → Inference → Post-Process → Stream), each running in its own Tokio task with bounded channels between them. When a stage falls behind, backpressure builds...
Tonight I ran 24. What made this possible: I built a Tokio-native LLM orchestration pipeline in Rust that routes inference through a local Mistral 7B model running on an RTX 4070. The agents coordinate through governance docs (CLAUDE.md, AGENTS.md) that define module ownership and test ratios, they don't communicate directly, they communicate through the codebase.
The recursive part: the orchestrator was built using the same multi-agent workflow it enables. The MCP server that lets Claude call the pipeline natively.
Technical details:
683 tests, 0 failures 1.53:1 test-to-production ratio enforced by pre-commit hooks
9-stage deduplication pipeline with circuit breakers
Sub-millisecond pipeline overhead (inference dominates at 3.6s on Mistral 7B)
Repo: github.com/Mattbusel/tokio-prompt-orchestrator
24 Simultaneous Claude Code agents on local hardware
I tripled my SaaS prices after 2 weeks and signups didn't drop
Then I tripled the price to $29.99 Pro / $149.99 Ultra.
Conversion behavior didn't change. If anything, traffic to the pricing page increased.
I think the problem was that $9.99 signaled "toy" to options traders who routinely risk thousands per trade. The higher price actually built trust.
Anyone else found that raising prices early improved conversion? Curious if this is specific to finance/trading products or a broader SaaS pattern.
Product: rot.trading (165K lines of Python, built solo in 9 days, $5/mo infrastructure)