Why we started writing

It took us twelve years, but here we are: the first post on the Precisit blog.

Our homepage has long opened on a field of stars and one sentence: “It all begins with our consultants.” We once left room below it for a longer story. The stars kept moving. The space stayed empty.

It was not for lack of things to say. Our clients, colleagues and ideas came first. Much of what we learned remained where it happened, in meeting rooms, in code and in conversations over coffee.

Between the question and the answer

Most work leaves behind two records: what was delivered and what people remember. The trail between them is more fragile. It contains the question that reframed a problem, the attempt that failed, the constraint that changed the plan and the small decision that made the next step simpler.

A finished interface rarely tells you any of that.

TensorLens lets you look inside the tensors of an AI model. PasskeyDemo makes passkey authentication something you can try and inspect. C3Planner helps plan the energy budget for a journey between worlds. Each tool shows what it does. A page about the finished result cannot hold the whole path that led there.

The blog gives part of that path a place to remain. An article can follow a single engineering decision, keep an experiment and its limitations together, or examine what twelve years of building a company have taught us so far.

Writing also puts useful pressure on an idea. If an assumption cannot survive a clear paragraph, it probably needs another look. An experiment deserves the same courtesy as a telescope: record where it was pointed, what it could see and what remained beyond its field of view.

What you can expect

Engineering articles will begin with a practical problem. The useful part may be a technique, a tradeoff or a mistake worth avoiding.

Research articles will make the question, method and limits visible. An inconclusive experiment can still be valuable when it rules something out or suggests a better question.

Company articles will use ordinary events and decisions to reflect on the employee experience, collaboration and our own ideas over time. Just as a product has a user experience, a workplace has an employee experience, shaped by choices that looked small when they were made.

There is no publication quota. The internet already has enough text written because Tuesday arrived. A post should earn its place by being useful, surprising or, on a good day, both.

Posts may be in Swedish, English or both. An exciting article cannot wait for its translation.

One article, several readers

Technology becomes interesting when it meets a person: someone trying to understand a model, sign in without a password or reach Mars with a limited energy budget. That is why we want to write about both how something works and why it was worth building.

The same carefully described decision can give an engineer a method to reuse, show a potential colleague what everyday work here is like and help someone responsible for a difficult problem see the consequence of a tradeoff. It is still one story. Different readers may find different things inside it.

You can find the finished tools on our projects page. Here we will look more closely at some of the questions around them.

Come along

The RSS feed is the simplest way to follow new articles, and we will also share them on X.

If something here makes you curious, or gives you reason to disagree, we would be glad to hear from you. You can reach us through the contact page, and the coffee is on us.

The first post took twelve years. We hope the next idea finds its way here a little sooner.