Into Containers
So starts the journey of containerizing Strackt. As always the basics are simple, but getting it to a production-grade level with enough rigor to not get in the way is where things get trickier.
Blog
Everything after the deploy, and the work of building strackt. Technical decisions, product updates, and the unfiltered building journey.
So starts the journey of containerizing Strackt. As always the basics are simple, but getting it to a production-grade level with enough rigor to not get in the way is where things get trickier.
Working quite a bit on the feedback loop. Events systems are working better and better and it shows in the implementation speed of new features, but also in the progression of the UI
Small chunks of time also allow for small steps of progress
It has been more than 9 months since my last update, it itches and I need to force my calendar to make more time for it.
I just got a renewal notice for the Strackt domains, which means that I've been working on this project for a year now. It's a good time to reflect on the progress made and challenges faced over the past 12 months. 🤔
Investing in refactoring saves you more time in building
Experiments fail. Time to learn, clean up, revert and get on with a new idea.
Aligning and aggregating all the data streams between layers requires a lot of communication
Interacting with Strackt should fundamentally be a two track interaction; API and a front-end UI
Learning on the fly and dusting off my skills
We don't stack cookies.
Two essentials and one optional. That's the whole stack.
No advertising. No ad networks. Privacy policy