Background A nasty surprise Last summer while trying to deliver a feature for one of our customers, I encountered a nasty situation. The software we were developing, depended on a production grade license of Gurobi. People were on vacations except of my team and some unrelated staff, so developing the feature was in principle blocked. As I learnt due to some other situations, research
Claude Code is powerful. Without structure around it, every session starts cold, plans live in chat history, and the spec you cared about is buried in a thread you will never re-read. I built Arness because I got tired of two things at once: the ad-hoc-prompting ceiling, and the ceremony every framework adds when it tries to fix it. It is an open-source Claude Code plugin marketplace, and you driv
Hi everyone! I wanted to share a small project I’ve been working on lately. The premise is simple: every time we share a photo or a document, we inadvertently leak a massive amount of personal data — from home GPS coordinates to camera serial numbers and even the edit history of a PDF. Using "online privacy services" to clean your files always felt like a paradox to me (sending private data to a s
Most AI news tools try to solve information overload by summarizing more content, faster. That was not the product I wanted to build. I wanted something closer to a personal news radar: a system that could watch Hacker News, Reddit, RSS, GitHub, Telegram, and other sources for me, reduce the noise, connect the context, and still leave room for human judgment. So I built Horizon. Horizon is an ope
The Problem with AI Terminals Today Every AI terminal tool works the same way: you describe what you want, the AI suggests a command, you copy it, alt-tab, paste it, run it, check the output, alt-tab back, describe the next thing... rinse and repeat. There is a cognitive cost to every context switch. When you are debugging a production issue at 2 AM, those seconds add up. WinkTerm takes a differ
When you build a PowerShell project from multiple files, the natural structure is clear: enums first, then classes, then functions. Each group has its own place, and as long as dependencies only flow in one direction, that structure works perfectly. But sometimes a function depends on a class, and that class calls the function. There is no longer a clean boundary between the two groups — they need
If your team works with geospatial data, sooner or later you need a place where maps, layers, users, and edits live together. There are many capable SaaS platforms and proprietary solutions you can deploy on your own infrastructure, but there is another path: self-hosting an open-source Web GIS server. In this tutorial, we will deploy NextGIS Web on a low-cost VPS using Docker, and then configure
The "Ghost" in the Codebase We’ve all been there. You’re running a security audit on an old repository, and your scanner flags 45 "Potential Secrets." You spend the next two hours manually checking them, only to realize 44 are revoked, test strings, or old keys from a defunct project. In the industry, we call these Zombie Keys—credentials that look like a threat but are actually dead. The proble