Sajna Space 🚀

I’ve spent 20 years in IT — managing teams, building infrastructure that most people never see but everyone depends on. I’ve watched compute go from racks in closets to hyperscale data centres to the cloud. Every time, the pattern was the same: someone builds the platform, and then everything changes. What’s happening right now in space is that pattern — except the platform is orbit, the Moon, and eventually Mars. And the scale makes cloud computing look like a toy. ...

This is the final post in the Velocity vs Value series. Previously: The Velocity Trap, AI Greenfield vs Brownfield, and Measuring What Matters. AI coding tools accelerate delivery — we’ve covered the data in this series. They’re genuinely valuable. But acceleration without visibility creates a specific risk: quality degradation that nobody notices until it compounds. Here’s how it plays out: an AI tool generates a feature in 20 minutes. It passes all automated tests. CI is green. The PR is merged. Velocity: +1. Two weeks later, a security audit flags a pattern. A month later, a production issue traces back to a function with cyclomatic complexity of 47. Three months later, the module is hard to modify because the generated code lacks documentation and clear structure. ...

This is Part 4 of the Velocity vs Value series. Previously: The Velocity Trap and AI Coding Tools: Greenfield vs Brownfield. You understand that velocity alone doesn’t tell the full story. You’ve seen how AI tools accelerate delivery while introducing new quality considerations. Now comes the practical part: what do you actually measure to show your team’s real impact? “We need better metrics” is easy to say. Your stakeholders need numbers. Your board needs a narrative. Your team needs to know what success looks like — and how to promote what they deliver. You need a framework that doesn’t require a PhD in data science to implement. ...

This is Part 3 of the Velocity vs Value series. Previously: The Velocity Trap. Here’s a demo that writes itself: an engineer types a natural language description, and an AI agent generates a complete microservice in three minutes. Working tests. Clean structure. The audience applauds. Here’s what they don’t show you: that same AI agent, pointed at a five-year-old enterprise codebase with custom ORM patterns, undocumented business rules, and three layers of abstraction that made sense in 2021 — producing code that compiles, passes lint, and does the wrong thing in production. ...

This is Part 2 of the Velocity vs Value series. In the pillar post I introduced the tension between velocity mandates and value delivery. This post goes deeper into why velocity as a target fails — and what actually works. The Speedometer Problem Velocity was designed as a planning tool. It helps teams estimate capacity. It’s a speedometer, not a gas pedal. You don’t make a car faster by taping over the speedometer and writing a bigger number. ...

Velocity vs Value: How to Measure Success in the Age of AI There’s a moment every engineering manager dreads. You’re in a steering meeting, your platform just survived a massive overhaul, your small-but-senior team is finally shipping on a solid foundation — and someone says: “We need a feature per day. Just use the AI.” I want to talk about what happens next — not the political maneuvering, but the measurement problem underneath it. Because the question isn’t whether AI makes us faster. The question is: faster at what? And how do we prove it? ...

When your AI assistant tells you you’re a genius, you might want to worry. There’s a video making the rounds on X right now. In it, @atmoio tears apart how AI chatbots — Claude in particular — are turning tech CEOs into delusional yes-men magnets. The target? Gary Tan, CEO of Y Combinator, who recently published gstack on GitHub: a collection of markdown files with Claude Code prompts that role-play an entire engineering team. CEO, Engineering Manager, QA, DevOps — all played by one LLM. ...

Stop Throwing AI at Your Software Process. Start Strategically Placing It. A practical framework for integrating AI into brownfield software development The CEO’s Napkin vs. Reality I’ve sat in enough boardrooms to know the drill. Someone draws four boxes on a whiteboard: Idea → Design → Develop → Deploy Then the AI conversation starts, and those four boxes collapse into three: Idea → ☁️ AI Magic ☁️ → Money I get it. AI is exciting. The demos are impressive. But if you’ve ever managed a real software team — especially one maintaining systems that have been running for years — you know that napkin sketch is missing about 98% of what actually happens. ...

No AI 4 U I watched it happen in real time at a Fortune 500 cybersecurity company. The board decided AI was the future. A mandate flowed down: “Present your AI adoption plans.” Middle management dutifully passed the hot potato to their teams. Teams — with no clear mission, no vision, no defined goals — started hunting for tools on their own. Every single initiative hit the same wall: InfoSec. ...

Why Bother? I’m a manager/team lead/product owner at a major network and cybersecurity company. My days are a juggling act: Jira boards, Gmail inboxes, Google Drive docs, SharePoint migrations, and IATF audit preparations — plus a private land development project that involves 22 Google Drive files, bank negotiations, and demolition planning. At some point, I thought: what if something could handle the routine stuff while I sleep? Not another chatbot. Something with *access *to my tools, my context, my projects — and the ability to act independently. That’s how Kalcifer was born. ...