Overthinking about the future feels like planning but produces no decisions. Set a short, fixed time to think about big questions, turn worries into checkable actions, commit to a 90-day plan you only review at the end, and let the daily work answer questions that thinking cannot.
What people tell me
I spend hours thinking about my future instead of studying. Will there be jobs in two years? Did I choose the right field? Should I switch to something else? What if the market gets worse? I read threads and watch videos about the future of tech late at night, and I end up anxious and tired. When I finally sit down to learn, my mind keeps going back to these questions and I cannot concentrate.
A composite of the messages behind this question, with personal details left out.
Key takeaways
- Overthinking feels productive but rarely produces a decision. Planning ends in an action; worrying loops.
- Give big questions a fixed slot, such as 30 minutes on Sunday, and park them the rest of the week.
- Turn each worry into something you can check or do, or accept that it is outside your control.
- Commit to a 90-day plan and only review it at the end. Constant reevaluation is the enemy of progress.
- Skills that transfer, such as fundamentals, problem solving and communication, reduce the stakes of any single bet.
Planning versus looping
There is a difference between thinking about your future and overthinking it. Planning ends with a decision or an action: "I will focus on backend for the next three months." Overthinking goes round in circles: "But what if backend is not the right choice? What if the market changes? What about AI? What if I should have done something else?"
A useful test: after thirty minutes of thinking, has anything changed about what you will do tomorrow? If not, you were looping.
The questions themselves are reasonable. The problem is asking them every day, with no new information, at 1am.
Why the loop is so sticky
- Uncertainty feels dangerous, so your brain keeps searching for a certain answer. There is none, so it keeps searching.
- Online content feeds it. Videos and threads about "the end of programming" or "the best field in 2027" are made to be watched, not to help you decide.
- Thinking feels safer than doing. Learning exposes you to not knowing things. Thinking about the future lets you avoid that discomfort while feeling busy.
Sort your worries into three buckets
Take the questions that keep coming back and write each one down. Then sort them:
| Bucket | Example | What to do |
|---|---|---|
| I can check this | "Are companies hiring junior backend developers?" | Look at real listings on Sefism jobs for 20 minutes and note what you see |
| I can act on this | "What if my skills are not good enough?" | Pick one skill to improve this month and start today |
| Outside my control | "Where will the whole industry be in five years?" | Accept you cannot know, and choose skills that transfer |
Most of the anxiety lives in the third bucket. The honest answer there is: nobody knows, including the people making confident videos. What you can do is build skills that hold their value in many futures.
Build skills that survive many futures
When you cannot predict the future, you prepare for several. The skills that tend to hold their value across changes in tools and trends are:
- Fundamentals. Programming, data structures, how the web and databases work.
- Problem solving and debugging.
- Communication. Explaining, writing, asking good questions.
- Learning speed. The ability to pick up the next tool quickly.
- Shipping. Actually finishing and deploying things.
The blog post on the fundamentals worth learning as a software engineer goes deeper. If AI is the main source of your worry, read Is it still worth becoming a software engineer? once, then stop researching it for a month.
Give the big questions a fixed slot
This is the most useful habit I suggest to people stuck in this loop:
- Choose one 30-minute slot a week, for example Sunday afternoon.
- During that slot, you are allowed to think about the future as much as you like. Write your thoughts down.
- At the end, write one decision or action for the coming week.
- The rest of the week, when a big question appears, write it on a "Sunday list" and return to your work.
It sounds too simple to work. In practice, parking the thought is much easier than fighting it, because you know it will get its time.
Commit to 90 days
Constantly re-evaluating your path is like digging up a seed every day to check if it is growing. Pick a direction and commit for 90 days before reviewing. For example, the Backend development roadmap, or DSA alongside one project.
| Period | Focus | Review question |
|---|---|---|
| Days 1 to 30 | Foundations of your chosen track | None. Just do the work. |
| Days 31 to 60 | One real project using those skills | None. Keep going. |
| Days 61 to 90 | Deepen, polish, start sharing work | Day 90: what did I learn, what do I enjoy, what next? |
At day 90 you will have evidence about your interests and abilities that no amount of thinking could give you.
What a good Sunday slot looks like
Here is an example of the slot in practice. You sit down with a notebook and your "Sunday list" from the week. It says: "Will AI replace junior developers?", "Should I switch to data?", "Is my project good enough?".
- For the first, you note that you have already read one careful answer, nothing new has happened, and you move on.
- For the second, you write: "Not before day 90. Note it for the review."
- For the third, you write an action: "Ask one person for feedback on the project this week."
Twenty minutes, three decisions, and a week that belongs to learning. The questions have not been ignored. They have been handled.
Limit the inputs
- Unsubscribe from channels that mostly predict doom or hype.
- No future-of-tech content after 9pm.
- Replace one hour of reading opinions with one hour of building something.
Common mistakes
- Waiting for certainty before starting. It never arrives.
- Switching paths every few weeks. See How do I stop switching technologies and commit to one path?.
- Treating one viral post as a trend. Look at real job listings instead.
- Thinking at night. Everything looks worse at 1am. Decide in daylight.
- Confusing research with progress. Reading about fields is not learning a field.
If you are still stuck
Read I know what I need to do, but I feel overwhelmed by how much there is to learn next. And if the loop keeps winning, talking it through with someone who has seen many careers unfold can break it quickly. Join Sefism, where learning is free, you get credits when you join and your first roadmap is free, then ask your question or book a 1:1 session.
Was this answer helpful?
Read next
Your situation is not quite this one?
Members get written answers to their own questions, a roadmap built for them and feedback on their projects. Early access is open: sign up and your account is active shortly after. Prefer to talk? A free call works too.