Search for a command to run...
A reflection on growth, judgment, and long-term thinking
I am a full-time Software Engineer and Technical Content Writer. I code and write about React, Vue, Flutter, Laravel, Node, Strapi, and Python. I'm based in India🇮🇳 and currently work remotely for CloudAnswers.
I also author technical articles for tech startups that include Strapi, Twilio, CircleCI, Lightrun, CSS Tricks, Draft.dev and many other tech companies.
No comments yet. Be the first to comment.
Never wonder if your power is out again. Using ESP32 to bridge the gap between grid and backup.
Why infinite renders happen, how to reproduce them, and how to fix them permanently - manually and with an LLM
How I moved external APIs to build time and made my static blog feel alive.
Notify users instantly when your app gets a new deploy - no service workers needed
2026 feels like a genuine inflection point in my software engineering journey. By February 2026, I will have completed four years as a professional engineer, starting with my first full-time role at CloudAnswers in February 2022. At this stage, my aspirations are less about titles or rapid jumps and more about clarity — how I think, the kinds of problems I choose to solve, and the impact I want my work to have over time.
This post is not a checklist of goals. Instead, it’s a reflection on the direction I want my career to move in — as an engineer who values strong fundamentals, meaningful leverage, and sustainable, long-term growth.
By 2026, my primary aspiration is to be fundamentally strong.
Not just "good at React" or "familiar with backend systems" but genuinely comfortable explaining why things behave the way they do:
How JavaScript works under the hood
How browsers render, schedule, and optimize work
How React actually reconciles, schedules, and re-renders
How data flows through a system end-to-end
I want to be the engineer who can debug issues calmly because I understand the system — not because I’ve memorized fixes.
Another aspiration is to shift from feature-level thinking to system-level thinking.
Instead of asking:
“How do I implement this requirement?”
I want my default question to be:
“How does this decision affect the system six months from now?”
That means caring about:
Trade-offs
Maintainability
Operational complexity
Developer experience
Good engineers ship features. Great engineers design systems that survive change. This shift usually happens when you’re trusted to own a product end‑to‑end, responsible not just for fixing bugs or adding features, but for the long‑term health and evolution of the entire system.
By 2026, I want my value to extend beyond code.
This includes:
Explaining complex ideas clearly to other engineers
Writing thoughtful PR descriptions and design docs
Adding working evidence in the PRs in the form of videos and screenshots
Helping juniors build correct mental models
Disagreeing respectfully and productively
Software engineering is a team sport. Clear thinking is useless if it can’t be communicated.
One of my strongest aspirations is to build leverage.
Instead of solving the same problems repeatedly, I want to:
Automate workflows
Build internal tools
Create systems that scale my impact beyond my own output
Leverage is what separates engineers who work hard from engineers who work effectively.
Technical skills can be learned. Judgment takes time.
By 2026, I want to develop a strong engineering taste:
Knowing when not to over-engineer
Knowing when technical debt is acceptable
Choosing boring solutions when they’re the right ones
This kind of judgment only comes from reflection, mistakes, and intentional learning.
Finally, I aspire to stay curious — but sustainable.
Not chasing every new framework, but:
Learning deeply
Picking tools intentionally
Balancing ambition with health
Longevity matters. I want a career that compounds, not one that exhausts me early.
By the end of 2026, I want to have launched at least one app that real users can use — not just a side project living on GitHub.
This aspiration is less about building a startup and more about closing the loop as an engineer. From idea to execution to feedback, I want to experience the full lifecycle:
Identifying a real problem (even a small one)
Designing a simple, opinionated solution
Making trade-offs under real constraints
Shipping, maintaining, and iterating based on usage
Building a personal app forces a different level of ownership. There is no product manager, no deadline imposed by someone else, and no ambiguity about responsibility. If something is broken, unclear, or poorly designed — it’s on me.
More importantly, it sharpens judgment. You quickly learn what actually matters to users, which abstractions are worth the cost, and which technical decisions age poorly once real usage begins.
My aspirations for 2026 are less about where I work and more about how I work and think.
If I can be a calmer problem-solver, a clearer thinker, and an engineer who builds systems that last — I’ll consider myself on the right path.
I plan to revisit this post at the end of the year to assess how closely my reality aligned with these intentions, honestly.