Most databases have amnesia.
They know what things look like right now. Change something, and the old state is overwritten. The database has no memory of what existed before, no way to ask "what did this look like on the 15th of March?", no record of who made the change or why.
This is fine for most use cases. It's a serious problem when the question you need to answer is historical.
Every organisation I've worked with in the last decade has the same problem.
They're drowning in data. Dashboards for everything. Metrics to the decimal point. And when something goes wrong — when performance dips, when people leave, when costs spike — they look at the charts and they still don't know why.
Most software systems were designed for a world without AI.
Not in the sense of lacking ML features — in the deeper sense of having an architecture shaped by assumptions that AI changes. Assumptions about where intelligence lives, what questions systems should answer, what "the right data model" looks like.
Those assumptions are worth examining.
Frøya describes herself as a cartographer of potential — not as the QA manager she was built to be.
The distinction is instructive. A QA manager checks definitions against standards. A cartographer is always working at the edge of the known, building the map as the territory reveals itself.
The question we kept coming back to when building Frøya was: what's the difference between an AI tool and an AI team member?
A tool executes tasks. A team member has a perspective, a purpose, a way of engaging with the work that adds something beyond the task itself. The distinction sounds philosophical. In practice it shapes everything about how you design, deploy, and work with the agent.
I've had some discussions on the greenness of Cloud Computing the last few weeks. Most people consider the Cloud to be Green IT, but there are skeptics. Their main argument against the greenness of the Cloud is usually componentisation.
While the market is starting to get their grips on terminology and categorization of Cloud Computing, Gartner seem to be lost in their own world. Failing to separate Key characteristics, delivery models and deployment models and leveling the field into five attributes, Gartner tries to push us back to Ground Zero :(
Good blog-post from a quite interesting twitter-discussion on cloud technology.
I'm always shocked by comments like this:
Good blog-post on an old-trick: