Escaping My Old 'Telegram Mindset' in Product Architecture
About my 'Telegram mindset':
For a long time my main project was Fullyst, a service that lives entirely inside Telegram. Naturally, everything there is built around the Telegram ID. For me it was the single source of truth and the unique user key.
Now, while building my new project Saylify, I carried over some of Fullyst’s architectural decisions out of habit. When I finally got to the standalone web app, I realized I had once again treated Telegram ID as User ID in Saylify.
I ended up having to redo quite a lot: switch to UUIDs, store mappings to OAuth providers, and decouple the product core from Telegram, which in Saylify is just one of the usage channels.
Soon I will write about verifying Improvy OÜ in the Apple Developer Program, the adventures around that, and why I needed it in the first place.
And this post is also the first time I have mentioned the name of the new project 😉
More to explore
Startup Taxes Between Estonia and Portugal: A Quick Reality Check
As a tax resident of an EU country who files my own returns, today is my quarterly 'Tax Day'. On this day I set aside a few hours to file social security report…
Saylify Update: Fighting Perfectionism, Refactoring, and Finding the Right Focus
I have not written anything about Saylify for a long time, even though I planned to launch in January. Unfortunately, life likes to throw in challenges you can …
Human-Like Memory for LLMs
TL;DR I wrote a manifesto-style essay about a memory model for LLMs that is as close as possible to human memory and lets the system build a relationship histor…
When Companies Finally Say the Ugly Part Out Loud
Now we are finally fucking talking. Not all that crap like "internal policies", "no explanation needed", "just because".1Office are the first who wrote it plain…