Hey Everyone!
This is my first post on the Dev.to Website! I am excited to see the community and what it has to offer!
To begin with, I do have programming experience but I want to take the time and try to blog my journey to refine my Full Stack Engineering skills as well as learning to become an AI Engineer!
Goal for 2026
My goal is to be able to not only refresh my skills as a Full Stack engineer but to be able to have a focus in AI on top of that. In other words, a Full Stack Engineer with a focus on AI/ML implementation! I will post articles this year discussing my simplified views of what I have learned so far.
If you have any suggestions on learning AI engineering/Full-Stack engineering, I would love to hear from you!
Top comments (7)
Came back to read where it all started 😄 Funny to see “become an AI Engineer” as your 2026 goal, compared to your AI fatigue post this week. Has your view of AI changed a lot since January?
Since you asked for suggestions (9 months late, sorry!): becoming an AI engineer isn’t as hard as it looks if you commit to it. AI was built by humans, so it can be understood by humans. My advice is to focus on algorithms, data structures, and the basic math behind ML. In my work on AI training platforms, the problems AI can’t solve are almost always the ones that need deep fundamentals, not more tools.
Also, as someone from Japan, seeing Pokémon on your portfolio made me smile!
It’s been really fun chatting with you in the comments lately. Looking forward to more!
Hey thanks Takefumi! Glad you went to the beginning of time to see this lol.
Nothing really change on my view of AI. It's more of a reminder of what AI has become in the last few years for me such as public opinion, the capabilities, etc.
Yea, the AI Fatigue post basically contradicts of what I want to become. Though, I don't want to avoid it in a sense. The goal kind of change, but I want to learn the basic of AI so that I don't feel left behind.
Glad you like the Pokemon in my portfolio and thanks for the suggestions! Looking forward to seeing you again!
Haha, it was worth the trip 😄 I also read your second post on AI vs. ML engineers, and you'd already covered the math foundation there, so you were way ahead of my advice. I clearly have a lot to learn from you too.
And honestly, as someone who works in AI training, I think learning the basics is exactly the right move. You're not behind at all. Looking forward to seeing you again too!
Great start and clear goals for 2026!
I’m also focused on long-term growth over short wins. One thing I’ve noticed in scaling content is how feedback loops shape priorities more than initial goals.
Curious — how do you plan to measure progress toward those goals month by month, not just at the year level?
Hey Josef. Hope you are well!
I am debating on whether I should post my weekly goals or post the things I learn to as an formal article. For example, I posted an article about "AI Engineer vs. ML Engineer" in a simplified definition.
For right now, I think of sticking to formal articles since it allows me to enhance my knowledge by simply writing it out. What do you think?
Hey Francis, great question.
I’d actually keep the formal articles as your core. Writing structured posts forces deeper thinking, better research, and clearer explanations. That compounds your knowledge much more than quick updates.
You can still share weekly goals or learnings, but maybe as lighter posts or short notes. Think of them as “in public progress logs,” while articles are your “knowledge assets.”
So not either-or.
Formal articles build expertise.
Weekly updates build consistency and connection.
If you have the energy, keep articles as the foundation and use goals/learned posts to fill the gaps between them.
Thanks for the advice Josef. I will keep this in mind for the future :D
Some comments may only be visible to logged-in visitors. Sign in to view all comments.