Whoobe 0.2.0, named Conduct, adds the controls a security officer asks for: an audit log, mandatory two-factor authentication, single sign-on, data subject tools and metrics. Just as important is how it was released: with the tests, the results (the failed runs included) and the limits in the open.

Why AI Makes Quality Assurance More Critical Than Ever

An AI assistant does not remember yesterday and will cross a line if that is the shortest path. How written plans, now public in the repository, set decisions and limits before the code: one real case from this week, what a plan contains, and where plans fail.

A senior architect and an AI assistant built Whoobe in about eleven weeks. The numbers, with their sources and dates, the decisions that stayed human, the defects the tests and reviews found, and what the case does not show.

Where the human retains architectural oversight while the machine handles the code-writing heavy lifting—offers the opportunity for some fundamental engineering insights into this execution model.

A deep dive into how Whoobe One Spike bridges the gap between pure frontend components and remote APIs without custom controller layers.

A deep dive into engineering a high-performance Product Information Manager (PIM) using PostgreSQL JSONB and Zod validation, leaving database bloat behind.

Storing and executing API keys, OAuth tokens, and server-to-server credentials securely within a server-side proxy gateway.

An architectural breakdown of how Whoobe leverages a unified TypeScript stack, PostgreSQL JSONB, and a server-side proxy gateway to solve the infrastructure, memory, and validation constraints found in legacy enterprise PHP setups.