Article
Why I Think Long-Term About Work, Money and Life
A few days ago, I attended a university reunion, and near the end of the evening, when only a few of us remained, I asked my former classmates about their goals for 2025. One of them smiled at the question, turned it back to me, and the conversation quickly moved on. This small moment reminded me how natural it feels for me to think about the future and set goals, compared to the way others might view it.
For as long as I can remember, I have always thought in the long term. It is not a deliberate choice or a strategy I picked up along the way—it is just how my mind works. Whether it is a decision at work, a financial plan, or even personal goals, I naturally gravitate toward thinking about the bigger picture and what comes next. This forward-leaning mindset is one of the traits I have come to recognise as part of my INTJ personality — it is not something I chose, it is just how my attention tends to settle.
Long-Term Thinking in My Work
In my professional life, long-term thinking is not about perfectly predicting the future. It is about identifying the things that truly matter, the projects and goals where I want to focus my energy—those that carry lasting value.
This is why I deeply enjoy building teams or rethinking how we work with data. These kinds of efforts demand a clear vision for the future and a dedication to creating changes that have a lasting and tangible impact.
Long-Term Thinking in Finances
Long-term thinking in finances is tied to how I have approached saving and spending my whole life. Being mindful about resources and consistently setting money aside reflects my commitment to building a stable future. For me, it is about creating habits that align with patience and purpose, rather than chasing short-term rewards.
Continue reading
Enter your email to unlock this article and join the newsletter. You can unsubscribe anytime.
Summary
If you have any thoughts, questions, or feedback, feel free to drop me a message at mail@richardgolian.com.
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.