Insights
Engineering perspectives on architecture, product development, AI, and the everyday decisions behind useful software.
From the engineering desk
Browse practical articles or follow the latest technology updates.
Subscribe via RSS →Curated links from external sources — not 360Softy original articles.
Building Automated Developer Pipelines Here is how I automated my LeetCode progress, LinkedIn posting, and ATS resume updates using GitHub Actions and Python! Event-driven automation saves hours. Building in public creates continuous proof of work.
Tired of paying $10/month or sitting through 30 seconds of ads every 3 songs? Me too. So I built HeySongers — a completely free, open-source music streaming app for Android and Windows. Here's what makes it different: No ads. Not a single one. No banners, no video ads, no sponsored playlists. No premium tier. No "limited free plan." No catch. Just music. If you're tired of the subscription economy eating your wallet, give it a try: ⬇️ Download APK/EXE ⭐ Star on GitHub Built with ❤️ by geethudin
I wrote a single-file INI parser/editor for .NET that preserves formatting using regex instead of dictionaries with JSON support. I've been experimenting with a different approach to editing INI files in C#. Most libraries parse the file into dictionaries or objects and then regenerate the entire file when saving. That works well for configuration data, but it usually destroys comments, blank lines, indentation, entry order, or duplicate keys. Instead, I treat the INI file as plain text and inde
A week of Claude Code and Codex work leaves enough local evidence to answer concrete questions. When were sessions active? Which provider produced the activity? Which models appeared? How did the token mix change by day? It does not prove that the code was correct, the week was productive, or an API-value estimate was money spent. That boundary is what makes a weekly report useful. A readable report should cover today plus the previous six local calendar days. The headline, daily bars, provider
The most dangerous number in an AI coding dashboard is the one labeled cost without a definition. A local tool can reconstruct token activity from Claude Code and Codex session records. It can apply a dated model-price table. That produces an estimate with a clear use: comparing periods and understanding the shape of local activity. It does not produce an invoice. Claude Code and Codex do not write identical usage records. Claude can expose input, output, cache creation, and cache-read fields on
Short version first, for anyone who just wants the outcome: I run Claude Code on a flat monthly subscription, not pay-as-you-go. For months that plan never gave me a reason to look closely at it, so I stopped looking. Then an overnight automation burned through a week's worth of it in two days, the account locked with four days still to go, and I bought my way out at list price. That cost enough to make me build a small usage meter that now tells me, in plain language, whether I can spend more o
Building a Live Status Dashboard for Your Python Bot A JSON health check is enough for a hosting platform, but it's not much use to you when you want a quick, human-readable view of whether your bot is actually doing its job. This guide covers building a real python bot status dashboard — with proper HTML, CSS, and a bit of JS — using nothing more than StayPresent's web.html() and the HTTP server it already runs. Why a Dashboard Beats a JSON Blob How web.html() Works Serving Static Assets Alon
Comments
Let’s start with a conversation
An idea, a challenge, or a system that needs to work better. We’ll help you understand the next step.
Prefer email? [email protected]
