Browser AI vs. Terminal AI: What Changed When I Moved My Dev Workflow to the CLI

Sun, 24 May 2026 00:00:00 +0000

I built an entire website through a browser-based AI conversation. Then I switched to a terminal-first agent. Here’s what each approach actually gets right — and where each one falls apart.

Building a Zero-Cost Private AI Lab on Consumer Hardware

Sun, 24 May 2026 00:00:00 +0000

How I built a fully self-hosted AI inference environment with GPU passthrough, hardened containers, and zero-trust edge access — on hardware you can buy at Micro Center.

Mon, 01 Jan 0001 00:00:00 +0000

Domain strategy for wombat websites

You said: Good morning! Let’s explore ideas for a public website that aligns with my goals for wwwombat.tech. I own two domains: wwwombat.com and wwwombat.tech. Would one be more suitable for research and public tools, and the other domain be more oriented towards commercial sales? Help me explore some ideas based on what you know about me and this project so far.

Claude said: Good morning! This is a great strategic question, and your two domains give you a natural split that a lot of solo founders wish they had from the start. Here’s how I’d think about the division: wwwombat.tech → the commercial front door. This is already where you’ve anchored your brand identity — your Open WebUI is white-labeled to it, your consulting vision lives here. The .tech TLD signals professional capability to enterprise buyers. This domain should be the polished, conversion-oriented site: who you are, what you offer, case studies, a contact/booking flow. Think of it as the site a CISO or IT director lands on when evaluating whether to bring you in. wwwombat.com → the public-facing lab and reputation engine. The .com carries universal credibility and is easier to share casually. This is where you publish the work that earns the consulting engagements: writeups of your homelab architecture, tool demos, CVE analysis walkthroughs, open-source utilities (like your NVD tool or filter functions), maybe a blog tracking your build-in-public journey. It’s your technical portfolio and content marketing engine rolled into one. The strategic logic is that .com builds your audience and credibility (people find you through your research), and .tech converts that credibility into revenue (people hire you through your services page). Each domain links to the other, but they serve different visitors at different stages. A few concrete ideas for each: For wwwombat.tech, the commercial site could feature a clean services page (AI infrastructure consulting, private deployment architecture, security log analysis pipelines), a “how it works” section showing your hybrid local/cloud approach without giving away the keys, and eventually client testimonials or anonymized case studies. Even a simple single-page site with a Calendly embed would be a strong start while you’re still in school. For wwwombat.com, the research/portfolio side could host things like an interactive version of the implementation report you just shared (sanitized, of course), tool releases or demos, a blog with posts like “How I built a zero-cost private AI lab on consumer hardware” or CVE deep-dives. This is the kind of content that gets shared on Reddit, Hacker News, and LinkedIn — which is exactly how independent consultants build pipeline without a sales team. One thing worth considering: you could start with just one site and redirect the other domain to it until you have enough content to justify both. Given where you are right now — still building the stack, still in school — I’d probably launch wwwombat.com first as the portfolio/blog, since publishing technical content is how you’ll start building a reputation. Then stand up wwwombat.tech as the commercial site once you’re closer to actively taking clients. Want to dig into the structure or content strategy for either site, or talk about the tech stack for building them?

Posts on WWWOMBAT

Browser AI vs. Terminal AI: What Changed When I Moved My Dev Workflow to the CLI

Building a Zero-Cost Private AI Lab on Consumer Hardware

Domain strategy for wombat websites