AkitaOnRails Blog

Recent articles

October 2026

17 articles

Best Open Source LLM: Strata with Qwen 3.8 Flash Next

Qwen3.8 Flash-Next served by the Strata engine scored 91, Tier A, on an RTX 5090, 1.5 points behind the B300 and at about 159 tokens per second. I explain how Strata fits a 125B MoE on a PC by using VRAM as an expert cache and RAM as the warehouse, why that matters with memory costing twice as much, and why it isn't magic: the 5090's memory bandwidth is seven times the Strix Halo's and almost 30 times PCIe's, and even on my machine it takes up almost all the RAM and VRAM. I show the install, a service that loads and unloads the model on its own, the OpenCode configuration, why I consider my machine the minimum for real programming work, and why, even a bit less responsive than a commercial model, it's already almost good enough to replace the cloud day to day.

LLM Benchmark v4: consumer-grade open source on RTX 5090 or Strix Halo. And Strata?

I went back to consumer hardware after the datacenter tests. Qwen3.8 Flash-Next scored 91.0, Tier A, on an RTX 5090 with the Strata engine, 1.5 points behind the B300 at 159 tokens per second. It's a different model from the Qwen 3.8 27B I had called slow: a MoE with 6B active per token, served with the hottest experts on the card. Strix Halo scored 80.0 with the 27B, but at 7.7 tokens per second. It's the first local model to make Tier A on the v4, and it's worth testing in day-to-day programming, if you can find a 5090: NVIDIA denies the end of production but admits tight supply.

LLM Benchmark v4: can my team fit in a 4x b300/h200?

After ranking the big models, the leftover question: how many developers fit on a 4x B300 or 4x H200 pod? We measured real concurrency, with a latency SLO, and the answer changes everything: DeepSeek V4.1 Flash holds 32 comfortable users on B300 and only 8 on H200. Cost per comfortable user: US$ 1.13/hour on B300 versus US$ 1.80 on H200. When your own infra closes the math against a frontier subscription, and when it's just expensive vanity.

LLM Benchmark v4: open source that only fits in 4x B300!!

I rented 4x NVIDIA B300 on Runpod and ran my v4 sabotage benchmark on the open models that don't fit on a single card. DeepSeek V4.1 Flash, at 748B, tied the leaders at 92.5, on the level of hosted GLM 5.3 and GPT-6 Sol. GLM 5.3 full fell behind, the 1T Kimi K2 Thinking disappointed, and a 397B model plummeted from 94 in the cloud to 27 at home. The math: US$ 36 per pod hour, US$ 864 per day. When owning your own infra makes sense, and whether a big open model is already enough for your day-to-day programming.

LLM Benchmark v4: the top open source LLMs on a B300

I rented a 288 GB NVIDIA B300 on Runpod and ran my v4 sabotage benchmark on 14 open-weight models that don't fit at home. None of them serves fast the way it ships: GLM 5.3 Flash went from 10 to 141 tokens per second on configuration alone. Two open models reached 92.5, Sonnet 5 level, and a 27B fine-tune scored 88. A 397B flagship let an admin backdoor through, DeepSeek V4 Flash scored 86 in the cloud and 44.5 at home, and Nemotron cheated on a test. The math: the cloud API of the same model costs a dollar per run and the pod costs 218 a day. When owning your own infra is worth it, and whether a team fits on one card.

I Trained My Own AI Model (Spoiler: It's Just for Study)

One exercise was missing: training an LLM from scratch. I started from Karpathy's microgpt, 200 lines of pure Python, and expanded it into a lab with a tokenizer, pretraining, SFT, an OpenAI-compatible server and OpenCode integration. Under two weeks, one RTX 5090, 10 billion tokens, 137 hours of training, at most around R$ 80 of electricity. The final model has 337 million parameters, gets 58 out of 100 simple Python functions right and scores zero on anything that requires acting in a repository. I explain each step, the stumbles, the dimensions against GPT-2 and frontier models, and why I think the future is smaller, specialized models.

I Self-Published My Own Book/e-book: Competent Enough

I published my book about AI, for free, in EPUB and PDF: the blog's 131 posts from 2026, almost half a million words, reorganized into 20 chapters, 10 appendices, a glossary and more than 300 references. This text is the technical backstage: the inventory with a hash per post, the contract every agent read before writing, the parallel drafts, the invisible per-paragraph marker that ties the book to the blog, the checker that fails a chapter with an error, what the fact-check caught wrong in my own posts, and the Quarto, Typst and Pandoc pipeline that generates everything. It's a preview: open an issue if you find a mistake.

AI Reverse Engineering: Is Adobe Dead?

In the same week, a dev dropped seven Adobe clones built with Claude, REA passed 100K stars promising to 'reverse engineer anything', and retro gaming got a new port every day. The viral conclusion: no binary is sacred, Adobe is dead, programmers are dead. I explain what each of these things actually does: PhotoCraft is an alpha with 800 open issues, REA is a toolbox that requires the binary and Ghidra, and retro moves fast because an 8 MB ROM turns into 135K lines of C. Rewriting Bun cost US$ 165K with the author and 64 agents; Photoshop doesn't even have an open binary in the parts that matter. Reverse engineering got easier. Magic still doesn't exist.

Linux users: always choose BTRFS, not EXT4

Sequel to the NAS disaster article: filesystem choice is a life-or-death decision for your data. The history of ext4 and btrfs, snapshots, subvolumes, reflink deduplication, corruption protection, compression measured in real GB (630 GB free on 2.2 TB), ZFS vs btrfs on NAS, snapshot boot recovery with Limine and MicroOS, and storage hygiene in the AI coding era: Rust, Docker, model caches, agent worktrees and how to automate cleanup.

LLMs + Agents = competent enough

A synthesis of what I've been measuring and writing: LLMs converged. The transformer architecture got near the ceiling, the parameter war is over, and the leap everyone felt in 2025 and 2026 came from the agentic harness (tool calling, prompt caching, long sessions), not from a base intelligence orders of magnitude larger. I retell the timeline from 2019 onward with sources, explain why the agent allows a less dense model, and why that's already competent enough to automate real software engineering.

Are There Better Languages for Programming with LLMs?

DHH converted his Campfire to several languages with AI and started posting that Rust won. Instead of fighting on X, I built a reproducible benchmark: 7 languages, 4 LLM configurations, 112 implementation attempts, and a queue-under-pressure test with Elixir, Rust, Rails and plain Ruby. Result: no language ranking holds up, concise Ruby cost more tokens than Rust, strong typing spared no repair at all, and under load the four stacks tied on throughput. What matters is testing and discipline, not language.

Which Jev-like AI Decision/Classifier Model Is Best?

I ran my own decision-model benchmark: Jev, Clef, OpenAI Decisions and Microsoft Decision-1 in the cloud, plus eighteen open configurations (Perplexity Decider 27B, Decision 3.0 and Edge, Clef-flash, Kev, Jebadiah, Mapika, Eikos, Laya, Julia, GLiNER, Simple-Jev) on my Strix Halo, across more than 22 thousand classifications with cases in English and Portuguese. The top now has two open-weights models: Perplexity and Decision 3.0 tied at 99.4%, with identical labels on the 1,024 classifications and 100% in Portuguese. Microsoft Decision-1 tied Jev at 97.6% while being the cheapest hosted one. Full table, cost in support emails, gotchas, and where the data converges.

Disaster on My NAS! How I Almost Lost 90 TB of Data

I swapped one drive in my Synology DS1821+ and woke up the next day with two critical drives in an array that only survives losing one. Full post-mortem: why SHR-1 wasn't enough, the warning DSM never sent, the R$ 185 thousand for a QNAP bought in a hurry, and the recovery: parallel NAS-to-NAS rsync, the slow drive holding the array back, the verification of 5.9 million files, the thick provisioning scare, and both NASes healthy in RAID-6.

Understanding the Jev Hype: What Is It For?

Jev is a hosted classifier, and the shock of '193x faster' only exists because so many people use a chat LLM as an expensive classifier. I publish Paulo Câmara's essay (LUA Vision) with his charts, explain what a classifier is and why it's the first thing a computer scientist reaches for, compare the open alternatives Clef and Laya, show the public Decision Index ranking, and close with how to think about this kind of tool in your own project.

September 2026

16 articles

Talking a Bit About My AI Skills

Agent skills are just prompts in text files. I keep 25 in my my-skills repo, from pr-audit to fact-check, and they have already closed over a thousand PRs and issues across my projects. The recommendation: don't copy somebody else's skill, build your own.

August 2026

11 articles

July 2026

17 articles

June 2026

10 articles

May 2026

12 articles

April 2026

18 articles

Seedance 2.0 Is Finally Out: First Impressions

ByteDance opened Seedance 2.0 to the public today after months of restricted access. I tested audio-driven lip sync with my anime avatar, and a Blender render fed in as a video reference. There's real work you can do here, but it's nowhere near professional production yet. Also: deepfakes just stopped being hypothetical.

March 2026

13 articles

February 2026

17 articles

January 2026

10 articles

September 2025

12 articles

August 2025

2 articles

June 2025

1 article

May 2025

7 articles

April 2025

17 articles