Article
The end of 2024 is approaching, and I find myself on a train, heading to my hometown to spend the holidays with my family. In just a few hours, I’ll be in Banská Bystrica, the place I hold so dearly in my heart. As I sit here, I’ve been reflecting on what 2024 has taught me and what challenges await me in 2025.
The Biggest Lesson of 2024
When I first considered what 2024 taught me, my mind wandered to the usual contenders: professional missteps, personal struggles, or relationship challenges. But none of those compared to the realisation that health—my own health—had been neglected.
Yes, I know what you’re thinking. Everyone knows health is important; it’s obvious. And to those around me, it probably seemed like I understood this too. I’ve often told my colleagues, "Health comes first," whenever they faced an issue. But here’s the uncomfortable truth: I didn’t live by my own words.
In my professional life, I’m quick to act when problems arise—a data discrepancy, a sudden error, or an unresolved issue. These challenges can frustrate me, but they also motivate me to dive in and fix them immediately. Why, then, don’t I respond with the same urgency when it comes to my health? Why don’t I pay attention to my body’s signals and take them seriously?
Continue reading
Enter your email to unlock this article and join the newsletter. You can unsubscribe anytime.
Summary
Common questions on this article's topic
Why do professionals often neglect their own health?
What is the intention-action gap in health?
Can treating health like a work project actually help?
Why is sleep quality so important for professionals?
Related articles
My body was not broken. Quite the opposite – it was smarter than me.
More articles
Prague, 13 May 2026. On my way to work I started thinking about something that stayed with me for days. If most routine work on a computer disappears in the next ten years, and a large share of repetitive manual work disappears with it, what happens to the flow of money? Who pays whom for what? Which economic layers will exist, how large will they be, and what relationships will run between them? This is the six-layer map I sketched as an answer.
I am building an AI system to predict the S&P 500. It runs on my own machine, uses free public data — yfinance, FRED, the Shiller dataset — and grades every forecast against reality. This series documents the build itself: the decisions, the methodology, the mistakes. What I will eventually share from the running system is a separate question, and an honest one.
Yesterday I could not tear myself away from the computer. When I lifted my head, it was half past eight in the evening. I had been sitting alone upstairs for about three hours.
Will AI take my job? A certified Google trainer told me in June 2024 that my profession would cease to exist. Twenty-two months later, my job title has not changed — but ninety percent of what I do during the day is different. I have delegated more of my thinking to AI agents than I thought possible. I am not afraid. This is why, and what it means for anyone asking the same question.
One hour. Fifty-five minutes. That is how long it took to build what a Czech software firm had quoted at over €50,000. I built it with Claude Code. Not a prototype. Not a proof of concept. A working tool — the one the company actually needed. By the evening of the same day, it was running on staging. This is not about Claude Code. It is about what Claude Code exposes.
I have conducted roughly one hundred and fifty practical interviews over the past four years. Fifty for data specialist roles. A hundred for advertising and performance marketing specialists. Almost every one of them involved sitting down with a candidate over a practical task — something close to a real problem we actually need to solve at the company. Not theory. Not trivia. Applied problem-solving. Over time, I started noticing a pattern.
Before you can teach AI to understand anything, you need to see what it is hiding from you.
The moment other people needed access to it, the problem changed completely. It was no longer about whether the agent could learn. It was about who gets to teach it.
I wanted to build an agent that doesn't just assist. One that acts.
This is what I learned about local vs cloud AI, and why I switched to Claude Code.
Four days in Catalonia. No computer, no AI, almost no social media. I bought this notebook so that I could write down what I would think about, and what I would come across and learn on the trip.
