Planning My 2026 Goals as a Developer: Lead, Open Source, Write Weekly

How I plan my 2026 goals as a developer: lead my team better, release one open source project, and blog every week, broken into things I can measure.

Kasidit Wansudon4 min read
careergoalsopen-sourcewriting

The start of the year is when everyone sets goals, and when most of those goals are forgotten by March. This year I tried a different way of planning my 2026 goals. Instead of writing a long list, I chose just three things and broke each one into something I can do this week. I am writing this at the start of the year, so there are no results to show off yet, only a plan and the reasons behind it, which I want to record so I can compare at the end of the year.

Why Only Three Goals

Last year I set too many goals: learning a new language, building a personal app, reading books, exercising. In the end everything was half done, because my day job already took most of my time. This year I set rules that the goals must:

  • Number no more than three
  • Each have something I can do every week, not something to do all at once at the end of the year
  • Be measurable as done or not done, without interpretation

Goal 1: Lead the Team Better

I work as a full-stack developer and have started taking on more of a coordinating role with teammates. What I realized is that I still solve problems by doing the work myself too often, instead of helping others solve them, which does not scale.

I broke this goal into measurable behaviors:

  • Every time someone asks me something, ask one question back before giving the answer, such as "what do you see when you look at the log?"
  • Write short documentation every time I do work that others might have to repeat, such as deploy steps or system recovery
  • Every week, note one thing the team is stuck on and one thing I will try to adjust

I did not set a goal about getting a particular title, because that is not something I control. What I can control is whether I practice leadership skills every week.

Goal 2: Release One Open Source Project

I have used open source every day for years, but I have never had a project of my own that others can really use. This year I want to change that.

I have not locked in what to build yet, but I have criteria for choosing:

  1. It solves a problem I run into myself every day, so I will have the energy to keep going even if nobody uses it
  2. It is small enough to release a first version within two to three months, because anything bigger is very likely to be abandoned halfway
  3. It has a README that lets a stranger install it in ten minutes

Lately I have been using AI to help write code more, and I have started seeing repeated problems, such as AI changing things beyond the scope or saying it is done when it has not been tested. The project I build may end up around there, but it is still only an idea.

What I can do every week is spend at least one session per week on this project, even if it is only noting problems or writing short code.

Goal 3: Write Every Week

I started this blog in December, and I explained why in Why I Started Writing This Blog. This year's goal is to keep a rhythm of one post per week for the whole year.

Rules I set so I do not quit halfway:

  • Write from work I actually did that week, with no need to hunt for new topics
  • The first draft does not need to be good, it just needs to be finished
  • Keep a backup list of at least five topics for weeks when work is heavy

Turning Goals Into a Weekly Checklist

What I learned from IT work is that a good plan breaks into small pieces you can check. So I use a simple checklist every Sunday.

Week __
[ ] Team: ask back before answering at least 3 times
[ ] Team: write 1 document others can repeat
[ ] Open source: 1 work session (note what I did)
[ ] Writing: 1 post
Notes: what got me stuck this week

This checklist does not measure success, it measures consistency, which I believe is what produces results in the long run.

What I Will Not Do

Saying what I will not do matters as much as saying what I will do. This year I will not start any new personal projects until the open source project releases its first version, and I will not chase every trending new tool unless it helps the work I am already doing.

Summary

My 2026 goals are three: lead the team better, release one open source project, and write every week. Each is broken into something I can do within a single week and verify with a checklist. For now it is only a plan. At the end of the year I will come back and write again about what worked and what did not.

Questions or thoughts?

Leave a note in the guestbook or reach me on X.