Now

Life right now is a mix of software engineering, building SparkTribe, creating content, learning new technologies, helping people, and trying to make better use of my time. I'm experimenting with AI, preparing for what's next, and documenting the journey along the way.

I'm currently working as a Software Engineer on a large enterprise client account, focused primarily on AWS CDK with TypeScript and cloud infrastructure modernization.

A big part of my work involves migrating legacy, hand-written CloudFormation and SAM infrastructure into AWS CDK across multiple applications and environments. The interesting part isn't simply converting infrastructure into code — it's doing it safely while preserving existing resources, avoiding unnecessary resource replacement, and maintaining zero downtime as changes move from development toward production.

I'm working on several infrastructure migrations in parallel, each at a different stage of the journey. Some have already been validated in production, while others are moving through earlier environments before being promoted forward.

I'm also involved in re-platforming a legacy application from shared infrastructure to dedicated, per-environment compute, alongside application modernization and a database migration.

This involves coordination across infrastructure, application, and security teams, with careful environment-by-environment rollout and validation.

I also review infrastructure-as-code changes from other engineers.

For me, a good code review isn't just about whether a diff looks clean. I try to understand whether the change actually behaves as expected, follows engineering standards, and avoids functional regressions before it moves into higher environments.

Another part of my work is identifying and safely decommissioning orphaned or deprecated AWS resources.

Before removing anything, I verify that the resource is genuinely unused. The goal is not simply to clean things up, but to do it safely without affecting a running application or dependent system.

I'm also exploring how AI can make engineering teams faster without sacrificing engineering standards.

I've been working on internal tooling and reference patterns that help AI coding assistants work with proven infrastructure patterns rather than generic suggestions.

I'm particularly interested in the intersection of good engineering practices and AI — how we can give AI better context, better patterns, and better guardrails instead of simply asking it to generate more code.

AWS · AWS CDK · TypeScript · CloudFormation · EC2 · Lambda · IAM · Secrets Manager · GitLab CI/CD

I'm building SparkTribe — a community focused on helping students and early-career software engineers become better prepared for their careers through structured learning, practical guidance, and consistent execution.

I'm trying to build something that goes beyond giving people information. I want to help people get clarity, take action, stay consistent, and actually make progress.

Explore SparkTribe →

I'm continuing to create content on LinkedIn and YouTube around software engineering, careers, motivation, lifestyle, financial freedom, mistakes I've made, and lessons I'm learning along the way.

I enjoy taking something I've experienced or learned and turning it into something that might be useful to someone else.

I spend time guiding college students and entry-level software engineers who are trying to figure out what to learn, how to prepare for placements, and how to build a career in technology.

A lot of people don't necessarily need more information. They need clarity about what to do next.

I enjoy helping them find that next step.

I'm also exploring more opportunities to speak at colleges, communities, and events about software careers, learning, motivation, and building a career in tech.

I enjoy conversations where I can share things I've learned from my own journey and hopefully help someone avoid a few mistakes along the way.

I'm trying to stay curious rather than chase every new technology. Right now, a few areas have most of my attention.

I'm going deeper into AWS and cloud infrastructure, especially the engineering practices behind reliable production environments.

I'm particularly interested in understanding not just how individual AWS services work, but how they come together to support real systems.

AI is one of the areas I'm spending the most time exploring right now.

I'm interested in what AI agents can actually do beyond generating text — especially how they can use tools, connect different systems, automate repetitive work, and turn workflows that normally take hours into something that takes minutes.

I'm trying to move from simply using AI to understanding how to build useful things with it.

I'm building a stronger understanding of system design and how large, reliable systems are designed, scaled, and evolved.

I want to understand the decisions behind systems rather than simply learning architecture diagrams.

I'm continuing to strengthen my problem-solving skills and preparing myself for the next stage of my engineering career.

I enjoy DSA because it teaches a way of thinking that extends beyond interview problems.

I'm also working on becoming a better communicator.

I want to explain technical ideas more clearly, tell better stories, and become more confident and effective when speaking in front of people.

One of the things I'm most excited about right now is the amount of leverage AI can create.

I'm experimenting with AI and agents that can take work that normally requires hours of manual effort and complete it in minutes.

I'm particularly interested in what happens when AI stops being just a tool we chat with and starts becoming something that can actually execute workflows.

The exciting part isn't simply that AI can generate code faster.

It's that one person can potentially build, automate, create, and accomplish much more than before.

I'm still figuring out where the real value is, but I want to learn by building — not just by watching demos.

I'm creating content on LinkedIn and YouTube around software engineering, careers, motivation, lifestyle, financial freedom, mistakes, and lessons I'm learning along the way.

I don't want content creation to be separate from my life.

I'd rather build something, learn something, experience something, and then share what came out of it.

Sometimes it might be something technical.

Sometimes it might be a career lesson.

Sometimes it might simply be something I'm figuring out about life.

The goal is to document the journey honestly and hopefully make something useful along the way.

This is what I'm reading right now.

I'm usually drawn toward books about habits, money, mindset, growth, and understanding how people think.

• Atomic Habits
• Rich Dad Poor Dad
• Unlocking the Unicorn Secrets — Ishan Sharma
• How to Win Friends and Influence People

I don't read just to finish books.

I try to take something from them that I can actually apply to my life.

I'm learning how to manage everything I want to do without losing myself in the process.

A full-time career.

Building something of my own.

Creating content.

Learning new technologies.

Preparing for what's next.

Speaking.

Helping people.

Staying healthy.

Travelling.

And still having a life.

There is always something else I could be doing, learning, or building.

I'm slowly learning that growth isn't just about doing more.

It's about figuring out what deserves my time and learning how to focus on it.

Code and social media have already shown me how one person's work can reach far beyond the time spent creating it.

AI and agents are taking that idea even further.

I'm excited to explore what happens when technology, content, and distribution come together — and to see what I can build with them.

I like the idea that something I build or create once can continue helping people long after I have finished creating it.

I don't have a perfectly mapped-out five-year plan.

I'm trying things, learning, building, making mistakes, changing my mind, and documenting what I discover.

Some things will work.

Some won't.

That's okay.

I'm more interested in building a life that I genuinely enjoy than following a predefined path just because it is considered successful.

That's what I'm up to right now.