General

I am Sanjeev: How I Went From Picking Up Shrapnels to Picking Up Coding

May 25, 2026

Yes, you're seeing a picture of me with a bunny as the cover image of this post 😄. His name is Mochi. He is very destructive and currently lives in Manchester. As we speak, he is probably trying to eat my friend's shoes or causing some other form of chaos.

He isn't actually mine. Mochi lives with one of my friends, who has two bunnies: Mochi and Poffin.

I don't have many photos of myself, nor do I really use social media. I'm a very private person. The few pictures I do have are usually of me standing in front of a Formula car, holding a bow and arrows, or hanging out with Mochi.

A Bit About Myself: Why Did I Spin Up a Personal Website?¶

At this stage in my career, and in life, everywhere I go, people ask for my socials and want to know a bit more about me. I will never be on social media, but I do have LinkedIn, which I share when people ask.

I needed a way to make myself publicly available, and I finally feel ready to do so. I feel that what I have to share can help a lot of people, or at least I hope it does. Over the years, I've received feedback from colleagues, friends, and even complete strangers about how my story, achievements, and advice have helped them. Some of them are doing really well in life now, partly because of that spark they got from me, combined with their own hard work and determination.

I thought a personal website would allow me to control the content and make myself publicly available in my own way. For example, I can share my photography work when people ask for my Instagram, which I don't have, after meeting me on road trips or seeing me out with my cameras. I can use it to network within my field, document my journey, and keep a diary of sorts where I can publish whatever I want in a format I'm happy with.

As you know by now, my name is Sanjeev. You can learn a bit more about me by exploring the home page.

I was born in Sri Lanka and arrived at London Heathrow Airport in 2011. I've now been in the UK for around 15 years. My family came to the UK after fleeing the Sri Lankan Civil War, specifically during its final stages. Like many others, we were looking for safety and the opportunity to build a new life. Looking back, it was a life-changing journey that shaped who I am today.

Sri Lankan Civil War / Life in Sri Lanka¶

I spent most of my childhood in Sri Lanka running into bunkers, hearing bombs drop, collecting shrapnel, and getting up to other interesting things that I won't share here, as that could be a separate post in itself.

I wasn't really in school until I came to the UK around Year 5 or 6, so when I was about 9 or 10 years old. The war disrupted education for many of us, and even when I did attend school in Sri Lanka, we would often end up being sent into bunkers anyway.

Not truly being in school was quite fun I think. To be honest, I wouldn't know any different, as we were never formally educated for much of that period.

Getting visas to come to the UK was a long process. Literally long, as the queues and waiting times were endless, and long from a paperwork perspective too. Thankfully, through a combination of hope, faith, and a bit of luck, we eventually got our visas after spending a year or two in another part of Sri Lanka where my people were not always particularly welcome at the time. There was a significant divide back then, and to some extent, there still is today.

Those years before coming to the UK were eye-opening. I had grown up in a heavily segregated environment where schools were often divided by language, ethnicity, and religion.

I ended up attending a Christian (or possibly Catholic) Tamil boys' school, I honestly can't remember which now. They were quite open to accepting anyone, provided you spoke Tamil. It was a strict school, and it taught me a lot of discipline, although the punishments could be brutal 🙃.

I spent my final years there before moving to the UK in 2011.

Coming to the UK¶

Coming to the UK was a privilege, and in many ways it was similar to how it was portrayed in some of the films I had watched in Sri Lanka. Back then, the military had significant control over what you could watch, and if you were caught with certain films, the consequences could be quite harsh.

The UK felt like a completely different world. The roads weren't bombed to pieces. There were no bombs dropping from the sky. Everywhere seemed clean compared to what I was used to. There was no shrapnel to collect, no soldiers carrying AK-47s, and people seemed to be living in peace. Most importantly, people seemed happy.

Then there was the whole debacle of living in Croydon, which was a life-changing experience in itself.

From the day we arrived in the UK, the one thing my parents, especially my mum, drilled into my head was the importance of education. If I didn't get 100%, I was apparently a failure.

Looking back, I think she was terrified that I might end up going down the wrong path. In her mind, that meant getting involved in gangs, selling drugs, getting kicked out of school, or ending up in prison.

I was a rebel, and to some extent, I still am. The difference is that I chose to go my own way in a positive sense.

I suppose I didn't quite fulfil my mum's dream of becoming a doctor or a lawyer 😆. To this day, she doesn't think typing away on a computer all day counts as a real job, so there's that.

That said, I don't think she worries about me anymore. I must be doing something right.

Skipping to the Nice Parts¶

Now, skipping past the wars, coming to the UK, life in Croydon (which was heaven for me compared to a war zone, regardless of what people think of Croydon, it's really not that bad, people; don't believe everything you see in the news), adapting to the culture, and integrating into the western world...

Let's skip ahead to how I ended up in the world of coding and software engineering, the very reason you're on this website.

Pilot¶

I always wanted to become a pilot and fly planes. Growing up in Sri Lanka, I was getting bombed by fighter jets, and seeing one in the sky was a big deal. The same went for drones.

As kids, we would sneak out to nearby military bases. Many of them were positioned in large open fields, making it possible to spot drones and, occasionally, fighter jets. Our parents hated this. Whenever we heard the sound of aircraft, we were supposed to be running into bunkers, not trying to get a better view of them.

I became fascinated with fighter jets and always dreamed of flying one myself. If I had told my parents that back then, they probably would have locked me in a bunker (there were different types, open and closed bunkers 😅). The irony was that those same fighter jets had caused immense suffering within our community.

My mum nearly died because of one. A bunker-buster bomb landed at her workplace. Thankfully, it failed to detonate, but it still collapsed the bunker she was sheltering in. The workers had to be dug out afterwards.

Becoming a pilot was an expensive career path in the UK back then and, for the most part, it still is today, although there are now some fully funded commercial airline pilot programmes available.

When I was in secondary school, however, you largely had to fund it yourself. Neither my family nor I had £100,000 lying around. Many aspiring pilots ended up remortgaging their homes or taking out significant loans to pay for flight training.

My parents are successful in business and are financially comfortable now. They could probably fund whatever my little brother wants to do with his life (assuming he can eventually get off TikTok for five minutes), but that simply wasn't an option for me back then.

So I switched my focus to the next area that had always fascinated me: technology.

The house we lived in while I was growing up in Sri Lanka didn't even have electricity. We fetched water from a well, our neighbour's cow provided milk, much of our food came from local farms, and we grew some of our own fruit and vegetables.

We rarely went into the city because it wasn't particularly safe. Technology wasn't really part of everyday life where we lived. The wealthier households had electricity, a television, and perhaps a landline telephone. For everyone else, life was much simpler.

Poking Around With Computers Like a Caveman Discovering Fire¶

It all started in primary school in the UK, where I got used to using computers, both laptops and desktops.
Google Translate was incredibly useful back then because I didn't know any English.
I learnt most of my English with the help of other kids at school who spoke Tamil and various other languages.
At first, I wasn't particularly fascinated by computers. I was far more excited about watching cartoons on TV, which was amazing considering we didn't even have a television in our house in Sri Lanka because we had no electricity. I did manage to watch some cartoons at our wealthy neighbour's house though, as they were quite fond of me.
At some point in Year 6, my class was taken to Whitgift School, a rather fancy private school with its own zoo and everything. We learnt Scratch there and built little games as a class. Looking back, there were only a handful of us who were genuinely excited about doing some form of programming, if you can even call it that, and I was definitely one of them.
What really got me excited wasn't Scratch itself. It was seeing one of the teachers remotely controlling all the computers in the classroom. You could see the mouse moving on its own, applications opening, windows changing, and all sorts of things happening across the machines. It completely blew my mind. Looking back, that's probably what sparked my interest in technology and computers more than building games in Scratch ever did.

How the Computer Science & Coding Journey Started¶

The pilot dream was shattered, so I put it in my backlog. I'm alive and well, and there are plenty of other things I can do in this great country.
Secondary school was a struggle, which could easily be another blog post or an entire book in itself. I'll spare you the details for now.

GCSEs¶

I picked Computer Science for my GCSEs, thanks largely to the influence of someone who is now one of my closest friends.
He's also a software engineer who is doing really well in his career. He loves Next.js and Vercel 50% of the time and hates them the other 50%, yet he'll never move away from them. He's also the sort of opinionated developer who hates everything and constantly threatens to build his own version of whatever he dislikes...
I think that's when I first truly came across Vercel. He recommended that I follow the Next.js documentation because, according to him, it was the best documentation he had ever seen. Given that he hates and nitpicks absolutely everything, him genuinely liking something was a strong endorsement. To be fair, the Vercel and Next.js documentation is undeniably excellent. Stripe might take second place on that list.
Fast forward a few years and I came away with some decent GCSE grades.
I was coding in Python and building all sorts of command-line applications, from ATM simulators to whatever random idea I found interesting at the time.
I loved learning from Tech With Tim and Corey Schafer. I probably owe many of my early opportunities in technology to them.

A-Levels¶

I picked Computer Science at A-Level.
I was still coding in Python and started experimenting with Tkinter, Kivy, Selenium, and a few other technologies.
I also tried to learn Django and failed catastrophically. I was trying to learn to fly before I could even walk... That experience destroyed my confidence so badly that I started telling my friends I was going to become a marine biologist instead 🤣. The only thing I knew about marine biology at the time was that they studied fish or something. Yes, I was in a very low place after Django defeated me.
Looking back, it's quite funny. These days I specialise in the Python ecosystem, particularly Python, Flask, Django, and Wagtail. I've spent enough time with them now that I'd comfortably consider myself an expert.
A-Levels during COVID were interesting. It wasn't too bad for me because I was incredibly introverted during my secondary school years, so staying indoors wasn't exactly a challenge. That said, my eyesight definitely got worse.

University of Portsmouth (Yes, It's Not Cambridge, Oxford, Stanford, or Harvard)¶

If you're looking for a Cambridge, Oxford, Stanford, Harvard, or MIT graduate, that's not me. To be honest, I don't think my way of working, mentality, or attitude would have been the right fit for those universities. They work for some people; they probably wouldn't have worked for me.
My only connection to those highly regarded universities is that I've interviewed and reviewed applications from graduates of Cambridge, Oxford, and other prestigious institutions while hiring for software engineering roles. Some applications were fantastic, while others looked almost identical, lacking evidence of passion, curiosity, side projects, or genuine effort. The strongest candidates I've seen came from all sorts of backgrounds, top universities, other universities, and some who never went to university at all. The people we hired have gone on to do exceptionally well.
One thing I really like about software engineering is that, for the most part, the barriers to entry are relatively low. If you're willing to learn, build things, and put in the effort, there are opportunities available.
I chose the Software Engineering course at the University of Portsmouth rather than Computer Science. The Software Engineering course had less theory, more hands on projects, and modules focused on JavaScript and web development, which I desperately wanted to learn after being defeated by Django.
I spent a lot of time working with JavaScript, HTML, CSS, and a bit of Express.js. It was mostly vanilla web development, which gave me a solid understanding of how things actually worked under the hood. Looking back, that depth helped me later when working with larger frameworks.
For the first time, I genuinely enjoyed education. The Software Engineering course was highly practical, which suited me perfectly. Building projects and being assessed on them felt far more rewarding than traditional exams. University was a breath of fresh air after school.
Because I was constantly going above and beyond the course requirements, I found much of the university content relatively straightforward. I spent most of my time coding, building projects, experimenting with new technologies, and generally having fun.
And yes, I finally learnt Django and defeated the Django demon. Thanks, Corey Schafer.

Work Experience During University¶

I secured an internship at JPMorgan Chase & Co. To say I learnt a lot there would be an understatement. Around that time, opportunities seemed to be appearing everywhere.
Alongside that, I worked part-time in various roles for the university, including marketing, campaigns, student engagement, and a variety of other odd jobs.
In many ways, those work experiences developed me more than the university course itself, because I was slowly breaking out of my introverted shell. When you're giving talks, leading campus tours, answering questions from prospective students and parents, keeping groups of 15-20 people engaged, making jokes, and doing it all dozens of times a day, it can be exhausting as an introvert. Over time, though, you learn how to manage the situation mentally and become more comfortable in your own skin.
I deliberately kept taking on jobs that required me to be out in public and interacting with people. I wanted to overcome my anxieties and fears around speaking to strangers and putting myself out there.
For a period, I worked in a sales-focused role at the university. Had I been a permanent member of staff, the bonus I generated on one particular day would have exceeded two weeks' worth of salary. At that point, I was getting very close to defeating my anxious self.
Surprisingly, I started to love sales as my confidence grew. I wasn't doing it for the money; I was doing it for the experience. By then, I was already working as a junior software engineer and earning a decent salary. I actually took annual leave from my engineering job so I could continue doing the sales role because I enjoyed it that much.
Most of the time, I was selling graduation-related items and clothing. We each had a sales counter tracking our performance, and I regularly ended up near the top of the leaderboard.
My fastest and biggest sale happened within about five seconds of meeting a customer. I sold over £500 worth of items almost instantly, and by pure coincidence, my manager, had taught me most of what I knew about sales, was standing right there watching. He was completely shocked. By that point, I had a carefully refined script running in my head. I was so practised that I almost felt like a robot. I wasn't even being myself anymore; I was operating in some strange trance-like flow state.
Looking back, these seemingly unrelated odd jobs helped build my confidence more than anything else. They shaped me into a person I never thought I could become. As valuable as my internship at JPMorgan and my role at the ONS have been, I don't think either would have given me that same personal growth. I genuinely don't think I'd be where I am today without those experiences.

Internships & Industrial Placements¶

If you're interested in the details, have a look at my home page and scroll through my experience section.
During university, I received three industrial placement offers: one from the Office for National Statistics (ONS), Civil Service, and two from startups.
At the time, the ONS offered the lowest salary at around £22-23k. These days, placement students and interns can earn around £27-30k at the ONS, which is pretty competitive.
One of the startups offered around £24k.
Another startup reached out to me directly. They didn't normally take placement students, but they liked my LinkedIn profile and, more importantly, my Django projects. They offered mentorship and a salary of up to £55k, which was a huge amount of money to me at the time, and still is to many people today.
In the end, I received offers from both the ONS and the startup offering £55k. The startup was incredibly tempting.
Despite that, I chose the lowest paying role and signed with the ONS. After doing my research and speaking to people who worked there, I felt it would give me the best opportunity to grow as an engineer. Looking back, it was one of the best career decisions I've ever made.
I know people who accepted offers from some of the other companies I was considering, and many of them have gone on to have successful careers too. However, for me personally, choosing growth over salary at that stage of my career paid off enormously.
Money isn't everything, especially when you're early in your career and have the opportunity to trade short term earnings for long-term growth, learning, and experience.

Graduation (I Didn't Go to It)¶

I decided not to attend my graduation ceremony. At the time, I saw it as a waste of time. By then, I was constantly working, learning, and building things. There were periods where I'd spend days coding, experimenting with neural networks, and generally being obsessed with technology, sometimes 2-3 days without no sleep (was working on a project related to ML/ NN).
Instead, during graduation week, I worked on running the graduation events. It was paid work, but like many of the jobs I took during university, I did it more for the experience than the money. I was still focused on evolving beyond my introverted personality.
Having worked behind the scenes from start to finish, I wasn't particularly fond of the heat, the long days, or the overall process. And yes, I know I'm from Sri Lanka, but 40°C in Sri Lanka feels better than 30°C in the UK with humidity.
Rather than attending my own graduation, I spent that time running a successful community session at work for more than 60 engineers. It was either a JavaScript or Python session, I genuinely can't remember now, as I ran quite a few of both. We covered frameworks, industry trends, template repositories, and other topics. Looking back, those community sessions became an important part of my career development.
I'm not against celebrating achievements or attending your well earned graduation. It just wasn't really my thing, and I had other priorities that week.
What I did enjoy was seeing the excitement on the faces of students and their families. Helping people collect their graduation attire, showing them how to wear it properly, guiding them through the event, and helping reduce some of their anxiety was genuinely rewarding.
The amount of work that goes on behind the scenes to run an event of that scale was also an incredible learning experience. We were often starting work at 7 a.m., five days a week throughout the graduation period.
Me attending a graduation ceremony like that? BIG NO.
Me helping run the graduation ceremony and making sure everyone else had one of the best days of their lives? HUGE YES.

My Career Trajectory So Far¶

If you'd like more detail, have a look at my CV or scroll through the home page.
Since joining the ONS, I've tried to take every opportunity available to me.
My career progression has been relatively rapid, which came with its own challenges. The progression framework wasn't really designed for someone moving through it at the pace I was.
It didn't start with big projects or leadership opportunities. It started the same way it does for most engineers: picking up tickets, writing code, asking lots of questions, and dealing with imposter syndrome.
While my technical skills grew significantly, I don't think technical ability alone explains my progression. What helped most were the non-technical skills, saying yes to opportunities, volunteering for things outside my comfort zone, and getting involved wherever I could.
Where there is stress, there is growth and evolution.
You don't grow in comfort.
You either get worse or get better; you don't stay the same.
Many of the people who taught and mentored me early in my career were incredibly supportive. They often commented on the level of drive and curiosity I brought to my work. While they hadn't seen many people approach things the way I did, I've since met and worked alongside plenty of highly motivated individuals who inspire me just as much.
People often asked me where my motivation came from. My answer was always the same: "You have to do your best work when you're the least motivated."
My flexi-hours balance ballooned. My annual leave entitlement effectively grew from around 25 days to over 65 days because I was apparently working too much. Personally, I didn't see it that way. I was learning, growing, and evolving. I was genuinely happy.
This was also where all those seemingly unrelated odd jobs started to pay dividends.
Within a few months, I was building proof-of-concepts, taking initiative, creating technical and non-technical presentations, pitching ideas to stakeholders, securing buy-in, and helping turn ideas into production systems. At the same time, I was mentoring my first placement student while still being a placement student myself.
I spent a huge amount of time public speaking, delivering presentations, contributing to innovation initiatives, volunteering for projects outside my day job, and working with various communities, steering groups, and working groups across the organisation.
I was invited to contribute to the Technical Advisory Group (TAG), the Software Engineering Community of Practice (CoP), and later helped found the Community Tech Exchange initiative through the Innovation Team.
I was often the youngest person in those meetings, which was slightly terrifying considering many of the engineers around the table had decades of experience and held roles such as Technical Lead, Principal Engineer, or Architect.
For more information, have a look at the Beyond the Code section on my home page.
One of the highlights of my career so far was presenting to Alison Pritchard, Deputy National Statistician at the ONS. It was incredibly nerve-racking, but all those years of public speaking, sales work, presentations, and community involvement led up to moments like that.
None of this would have been possible without the mentors, teams, friends, and support networks that helped me along the way.
At the end of the day, good people, strong networks, and genuine friendships are what take you far in life.
Within the Software Engineering community at the ONS, I became one of the fastest-progressing engineers in the organisation. Ironically, the second fastest is my tech lead. Naturally, that means my next goal is to beat his record too.
Today, I'm a Senior Software Engineer operating at a lead-engineer level in many areas of my work, soon to progress to the next level once again (again there are challenges are the progression framework isn't designed for a person like me, but the org looks after me well by now). As I write this blog post, my tech lead is off for a few weeks using some of the mountain of leave he's accumulated, while I'm stepping into the technical lead role temporarily. We can't both be off at the same time.

What Am I Doing With My Life Now?¶

Chasing dreams, finding opportunities, and seeking experiences that help me grow whether that's in my career, mentally, physically, or spiritually.
This means reading all kinds of books, from spirituality and business to self-improvement and strategy. It also means spending time in nature, meditating, travelling, and learning new skills whenever I get the chance.
Remember when I said I wanted to be a pilot? I've started taking the early steps towards making that happen. Not because I want to become a commercial airline pilot, but because I'd love to earn my pilot's licence and fly for the sheer enjoyment of it and take friends along for the ride.
I'm a competitive recurve archer, currently being coached by one of the finest coaches in the UK, whose own coach was an Olympian.
After an assessment and consultation, he agreed to take me on as a student, which was a huge honour. I shoot an Olympic recurve bow, and I've recently started competing.
My goal is to shoot two to three times per week, alongside a coached session and regular competitions. Archery is one of the most complicated, stressful, frustrating, and rewarding things I've ever done. Recurve archery, especially at a competitive level, is largely a battle of mental management. Ironically, I hated archery when I first started, which is exactly why I stuck with it. That's where growth happens. There is no growth without discomfort.
I have serious goals within archery and hope to compete at a national level one day. We'll see how that journey unfolds.
Thankfully, my coach thinks I'm on the right track.
I'm also naturally quite good at running, so I figured I might as well start entering races. It still isn't fun, though. Running still sucks.
You can find my upcoming races at the bottom of my home page.
I love go-karting, and a while ago I completed a Formula car experience at Silverstone. My next step will probably be outdoor karting at around 70 mph. After driving a Formula car around Silverstone, though, 70 mph somehow feels a lot less intimidating. I may do a few more simulator sessions before heading back to Silverstone again.
Photography is another hobby I've been exploring recently. I picked up a film camera and have been having a lot of fun with it. Once I've had my latest rolls developed, I'll start uploading some of the photos to the photography section of this website assuming I actually get around to enabling that page.

Why a Static Site?¶

I decided to build this personal website as a static site. See my article on SSG, SSR, CSR, and ISR if you'd like a deeper dive into those concepts (I mostly wrote that article to re-learn them myself).

I've always preferred starting projects with the most vanilla, bare-bones solution possible and then evolving them over time.

Even now, I can already see valid use cases for introducing technologies such as Next.js, Vercel, and other modern tooling. With v0, Tailwind CSS, and a headless CMS such as Contentful, which I've previously integrated into a production Python Flask application, I could migrate this website fairly quickly if I wanted to.

As the website grows and the requirements become more complex, I expect the tech stack to evolve with it.

The funny thing is that I already know many of the functional and non-functional requirements I'd eventually want to support. However, I genuinely enjoy building things in the simplest possible way first and then upgrading them later. It makes you appreciate the benefits and trade-offs of those upgrades much more.

The same applies to technologies such as Contentful, Next.js, and other frameworks. If you've never built something without them, it's difficult to fully appreciate what they're solving.

One thing I've noticed throughout my career is that many people jump straight into large frameworks and complex architectures without first understanding the fundamentals. In my opinion, that often comes at the expense of depth. Building things from scratch, or at least in a more vanilla way, forces you to understand how everything fits together underneath the abstractions.

That's one of the reasons I often build the same type of project multiple times using different technologies. For example, I've built blog applications in both Flask and Django (see my GitHub repositories) simply to understand the differences properly rather than relying on assumptions.

In many ways, this personal website is another experiment in that philosophy.

Special Shout Out To [NAME CLASSIFIED FOR NOW]¶

This person asked me a simple question, and it ignited something in me that resulted in deploying this website to both Netlify and Vercel at the same time.
The question was something along the lines of: "I wonder what this would look like deployed on Vercel?"
My response was simple: "Only one way to find out."
While I was experimenting, I ended up fully building out the website, replacing all the placeholder content, and turning it into something real.
It's a good reminder that you need people around you who ask interesting questions, challenge your assumptions, and spark your curiosity.
Yes, this website was auto-deploying to both Netlify and Vercel simultaneously 😅. I wanted to see how the platforms differed in practice rather than relying on marketing material or opinions from the internet.
After spending time with both platforms, I found myself gravitating heavily towards Vercel's ecosystem, developer experience, tooling, and overall product vision.
Over the past year, I've spent a lot of time researching Vercel and, naturally, that meant researching many of its competitors too.
I could probably write an entire blog post comparing Vercel, Netlify, Railway, Render, Fly.io and other modern deployment platforms, explaining why each exists and where they shine. Maybe I will one day.
In the end, I shut down the Netlify deployment and moved to a paid Vercel account.
I also have plans to build a CRM and CMS-powered platform for multiple archery clubs, and at the moment Vercel, Next.js, v0, and the surrounding ecosystem are very high on my list of technologies to use.
Whether you like Vercel, dislike Vercel, or have never used it, I think most developers would agree on one thing: they care deeply about developer experience.
The documentation is excellent, the onboarding experience is polished, and the platform generally stays out of your way so you can focus on building things.
Coming from a very opinionated Python ecosystem, I don't say that lightly. My contractor friend with the love-hate relationship with Vercel was right: the documentation really is that good.

This Website's Tech Stack¶

Python, Pelican, HTML, CSS, Jinja2, Tailwind CSS, Astral tooling (uv, Ruff, etc.), and Vercel.

Tech Stack as This Website Evolves¶

Vercel products, Next.js, Contentful, and whatever else makes sense as the requirements evolve.

What's My Plan for This Site?¶

I want to write a lot more technical blog posts, particularly around Python, Django, and Wagtail.
I've had the privilege of learning from some of the best Django and Wagtail engineers in the world at Torchbox (TBX), and over the years I've developed a fairly deep understanding of these frameworks and their internals.
I've also started getting more involved in the Wagtail open-source community.
I want to share my experiences with JavaScript, React, and some of the technologies I'm currently learning and experimenting with, such as Next.js and the Vercel ecosystem.
Beyond software engineering, I want to use this website to document my journey and achievements. There will be dedicated sections covering archery, photography, racing and go-karting, running, and whatever other adventures I end up getting myself into.
I already have designs and code prepared for many of these sections. They'll be enabled and made public gradually as the site evolves.

If you'd like to follow along, there's an Atom feed - no newsletter, no tracking, no marketing emails, just good old RSS.

Follow Me On¶

Back to All Posts