Why SALIM Technologies exists
We kept building products, learning things, and letting the lessons evaporate. The company exists to fix that, build, write it down, open-source what helps.
SALIM Technologies builds software. That's the one-line version. The longer version is about how and why, and this journal is where we'll write both down.
The pattern that became a company
For years the pattern looked like this: notice a problem, build a tool for it, ship it, learn a pile of things keeping it alive… and then the next project starts and the lessons evaporate. Knowledge lived in someone's head, in a private repo README, or nowhere at all.
Meanwhile the products themselves kept being useful. Small businesses bought them. Couples used one through a pregnancy. Developers built on an API. The software deserved a proper home.
So the entity exists to give the work structure, a company that builds, maintains, and documents products, and treats the writing-down as seriously as the shipping.
What we believe
Build small. Ship early. Write down what you learn. Kill ideas that don't deserve more time. Open-source what can be useful to others.
That's the operating system. A few notes on it:
- Build small, every product here started as a version one person could carry. Some stayed small on purpose.
- Ship early, the market is a better critic than any internal debate. Most of what we now know came after launch, never before.
- Write it down, hence this journal. Every product has a story of why it exists, and we're going to tell them all.
- Kill ideas, the graveyard is part of the portfolio. Ideas that don't earn more time get archived honestly, not zombie-maintained.
- Open-source, when a tool we need internally would help others, it goes public with a real license.
What's here
Right now: eight products in various stages of life, one mobile app, one open-source project, and this journal, which will carry the stories behind all of them.
If that's the kind of thing you like reading, you're in the right place.