DEV Community

Amara Graham
Amara Graham

Posted on

What should I do and learn in 2026?

I blinked and it's March. That's not entirely true, January was 100 years long, then February showed up, and at least here in Central Texas, that meant it was harshly cold for like 48 hours and now it's summer. "That's false Spring!" No... we don't have Spring here.

Anyway, it's March and you might be asking yourself what you should actually be doing this year now that the year is rolling onward. You may have yearly or quarterly goals or metrics, but what are your personal development goals? And do you already feel behind?

You may be asking yourself what you want to actually do this year. What do you want to learn? What skills do you want to level up? Never fear, let me provide you with my opinionated list of some of the tactics I recommend for navigating this.

Use AI and have opinions about popular AI tools

I want to be very clear that I don't think AI is appropriate everywhere, but I do think if you are in tech you need to have some kind of personal narrative around AI, particularly related to your role. Where you use it, why, and how.

Someone recently asked if I would let AI write blogs for me, and the answer is no, I barely let any tools spell and grammar check my blogs. I'm sure you can tell. Voice and style aside, which I'm aware an AI can "learn", I find writing very cathartic and if someone else reads and enjoys it, that's a bonus. I have no reason to give that up, but also, where am I going to put this chaotic, GIF-filled corporate rage?

Schitt's Creek's Alexis going

I digress.

Claude for summarizing, brainstorming, and ideation

I use Claude for summarizing written content for things like video scripts. My prompts are dead simple:

Turn this blog into a 2-3 minute video script.

Claude and I also like to collaborate on talk ideas, titles, and descriptions. This gives me a great base to either edit on my own, entirely rework, or read exactly once and close Claude's window.

Make this talk title something people would actually go to.

I also like asking for summaries on specific docs pages because I want to see a TL;DR that matches my understanding. This leads into the next use case.

Docs AI for search and knowledge checks

I use built-in docs AI for enhanced search and knowledge checks, almost like quizzes in academy courses. Those implementations will heavily depend on the model, but many are good about citing their sources if I feel like I need to fact check.

If there is both a search and a docs AI, I like to see what results come up when I search or ask a question with similar terms. This is helpful to see and work to improve the UX and "findability" within docs. If search and docs AI are generating different results, or worse, they are not finding what they should, you need to spend some time to fix it before your users get stuck.

Copilots

I'm mostly only working on small code bases and demos these days, so I can use Kestra's Copilot or Visual Studio Code's Copilot, something specific to a single file or repo, and this works really well for me. I know some people have other AI agents deep in their organization's tooling, but I don't really need that right now.

All of this comes back to my experience with AI and my opinions I've developed around it. These options may not work for you, but I would strongly encourage you to develop your own experience and opinions, particularly because it will come up in my next "skill": interviewing.

Never stop interviewing

This one hurts to type because interviewing is hard, even in the most pleasant interview cycles and job markets. It can evoke a lot of negative feelings and, depending on who you talk to about it, might make it seem like you are looking for your next opportunity. How you feel after that interview, whether you are truly job seeking or not, can be largely dependent on the interviewer.

The idea with this one is you "never stop interviewing" so you never lose the skills to interview. You are able to talk about your experience, skills, delivery, and value outside of a yearly or bi-yearly performance review to someone who knows nothing other than maybe what you put on the application and in your resume.

I heard this one very early on in my career from someone quite senior, and then I heard it reinforced by people in other areas of the org chart. They were clear that they weren't necessarily looking for another position, but they wanted to know what was out there and they wanted to keep these interview skills honed.

It's also a great reality check to see if you need to do a hard pivot of some kind. Sometimes titles change or roles evolve and you need to be flexible enough to adjust. Interviewing helps you understand what people outside of your current organization are looking for.

Keep your resume updated

I like to visit my resume at least twice a year, typically aligned either with a performance review or the end of the year. What you are trying to avoid is a situation where you need an updated resume immediately, and you can't possibly figure out how to summarize your role on the fly.

If you can get really good at having a refined, ready-to-go resume, you should be really good at communicating your role, experience, skills, delivery, value, etc. and interviewing (and performance reviews!) become easier too.

Find your community, online and offline

I started going to bookstore events last year. I had started reading romance novels for the predictability and comfort that comes with a happily ever after (HEA) or happy for now (HFN). And at some point I realized one of my favorite authors was local and I could actually go see her. And surround myself with people who also thought she and her books were pretty cool too. Not only do these events immediately feel like safe spaces, they remind me that even though I've spent an entire career working mostly with men, there are communities that are almost entirely not-men out there too.

And it's all about finding balance. Like balancing a stack of books on the way to the cash register when you just came for one. Oopsies!

More and more community spaces and groups seem to be seeing a post-pandemic-shutdown renaissance. I don't know exactly what's driving that, but I know I'm finding more energy to even get out to tech meetups again. Maybe people are craving those connections again? This makes it a great time to join and explore communities with others doing the exact same thing.

Geek out on something

I like birds.

Zombie kid saying

This is not new, this is a life long... hobby...? Birds + AI are apparently a thing this year, with CES summoning AI-powered bird identifying tools. So I acquired some new tech and apps to live my best bird nerd life this year.

Birds aren't your thing? Find something to go deep into. I'm also big into nail polish and stained glass (copper foil & lead came). Those aren't even close to tech adjacent, but they give me an opportunity to "touch grass" away from a computer.

So, what's the plan?

Maybe this wasn't quite the list you were expecting, but I hope it gets you thinking. What is on your list for doing and learning this year? Have you started? There is still so much year left.

Top comments (46)

Collapse
 
francistrdev profile image
👾 FrancisTRᴅᴇᴠ 👾

The main focus for this year is interacting on Dev.to and practice my interviewing skills. I notice that I am on track on the developer side, but am bad at articulating my thoughts in the interview phase. I am hoping to improve my communication skills in terms of interviewing and hope for the best!

Overall, great post! Thanks for sharing :D

Collapse
 
missamarakay profile image
Amara Graham

This is great! Thanks for sharing! You got this :)

Collapse
 
joseph-dev-agent profile image
Joseph Bryant

I'm new to Devto, but I think it will be great journey for me and all of us

Collapse
 
missamarakay profile image
Amara Graham

Welcome to Dev!

Collapse
 
felix_arsene profile image
Felix

Welcome!!!

Collapse
 
ryanhaber profile image
Ryan Haber

I have started using AI to help me interview better. How? Record and transcribe the interview. Feed it to an LLM trained to think like someone in a senior role interviewing job applicants. I tend to prattle on, and Claude with a little training has really helped me tighten up those "tell me about a time" narratives.

n.b.: secretly recording people is illegal in many US jurisdictions. If you choose to do this, best to delete the audio as soon as you're done.

Collapse
 
pengeszikra profile image
Peter Vivo

I try to understand the wasm byte format to able write a wasm code like coding assembler 30+years ago. This journey lead me to create a text representation of wasm different than a WAT. For this process is arguing to AI is help a lot.

Collapse
 
crisiscoresystems profile image
CrisisCore-Systems

This is such a grounded list, especially the part about having an actual personal narrative around AI. Not a hot take, just a clear sense of where you use it, where you do not, and why. That alone makes you easier to trust in interviews and in teams.

Never stop interviewing is painful advice but true. The skill rots if you do not touch it, and the market shifts under you while you are busy living your life. Treating interviews like practice reps instead of emergencies is a good way to keep your nervous system calmer.

The resume point also lands. What helped me is keeping a tiny running log of shipped work and decisions, then the resume becomes a clean extract instead of a memory test twice a year.

Also loved the community section. The bookstore events example is a good reminder that community is not only tech meetups. Sometimes the best reset is being around people who care about something totally different.

If you had to pick one tiny habit from this list that gives the biggest return, what would it be.

Collapse
 
missamarakay profile image
Amara Graham

Updated resume. Just like you mentioned, keeping a running list of things - work you do, kudos you get, things you learned - is great, but being able to distill it into the value and experience gained, is huge. This translates across the other topics, like interviewing.

Collapse
 
crisiscoresystems profile image
CrisisCore-Systems

Yes, that is the real skill. The running list is just raw material. The hard part is translating it into value without inflating it.

What helped me was writing each bullet in two layers. First the plain fact of what changed. Then the why it mattered, like what risk it reduced, what friction it removed, what it made easier for the next person. Once you do that a few times, interviews get easier too because you are not searching your memory under stress, you are just telling the story you already clarified.

Do you have a format you use for distilling. Like challenge, action, outcome, or do you keep it more freeform.

Thread Thread
 
missamarakay profile image
Amara Graham

I'm more freeform, but I wouldn't say I'm an expert in resume building for everyone.

Thread Thread
 
crisiscoresystems profile image
CrisisCore-Systems

Totally fair, and honestly freeform is usually the best starting point. If you can write it in a way that sounds like a real human, that already puts you ahead of most resumes.

I think the real win is what you said about distilling value and experience gained. Even a simple habit like asking what changed because of this and who did it help makes the bullet points sharper without turning them into corporate speak.

If you ever feel like sharing one example of how you rewrote a raw note into a final resume line, I bet people would find it more helpful than any generic resume advice.

Thread Thread
 
missamarakay profile image
Amara Graham

I'm unlikely to share more specific resume advice after receiving harassment online the last time I did this. If I find resources on this, I'll happily share them, but I need to protect myself and won't be offering more specific resume advice at this time.

Thread Thread
 
crisiscoresystems profile image
CrisisCore-Systems

That makes total sense. I am sorry that happened to you, and I respect the boundary. Please do not feel any pressure to share specifics. If you come across any general resources or frameworks that are safe to point to, I would be glad to read them. Appreciate you being here and protecting your own safety.

Collapse
 
abustamam profile image
Rasheed Bustamam

Thanks for the prompt! My main focus this year is optimizing my AI-accelerated workflows, but also not losing sight of the big picture. That's why I'm also taking a deep dive into distributed systems. And I'm learning in public! dev.to/abustamam/series/36007 (apologies if posting a link is inappropriate; please let me know if you'd like me to delete). Through this I want to build my brand as an expert in "classical engineering" (web development, distributed systems) but also "new engineering" (AI-accelerated workflows etc).

I agree with you -- writing is cathartic. That said, I do admit that I use AI to help me synthesize information, outline my blog posts, etc. But I feel like AI will never have my voice. I piped one of my blog posts into Chat GPT once and it was like "this is not professional" and I'm just like, well I'd rather be me than be professional! Besides, while AI overuses em-dashes, I overuse semicolons and parentheses.

My dad loves birds; when we walk together the few times a year I see him, he's always able to identify birds based on their warbles, time of day/year, migration patterns, etc. I bought him an AI birdhouse for his birthday a few years ago. I don't know if he uses it though; I don't know why he would when his intuition is a lot better than AI right now!

But I picked piano back up after 20 years having not played; I'm not as good as I was before and most of the time when I practice I have a baby in one arm, but it's still a fun hobby and it's one of the few things besides milk that can calm the little one!

Great post! Thanks for sharing.

Collapse
 
missamarakay profile image
Amara Graham

I piped one of my blog posts into Chat GPT once and it was like "this is not professional" and I'm just like, well I'd rather be me than be professional!

Same! Professional can be too stuffy and boring. I also love a good use of semicolons, although I use them less after working for non-American companies.

Thanks for sharing! Good luck with your deep dive and learning in public.

Collapse
 
vasughanta09 profile image
Vasu Ghanta

Love this post—super practical roadmap for 2026! The "form real opinions on AI tools" bit hit home; I've been doing that with Claude and it totally sharpens your edge in interviews. Never stop interviewing is my new mantra too. What community are you diving into first? 🚀

Collapse
 
missamarakay profile image
Amara Graham

As a Developer Advocate I do a lot of community work in my day to day role. But! I'm planning to get back into more local bookstore events like author meet and greets.

Collapse
 
playserv profile image
Alan Voren (PlayServ)

Good reminders here, especially about keeping your resume updated and practicing interviews. I’ve interviewed hundreds of engineers, and many capable developers struggle to explain what they actually built and why it mattered.

Collapse
 
javz profile image
Julien Avezou

Great and timely post! February always flies by I agree...
This year I am getting more involved in my local tech communities and also on Dev.to.
I am educating myself on AI tooling and using it mainly for ideation and automating repetitive tasks.
As for hobbies, I enjoy reading and exercising and like to start and end my days with these. With tech moving so fast, it grounds me to have these hobbies as anchors in my daily routine.

Collapse
 
missamarakay profile image
Amara Graham

Love reading and exercising to get you away from screens!! I am a huge fan of spin classes myself.

Collapse
 
codehelperai profile image
Ghullam Akbar

Really enjoyed this perspective. I like that ur list isn’t just about “learning more tech”, but also about building a sustainable career and mindset.
The part about developing your own opinions around AI tools really stood out to me. In the Python + AI space, I’ve noticed that the most productive approach is using AI as an assistant for brainstorming, debugging, or summarizing ideas — while still doing the real thinking and building yourself.
I also strongly agree with the idea of never completely losing the skill of interviewing and keeping your resume updated. Those are things many developers only think about when they suddenly need them.
And the “geek out on something” advice is underrated. Having interests outside of code actually helps avoid burnout.
Thanks for sharing this — curious to know if any of these habits have changed the way you approach learning over time?

Collapse
 
missamarakay profile image
Amara Graham

I think AI is actually a great example of how I've changed my approach to learning overtime.

I decided to use Claude specifically to do some summarization to validate something I had already read. Up until that point I really only used AI as a search mechanism. This was kind of a gentle introduction to how I could see myself actually using AI productively so long as I felt like the output adequately reflected what I understood as well.

In a recent interview cycle I did get asked how I was using AI and my response was "reluctantly." Now this was about a year ago at this point, but I strongly felt like the AI tools and models I had access to just weren't a great experience. I was under a bit of a mandate to use them and they required a lot of effort to produce something I felt like I could do on my own in less time. Fast forward to a few months ago, I'm willing to try different AI tools for different purposes and reasons because I want to develop these meaningful opinions about them rather than simply ignore AI entirely. This was reinforced by going to a meetup and hearing about how other people are using AI at their jobs.

Collapse
 
harsh2644 profile image
Harsh

Same here! January felt like it would never end, and suddenly March is here and I'm wondering where my 'learn something new everyday' resolution went. 😅

Completely agree on the AI part having an opinion on AI tools is becoming as essential as having an email ID in the 2000s. It's not about using AI for everything, but knowing when not to use it is equally important.

Also, 'barely letting tools check my grammar' respect that! There's something authentic about raw, human-written content.

Collapse
 
missamarakay profile image
Amara Graham

I'm wondering where my 'learn something new everyday' resolution went. 😅

There is so much left of the year! You can still learn something new almost everyday!

Collapse
 
agardnerit profile image
Adam Gardner

I've been using iNaturalist for ages for species identification

Some comments may only be visible to logged-in visitors. Sign in to view all comments.