6 posts tagged with "Productivity"

I forgot my anniversary twice in the same year. I committed AWS keys with GPS metadata still in the EXIF. I did Red Team work on Starbucks WiFi. I sent a 2am email to a CEO about "agile bullshit".

These are not hypothetical failure modes. These are the origin stories.

zero-trust-lifestyle is what happens when a security researcher gets tired of being the threat model. 33 bash scripts, each one born from a real incident, covering everything from OPSEC paranoia to relationship maintenance to corporate survival. Someone found the scripts folder:

"So I'm going through my colleague's scripts folder. This security researcher has automated their entire life. You're not gonna believe this shit."

Accurate.

You ask an AI agent to fix a bug. It fixes the bug, refactors three unrelated functions, renames some variables "for clarity", and force-pushes to main. You ask it to deploy. It does — to production, without asking, because you didn't say not to.

AI agents have a discipline problem. They're powerful, and that power without guardrails is genuinely dangerous. Not in the science fiction sense — in the "I now have to spend two hours reverting a cascade of well-intentioned changes I never requested" sense.

The root cause is that every agent operates in a vacuum. No shared rules, no accountability, no memory of corrections. It's like hiring contractors and giving none of them an employee handbook, then being surprised when they all work differently.

Contract Agents v3.0 is the handbook. 52 specialized agents across 8 divisions, all governed by one shared contract. The agents don't decide how to behave — the contract does.

Building a secure, feature-rich development environment shouldn't require weeks of configuration and security research. That's why I created DevBox — an automated provisioning script that transforms a fresh Ubuntu VPS into a production-ready development workstation in minutes.

I have an Obsidian vault. I have a Docusaurus site. I wanted most of the vault on the site — not a copy maintained separately, not a manual export, but the actual vault, synced at build time and published directly.

The problem: Obsidian and Docusaurus don't speak the same language. Wikilinks ([[Page Name]]) break MDX. Callouts (> [!note] Title) render as nothing. File paths assume vault-root-relative addressing that Docusaurus doesn't know about. You can't just point Docusaurus at a vault folder and expect it to work.

docusaurus-plugin-obsidian-vault handles the translation. At build time: pull the vault, transform the syntax, copy the assets, generate the sidebars, publish. The vault stays in Obsidian. The site stays in Docusaurus. They sync.

Year 1: Ship features in days. Year 3: Same features take weeks. Year 5: You're afraid to touch anything.

Sound familiar? What if your codebase could maintain constant velocity regardless of size? That's the promise of black box architecture—and now you can teach your AI assistant to think this way automatically.

I’m a dinosaur developer, and honestly, I wasn’t that into AI-coding until now.

Imagine coding with an AI partner that doesn’t just write code, but helps you plan, debug, and automate your workflow—all within VS Code. That’s Kilocode: a lightning-fast, open-source AI agent built to boost productivity, whether you’re just starting out or already deep in the dev world.