For me? Easy — I probably failed because of a lack of focus, too much time wasted on the internet, and it’s likely my planning sucked.

To make sure I don’t make those mistakes, I want to crystallize 3 things for myself:

1. What I will focus on in 2023
2. Some concrete goals
3. Day-to-day changes I want to make

Areas of Focus

I like having narrow fields of focus — if you’re focused on too many things, are you focused on anything at all?

Here are my 3 areas of focus for 2023:

🏋🏻‍♀️ Health

My health is okay, but historically, I have never thrown myself fully into improving it proactively. This year, I want to err on the side of being overly obsessed with how I feel and how much effort I put into my health.

🧑🏻‍💻 Career

The only carry-forward area from last year — I like working on my career as if it was just another side-project. I’m fortunate enough to have a job which gives me a generous amount of autonomy, and this year, the aim is to ensure I make the most of the opportunities I get.

After all, if I don’t do it, it won’t happen.

✍🏻 Writing

In 2022, I largely ignored my role as a content producer for this website. There was one (ONE!) new blog post, and a poorly maintained tech blog that saw no activity after one (ONE!) very fun to write post. In 2023, writing takes a front seat. I love it, and it teaches me a lot. More content on the website!

Concrete goals

No ‘planning for the next year’ post is complete without a set of some concrete goals. Here are (some of) mine:

🥅 India trip:

COVID and visa complications meant I haven’t visited India since 2019. This year, we go!

🥅 Driver’s license:

I do not have a driver’s license, but I’m working on it! I now have a permit and have begun practicing. The goal is to give my behind-the-wheel test sometime in Q2, and finally get this weight off my back.

🥅 50 total pieces of content:

Given that Frndship Time makes >30 pieces of content every year, if I am able to push out 20 posts on the website this year, this seems like a reasonable goal. 50 is a nice round number, and it’d be a nice milestone.

What do I change day-to-day?

All this big picture thinking is great, but I want to make sure it isn’t just words.

I need to change some parts of how I operate day-to-day to make sure I follow through on my intentions.

Here’s a list of changes that will have the biggest impact on my wellbeing next year:

1. No more infinity pools: “I want my attention back,” and I spent far too much of 2022 wasting away on the internet. For next year, I want to step away entirely from websites that end up offering bite-sized content with no end in sight. This leads me to the next change…
2. Consume more longform content: podcasts, long articles, audiobooks, books, and good TV shows are so much more enjoyable than a series of YouTube videos. They’re better thought out, are long enough that I need to be intentional about having them in my schedule, and much more rewarding.
3. More diligent planning: I’m not a good planner. Inaccurate estimations of how much I can do, and not spending enough time deciding how I’m going to complete long and complex projects really holds me back. I’m actively thinking about this and planning my months, weeks, and days better this year. A big shoutout to Things, Day One, and Linear — apps that make my life much more manageable.
4. Do more of what I enjoy: Leaving behind all the infinity pools frees up a lot of time, and I want to spend it doing things I actually enjoy. Gaming, sports, writing, cooking, more social events — everything is fair game.
5. Explore: This is different from the rest. For the last year, I’ve had my nose close to the ground and not tried to explore other things that I might enjoy. For 2022, this was a great decision, but I know there is more out there — I don’t know how I will do this in 2023, but I like having it on the front of my mind.

And that’s it! Onto 2023 — and here’s a question for you:

It’s one year from now. December 2023. The goals and habits you were hoping to achieve and build during the year didn’t happen. What is the most likely reason you failed?

This year was incredible in many ways, and disappointing in others. I learned more about myself and travelled more than I ever did before. Personally, there was a lot of progress, yet a lot left on the table.

The sheer volume of things I want to do is so high — and I’m learning to let that be exciting rather than disappointing.

Recap

Month-by-month highlights featuring what I did, where I went, and memorable moments.

January 🏠

• Moved into my new apartment
• Saw Hasan Minhaj in Sacramento

February 🎙🍷

• Launched Frndship Time Season 2
• Went wine tasting in Napa
• Went to Joshua Tree

March 🎸

• Saw John Mayer!

April ☕️

• Got my espresso machine. I love coffee!
• Saw Tom Segura live!
• Apple Pay-ed at a wishing fountain
• Got a Stream Deck

May 🏌️‍♂️

• Top Golf + good coffee!
• Got a Nintendo Switch, played Mario Odyssey

June ☀️

• San Diego summer trip

July ⚾️

• Finished playing Hollow Knight
• Saw my first ever baseball game

August 💼

• First ever business trip - spent 2 weeks in Boston

September 🏙

• Week-long Chicago trip
• Visited the biggest Starbucks Reserve in the world
• Built my custom keyboard

October 🏔 🪔 👻

• Parents visited from India
• Went to Yosemite and Tahoe
• Grilled all the food for a big party
• Diwali!
• Halloween parties

November

• Went to a candlelight Taylor Swift string concert
• Finished Hades
• Friendsgiving
• Wrapped up Season 2 of Frndship Time

December

• Trip to LA
• Happy birthday Parth!
• WORLD CUP 2022!
• Christmas celebrations
• Got my driving permit
• Friends visited SF

Reflections

For each ‘role’ in my life, what was the plan for the year? What actually happened? What went right and what went wrong?

Podcast Cohost 🎙

What was the plan?

• Do better episodes, focus on community, make weekly episodes

What happened?

• Made weekly episodes.
• They were higher quality, but could have been even more had I put in more effort.
• Laziness held me back from really having a smash hit S2.
• Nevertheless, had a good S2!

What went right?

• Weekly episodes, higher quality in general
• Still just as fun, not a chore

What went wrong?

• Did not foresee how much work high-production episodes and guest eps can be, I was not committed enough to see them all the way through.
• For some reason expected the entire year to be uniformly busy. This was not the case, some months were much busier, so we should have gathered our rosebuds while we could.

Ratik and I talked about our year in podcasting on the season’s finale.

Health 🏃🏻‍♂️

What was the plan?

Stronger habits, consistent eating well and physique improvements

What happened?

Very on-off in the gym. Not great with nutrition. When things were good they were good, but big issues getting back in the habit after taking a break.

What went right?

• When things were consistent, everything felt good
• Learnt that mornings are great for workouts with my schedule
• Started stretching routines mid-year and got in some stretching everyday consistently

What went wrong?

• Not getting back to the gym after breaks.
• Not tracking meals, weight, lacking consistency.
• Nutrition was the toughest, would succumb to laziness and skip meals/eat out whenever I wasn’t prepped enough

Website ✍🏻

What was the plan?

• Write blog posts consistently
• Play with paywalls, memberships, etc.

What happened?

• Upgraded to new website design
• Wrote 0 (ZERO!) personal blog posts
• Started a Technical Blog. Wrote once and enjoyed it.
• Realized personal blog is more of a ‘fun’ project where I do not want to chase a ‘target number’ for posts. I still do enjoy it and want to do it.
• Realized I’m not obsessed enough with writing posts even though I enjoy it, mainly because all my time gets sipped up by other things (I watch too much YouTube, and would like my attention back)

What went right?

• Spending the time and effort required to porting into a new website
• Tech blog kick off
• Public Journal format and posts

What went wrong?

• Great plans for Tech Blog were not followed through
• Tech blog works closely and has big effect on career learning. Not doing it is bad - didn’t do it because sinking time into YouTube

Finances 💸

What was the plan?

• Increase income from main source of income
• Know your expenditure power - exact budget and planned expenditures
• Grow the money you already have
• More income sources

What happened?

• Did increase income
• Set up recurring investments
• Got a credit card and started building credit
• Got Mint, Copilot, set up budgets, did not monitor or follow
• Did not look into expanding portfolio - just ‘set it and forgot it’. Just did some really laid back saving
• Realized there is much to learn. It is an ongoing process, and I need to stop thinking of person finance as a project that can be finished or solved. The nature of this work is ongoing.

What went right?

• Setting up first steps (credit card, recurring investments, Copilot for budgeting)

What went wrong?

• Treated things like a project, not as simply doing this because it’s good for me
• Did not follow through after the bare minimum
• Lack of effort. No plans/brainstorming/any effort towards additional income streams

Relationships ❣️

What was the plan?

No goals, but wanted to be better about keeping in touch. Show more appreciation to the people I love.

What happened?

• I wasn’t great about this throughout the year, but coming towards the end, I put in a lot more effort into calling old friends regularly and checking up on other friends
• I feel good about this towards the end of the year
• Even if I wasn’t thrilled in the beginning, the end is really promising and something I want to carry forward into next year

What went right?

• Having constant reminders to talk to people, reaching out over text and recurring phone call reminders

Miscellaneous thoughts

What worked day-to-day

Being in SF 🌆

I loved being in a city where I could go outdoors, explore food and activities, and meet interesting people. There is a lot to do here on any given weekend, and the weather makes it possible to do it throughout the year.

Having a ‘year theme’ 🥳

In 2021, I realized I was doing too much, and none of it particularly well. For 2022, I decided to narrow down my focus. Podcasting, career thinking, friends and relationships would be front-of-mind, and the website, music, etc would be on the back seat. The desired effect did happen - I poured in a lot of work into the podcast and my career, and at the end of the year I feel much more satisfied with how those went as compared to everything I (willingly) neglected.

Day theming 📅

Deciding in advance what ‘part of my life’ I would be spending the free time of my days on was brilliant. There is less need of planning, and everything important gets attention through the week.

Pouring time into friends 👯‍♀️

I was more ‘present focused’ this year. Given the choice between a night with friends or working on my side projects, I always chose the social event. Looking back, I am glad I did this - I now have a circle of friends in the city with whom to do things, and with whom to learn and grow.

What was bad day-to-day

YouTube & Procrastination 📺

I watch a LOT of YouTube and procrastinate on Reddit more than I’d like to admit. It’s… a problem.

From watching meaningless content and procrastinating to taking away time from the things I really want to do, this habit is the #1 culprit behind all the potential I left on the table in 2022.

Lack of Effort 💤

There is so much I want to do. The possibilities are endless, and if I wanted, I could fill up my entire life with meaningful things that I want to do. Alas, I’m lazy and procrastinate too much. This meant not enough effort went into doing important things.

Closing Thoughts

In 2022, there was forward progress, but so much left on the table. This is because of no other reason except procrastination.

As for trips and ‘living in the present’, this year was incredible. 5-6 trips, lots of parties, events, and on a social level, one of the best years of my life.

There is so much I want to do and the possibility of so much that excites me. There is no way I can incorporate all of it into my life, but the good feeling is that I can never run out of things I want to do.

Onto 2023!

What is refactoring?

Refactoring is a process of improving the readability, modifiability and ease of debug of existing code. It is not about adding new functionality. Refactoring transforms a mess into clean code and simple design.

Here are some of the basic categories of refactoring techniques:

Quick summary of each category

Method composition:

Much of refactoring is dedicated to how we write methods. In most cases, “excessively long functions are the root of evil”. All techniques in this category aim to streamline methods, improve readability, remove duplication, and increase ease of future modifications.

Favorite techniques:

1. Extract method
   • The more lines found in a method, the harder it’s to figure out what the method does. This is the main reason for this refactoring.
   • Besides eliminating rough edges in your code, extracting methods is also a step in more readable code. It reduces duplication and isolates parts of the code for easier debugging.

1def printOwing(self):
2    self.printBanner()
3
4    # print details
5    print("name:", self.name)
6    print("amount:", self.getOutstanding())

1def printOwing(self):
2    self.printBanner()
3    self.printDetails(self.getOutstanding())
4
5def printDetails(self, outstanding):
6    print("name:", self.name)
7    print("amount:", outstanding)

Data organization

All of code is about data and the operations you perform on it. It is possible to write functional code without thinking too hard about the data you are handling. The techniques in this category help with “replacing primitive data types with rich class functionality”. Pieces of data that should be looked at together become members of a class rather than independent primitives. Proper data organization and method composition alone can bring major improvements in your code.

Favorite techniques:

1. Replace Data Value with Object
   • With replacement of a data value with an object, we have a primitive field (number, string, etc.) that’s no longer so simple due to growth of the program and now has associated data and behaviors. On the one hand, there’s nothing scary about these fields in and of themselves. However, this fields-and-behaviors family can be present in several classes simultaneously, creating duplicate code.
   • Therefore, for all this we create a new class and move both the field and the related data and behaviors to it.

Simplifying conditionals

Conditionals have a tendency to get more complicated over time. In my experience, trying to untangle a conditional can be a frustrating experience. The techniques in this category help you write conditionals that are easier to follow, more expressive and robust.

Favorite techniques:

1. Replace Nested Conditional with Guard Clauses
   • When you have a group of nested conditionals and it’s hard to determine the normal flow of code execution, this refactoring comes in handy.
   • We isolate all the special checks and edge cases into separate clauses and place them before the main checks.

 1public double GetPayAmount()
 2{
 3  double result;
 4
 5  if (isDead)
 6  {
 7    result = DeadAmount();
 8  }
 9  else
10  {
11    if (isSeparated)
12    {
13      result = SeparatedAmount();
14    }
15    else
16    {
17      if (isRetired)
18      {
19        result = RetiredAmount();
20      }
21      else
22      {
23        result = NormalPayAmount();
24      }
25    }
26  }
27
28  return result;
29}

 1public double GetPayAmount()
 2{
 3  if (isDead)
 4  {
 5    return DeadAmount();
 6  }
 7  if (isSeparated)
 8  {
 9    return SeparatedAmount();
10  }
11  if (isRetired)
12  {
13    return RetiredAmount();
14  }
15  return NormalPayAmount();
16}

2. Introduce Assertion
   • In the case where certain conditions must be true for a portion of code to work correctly, this refactoring technique comes in handy. We replace all our assumptions with specific assertion checks.

1def getExpenseLimit(self):
2    # Should have either expense limit or
3    # a primary project.
4    return self.expenseLimit if self.expenseLimit != NULL_EXPENSE else \
5        self.primaryProject.getMemberExpenseLimit()

1def getExpenseLimit(self):
2    assert (self.expenseLimit != NULL_EXPENSE) or (self.primaryProject is not None)
3
4    return self.expenseLimit if (self.expenseLimit != NULL_EXPENSE) else \
5        self.primaryProject.getMemberExpenseLimit()

My experience

I want to talk about my experience from 3 different angles. How my behavior changed, how I look at coding differently now, and the best practices I’m taking forward with myself.

1. How my behavior changed
   • Almost everything I learned made me respect OOP concepts more.
   • I started using multiple files more, I used classes, data structures and functions more intentionally and “really thought about what code should look” like before jumping into the mechanical side of coding.
   • Once code was refactored, it reduces the cognitive effort required from a future reader/owner. This made me a lot more productive - I was spending much less time and mental effort trying to figure out what code was doing. It was all in front of me.
2. How I look at coding differently now
   • Coding became fun again.
   • Over time, I have learnt that I enjoy making things. Podcasts, music, blog posts, or new features. I enjoy making high-quality things even more. I could feel a tangible improvement in my code quality and code health. I enjoyed looking at and writing new code once I refactored it or wrote it more intentionally.
   • “Thinking, planning and implementing code at the same time is a great feeling.” As I started writing more and more code, my process evolved. My current process is to think about what I’m coding using quick drawings on my whiteboard, then type out some pseudocode, and finally move pieces of the pseudocode around and write syntactically correct and complete code. The whole process leaves me more energized - I always feel like I’m in control. Bugs are caught quickly and easily. Harsh boundaries between different modules and methods take out any frustrations I would have felt from working with spaghetti code.
   • I have realized that writing code is an art and is about style. For example, consider the trade-off you need to make when writing function calls upon function calls. More functions and boundaries lead to more expressive code (which is good!) but might cause the reader to jump around different parts of a file in order to get to a particular function definition (which is not good). Performance aside, I will always prefer to write more functions in order to write more expressive code. I trust that readers and modern IDEs will make code navigation easy. That is my style. Someone else might write less functions, which makes the end result less expressive but slightly easier to navigate. That would be their style. Writing code is about style.
3. Best practices
   1. Code can keep improving, settle for good enough
      • Your code can almost always be improved. Settle for ‘good enough’ and move on.
      • You need to move to other things, and constantly cleaning up old code is not an option. Once you think a piece of code is expressive, easily modifiable, understandable, and will be easy to debug in the future, move on. This brings me to my next best practice…
   2. Keep a wishlist
      • I keep coming across code that frustrates me. I keep a track of such code and return to it when I have some downtime or I feel like cleaning up code.
   3. For best results, know your editor well.
      • The quicker you are able to implement the changes you want, the quicker you can move. You do not want the tool to become a source of friction between you and clean code.
   4. There are 2 golden rules to keep writing clean code without getting lost in the details:
      1. The broken windows rule
         • Don’t leave any ‘broken windows’ in your code. Broken windows are messy pieces in an otherwise clean file. If someone (you included) looks at a ‘broken window’ in code, you’re more likely to feel okay with making a further mess.
         • On the other hand, if you see a well formatted, well written file, you simply do not want to be the one who adds the first bit of mess into the clean file. Don’t leave broken windows in your code, and maintenance becomes natural.
      2. The campsite rule
         • Always leave the campsite cleaner than you found it. If you make any change to a file, make sure you’re leaving it in a healthier, cleaner state than you last found it. Even if the change is as small as deleting old commented out code or adding proper formatting, constant cleaning up can add up to big results.

Follow ups

I want to make refactoring a habit. All my follow ups circle around this objective.

1. Keep a running ‘Refactoring Opportunities’ list
   • I have a Notion page where I track code I’d like to clean up. I keep a track of what the current problem is, my initial ideas on how I’d change it, as well as the refactoring techniques I see myself using. I return to this list once/week and work on one of the entries in the list.
2. Share everything I learn
   • If I make a constant effort to share a change I made, I’m likely to hear other people’s opinions on it. More dialogue = more learning!

Article Body

I help produce a weekly podcast, and we have released about 19 total episodes. My podcast editing process has slowly developed and now I feel quick and comfortable editing up an episode in 1.5-2.5 hours as opposed to the 4-5 hours it used to take me in the beginning. This workflow is also far less frustrating and the end result is much better.

This post outlines my current editing process, take from it what you will!

Some background:

• I use Logic Pro X, but this workflow is adaptable to any audio editing software you wish to use.
• Here is the starting point: Ratik and I record individual tracks on our ends and send them to each other…

…and the edit begins. Let’s go over it step-by-step and look at some tips and tricks I use.

Step-by-step process

TLDR: Sync up the individual tracks, cut silences, listen through and split the episode into sections, clean up the sections, add the finishing touches, and you’re done.

1. Syncing

There are 2 main tracks (one for me, one for Ratik). In order to sync them up, we simply record some claps to both the tracks and use that to sync them up. Easy.

2. Cut silences

Each track has silent portions (for example, when I am talking, Ratik’s track is silent).

Even though it looks like there is no audio in flat waveforms, there is always some undesirable room noise, and it’s probably best to get rid of these sections from the track. Logic has a wonderful little tool for silence removal that I use all the time. You can do this step manually, but almost every audio editor will have some tool to help you do this. The default shortcut for removing silences from a track is Ctrl-X.

That’s preprocessing done! Let’s start cutting.

3. Listen through and split into sections

I like to listen through the entire episode and use markers to split the episode into logical (pun unintended) sections. This way, I can work on small sections at a time without getting overwhelmed, and I’m able to see if there are any glaring flow issues.

Here’s some things to keep in mind:

• Listening through the entire episode can be slow, so increase the playback speed! I use Varispeed to do this. More on this in the ‘tips’ section.
• Once the sections are split up, I color each of them differently so I always have a visual indication of how much of the section I still have to edit. Here’s an example:

4. Clean up sections

Now that the episode is split up, I jump into each section and ‘clean it up’. This involves removing any unwanted material, cutting out any misspeaks, and if required, making things a little more ‘snappy’. A lot of this is by feel. You will develop your own feel the more you edit.

This part of the process is the longest. Depending on how the recording session was, this can be easy or a bit of a chore. More on this later too.

5. Finishing touches: audio FX, theme tune, outro

Almost done. Before the episode can be shipped, I add in the intro jingle and outro music. Each track also gets a chain of FX (or plug-ins, whatever you want to call them) to make the audio sound extra crispy.

And that’s it! A fully edited episode. Time to export and upload.

Additional Tips and Tricks:

Varispeed

Varispeed is a Logic tool that allows you to playback your project at higher (or lower) speeds. Very useful when listening through. I listen through the raw episode at 2x speed and keep it there when cleaning up my sections. A lifesaver. Your DAW likely has a similar tool.

Templated projects

In step 5 above, I spoke about adding in the jingle and channel FX. These are repeated and the same for every episode, so I simply made a templated project file with the individual channel settings applied and the jingle already in there. Why do more work when fewer work do trick?

Keyboard shortcuts

My favorite part. Learning how to move around Logic and use your most used features using shortcuts will change your life. Here are some of the main keyboard shortcuts I use:

• Zoom and movement — Zooming into your timeline horizontally and vertically is something you will do all the time. Moving horizontally is also something you will do all the time. These are baked in by default.
• Varispeed: turning on and off — There isn’t a default shortcut for this, but I added one in.
• Go to next/previous marker — Again, a custom shortcut. I use this to jump between markers while editing. I am speed.

Chapters

Shoutout to Ratik for this one. Podcasts can be long and having ‘chapters’ really helps make a long episode more digestable. Here’s an example of the chapters in episode 17 of Frndship Time.

This is how I add chapters to each episode. You’re adding markers anyway, might as well take the small additional step and finish the job.

Some notes on recording

Like anything else, the better your input material is, the easier it is to have a great end product. If your raw recording session was good, you need very little work to make a great episode. The editing process becomes much shorter and simpler. I call these episodes ‘sushi episodes’.

Thanks for reading! If you have any questions, suggestions, or tips, let me know! See you later.

See you next week for a new post.

Thanks for reading! You can always email me to chat about this post - or anything else.

As is true for any advice or counsel you ever receive: Y.M.M.V! Your mileage may vary. Some advice can be a vice. Feel free to take what you can use, and leave the rest. There are no rules.

I also wanted my website to hold some technical, musical, and other ‘skill based’ guides and tutorials, but I haven’t done that either.

So, there’s two issues that I need to fix here:

1. A lack of consistency in posting
2. A lack of new genres of content (guides and tutorials)

I have tried to solve these problems in the past by trying a few things:

• I tried to build accountability by adding ‘see you next week!’ at the end of each post, but I ignored it each time (..hah, no excuses on that one)
• Simply trying harder and trying to write posts even when I didn’t want to

Safe to say, neither of those approaches worked, and I need a newer, healthier approach to do this. This post is all about the approach I’m using to be more consistent and introduce more content to the website.

The main reason why I’ve lacked consistency over the past year is that the kind of posts I was writing just took a lot of time. For posts like What do I do With My Life? and Getting Ready to Start a Career, the more I thought about them and mulled them over, the better the posts turned out. None of these posts would have been what they were had I just given them one week each. These types of posts take time, and I cannot expect to make posts like those every week. The solution then, is two fold:

1. More genres of posts!

   I’ve wanted to make tech and skill based guides, which would take much less time to make. In addition, this also solve my ‘lack of skill-based documentation’ problem.

   In addition, some weekly summaries of my daily updates can also be a great way to crystallize learning and put it across in a sharable way.

   If I add that kind of content and put out ‘classic’ posts (like this, this, and this one) once a month, a majority of my problems would be solved

2. A newer strategy to ‘making’ content

   ‘Document, don’t create’: Creating something new takes time and effort because you build things up from scratch. On the other side, if I simply document the things I’m learning and interesting conversations I have, content will create itself.

   As an example, I have been journaling for the last year and a half, and if I go back and pick up pieces from different entries, I could coalesce them into a new post with minimal effort.

   In fact, this strategy is the exact reason why Frndship Time (a podcast I started with my friend) is so consistent. We release at least 1 episode every week. The secret is that none of it feels like work. Ratik (the cohost) and I record our general conversations, do some minimal editing, and send the episodes out every week. In fact, we discussed this exact strategy on episode 2 of the podcast. Check it out:

This is all good in theory, but only time will tell whether I will be able to pull it off. If things go according to plan, I should be averaging more than 1 post a week, which is much more than what I was trying to do earlier, but with the new strategy, I am more optimistic this time.

Finally, accountability: each month, I’ll put out a ‘What you can expect this month’ post on the website. This will include all the posts I have planned out for the month, in addition to approximate release dates. I have to plan this out anyway, might as well turn it into a post. I’m already doing the ‘document, don’t create’ thing.

Okay, here’s the TLDR: expect more content. Expect different content. How I organize the tech/skill guides and the ‘classic’ posts is a bridge that we will cross when we get to it.

Thanks for reading, and I’ll see you next week!

See you next week for a new post.

Thanks for reading! You can always email me to chat about this post - or anything else.

As is true for any advice or counsel you ever receive: Y.M.M.V! Your mileage may vary. Some advice can be a vice. Feel free to take what you can use, and leave the rest. There are no rules.

I’ve been making content online for almost all of my adult life. I started when I was 14/15 and I’m still trying my hand at it. Eventually, the classic quantity vs quality question was bound to come up.

The classic, copout answer to this question is simple (and, I repeat, a copout): you need both! You need a balance! This is obvious, but I wanted to take a deeper dive at my personal situation and find an answer that works for me right now.

I believe there is an actual winner. This (short) post is all about why I choose to prioritise quantity in the short term while prioritising quality in the long run.

There are obvious arguments for both. There are success stories for creators who have focused on quantity (see: KhanAcademy, 5minCrafts, etc), and there are successful creators who have focused on quality (Kurzgesagt, CGP Grey, etc).

There is no question that both these approaches work and have their advantages. Let’s take a closer look at the advantages of focusing on quantity.

The more stuff you put out there, the more feedback you get, the more opportunities you have to improve your work. You also start generating a catalog of work. Quantity also gives you more opportunities to make things, which gives you more chance for practice. If I had focused the past 7 months on writing one big, grand blog post, there would be no chance of practice. It’s just constantly trying to get the best out of one piece of work. At the end of the day, you might not even end up putting the piece out there because it doesn’t ‘hold up to your expectations’. Isn’t it better, then, to focus your energy on making many imperfect things? Does shipping beat perfection?

On the other hand, quality has its own pros. If you create something extraordinary, there is a much higher chance that you’ll catch a ‘big break’, whatever that is. Your video/blog/podcast/music might go viral, suddenly garnering attention and critical acclaim.

The question is, which pros do you choose?

If I consider my particular situation, I am a beginner or enthusiast at everything that I do. My music skills are nascent, I haven’t had any real practice with video production, the podcast I launched earlier this year is my first step into the world of audio. At this ‘beginner’ stage, focusing on quantity will benefit me a lot more than focusing on quality. There is a reason why Frndship Time episodes are weekly. There is a reason why these blog posts (ideally) come out every week.

At this point, focusing on quality makes no sense. I simply do not possess the skills to make something extraordinary. Only with more creation, more practice, and more experience can I begin to pour my resources into focusing on quality. More practice and feedback also guarantee that I will get better at these skills.

I am not blind to the advantages of focusing on quality, though. The satisfaction and long term reward of creating something of the highest possible quality are unquestionable. The question then, is this: is there an approach that will allow me to get the best of both worlds? I’m glad you asked (you didn’t ask… but here’s what I think anyway)!

For the past few weeks, I’ve been focusing on creating regular, ‘decent’ quality content while also working on a couple of ‘high quality’ projects in the background.

For example, when it comes to content creation, Frndship Time and this blog are regular bits of content. I also (try to) make some new music every week. At the same time, I’ve been working on slightly more ambitious projects in the background. This allows me to reap the benefits of constant, quantity focused content creation while also being able to make quality focused content without the pressure that comes with just focusing on one project at a time.

Here’s the takeaway: when it comes to the quantity vs quality debate, just like anything else, there is no answer, only tradeoffs. You make a decision based on your current situation and priorities. Right now, I’m leaning towards quantity, but quality is always in my peripheral vision.

See you next week for a new post.

Thanks for reading! You can always email me to chat about this post - or anything else.

As is true for any advice or counsel you ever receive: Y.M.M.V! Your mileage may vary. Some advice can be a vice. Feel free to take what you can use, and leave the rest. There are no rules.

Here we are in January 2021. Having actually ‘opened up the box’ by writing ten posts, I’ve learnt so much more from blogging than I first expected. This is much closer to reality:

This is a quick post about everything I have learn from blogging for the past 7 months, and hopefully by the end of it, I can convince you to just get started with that one side project you’ve been meaning to start for a while. You know what I’m talking about. That project. Anyhoo, let’s take a trip back to May 2020, when I wrote my first post…

…the ‘blog’ started as I was about to graduate from Cornell. Putting two and two together, I put together a piece about my time in Ithaca. The post was about everything I had learnt, my experience with imposter syndrome and how it had changed me. The intention of the piece was simple: document my experience. It wasn’t meant to do anything other than act as a time capsule of my time as a Master’s student. However, writing the post had another unintended effect: offering solidarity! As the post went out, reader responses started coming in. A few readers reached out sharing how they also dealt with similar circumstances. This was the first of many experiences where a blog post’s effect was different (and much more fulfilling) from the intention of the post.

This is not to say that the original intention was lost. Over time, the post did act as a fantastic way of storing ideas and thoughts for the long term. Who knew writing = documentation?!

Next, I wrote about a framework I’d been using to learn new skills every week. A nerdy and neat idea in my head, my intention with this post was to simply start populating the blog. For all intents and purposes, this post was supposed to fly under the radar. Looks like the post missed the memo on that one. Almost every email I’ve received from a reader has spoken about how they’ve used the framework from this post for their personal use. Again, the eventual effects of the post were wildly different from the intent (in the nicest way).

The key theme after these two posts is that you don’t have any control over what the effects of your work will be. All you can do is make things and put them out there. Whatever follows is out of your hands.

Fast forward to July 2020, when I was getting ready to start my first job. Again, made sense to put all my thoughts about this into a post. At this point, I was getting better at writing posts. I had (unintentionally) developed a process for writing blog posts. Every post since this one has been a little easier, and has felt like a little less work each time. Here’s the takeaway: if you keep doing something, it will get easier. You will get better. It’s almost as if practice… makes you better??? Again, who knew.

Another sidenote: writing is so much more than putting words to paper! My 3rd post was the first time I experimented with new techniques. I added illustrations and more personality to the posts. Personality, storytelling and analogies are all things that turn a piece of work from an ‘information dump’ into something human. This is a takeaway that has helped me make my other projects better too. I would never have guessed that writing blog posts would help me in such a way. Finally, the biggest unintended (super positive) effect of this post was one of human connection – it led to conversations I wouldn’t have had otherwise. Readers reached out with stories that mirrored mine. I spoke to people about their experiences, what advice they had for me and vice versa. Solidarity is a powerful thing.

Fueled by these conversations and now aware of the power of solidarity, I wrote ‘What do I do With My Life?’. This was a post written to anyone feeling anxious about not knowing what they want to do with their lives. This post is by far my favorite out of everything I’ve written yet. It was a culmination of everything I had learnt so far. Namely: 1. solidarity is powerful, 2. how to follow a writing process to get from a tiny idea into a coherent blog post, and most of all – 3. personality and storytelling are what separate human work from information dumps. The effects of the post went far beyond anything I could have imagined. It generated the most reader responses, and each response was personal and heartfelt. This was the post that made me realise the most important lesson so far: your work has power. What started off as a simple idea in my head was now acting as a gateway for people to start talking about how they were changing their outlooks on their personal goals and lives. Your work has power!

Over the next few weeks, I wrote more ‘information dump’ posts. First, I wrote about my writing process (meta, I know). Then, about how I was keeping in touch with friends during the 2020 coronavirus pandemic. Finally, I put together a ‘getting started’ guide for people preparing to apply to graduate programs in the US. These posts did not have the powerful interpersonal and deep effects that previous posts did, but they drove value in a different way. They act as amazing FAQs. Every time I’ve gotten a question about my experience with applications or whenever I’m asked about how I write my blog posts, I simply reply with a link to the relevant blog post. Information dumps are useful!

That brings us to today, to this particular post. This post was supposed to be a simple listicle with quick bullet points about everything I’d learnt from blogging. However, as I began writing, I realized there was a lot more to talk about than a simple list of things I’d learnt. Essentially, you don’t know what a post will be until you start writing it. This final lesson can be generalized to anything you do: to figure out step 2, you need to take step 1. You don’t need to have all the details of a project figured out before you get started. Jump in and work things out as you go. Just get started!

After 7 months and 10 posts (quite a bad post/time ratio to be honest), here’s everything I’ve learnt about blogging condensed into a nutshell:

The most important thing is to get started. Sweat the details later, get started today. You cannot control what the effects of your work will be. Focus on creating solidarity with your work, throw your personality into everything you do, and always remember: your work has power.

So that’s everything I’ve learnt so far. Here’s a venn diagram of things I expected to learn and things I actually learnt.

Let’s come back to the boxes analogy from earlier in this post:

That’s the ultimate takeaway here: you don’t know what’s in the box unless you actually look in the box. So ‘open the box’ of whatever project you’ve been meaning to start. In other words, just start, and start today. Let me know if you do!

See you next week for a new post.

Thanks for reading! You can always email me to chat about this post - or anything else.

As is true for any advice or counsel you ever receive: Y.M.M.V! Your mileage may vary. Some advice can be a vice. Feel free to take what you can use, and leave the rest. There are no rules.

At the heart of it, any side project is a 3-step process:

1. Understand what you’re making/doing
2. Specify what constitutes a finished project
3. Implement your idea

I’m going to use 3 side projects to elaborate on each of those steps. The 3 projects are a music and video project that took under an hour to make, a semester long technical project, and an ongoing project: this website! Let’s get started.

1. Understanding what you’re making

This step is all about putting your abstract idea into words. You’re trying to answer the question “what am I making?”. The goal is to add more clarity to your idea. I suggest putting this into writing. There have been multiple situations where I had an idea that made sense to me in my head but looked questionable when put onto paper. At this step, there is no need to be overly specific. Just answer the “what am I making” question. Here’s how I did it for 3 of my projects:

1. Tiny music project: a random video with some original piece of acoustic music
2. Branch predictor project: functional level models of 2/3 branch predictors in C++
3. Personal website: a website that can be a home to all my work and also act as a blog

2. Specification:

You have an idea of what you’re making. Now, specify details before you get started. Answer the question: ‘what constitutes a finished project?’. The goal here is to remove any vague descriptions and set concrete expectations from the project. I like to be as objective as possible here. ‘Specification’ calls for specificity (wow). Be specific! For my projects, I like to make a list of outcomes that need to be done to call the project ‘finished’. Here are some of my lists:

1. Tiny music project:
   • A chord progression
   • A video
2. Branch predictor project:
   • 1-level predictor functional level model
   • 2-level predictor functional level model
   • Binary instrumentation tool
   • Everything parameterized and extensible
3. Personal website: a website that can be a home to all my work and also act as a blog
   • A main home/landing page that holds links to all my work
   • A blog page with hero image support
   • A first post with a vision for the website

The point of making these specifications is so you know exactly what you’re trying to build. In my experience this step also makes it more likely that you will be happy with your finished project, but your mileage may vary.

3. Implementation

You now have an exact idea of what your project involves. Time to work on it! You’re looking to answer the ‘how do I make this’ question and then follow through. The goal is to start working on your project, deal with problems, and keep going until you finish. In my experience this step is made infinitely easier when I do steps 1 and 2 well. Otherwise, the lack of clarity is demotivating.

This is also about 80% of the total work of the project, and involves dealing with problems that you don’t foresee. For example, here are problems that came up when I implemented my projects:

1. Tiny music project:
   • I’m very new to writing my own music. I got stuck many times and changed up the progression at least 3 times until I had something I was happy with.
   • I had some technical difficulties with recording as my mic just stopped working. Did not see that coming.
2. Branch predictor project: functional level models of 2/3 branch predictors in C++
   • There were parts of the code that required C++ tricks I hadn’t worked with before. Reinterpret casting, compiling Intel’s pintools, issues with huge Makefiles and writing and debugging code.
3. Personal website:
   • This was my first time being exposed to any sort of web development. Setting up and learning Jekyll was a big task.
   • I also ran into issues with GitHub pages

And that’s mostly it! Here’s some final things to note:

It’s okay to abandon projects if you don’t think they’re working, but abandoning something because it’s too much work just doesn’t feel right (I’ve been guilty of this a lot: my YouTube channel still is a good idea in my head, but just too much work so I don’t get around to it).

The whole process is iterative! During implementation you may realise your spec needs to change a little bit. Do it! If you think something is too difficult and needs to be made easier so you can finish it, that’s a great call.

At the end of the day, side projects are voluntary. I abandon side projects if I stop enjoying the process and ‘finishing the project’ is the only motivator.

There are so many more details that I wanted to talk about in this post, but there just isn’t any room. If you want to talk about any of your side projects or if you have an approach that works well for you, let me know! I’m always willing to talk.

See you next week for a new post!

Thanks for reading! You can always email me to chat about this post - or anything else.

If you do any kind of creative work & have a couple of hours to kill, read Show Your Work by Austin Kleon

An alternative, if you will, to self-promotion. I’m going to try to teach you how to think about your work as a never-ending process, how to share your process in a way that attracts people who might be interested in what you do, and how to deal with the ups and downs of putting yourself and your work out in the world.

I picked up this book on a Wednesday at 3pm and couldn’t out it away until I was done 2 hours later. This will change how you view your creative work and how you share it.

If you’re looking to read real, interesting, heart warming behind-the-scenes stories from the biggest businesses in the world, read…

…Ride of a Lifetime by Bob Iger

Don’t let ambition get ahead of opportunity. By fixating on a future job or project, you become impatient with where you are. You don’t tend enough to the responsibilities you do have, and so ambition can become counterproductive. It’s important to know how to find the balance—do the job you have well; be patient; look for opportunities to pitch in and expand and grow; and make yourself one of the people, through attitude and energy and focus, whom your bosses feel they have to turn to when an opportunity arises.

Can’t say enough nice things about the stories from this book. This isn’t a book about a business or advice, it’s a lot more valuable than that.

…or Shoe Dog by Phil Knight

Just before getting on the plane home we signed deals with two Chinese factories, and officially became the first American shoemaker in twenty-five years to be allowed to do business in China. It seems wrong to call it “business.” It seems wrong to throw all those hectic days and sleepless nights, all those magnificent triumphs and desperate struggles, under that bland, generic banner: business. What we were doing felt like so much more. Each new day brought fifty new problems, fifty tough decisions that needed to be made, right now, and we were always acutely aware that one rash move, one wrong decision could be the end. The margin for error was forever getting narrower, while the stakes were forever creeping higher—and none of us wavered in the belief that “stakes” didn’t mean “money.” For some, I realize, business is the all-out pursuit of profits, period, full stop, but for us business was no more about making money than being human is about making blood. Yes, the human body needs blood. It needs to manufacture red and white cells and platelets and redistribute them evenly, smoothly, to all the right places, on time, or else. But that day-to-day business of the human body isn’t our mission as human beings. It’s a basic process that enables our higher aims, and life always strives to transcend the basic processes of living—and at some point in the late 1970s, I did, too. I redefined winning, expanded it beyond my original definition of not losing, of merely staying alive. That was no longer enough to sustain me, or my company. We wanted, as all great businesses do, to create, to contribute, and we dared to say so aloud. When you make something, when you improve something, when you deliver something, when you add some new thing or service to the lives of strangers, making them happier, or healthier, or safer, or better, and when you do it all crisply and efficiently, smartly, the way everything should be done but so seldom is—you’re participating more fully in the whole grand human drama. More than simply alive, you’re helping others to live more fully, and if that’s business, all right, call me a businessman.

Possibly the one book that I would recommend you read no matter what. I struggled to pick one single highlight to include from this book, but the one above only does partial justice to the story of how Nike came to be.

If you have just graduated from college/if you’re starting a new job/if you’re generally confused about the ‘what do I do with my life’ question, read Designing Your Life by Bill Burnett and Dave Evans

We all know how to worry about our lives. Analyze our lives. Even speculate about our lives. Worry, analysis, and speculation are not our best discovery tools, and most of us have, at one time or another, gotten incredibly lost and confused using them. They tend to keep us spinning in circles and spending weeks, months, or years sitting on that couch (or at a desk, or in a relationship) trying to figure out what to do next. It’s as if life were this great big DIY project, but only a select few actually got the instruction manual. This is not designing your life. This is obsessing about your life. We’re here to change that.

Even if you already have most of the insights this book talks about, some of the exercises and insights will be new to you.

If you’re in the mood for a fuzzy, cute, romantic-comedy, read…

…The Rosie Project by Don Tillman

Amazing. She retains a professor of genetics, an alien of extraordinary abilities, to help find her father, she travels for a week, spending almost every minute of the waking day with him, yet when she wants the answer to a question on genetics, she goes to the Internet.

…or Eleanor Oliphant is Completely Fine by Gail Honeyman

Eleanor, I said to myself, sometimes you’re too quick to judge people. There are all kinds of reasons why they might not look like the kind of person you’d want to sit next to on a bus, but you can’t sum someone up in a ten-second glance. That’s simply not enough time. The way you try not to sit next to fat people, for example. There’s nothing wrong with being overweight, is there? They could be eating because they’re sad, the same way you used to drink vodka. They could have had parents who never taught them how to cook or eat healthily. They could be disabled and unable to exercise, or else they could have an illness that contributes to weight gain despite their best efforts. You just don’t know, Eleanor, I said to myself.

There are 2 kinds of people on this planet. People who enjoy the warm, fuzzy feeling that good romantic comedies give them, and liars. These books are just as good as they are advertised to be. Recommend!

If you’re in any engineering job (especially software engineering) OR if you’re simply trying to change how you think about problems and solutions, read Pragmatic Thinking and Learning by Andy Hunt

This book is different when compared to the others on this list. Written a lot more in a textbook-style format, this isn’t a book you binge or read passively. This is a book you have on your bookshelf and keep going back to until you’re able to internalize everything it talks about. I have a bunch of unfinished notes from this book if you prefer to get a taster for what it’s actually like. Email me if you’d like a pdf of the notes!

If you’re not the happiest about your day-to-day habits and want a no-nonsense self-help book, read Atomic Habits by James Clear

You do not rise to the level of your goals. You fall to the level of your system

The only real self-help book that I would recommend you read. Again, like any other self help book, this could have been much shorter, but James Clear keeps everthing concise and straight to the point. One of my favorites this year.

I hope you find some value in these recommendations. If you have any books that you would like to put on this list, let me know! As the recommendations keep coming in, I will include them below. Just make them contextual! For example, “if you < mood or life event or other context >, you should read < book name >”. I look forward to adding your recommendations in!

Happy reading!

Applying to the US for a Master’s degree in a STEM major can be daunting. It isn’t that there is a lack of information, but the opposite. The internet is flooded with information about this - all of which seems relevant. The process can be overwhelming and stressful. This post is meant to be a (very) gentle introduction to anyone considering further studies after finishing their undergraduate courses. It will walk you through the very basics and point you to resources that I found useful back when I was applying. Let’s get started!

There are 4 main steps to the application process

1. Give 2 exams
2. Decide where you want to apply
3. Prepare your application
4. Apply!

Let’s break down each step.

1. Give 2 exams:

You have probably heard of the GRE and the TOEFL. Almost all US universities require you to give these tests as part of your application.

What are these Tests?

Here’s a quick summary:

The GRE (or Graduate Record Examination) is a standardized test that is often required when you’re looking to apply to graduate programs in the US (or other countries too). It covers basic high school math and verbal reasoning. In other words, math and English.

The TOEFL (or Test of English as a Foreign Language) is a standardized test to measure the English language ability of non-native speakers. It gauges whether or not you have the English language skills (speaking, listening, reading, writing) required to be eligible to study at US (and other) universities.

99% of the time, you will be required to give both exams as part of your application and the scores you receive will have a direct impact on your application, so it’s really important that you do well on these exams! Here’s the thing about these exams: you can give them without really knowing the exact program or courses you want to study when you apply. The implication here is that you can give these tests early on without having decided on where you want to apply, and without worrying about the rest of your application.

Some logistics to consider

Cost (as of October 2020):

• TOEFL: $180
• GRE: $160

Your scores are valid for 5 (GRE) and 2 (TOEFL) years. This means you can give these tests whenever you have the time to prepare, and use the scores a few years later.

A ‘good score’ for the GRE depends on where you choose to apply and to what program. Higher ranked universities will ask for higher scores. Some people prepare for a 1-2 months, some prepare for much longer. There is no single right way. Assess your personal situation and choose what works for you.

These are standardized tests. That means with a good preparation strategy and abundant practice, you will do well!

The only advice I would give is to give a mock GRE exam (linked below) before you start any sort of preparation. That will give you a sense of the exam and establish a baseline performance level. From there, you can prepare and see your score improve.

There is a world of resources on how to prepare for the GRE and TOEFL. Don’t get overwhelmed! Pick a strategy you can execute and you will be okay.

Further resources:

1. Official GRE website (find the mock GRE exam here)
2. GRE preparation guide

Now that you’ve given the 2 tests, it’s time to consider where you want to apply for graduate school…

2. Decide where you want to apply

This entire step requires you to answer one question before you get started:

What do you want to study?

Answering this question is very important, it will guide your decisions on where you end up applying. Here are certain things you should keep in mind when deciding on your final list of universities:

Courses offered

Once you know what you want to study, you can use that information to decide which courses you will want to study, and you can check whether a particular university offers those courses and what the reputation of the course is.

Cost

Some universities have higher tuition costs than others. Particular universities may offer better chances of financial aid. Some cities are more expensive to live in than others. Find out what these numbers look like and make an informed decision.

Rankings

Here’s some advice: if you’re applying to multiple universities (you should), consider splitting them up into 3 ‘tiers’. Apply to a few colleges that are your ‘ambitious’ choices. These are your dream schools. Apply to a few that are ‘mid tier’ – these will offer higher acceptance rates and you will have a better chance of getting in. Apply to at least one ‘safe’ choice – a college you are almost certain you will get into.

Personal experiences

It’s always good to consider the personal experiences of the alumni of a particular college. Try to use LinkedIn or ask your friends if they know anyone who has been to a college and ask them about their experience. This can help you in making a better decision!

In a nutshell: apply to multiple universities, consider ‘tiering’ your choices, and focus on the courses offered, total cost, and rankings to put together a list. Remember, college websites are your friends! Colleges put up a lot of information on their websites including costs, course listings, and sometimes even expected GRE/TOEFL scores.

Further resources:

1. USNews is a great resource for university rankings

Time for step 3…

3. Prepare your application

A ‘complete’ application includes your test scores, a statement of purpose, a few letters of recommendation, a resume, and some documentation (mainly your undergraduate transcripts and provisional degree). So far, we’ve looked at the exams you need to give and how to decide where to apply for colleges. The next step is to complete the rest of your application. Here’s some quick information on the statement of purpose and letters of recommendation:

Statement of Purpose (SoP):

The SoP is a brief essay that answers a few questions: why do you want to study at a particular university? Why are you a good fit for that program? Why is the program a good fit for you? How are you qualified for what the program demands?

Here are some starting tips to keep in mind:

1. you are telling a story, not writing a series of events
2. you’re telling them why you want to study what you’re applying for and
3. why they’re a good fit for you and vice versa
4. you’re trying to make the case that you are really passionate about what you’re going into
5. talk about specifics – why their university? Why that program? What do you know that’ll help you there – what do you want to learn that they teach there? Any professor whose work matches what you want to learn?

You want to include:

1. your goals in the short and long term
2. what you want to gain from the degree and how you plan on using it
3. evidence of your past successes: GPA, publications, projects deployed, etc.

This may be a good resource if you’re looking for a format to get started with.

Here are some samples that I used.

Just keep in mind that there is no ‘correct’ way to write an SoP. These are good guidelines, but if you feel your story is better told in a different format or structure, do that! Most importantly, keep writing and changing things rather than trying to get the first draft perfect. Iteration is your friend!

Letters of Recommendation (LoRs)

These are letters that your professors (or work supervisors) will write endorsing you as a deserving candidate for a place at the university where you’re applying to.

Here’s some things to keep in mind:

1. When you ask your professors (or supervisors) to write you an LoR, express what you think they should highlight. Express your expectations!
2. Keep in mind that as you apply, your professors (or supervisors) will have to submit these letters on their end. Therefore, it’s important that you keep in touch with your professors because you may have to remind them to subit the LoRs in case they forget.

Transcripts and provisional degree:

You don’t really need to do much here, just find out how you can get your transcripts and provisional degree from your college and have it sent over to wherever you are applying. Some colleges accept these documents sent to them via your college’s email ID, some require physical copies, check what the college is looking for!

Resume:

You will likely need to send in a resume as part of your application. Keep in mind that you are also sending in an SoP, so if there is any information that you would like to cover that you did not include in the SoP, this may be a good place to do it!

So there it is. A complete application. You now have your SoP, LoRs, you have your documentation ready and you have your standardized test scores. You have also decided where you want to apply. That leaves you with only one thing to do…

4. Apply!

The most important thing when applying in to figure out when the application deadline is for the programs you are applying to. Make sure you know exactly when those are! Again, college websites have this information readily available.

The first application you fill out may take an hour or so as you get used to the process, but everything from there onwards should be quick and straightforward.

So there it is! A gentle introduction to applying to universities in the US. You will eventually realize that this is just the tip of the iceberg. There are so many more moving parts: how long do you study for the GRE? What about visa logistics? Should my SoP be different for each college I apply to (yes, but also a little bit of no)? These are questions that need to be answered, but hopefully now you don’t get overwhelmed about the entire process. It’s really just 4 basic steps!

1. Give 2 exams
2. Decide where you want to apply
3. Prepare your application
4. Apply!

If you have any further questions, quick Google searches will get you a long way. For anything that Google cannot answer, I’d be willing to help. Contact me here!

Happy applying!

There is a running joke among my friends about my ineptitude at keeping in touch. It may be an understatement to say that I was notoriously bad at keeping in touch. I’m not the best at texting back, and my ability to set up and commit to phone calls is… sigh. All of these are exact reasons why you should listen to me! I’ve made mistakes and experimented with different ways to keep in touch digitally and (I think) I finally have something that works very well.

This post is about things that make keeping in touch easier and how Discord has helped me immensely. The only reason I’m writing this post is because of how excited I’ve been about this app recently so most of it is likely to be… garbage fanfare about an app. Right up my alley. Let’s jump into it.

When it comes to keeping in touch digitally, the default ways are texting and calling. These serve the purpose but are overall poor options. Texting is inefficient and annoying – it’s completely asynchronous and you can never really tell someone’s tone through texts. Highly dissatisfying. Calls fix some of this, but they have their issues. Calls (if you aren’t good with them) need to be set up and when they happen they’re almost always… not great. They’re okay, but not great.

The problem with both of these options (texting and calling) is that we try to do digital communication in a way that is nothing like real life interaction.

We try to do digital communication in a way that is nothing like real life interaction. Bad idea.

Enter Discord. Discord almost perfectly emulates real life interaction. But… what even is Discord?

On the surface, Discord is “chat for gamers and a place for communities to interact”. Self explanatory but also jargon-y.

Think of Discord as a (digital) town. The way towns have houses, Discord has servers. Say it with me now: servers are like houses. The way houses have occupants and rooms, each Discord server has members and channels. The rooms (audio channels) are where the magic happens. In real life, you can tell who is sitting in a room, you can walk in & start talking to anyone inside. This is exactly how audio channels work in Discord. They’re rooms you can enter with one click. One click being the key words here: no scheduling required! No wondering whether someone is free! No friction! This is a huge deal for bad keeper-in-touchers like myself. This lack of friction also means you’re much more likely to consistently talk to people day after day. In other words, this makes it easier to keep in touch :)

Finally, in real life, conversations are rarely the only thing happening in social interaction. A lot of our conversations happen while we watch movies or play games. By combining Discord with Netflix Party and online board games (here’s my favorite), you can emulate this really well.

To recap, Discord emulates real life interaction by doing three things:

1. removes friction between the ‘wanting to talk to someone’ and actually being able to talk to them
2. makes it possible to keep in touch by making things so easy and natural
3. allows for you to talk to people while you do a third thing (movies, board games, etc)

I’m only scratching the surface of what Discord is capable of. A few weeks ago, I used an audio channel in my server to hold a live event about writing processes. I’m planning to do more stuff like this! Come let me know whatever you want to talk about! :)

This post was never meant to be a post about how to keep in touch better in general – I’m the last person who should be talking about this, but I hope you got something of value from this and maybe even give Discord a try. Thanks for reading this quick post!

My Writing Process

Writing blog posts / YouTube videos / anything creative can be a frustrating process. There is a lot of friction which can cause severe discouragement which leads to people stopping (trust me, I gave up doing YouTube videos because I just didn’t have a fun time making them anymore — and this was mostly down to the writing process). Over time, though, I’ve come up with a writing process that helps me avoid these roadblocks. It helps me take an idea and turn it into a 1000+ word post without getting overwhelmed. My goal with this post is to walk you through this process in the hopes that you find some value in it and it helps you in your writing.

In a nutshell, my process takes an abstract idea, slowly adds context and structure until I end up with something I’m happy with.

The 5 steps I go through are the following:

1. Idea conception (come up with ideas and remember them)
2. Mind dump (flesh out ideas)
3. Mind mapping (create links between your concepts so they make logical sense)
4. Outline (create structure in a written form)
5. Final post (editing and filling in the gaps)

Let’s do a deep dive into each step:

1. Idea conception:

I don’t think any of us have our best ideas when we sit down and actively try to come up with them. In my experience, ideas for posts/videos/podcasts come and go at all times throughout the day when I’m travelling, showering, talking to someone or reading.

The key here is to record all your ideas and build an archive in a notes app or notebook. It’s much easier to keep writing when you have an ‘idea bank’ than it is to come up with a new idea from scratch every time – this way you never start from a blank sheet.

At this point, all you have is an idea. It’s time to populate it with some concepts and things you want to talk about.

2. Mind dump:

Once I pick an idea from my idea bank, I spend a few minutes listing out all the things I want to talk about in the post. I don’t worry about the structure or how things link together at this point. This is a simple mind dump. As an example, here’s my mind dump for this post:

Now that the idea has been populated with a few solid points of discussion, it’s time to create links between these points. Hello step 3!

3. Mind mapping:

Time to add some sort of structure! A mind map is a great way to do this. I put down all my ideas and see how they link to each other. Here’s what the mind map for this post looked like (I know the scan quality sucks… blame CamScanner):

4. Outline:

The post now has ideas and links between them, but it is still far from complete. Outlining is all about taking your mind-map and giving it procedural structure. I like to use a whiteboard and a classic intro-body-conclusion split. Here’s a whiteboard outline of my last post. It’s… messy to say the least.

A lot more can be said about what makes a good introduction and a good body, but I am in the very early stages of learning. At the end of this step, 90% of the work is done. The only thing that remains now is to write out the post in complete paragraphs and sentences. Enter step 5…

5. Final post:

I usually spend the least amount of time in this step (I get impatient). There is a lot of value in doing this slowly, though — you pay more attention to ‘cutting the fat’ out of your post and you end up with something much more cohesive. One of my favorite quotes about writing:

“I didn’t have time to write a short letter, so I wrote a long one instead.” – Mark Twain

Editing turns a post from ‘good’ to great. Again, I’m guilty of not doing this well. It helps to have someone else read through the post and help you cut down and polish your language (can you help me with this? Please help!). When I can’t get a hold of people to vet my language, I just use an online editor. It isn’t great, but it helps.

And that’s it! The post is done! If there are any illustrations or images, they go in now. Happy publishing!

My process is probably too extensive and unnecessary, but I don’t have a natural knack for writing and a set process helps. The entire process starts with a small idea to which I iteratively add context and structure until I end up with something I’m happy with. Please remember that writing is a highly subjective process – what works for me may not work for you. Regardless, the idea of slowly building out a post in tiny increments (thank you, iterative development!) works really well for me.

Having experienced this problem first-hand and having spoken to other people who have felt the same way, I want to use this post to make a case for why uncertainty is okay. Not only this, but also why it is best to approach this situation with a mindset of curiosity and experimentation rather than allow it to bring us anxiety and a sense of dread.

The paradox of making big life choices early on in our lives is that we are required to make high stakes decisions at a time when we know very little about ourselves. We are poorly equipped to make these choices, and that’s what breeds the anxiety.

Ideally, we want to be making these decisions when we know a lot more about ourselves. There are 2 ways to do this:

1. make these decisions much later: Unfortunately, this is impractical for obvious reasons. This brings us to option #2…
2. learn more about yourself right now:

An ideal situation! If you can learn more about yourself and arm yourself with the intel needed to make a string of well-informed decisions, that will be the end of painful ambiguity and cluelessness.

The question naturally arises: how does one go from the conventional situation to the ideal one? I’m glad you asked! Allow me to explain using an overly general, poorly illustrated, no-one-asked-for-this, unnecessary analogy. Welcome to the Life Choices Ice Cream Parlor!

Let’s say you walk into an ice cream parlor with one goal - buy a huge, huge bucket of ice cream that will last you several years. Here’s the catch: you don’t know how any of these flavors taste.

Picking one at random seems like a bad idea, what if you buy a bucket of “Web Designer” ice cream and hate it?

Instead, a much better idea is to ask for tasters. Experiment! Try some “Data Science” ice cream. Ask for a taste of the “Distributed Computing” special. Take a deep dive into the “Introduction to Econometrics” sundae. As you try more of these flavors, you begin to develop a sense of what you like, and equally importantly, what you don’t like. What this translates to in real life is getting ‘tasters’ of your options. These tasters are in the form of courses, independent projects, online research, and reaching out to people who have been working in the field you are considering.

By asking for these ‘tasters’, you learn a lot more about yourself. Your likes, your dislikes, your interests, and a lot more. The end result is, you walk out with a tub of ice cream you know you will enjoy.

“Let go of certainty. The opposite isn’t uncertainty. It’s openness, curiosity and a willingness to embrace paradox, rather than choose up sides.”

- Tony Schwartz

When I graduated with my Bachelor’s degree in 2019, I thought I was going to walk out with a tub of Embedded Systems ice cream. Instead, after taking a great Computer Architecture course during grad school, I realized I enjoyed it a lot more. Had I not taken this course, I wouldn’t have known what I was missing out on. This also leads to an equally important side point that I failed to see as a college freshman: “What do I do with my life” is a flawed question! It assumes that adulthood is this monolithic, long, monotonous journey containing one single activity or job, but it isn’t! If Julia Child can be an extraordinary chef while also being a US spy (this is true), you can do different things too! I am a hardware engineer by day and musician + writer by night. Let go of any fear that you are ‘locked in’ to your choices.

At the end of the day, if you find yourself feeling anxious about not knowing what you want to do and not knowing how to make the decision, please remember that you are not alone! This is the norm, and I’m a big fan of experimenting and broadening my horizons before I make a decision. Study broadly and without fear, and you will end up with multiple flavors of ice creams - all of which you know you enjoy.

See you next week for a new post.

Thanks for reading! You can always email me to chat about this post - or anything else.

As is true for any advice or counsel you ever receive: Y.M.M.V! Your mileage may vary. Some advice can be a vice. Feel free to take what you can use, and leave the rest. There are no rules.

I recently graduated from a Master’s program. This signals the end of my formal education (for now?)! At this age, most of my friends are also finishing up college and getting ready to enter the workforce. Given this trend of transitioning from formal education into beginning our careers, most of our conversations center around how starting a career is going to be different when compared to formal education. This is a post about what I think the key differences are between the worlds of formal education and career development, and how I plan on changing my approach to stay afloat.

Disclaimer: I’m the least qualified person to be talking about this. This post is entirely speculative and I’m sure things don’t actually work this way. I just wanted to put my thoughts out there.

The way I see it, formal education is like being plopped into a river. You go where the river takes you. This is perfectly fine, because at the age where you enter formal education, you probably are not intelligent enough to make your own decisions. You probably aren’t intelligent enough to tell the difference between a spoonful of food headed your way and an airplane either (if you are a 2 year old who can do this, please contact me).

This isn’t to say that you never get to make your own decisions: every now and then there will be a fork in the river, and you will need to make a decision. Think of situations where you had to decide what you wanted to go to college for, or when you had to declare your major. Although these are decisions you are making, they only lead you into another stream in the river, where you, once again, follow the flow.

The situation so far can be summarised this way: there was always an end goal in mind, (example: getting a degree, scoring an internship, etc) and you followed the flow of a river to get there. The river is the ‘template’ or a set of proven steps you could follow to achieve said goal.

Now that formal education is over, the situation is different. It’s as if the river has led me out to a massive open field. There is no real flow, I can go where I want, I can do what I like, and I have the power to make all my decisions.

I am not used to being in such a situation, and I’m beginning to realise that I now have to think critically about how I will approach this open field. In order to do this, I first need to understand the key differences between this situation and a go with the flow situation I was in until a month ago.

So, how is this situation different?

1. This is a long-haul thing

Formal education lasts around 21-22 years, but is actually broken down into many 4-5 year blocks (primary school, high school, college). It’s a structured system. A career path, on the other hand, is (on average) a ~30 year stretch. The key takeaway here is that your ‘end goal’ will keep changing and shifting. Maybe after a year of being a mechanical engineer you realise that you enjoy management. Your goalposts will keep changing as you change, and as you learn more about yourself and the industry you’re in.

2. You are in full control

Outside of ensuring your financial security, you now have very few obligations. You can choose to switch careers, you can choose to turn down a promotion, you could even choose to start your own company. The possibilities are endless, and this seems like an overwhelming amount of control,

Those are… major differences. How do I change my approach to deal with these characteristics?

Starting with the fact that this is a long-haul situation, I have 2 thoughts.

First, given that the end goal isn’t going to be fixed, it might be a good idea to switch from a goal-oriented mindset to a behavior-oriented one. Here’s what that means: there is nothing wrong in setting a goal of scoring a promotion, but maybe after 6 months at the job I may realise that I simply do not want to continue working in the current team. Instead, setting the intention of learning as much as possible from the people and industry around me makes much more sense. A few months down the line, I will gain skills, experience, and I will be in a much better position to set a goal.

Secondly, it’s probably a good idea to get comfortable with uncertainty. As I start a job, I know very little about the industry, the work, and whether I will enjoy it. I don’t want to be making any decisions at this stage. It makes much more sense to wait, get some more intel, and make decisions further down the line.

Next, the overwhelming amount of control. Yeesh. You can walk wherever you want in the open field that is career development. You can lock yourself into a job and rise up the ladder, you could sample many things and decide what you enjoy best, you could say ‘to hell with it’ and start your own venture. Having so much control and zero ‘default flow’ means it’s really important to be intentional. The field is huge, and you want to know why you are heading in a certain direction rather than wander around aimlessly.

I also want to experiment. When I first joined Cornell, I came in with the intention of studying Embedded Systems. I thought I knew exactly what I wanted and I didn’t think I could enjoy anything more. I was (wait for it) wrong. I ended up taking a couple of courses in computer architecture that completely changed my mind. Embedded Systems never stood a chance. Point being, you don’t know what you really want until you’ve tried several things. Career development is a long road, and I do not wish to tie myself down until I’ve had the chance to experiment with options.

The idea is to try something, get feedback (from yourself and people around you), adjust course, and try again. The biggest thing I will do now is ask for advice. From friends who have been in this situation before, from people I will have the chance to work with, and of course, from my parents.

So, where does this leave us?

I’d like to state again that this is purely speculative. I have no idea what I’m talking about, and these are just thoughts. I will be taking my own advice on learning and getting constant feedback and changing how I perceive career development and my approach. This is just my initial mindset as I start my career, and things will change, but in my opinion, this is a good way to begin.

Let me know if you think this sounds familiar to you or if you think things are different (I am 100% sure that they are). Do you think I am over simplifying/over complicating the situation? I certainly think I am. Let me know!

This post is inspired by Tim Urban’s post about career paths.