The years start comin and they truly don't stop comin'.
Well it was definitely a year. I don't have too much nice to say about it, so let's just move on to the aspirational goals for this year.
Not hype. Not hustle. Just… direction.
None of this is concerning Content Creation and i'll probably make a seperate post to that specefically
New Year, New Direction
If you always do what you’ve always done, you’ll always get what you’ve always got.
Last year proved something pretty clearly: I can build a lot of things. It did not prove that I can finish them consistently, ship them cleanly, or focus long enough for them to matter.
So 2026 is about doing less — but doing it properly.
No more “almost done.” No more graveyard of promising side projects. No more confusing motion with progress.
A Quick Look Back
Short version: I built a lot, learned a lot, and closed very little.
There were good experiments, solid technical progress, and some genuinely useful systems that came out of the chaos. But too many things stalled in the last 10–15%. Not because they were impossible — because I let myself get distracted by the next shiny idea.
2025 was about capability. 2026 is about execution.
The Big Themes for This Year
1. Taking every day one project at a time
No more leaving projects 89% complete before shoving them to the side and forgetting all about them. This year I’m taking it one (okay maybe three), projects at a time.
To completion.
That means boring work. Cleanup. Docs. Edge cases. Launch checklists. The unglamorous parts that actually turn something into a real thing.
2. Systems over bursts of motivation
Motivation is unreliable. Systems aren’t.
I don’t want another year powered by last-minute pushes and adrenaline. I want repeatable workflows, predictable progress, and fewer “I’ll just rewrite this later” moments.
If a project can’t survive without constant heroic effort, it’s either scoped wrong or not worth doing yet.
3. Fewer experiments, more impact
I like trying new ideas. I’m good at starting them. That’s not the problem.
The problem is spreading energy across too many directions and ending up with nothing that actually compounds. This year is about choosing a small number of bets and pushing them far enough to matter.
Depth beats breadth.
Core Goals
🚀 Career & Projects
- Ship at least one primary product end-to-end. Not a demo. Not a prototype. Something real, deployed, documented, and usable.
- Turn one long-running project into something sustainable. That means stability, maintenance, and an actual roadmap — not just features.
- Publicly share progress. Write, document, or log what I’m building so it doesn’t all stay trapped in my head.
🧠 Learning & Skill Growth
- Level up system design. Fewer ad-hoc decisions, more deliberate architecture.
- Get sharper at finishing. Scoping, prioritization, and knowing when something is “done enough.”
🛠 Systems & Setup
- Standardize my stack. Less reinventing the same foundations for every project.
- Automate the boring parts. Builds, deploys, backups, documentation — anything that steals focus from actual problem-solving.
- Create a single source of truth. One place for plans, specs, and decisions so projects don’t drift.
💪 Health & Life
- Consistency over intensity. Show up regularly instead of burning out in short bursts.
- Protect deep work time. Fewer fragmented days, more uninterrupted blocks.
- Actually log progress. If I can’t see it, I can’t improve it.
What I’m Saying No To
- No more half-finished projects “for later.” If it’s started, it gets finished or killed.
- No features without a purpose. Every addition needs a clear reason to exist.
- No building just because I can. Technical novelty alone isn’t a goal.
- No pretending busy equals productive. If it doesn’t move something forward, it doesn’t get priority.
How I’ll Measure Progress
- Quarterly reviews. What shipped, what stalled, what got cut.
- Binary outcomes. Launched or not launched. In use or not in use.
- Project caps. No more than a small, defined number of active builds at once.
- Visible artifacts. Repos, docs, deployments — proof that work actually exists outside my head.
If a project can’t show tangible progress in a quarter, it gets re-scoped or dropped.
Closing
I’m not trying to do more this year. I’m trying to do better.
Finish what I start. Build things that last. Create systems that outlive motivation.
If you’re following along, you’ll see what ships — and what doesn’t. Either way, this is the year of fewer ideas and more outcomes.
Let’s make it count.