Another year, another chance to grow. As I sit here planning 2026, I'm struck by how different this feels from past years. I'm not chasing the next shiny thing anymore, I'm being intentional about what matters.

What Matters Most in 2026

Looking ahead, three things anchor everything else:

1. A stable career that develops my skills
Not just any job, but somewhere I can grow, learn, and build things that matter. With AI reshaping the industry faster than ever, staying technically sharp isn't optional anymore.

2. Time with family
It's easy to get lost in code and projects. 2026 is about balance, by being present with the people who matter while still pursuing what excites me technically.

3. Staying relevant in a rapidly evolving world
This one keeps me up at night. AI tools are getting better every day. If I'm not actively learning, I'm falling behind. Comfort is the enemy of growth.

The Hard Truth About 2025

Let me be honest: I'm afraid of becoming obsolete.

As AI gets more prominent, I can't imagine being comfortable with my future if I'm not working hard enough to keep myself relevant. ChatGPT can write code. GitHub Copilot can autocomplete entire functions. Where does that leave developers who don't evolve?

That fear, a healthy fear, I think—drives me to keep learning, keep building, keep pushing.

What I Got Right in 2025

Before planning forward, I need to acknowledge what worked:

Independence

I learned to be truly independent this year. Not just technically, but emotionally and mentally too. I stopped waiting for permission or perfect conditions. I just built things.

Focus Over Fun

This was huge: I stopped chasing projects just because they seemed fun. Instead, I asked: "How will this help me in the future?"

That filter changed everything. I spent six months on my self-hosted infrastructure instead of bouncing between half-finished side projects. The result? 99.99% uptime, real production experience, and skills I use daily.

Doing One Thing Well

I used to start ten projects (or is it 15? or 20? I can't even remember!) and finish none. In 2025, I learned to make one thing the best it can be before moving on.

My infrastructure project. My blog system. My IoT setup. Each one got my full attention until it worked well, not just "good enough."

What I Got Wrong in 2025

Impatience

My biggest failure: always wanting things done fast.

I'd rush through configurations, skip documentation, cut corners on testing. The result? Bugs I had to fix later, configs I had to redo, time wasted because I was "saving time."

In 2026, I'm slowing down. Details matter. Doing it right the first time is faster than doing it twice.

Passivity

Sometimes I need a "push" to do something instead of proactively doing it myself. I'd wait for motivation instead of creating it. I'd consume content instead of creating it.

That changes now.

Technical Goals for 2026

1. Deep Dive into PostgreSQL

I use PostgreSQL daily, but I'm not fluent yet. I want to understand:
- Query optimization and EXPLAIN ANALYZE
- Indexing strategies that actually matter
- Replication and high availability
- Performance tuning for production loads

No more copying Stack Overflow solutions without understanding them.

2. Master Docker & Containers

I've used Docker, but I'm still learning. This year:
- Docker Compose for multi-container setups
- Container optimization (smaller images, better caching)
- Orchestration fundamentals
- Production-ready containerized deployments

3. Infrastructure & IoT

Two parallel tracks:

Infrastructure: Make everything more automated and cleaner. Less manual intervention, more scripts, better monitoring. If I'm doing something twice manually, automate it.

IoT Smart Home: Build a smart home system that integrates an LLM for controlling IoT devices. Imagine saying "turn off all lights downstairs" and having it work through natural language processing, that's the goal.

4. Open Source Contributions

I've been a consumer of open source for years. Time to give back. Even small PRs—fixing docs, reporting bugs properly, contributing features—count.

Content & Sharing Goals

Monthly Blog Posts

Continuing my technical writing journey. Topics will center on:
- My experiences and what I'm learning
- Project breakdowns and how-tos
- Failures and what they taught me
- Infrastructure deep-dives

No pressure to be "viral", just authentic sharing of my journey.

Open Source Presence

Beyond blog posts, I want to be more visible in the community. Contributing to projects I use, sharing what I build, helping others when I can.

Beyond Code: Personal Goals

Fitness

Code better when my body works better.

Gaming

Reaching Diamond rank in League of Legends. Yes, it's "just a game," but it teaches:
- Strategic thinking
- Handling pressure
- Learning from mistakes quickly
- Consistent improvement

Plus, it's fun. Balance matters.

Language Learning

Continuing my Japanese N3 journey. Already invested time, not quitting now. Language learning teaches patience—something I need to practice.

Travel

Exploring other states in my country. Experience new places, new food, new perspectives. Life isn't just sitting at a computer.

The Big Theme: Critical Ignoring

Here's the skill I'm most excited to develop: critical ignoring.

I discovered this concept in a WSJ article and it clicked immediately. In a world where everyone screams for your attention—social media, news, trends, drama—the ability to intentionally ignore what doesn't matter is a superpower.

Critical ignoring means:
- Not checking Twitter/X obsessively
- Skipping the outrage of the day
- Ignoring tech trends that don't align with my goals
- Saying no to distractions disguised as opportunities

I'm tired of feeling like I need to know everything, read everything, react to everything. I don't.

Focus beats awareness. I'd rather be great at three things than mediocre at twenty.

Building Consistency, Breaking Passivity

Two habit changes drive everything else:

Building: Consistency

Showing up daily, even when motivation is low. Whether it's:
- Writing code
- Exercising
- Blogging
- Learning Japanese
- Practicing League

Consistency beats intensity. Small daily progress compounds.

Breaking: Passivity

No more waiting for the "right moment" or the "perfect motivation." Taking action creates momentum, not the other way around.

If I want to learn PostgreSQL → open the docs and start reading.
If I want to contribute to open source → find an issue and start working.
If I want to exercise → put on shoes and start moving.

Action first. Motivation follows.

What Success Looks Like

End of 2026, looking back, what would make me proud?

Not a checklist completion. Not "did I achieve every single goal."

Instead: Did I grow? Did I stay consistent? Did I focus on what matters?

If I'm:
- More skilled technically than today
- More consistent in my habits
- Better at ignoring noise
- Contributing to the community
- Healthier and more balanced

Then 2026 was a success.

Final Thoughts

This isn't about becoming someone else. It's about becoming a better version of myself.

I'm not trying to be a 10x developer or a productivity machine. I'm trying to:
- Build things I'm proud of
- Learn continuously
- Stay relevant in a changing world
- Be present with family
- Enjoy the journey

AI will keep evolving. Tech will keep changing. Social media will keep screaming for attention.

But I have a plan. I have focus. And I have 2026 ahead of me.

Let's make it count.

What are your goals for 2026? Are you also working on "critical ignoring"? I'd love to hear your thoughts, feel free to reach out at [email protected] or connect with me on LinkedIn.