MITHANDIRWhat we learn
by building.
Operations, systems and applied AI, told from the inside. Each note comes from a problem we solved at a company and is reviewed by the person who built the system.
Multi-tenant: the error you can't see
Isolating each company's data in a single database looks solved until it isn't. Why fixing the search_path isn't enough and where to really look.
More notes
04Palantir and Mithandir: a shared vision of operational transformation
Why we, the founders of Mithandir, take Palantir as a reference: connecting data, understanding processes and turning that knowledge into action. What we share, what we don't, and what we learn.
Globant and Mithandir: one business need, two ways to approach it
Globant built a global company around turning operational problems into technology that works. What service we offer, where the two proposals overlap, and what its growth and its slowdown teach.
Forward Deployed Engineering: what it is and how an FDE works
What Forward Deployed Engineering is, what an FDE does, the skills it takes and how it differs from a consultancy or a software shop. With a real case.
Invoicing with ARCA without leaving your system
Electronic invoicing is usually a separate step that someone does by hand at the end of the day. What it takes to build it into the system your team already works in.
No more notes on this topic yet.
Every note comes from a system that is running.
- 01
A real problem
It comes from an implementation: something we saw fail, measured or solved inside a company.
- 02
Writing
It is written with the person who solved the problem, from their notes and the system logs.
- 03
Technical review
The person who built the system reviews it. If a fact cannot be verified, it is not published.
- 04
No calendar
We publish when there is something worth telling.
Have a similar problem?
What we write comes from systems that are running. Yours could be next.