Ubunye Engine Part 5: Building With an Agent. The Real Numbers
This project was built with an AI coding agent as a collaborator throughout. The numbers tell a story that the AI industry mostly avoids having. Here they are.
# ubunye series
5 posts
Ubunye Engine Part 4: From Kaggle to Production
After all the unit tests and CI pipelines, the question remained: does it actually work on real data? The Kaggle Titanic dataset became the proving ground. This post covers what it proved, what it did not, and how Ubunye compares to existing frameworks.
Ubunye Engine Part 3: The Boring Work That Ships Software
Documentation, CI/CD, PyPI publishing, and the subtle bugs that live in single lines of code. The thesis is simple: finishing is rarer than starting, and the boring work is what separates a repository from a product.
Ubunye Engine Part 2: The Model Registry and Hexagonal Architecture
The model registry was where the project went from interesting framework to something a team could actually use in production. The design principle behind it turned out to be the most significant architectural decision in the entire project.
Ubunye Engine Part 1: Why Convention Is the Real Deliverable
Every data team eventually hits the same wall. Notebooks work locally. Spark jobs work on the cluster. Nothing works together. This is the problem Ubunye Engine was built to solve.