About Linux Heart
I’m Eugene Blago. Linux Heart began as my personal technology blog. Over time, building software became inseparable from learning how to turn it into a business, and I wanted this site to reflect that work.
Today, Linux Heart is where I write about products I have helped build, the decisions behind them, and the experiments we ran to find an audience. That includes development, design, course creation, launches and marketing. Some ideas found a useful direction. Others cost time and money without becoming something we could grow. Both belong in the record.
Products behind the stories
One of those projects is Nutrinaut. It began with a straightforward idea: make food logging easier by estimating a meal’s nutritional content from a photograph. Working on the product and collaborating with creators led us toward a broader question about training, sleep and recovery. The app now brings supported wearable records together with food logging and the context people choose to record about their day.
On this blog, I am documenting that journey through concrete examples: why we changed direction, how we approached athlete collaborations, what happened as we moved between TikTok, Instagram and YouTube, and the difficulties of building for Android. Finding a promising idea and finding a repeatable business have been two different challenges.
Another project is Inlecto, our learning app. We developed the software ourselves and hired teachers and specialists to help create the learning material. Building it meant working on the lessons as well as the application: what to teach first, how much to include in one session, and how to give someone a useful way to practise.
Inlecto’s course catalogue includes Speak with Clarity and Confidence, Active Listening That Builds Trust, and Clear Mind, Deep Flow. These are examples of its focus on communication and practical personal development. The learning experience combines short lessons, course roadmaps, reflection and exercises. Our work has also involved mobile and web versions, different languages, and the ongoing task of keeping the learning experience coherent as the product changes.
What I want to share here
I am most interested in the decisions that become clearer with hindsight: a feature that was easy to demonstrate but harder to make useful, a collaboration that attracted attention without becoming a dependable channel, or an implementation detail that changed the experience for the person using it.
Where I have public examples, screenshots or dated records, I will use them. Where I am describing my own recollection, I will say so. I work on the products discussed here, and that relationship is part of the story.
The older posts remain part of Linux Heart’s history. The newer ones follow the same curiosity into software, education and business: build something, see what happens when people encounter it, and write down what the experience taught us.