engineering
Making Telli.sh More Stable
A simple look at the recent fixes that made recording and deployment feel more reliable.
T
Telli.sh Team#stability#deploy#recording#testing
We spent the last few updates making Telli.sh feel steadier and easier to trust.
That meant fixing the kinds of problems people notice in day-to-day use:
What we improved
Recording
- Stopped the app from jumping back to the start screen when a recording ends.
- Fixed a first-click issue that could interrupt the first recording attempt.
- Made the ending flow feel smoother so the app clearly shows it is finishing up.
Uploads and saved notes
- Added extra checks so progress updates stay tied to the right user.
- Cleaned up exported file names so they are safer and more predictable.
- Reduced the chance of leftover temporary state causing trouble later.
Deployments
- Fixed a path mismatch that was causing our deployment check to look in the wrong place.
- Added tests so the same mistake is less likely to return.
- Kept the deploy check tied to the real production address.
Blog writing
- Kept the blog simple and file-based.
- Added a command that creates a new post draft with the right format every time.
Why this matters
The best stability work is usually the kind you only notice when it is missing.
If we did this well, Telli.sh should just feel calmer: recordings start more smoothly, endings look cleaner, and updates ship with fewer surprises.