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
The Failure of AI Skepticism: Why Manual Coding Is Already the Wrong Layer
In recent months I keep seeing the same pattern: someone posts another example where some "vibe coders" used AI to generate a project, left API keys on the fron…
You Don’t Need a Perfect Modern Stack to Agentize Your SDLC
Continuing the idea from the previous post. Many companies believe that to add agents to their SDLC they first need to completely get rid of legacy, move to mic…
AI in Software Development: What Comes Next?
AI. What’s next? Up until around December, using AI in development basically meant: prompt -> copy some code -> paste -> tweak -> repeat. Now this a…
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…