Qwen 2.5 Coder 7B is the most accurate of the three for Python and TypeScript completions. Phi-4 Mini (3.8B) uses the least VRAM and runs nearly twice as fast. Pick it when memory or latency counts more than raw accuracy. Gemma 3 4B sits in the middle. It is the best choice when you need one model for code, commit messages, docs, and error explanations. Below are the benchmark numbers, the test method, and how to set up each model in VS Code or Neovim.
Latest
Hands-on experience with AI, self-hosting, Linux, and the developer tools I actually use
AI-Powered Log Analysis: Find Anomalies in Server Logs with Local LLMs
A local LLM like Llama 3.3 70B or Qwen 2.5 32B running through Ollama can read your structured server logs faster than grep or awk. Pipe parsed log data through a prompt that asks the model to flag odd patterns, link error cascades, and guess at root causes. You get a useful incident summary in seconds. This fills the gap between plain text search and pricey tools like Datadog or Splunk . Best of all, no log data leaves your network.
Automate Code Reviews with Local LLMs: A CI Pipeline Integration Guide
You can plug a local LLM into your Gitea Actions, or any CI system, to review pull requests on its own. The pipeline pulls the diff, feeds it to a model running on Ollama , and posts structured feedback as PR comments. No code ever leaves your network. The setup needs three parts: a self-hosted runner with GPU access, a review prompt template, and a short Python wrapper.
Why Local LLM Code Reviews Make Sense
Static analysis tools like ESLint , Ruff , and Semgrep are great at catching syntax errors, style slips, and known vulnerability patterns. What they miss are logic bugs, unclear variable names, missing edge cases, and design concerns. An LLM fills that gap because it reads code in context. It can tell you that a function does the wrong thing, not just that it’s formatted wrong.
Debian Router with nftables: CAKE SQM Reaches 15ms Latency
Yes, a plain Debian 12 or Fedora Server install on cheap x86 hardware, or a Raspberry Pi 5, makes a better router than most consumer gear. It often beats boxes that cost twice as much. You need two network interfaces, a few config files, and about two hours. The result is a gateway with a real stateful firewall via nftables , proper DNS and DHCP from dnsmasq , and traffic shaping that works through CAKE SQM. Every config is plain text you can track in Git.
FastAPI Webhook Bot: GitHub and Gitea Automation
You can build a bot that labels issues, enforces PR naming, posts review comments, and triggers workflows. Write a FastAPI app that takes webhooks from GitHub or Gitea , checks the signature, and calls back to the right API. The same handler works for both forges. Header names and payload shape differ a bit, so one codebase can serve both.
How Repository Webhooks Work on GitHub and Gitea
Both GitHub and Gitea let you set up webhooks at the repo, org, or (for Gitea) system level. When an event fires (someone opens an issue, pushes a commit, opens a PR) the forge sends an HTTP POST to a URL you control. The body is JSON and describes what happened.
Run Home Assistant in a Proxmox VM for Maximum Flexibility
Running Home Assistant OS (HAOS) inside a Proxmox VE virtual machine gives you the full, officially supported installation - add-ons, Supervisor, automatic updates - while sharing hardware with other VMs and containers. On a modest Intel N305 mini PC, you can run HAOS alongside Plex, Vaultwarden, Nextcloud, and a WireGuard VPN with room to spare. The entire setup takes under 30 minutes. Download the HAOS QCOW2 image, create a VM in Proxmox, import the disk, boot, and you are up and running.






