This post covers the latest week (November 22–28).

I didn’t write a post last week, because I didn’t have anything to say. Here are some things I could write about:

  1. Feedback I’ve received from the cofounders of the startup I’m developing for.
  2. Ways I can make my code better, and an exploration of what ‘better’ means.
  3. Checklist of best practices/little things I forget to do.
  4. Collection of resources I’ve consulted as I develop.
  5. Sources of friction in learning/working.
  6. I’m working in a distributed team. Evaluation of pros vs cons of distributed teams; my own take on how it’s working out…

I’ve been writing about my experience learning fullstack software development — my goal is to be good enough to land a SWE internship next summer.

This post covers the latest week (Nov. 8 ~ 14).

What’s worked well:

  • Communication: I keep thinking good work is about work. That’s half the battle. Clear, honest communication counts.
  • Balance: I’ve tried to strike a balance between thinking and doing. When I’ve stuck to that, it’s proved valuable.

What’s gone poorly:

  • Input volume: I’d hoped to spend 20 hours a week on this. My current high is 15.
  • Rashness: Thinking before doing is a constant struggle. One that pays huge dividends.

What I’ve built:

This repo contains my (almost-) latest work. I can share more when we start to put the frontend I’m building into production.

Older work on GitHub: https://github.com/anirudhkannan9


For the past ~2 months I’ve been writing about my experience learning fullstack software development — my goal is to be good enough to land a SWE internship next summer.

This post covers the latest week (Nov. 1 ~ 7).

Biggest learnings:

  • Importance of routine. A good routine can inoculate your plan against the bumps on life’s road. A lack of one can mean you stumble about blindly.
  • Make contact. I started this with the goal of landing a SWE internship next summer. I’m pretty much there today — half a year ahead of schedule. This is because I didn’t…

For the past eight weeks I’ve been writing about my experience learning fullstack software development — my goal is to be good enough to land a SWE internship next summer.

This post covers the latest week (Oct. 25 ~ 31).

What went well:

  • Learning in public, pt. 2: As a result of my publicising my efforts (in this case, via my network, not necessarily online), I was asked to build out the frontend for a startup that a couple friends are running. I said yes, and despite being out of my depth, I’m sanguine.
  • Thoughtfulness: I strongly believe that there…

For the past seven weeks I’ve been writing about my experience learning fullstack software development — my goal is to be good enough to land a SWE internship next summer.

This post covers the latest week (Oct. 18 ~ 24).

What went well:

  • Learning in public: If you’re on Twitter, you’re probably aware of the “Learning/building in public” trend. One great example is Mckay Wrigley. I do this too: I write weekly blog posts, and tell people in my network about what I’m working on. This habit might just have led to something great. I’m on the precipice. Stay tuned.


For the past six weeks I’ve been writing about my experience learning fullstack software development — my goal is to be good enough to land a SWE internship next summer.

This post covers the latest of those weeks (11/10 ~ 17/10).

What went well:

  • GitHub habits: I adopted a slightly new approach on GitHub, wherein I maintain the branches that represent my commits for each exercise. It’s a trivial change with marginal benefit, but it takes no effort. I now have a catalogue of my progress, detailing (roughly) how long each exercise took and giving me more granular data regarding…

For the past six weeks I’ve been writing about my experience learning fullstack software development — my goal is to be good enough to land a SWE internship next summer.

This post covers the latest of those weeks (4/10 ~ 10/10).

What’s gone well:

  • Routinizing: I’ve established a regular sleep schedule. This means I have a routine in which I spend the first couple of hours each day to working on this. I went from 6 hours spent on software last week to 13 hours this week. …

For the past five weeks I’ve been writing about my experience learning fullstack software development.

This is a retrospective covering my first full month working on this.

Biggest learning:

So far my biggest learning has had as much to do with how to learn as it does with the actual skills I’ve built.

My biggest bugbear over the past month has been simply finding the time to devote to this. I hadn’t anticipated that it’d be this hard; sure, school’s challenging, but I thought that I’d have established a regular routine by this point. …


The past week has been Week 3 of my learning experiment in which I attempt to teach myself web development, with the goal of being good enough to get a SWE internship next summer.

What’s gone well:

  • Tracking: It’s been a slow week as far as progress is concerned. But I wouldn’t even know that if I weren’t tracking. I have a separate slot in the Google Sheet I use to track my time dedicated to recording time spent on this project. Helps keep it top of mind.

What’s gone poorly:

  • Time: Old bugbear. Managing school and this has proven…

The past week has been Week 3 of my learning experiment in which I attempt to teach myself web development, with the goal of being good enough to get a SWE internship next summer.

What’s gone well:

Besides stuff mentioned previously:

  • Tracking: time, focus, energy. Tracking these things gives me a high-level metric that accounts for everything on the input side. It keeps me focussed on continually improving what I can improve.
  • Writing (pen & paper): Before each coding task, I write down the steps on a piece of paper. When debugging, I’ll speculate as to roots of the problem…

Anirudh Kannan

Student @ UBC (Vancouver, BC).

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store