Articles on open-source tools, infra, and dev practices.
Pick the model before you write the prompt. Lesson 1 of a four-part series on working with AI — model tiers, context windows, tokens, and a decision checklist you can keep.
Same model, very different results — because of the prompt, not the model. Lesson 2 of a four-part series on working with AI: prompt anatomy, acceptance criteria, and standing project context.
A model that re-learns your project every session will quietly break its own conventions. Lesson 3 of a four-part series on working with AI: documentation, rules, and skills — and which layer each piece of guidance belongs in.
Less for the same result, measured on screen — not a percentage quoted from somewhere else. The last lesson in a four-part series on working with AI: baselines, levers, and guardrails.
No jargon, no assumed tech knowledge — why sending every question to the same expensive AI model is wasteful, and how OpenTechnologyApp routes questions to different models automatically.
AI gets pushed into high-stakes roles by pressure from people and from the systems themselves. Heavy reliance erodes the human skills needed to check or replace those systems — atrophy is the amplifier that makes it hard to undo.
No jargon, no assumed tech knowledge — what happens to someone's accounts when they join or leave a company, and why forgetting to close one is a real security risk.
No jargon, no assumed tech knowledge — what a web browser actually is, what an extension adds to it, and why workflow tools would live inside a browser at all.
No jargon, no assumed tech knowledge — what it means to be 'compliant' with a security standard, and why it's proof, not paperwork.
No jargon, no assumed tech knowledge — what 'hosting' means, what it means to 'self-host' something, and why a business would choose to run its own chat and file-sharing tools.
No jargon, no assumed tech knowledge — what streaming and rendering software actually is, what a 'bridge' program does, and why it can't just run anything it wants on your computer.
No jargon, no assumed tech knowledge — what an AI model is, what an API key is for, and why someone would use two different AI tools together on purpose.
No jargon, no assumed tech knowledge — what a 'device audit' actually checks, why it isn't spying on anyone, and what happens when it finds a problem.
No jargon, no assumed tech knowledge — what 'scraping' job boards means, what 'auto-apply' actually does, and why a human still has to click submit.
No jargon, no assumed tech knowledge — what tools like Jira, Monday.com, and Salesforce are actually for, before any specific feature.
No jargon, no assumed tech knowledge — the difference between running your own server and paying for managed hosting, without giving up the savings of open-source software.
No jargon, no assumed tech knowledge — what a 'project management tool' actually does, explained the way you'd explain it to a friend who's never used one.
No jargon, no assumed tech knowledge — what 'uptime' and 'an outage' mean, and why a monitoring tool doesn't automatically watch your site for you.
No jargon, no assumed tech knowledge — what it means to build and 'deploy' an app, and what all those developer tool names (GitHub, Vercel, Supabase) actually do.
Google Workspace onboarding and offboarding as tracked, checklist-driven work — one status change spins up the Google task, the IT ticket, and the manager email it actually requires. Importable as an OpenTechnologyApp project template.
External requests land in a no-login portal, go through triage and approval, and only then become work — kept structurally separate from the sprint board so a client's ask never jumps the queue. Six queues, ten automations, two dashboards, built into OpenTechnologyApp.
Three queues for everything a public site generates — outages, traffic snapshots, and inbound contact-form submissions — sized to fit OpenTechnologyApp's free tier. One connection is fully automatic; the other two are yours to wire or fill by hand.
Ships today as OpenTechnologyApp's built-in Extend Platform — Stream + Content Ops template: one place to track machines, tools, health checks, control commands, and render jobs across OBS, ComfyUI, Blender, and more.
Device inventory, audit findings, scheduled daily/weekly audit work, and step-by-step triage playbooks — packaged as an importable OpenTechnologyApp template.
Scrape 15+ job boards, match by keyword and salary, and auto-apply with browser automation — no AI, no cloud services, no API keys. MIT-licensed and multi-profile from a single install.
Route bulk AI work to a self-hosted Hugging Face agent and reserve Claude for precision tasks — full quality, a fraction of the cost.
A Salesforce, Jira, and Monday.com alternative in one app — client portal, live dashboards, automations, and easy-to-use project templates for device management, access, and PM.
A practical guide to setting up Terminal, VS Code, GitHub, Claude Code, Vercel, and Supabase — from a simple blog with CMS to a full table management app. This guide walks you through each tool with real AI prompts you can drop in immediately.
A practical business guide to Brave Browser — privacy-first, Chrome-compatible, and a drop-in upgrade for your team.
A practical guide to secure, cost-effective open source infrastructure for growing businesses — covering deployment, hardening, and the business case for self-hosting.
Why smart businesses are ditching SaaS subscriptions for open source apps — and paying a fraction of the price.
A technical deep-dive into combining Fleet, OpenEDR, Wazuh, Keycloak, and Fail2ban into a cohesive compliance stack that produces audit-ready evidence for SOC 2, HIPAA, and PCI DSS.
