
## The TLDR

1. Build **SOMETHING**. Just start. 

2. Need an idea for what to build? Find a **problem** that bothers you (that you can solve with code) and solve it. Build a lil script for yourlself. _**Be your own first user**_.

3. Use existing tools as much as possible. Do not reinvent the wheel.

    - Idea Generation: ChatGPT, Notion AI
    - Frameworks: React / NextJS, Vue
    - Database & Auth: Supabase, Firebase

4. Tech stack doesn't matter. Pick what you're comfortable with. Try something new. Who cares, there is not wrong answer (except PHP, that's always the wrong answer)

5. Pick something that is completeable. My own version of the [Power law](https://en.wikipedia.org/wiki/Power_law) says that 90% of projects that go longer than 2 weeks will die. 

6. Build **SOMETHING**. Just start.

---

If you've made it to this blog post, :tada: welcome! Ideally, you're here because you're early in your career (or are a student), and want to get some insight into building side projects. 

## Some Backstory

After reflecting on my time spent hacking away on random shit in college, _**side projects built the foundation of my career**_.

You can take a look in the [About](/about) section, but the TLDR is that I was _**very**_ busy as a student in college. Although I was a late bloomer (first exposure to coding in Spring of Freshman year), after getting a taste of software engineering, I was set on building a ton of random stuff. Some early projects that I remember were:

- very basic UI wrapping logic that was normally a very manual task (getting Addresses and ZIP codes based on school name), which was used for an Esports & High School data aggregation project
- simple SMS bot for audience members of a pitch competition to interact with during the pitch
- (with a group of people) attempting to build an LCS match analysis tool
- a from-scratch emoji selector

<sub>(among other weekend scripts, hackathon projects, oh, and like, the rest of college lmao)</sub>

Notably, none of these were for any class. I built all of these because I was either a user, or it helped to solve some sort of problem that myself or friends were running into.

I spent nearly every free weekend morning / afternoon I had in a coffee shop working on stuff. It was never glamorous. It was not always productive. There were definitely some frustrating moments. But goddamn, _**I absolutely loved it**_.

There was always a new, interesting problem to solve. There was always an exciting piece of tech to try out, or a new update of React to play with. Don't get me wrong &mdash; this maniacal persistence of non-acedemic things definitely took a hit on my GPA. I wasn't terrible in school, but I also wasn't the best. I graduated from UW with a 3.3 GPA. 

Afters literal years of this dogged consistency, I started actually being able to ship coherent, good product. Not amazing, but enough to get by and go from idea to public URL.  

And from there, the rest is history. Buidling more projects turned into getting a chance to build a startup. That (very luckily) turned into getting acquired eventually. And now I spend my time enjoying work and hacking on random stuff for fun (like [resume.lol](https://resume.lol)).

## Step 1: Get Started

The first step of this framework is to build something, anything! Whether it's a solution to a problem you've been facing or an idea that you just can't get out of your head, the goal is to create something that you or your friends could use. By actually building something, you're taking action, gaining experience, and improving your skills. Don't stress about the end result, just have fun and enjoy the ride. Focus on learning, experimenting, and getting in a creative headspace. If your first idea ends up being shit, more ideas will naturally flow _**after**_ getting started.

## Step 2: Use Existing Tools

Secondly, your goal should be to use as many existing tools as much as possible. This could include AI tools to generate ideas (such as ChatGPT or Notion AI), frameworks to help build your project (such as React, NextJS, Vue, etc), and database solutions to handle database and authentication responsibilities (such as Firebase or Supabase). Using existing tools can save you time, effort, and frustration, and help you focus on what really matters: your project.

There really is no reason to reinvent the wheel here. Unless of course, your project is to reinvent the wheel, in which case, go ham on it. 

## Step 3: Tech Stack Doesn't Matter

Third, remember that the technology stack you use for your project doesn't matter that much. Sure, some technologies are better suited for specific tasks, but at the end of the day, they're just tools in a toolbox. So, don't be afraid to use something you're unfamiliar with, as it can be a great opportunity to learn something new and expand your skillset. Sometimes you can use a screwdriver to hammer in a nail. yolo

## Step 4: Pick Something Completable

Fourth: pick a project that is completable. You don't want to start a big, complex project that you won't be able to finish. Instead, aim for something that is achievable and can be completed within a reasonable amount of time. This way, you'll be able to finish what you started, feel a sense of accomplishment, and move on to your next project with confidence.

Ideally, pick a project that you think will take like 2 weekends to complete. If its longer than that, then following a rough [Power law](https://en.wikipedia.org/wiki/Power_law), 90% of projects that go longer than 2 weeks will die, in my personal findings.

## Step 5: Ideas to Get Started

Finally, just _**get started**_. That is all! Good luck, get out there, and start building!

---

Here are some ideas to get you started: 

- scraping data on the internet with Puppeteer and Node or Python
- building a Discord bot with JavaScript or Python
- developing a website with React, NextJS, or VueJS. 

:v:


How I think about and recommend building side projects for students and early-career professionals

Thoughts on building Side Projects


When I revamped by personal site, I used [Lee Robinson's site](https://leerob.io) as inspiration. One of the things I liked most that his site has is view counts on the articles that he has written. I wanted to have the same. 

![A screenshot of Lee Robinson's website](/images/post-content/simple-analytics/leerob.png)

Researching a bit and looking into the repo, at the time, Lee was calling the Google Analytics API directly from the NextJS API routes. 

At some point in time, I saw [Pieter Levels tweet](https://twitter.com/levelsio/status/1094844599296712705) some of his graphs for his websites and it the data was collected through Simple Analytics. 

After comparing the documentation and API references side by side, I decided to go with Simple Analytics because the API documentation seems far more straightforward, and many browsers and adblockers shouldn't block Simple Analytics, especially if I am using a self hosted version of it under `sa.evan.gg`. Although Simple Analytics is a yearly subscription, I figured the lack of headaches and dev annoyance would far outweigh saving $100. 

Simple Analytics also allows you to track data on unlimited sites with your subscription. That should be great when I launch more side projects :smile:

It was super fast to get up and running, and voila, I have view counts on my pages too. Thanks for the inspiration Lee!

```jsx
// Simple NextJS API route to fetch the page views!

import fetch from "node-fetch";

export default async function handler(req, res) {
    // pages = 1 or many slugs to query
    const pages = req.query.pages;
    const headers = {
        "Api-Key": process.env.SA_API_KEY,
    };

    if (!pages) { ... }

    const url = "https://simpleanalytics.com" +
        "/evan.gg.json" +
        "?version=5" +
        "&info=false" +
        "&start=2021-05-10" +
        "&fields=pages,pageviews" +
        `&pages=${pages}`;

    const response = await fetch(url, { headers }
        ).then((r) => r.json());

    if (!response?.pages) { ... }

    const pagesResponse = response?.pages
        .map(({ value, pageviews }) => {
            return {
                path: value,
                pageviews,
            };
        });

    res.status(200).json(pagesResponse);
}
```

The dashboard is pretty sick!

![A screenshot of some data from the dashboard](/images/post-content/simple-analytics/data.png)


Simple Analytics is a delightful analytics tool

Simple Analytics is Great


TLDR: I bought a Raspberry Pi, SSH into it, and write code and various scripts. I use the VS Code Remote Explorer to open up the files on the Pi as if they were on my machine! I provide a quick guide on how to set it up!

I bought a Raspberry pi over the 2022 holidays. My inspiration for doing so was a mix between wanting to have a small computer to run periodic automations, wanting a fun project that I can hack on with whimsy, and removing the irritation for paying $5/mo for cloud compute for what would essentially be the same thing as a Pi. 

Fortunately, I was able to get one of the [Raspberry Pi 4 8GB kits](https://www.amazon.com/dp/B08B6F1FV5?psc=1&ref=ppx_yo2_dt_b_product_details)! Even though it came with a 128GB SD card, I had a 256GB card lying around that I used instead of the one from the kit. 

Setup was actually rather easy — if you set up as well, I'd recommend using an ethernet cable since downloading the OS over Wifi is pretty slow. 

So here's a simple guide for setting it up:


0. Before you begin, I assume you've already setup your Raspberry Pi and have connected it to a monitor / keyboard / mouse as per the setup instructions that came with your Pi. You'll need to have it connected to a monitor for the next step.


1. Enable your Raspberry Pi to receive SSH connection over your local network. [I used this quick guide](https://www.raspberrypi.com/documentation/computers/remote-access.html). This is a pretty straightforward guide on how to enable your Raspberry Pi to be accessible via SSH within your ***local*** network. If you want to make your PI accessible ***outside*** your local network, you'll need to do some [additional steps](https://forums.raspberrypi.com/viewtopic.php?t=20826). You'll also want to write down the local IP address, which you can find using [this guide](https://helpdeskgeek.com/networking/what-is-my-raspberry-pis-ip-address).


2. Via your command line, SSH into your Pi. should be something like `ssh pi@192.168.1.X` where X is likely to be different based on your local network. It also probably depends on your router as well. You can learn more about that [here](https://networkengineering.stackexchange.com/questions/5825/why-192-168-for-local-addresses). You want to make sure that you can access your Pi from the device you want to use VS Code Remote Explorer.


3. [Optional] After you connect via command line first, you can add your machine's public ssh key to the `authorized_keys` file so you don't need to put in your password each time! [This guide](https://askubuntu.com/questions/46424/how-do-i-add-ssh-keys-to-authorized-keys-file) should explain how to do it easily. This is nice to do because otherwise VS Code would prompt you to put in the password each time it wants to connect via SSH. This is great if you want to SSH into your Pi from multiple computers (I use both my personal Mac and gaming PC to SSH in, depending on what I'm feeling).


4. Add VS Code Remote Explorer Plugin

![searching for the plugin](/images/post-content/pi-vscode/2.png)

![preview of the plugin](/images/post-content/pi-vscode/1.png)


5. Add your Pi! You can either do this by editing your `~/.ssh/config` file to add it as a host, or manually adding the Pi as a host via the UI in VS Code.


<figure>

![ssh targets dropdown](/images/post-content/pi-vscode/3.png)

<figcaption>
  Select SSH Targets
</figcaption>

</figure>


<figure>

![config screenshot with host info](/images/post-content/pi-vscode/config.png)

<figcaption>
  Add the SSH Host info to your SSH config
</figcaption>

</figure>

<figure>

![plus button to add host](/images/post-content/pi-vscode/replus.png)

<figcaption>
  Or you can manually add it with the "+" button under the SSH Targets dropdown
</figcaption>

</figure>

6. Connect to your host and you're done!


<figure>

![open the folder](/images/post-content/pi-vscode/reopen.png)

<figcaption>
  Click on the open folder button and then select the location you'd like to open up the file viewer
</figcaption>

</figure>

<figure>

![preview of working code](/images/post-content/pi-vscode/redone.png)

<figcaption>
  And now you can have an entire workspace accessible to you at any time on your local network!
</figcaption>

</figure>

7. [Optional] Generate an ssh key on the Pi and add it to your Github, so you can read and write to your repos from your Pi.

Happy hacking! Perhaps in a future article I'll write about what I'm using my Pi for. Let me know if there's anything interesting I should do :smile:


Access your Raspberry Pi from the comfort of your favorite machine via SSH and VS Code

Raspberry Pi and VS Code Remote Explorer (via SSH)


Almost everyone has had a side project they've worked on and eventually left behind. Software Engineers are no exception. I am certainly not an exception either.

Throughout the years I've been coding, I've almost always had a side project that I've hacked on to pass the time. Whether for learning new tech, pursuing a crazy business idea, or satiating a creative spur, I've almost always had a side project to keep my IDE warm.

Tonight &ndash; after being disappointed that no one was online in League &ndash; I opened up my CLI wistfully, not certain what I should work on. Should it be one of the 3 ideas I've been bouncing around in my head? Should it be the 2 half-baked projects I've been nursing?

Navigating to my `~/code` directory, I habitually typed `ls` and then hit enter. Then it hit me. `~/code` was _basically_ my side project graveyard.

![Screenshot of home directory](/images/post-content/side-project-graveyard/home-directory.png)

_**UGH.**_

Actually... Seeing all of those in one place is kinda cool. Slightly nostalgic. Slightly sad. I wonder if other people would want to see this.

Wait a minute... I might not be the only one! What if... what if I made a side project where people can share their dead side projects! Let me check to see if a domain is open!

![Screenshot of home directory](/images/post-content/side-project-graveyard/domain.png)

Sweet, we're good to go. Let me bounce this idea off of a few people first, ideally those who have had side projects, and especially ones that have died.

Then, I'd need to cobble together my personal boilerplate, decide if it should be anonymous or if I need accounts, and then...

_**UGH.**_

This is going to turn into another dead side project, isn't it? Fuck.

You know what would be cheeky? If I wrote a blog post detailing all of my thought process, and how it would have ended up as a dead side project within itself. Meta innit?

Well, damnit. I wanted to share these side projects via a cool site I made, but I guess a blog post will do as well.

So without further ado, here is a somewhat comprehensive list of my dead side projects.

#### Legend

:bulb: = mostly just an idea

:computer: = mostly just code

:ship: = actually shipped something

#### Side Projects

(oldest to newest)

- :bulb: CSGO pro match analysis - to be used for informed skin betting, of course
- :ship: Climb.gg - programmatically analyzing pro League of Legends matches (not mine, but I worked on it)
- :computer: EsportsEDU - non-profit to engage K-12 students through competitive video games and educational content
- :computer: RA tool - I made a little tool to help me be an RA in the dorms
- :ship: meme.dating - tinder, but match based on meme preference
- :computer: Requaint - personal CRM
- :ship: noni.menu - AR food menu app
- :ship: qwerty.gg / buildspace.io - teaching kids to code through video game examples
- :ship: Kanga - not really a side project, but I could never forget you :heart:
- :bulb: ShakerKit - bar-in-a-box kit to build out your home bar. equipment, ingredients, liquor
- :ship: CafeList - yelp / nomadlist, but for cafes. Gotta get the right vibe, yo
- :ship: ezclap.gg - http://niceme.me but for EZClap
- :bulb: producthunt.gg - product hunt, but specifically for gaming products
- :computer: i'd pay for that - a marketplace for ideas, vote saying you'd pay for something, and then the maker that makes the idea can buy a list of first paying users
- :ship: domainh.ax - site that looks up available domains
- :ship: hydrohomie.xyz - service that texts you reminding you to drink water
- :bulb: code snippet sharing service - be able to share code snippets with peers super easily
- :bulb: emojidomains - idk something to do with emoji domains
- :computer: domain trading cards - see your domains in a page as trading cards
- :ship: zentab - a beautifully animated new tab
- :ship: resumdx.com - keep your resume as a markdown file and generate a nice PDF for it every time without needing to do super weird Microsoft Word formatting
- :ship: lofi.vote - lofi music with presidential result twitter embedded
- :ship: meld - reddit/hackernews/designernews but merged into 1
- :bulb: keeb.page - place to share what keyboard parts you own / marketplace to buy/sell
- :computer: use old macbook and puppteer and cron jobs to scrape random websites - idk I feel like I should collect my own datasets or something


So yeah. Most of em are dead, but I learned a lot along the way.

:v: peace


Gone but not forgotten. Here's a list of my side projects that never grew old.

Side Project Graveyard


Over the past couple of years, I've been asked countless times by peers about how to land a job in tech. Whether it is your very first job at an internship/new-grad level, changing roles within tech, or the level above in your current career path, I give roughly the same advice.

A disclaimer: This method takes a considerable amount of work. As the old adage goes *"Luck is when preparation meets opportunity"*. This method's goal is to maximize both preparation and opportunity in your job hunting journey.

Another disclaimer: This method was initially developed for Engineering-related roles, but can easily be applied to non-engineering roles as well.

## The Barbell Method

In my time applying for jobs and positions, I have followed this approach that I have coined the "Barbell Method". Just like an actual barbell, what will lift you to success is focusing on your job applications in a balanced, yet focused way.

![Barbell](/images/post-content/barbell/barbell.png)

We can call one side of the barbell the "Many Side", and the other side of it the "Focused Side". With this method, you want to keep the balance of your time, energy, and focus roughly the same between the two.

Applying to jobs, landing an interview, and getting an offer is hard. It is hard because there are many variables out of your control that happen behind the scenes, with little to no insight as to what you can do to improve. Though it is hard, it is not impossible. Let's lay some ground work such that we're all on the same page.

Assumptions:

1. ***Applying online is a numbers game.*** Assuming you are applying for a role that you quality for, the more applications that are submitted, the more interviews you will land. Even if the conversion rate is (for example) 5%, submitting to 100 companies online should yield 5 phone screen interviews. Submitting to 200 companies should yield 10 phone screen interviews.
2. ***Interviewing is hard, so you want to maximize the chances that your interviews will be successful.*** You can do all the LeetCode, HackerRank, or CTCI you want, but at the end of the day, getting reps in the interview room with companies that you don't really care about is your best way at maximizing interview success. It sucks to say this, but it is the reality of the game if you're trying to land your dream job. Interviews are fucking tough. They're stressful to prepare for, they're stressful in the moment, and they're stressful waiting for the results. The best way to mitigate this is to normalize interviews and get comfortable with the process.
3. ***Companies want to hire people that ~~give a shit about them~~ are passionate.*** If you're a hiring manager with two equally skilled candidates, and one cares deeply about the company and has been a customer or user of the product for years while the other one did not express that, chances are pretty damn good that they will hire the more passionate person. I have personally made a hiring decision like this, and other employers will too.
4. ***Referrals matter A LOT, especially with decision makers.*** Having the hiring manager or engineering manager bring a applicant lead to a recruiter is going to have so much more weight than applying online. That being said, getting an acquaintance that works at the company (primarily on a different team or in a lower level position) to refer you won't help out a ton. However, having the decision makers refer you makes a world of a difference.
5. ***You have at least 1 dream company, ideally 2-3+.*** These are companies that you've wanted to work at for years, companies that build a product you use daily, or companies where you really vibe with their mission. Assuming you're reading an article about getting a job at your dream company, then you should at least have one.

With these assumptions in mind, let's dig into it!

## The Many Side

The state of even landing an interview in 2021 is kinda tough. Recruiters are abound, aggregate job boards are filled to the brim, and company "Careers" pages are flush with job listings. And even though this is the case, landing an interview is still a numbers game.

Why?

Well there are a handful of moving pieces that actually go into the job hunting process. First and foremost, there is the ATS (Applicant Tracking System). These systems, while necessary for recruiters and HR, are awful for candidates. The systems parse the words in your resume, looking for keywords to match against job descriptions, checking for similarities and if you qualify. Even if you're applying for jobs that you're fully qualified for, there is a very high chance that the ATS will automatically rule out your application for some unknown reason.

Another reason is that recruiters are picky! If you're getting dozens or hundreds of resumes a day, you're going to have to make some decisions about who to let through and who to not.

Given the status quo, the first side of the barbell is the "Many Side". The goal of the "Many Side" is to use the numbers game to your advantage.

Every applicant has some likelihood of an application getting accepted to the phone screen portion. No one really knows what their true percentage is, but similar to rolling a dice, you can try hundreds of times and derive what your initial success rate is.

So given Assumption #1, the number of interviews is always going to increase based on the number of applications you submit (duh). The unfortunate reality of this though, is that, very likely, everyone's starting percentage is going to be below 10% (and probably even below 5%). This means that you're going to be submitting a helluva lot of applications to a helluva lot of companies (at least 100 if you want a good chance at landing an entry job).

### Actually doing the "Many Side"

Cool, so now you understand the premise, so let's get into how you actually go about doing this in a systematic and scalable-ish way.

First, you're going to need a spreadsheet of some kind. The goal of the spreadsheet is for you to keep yourself organized throughout this process.

<figure>

![Google Sheet](/images/post-content/barbell/google-sheet.png)

<figcaption>
  Spreadsheet Internship for Summer 2017. ~70 companies were on this one. This one is pretty shitty.
</figcaption>

</figure>

<figure>

  ![Smartsheet](/images/post-content/barbell/smartsheet.png)

  <figcaption>
    Smartsheet for New Grad starting after 2018 Graduation. ~120 companies on this list. This one is much better, but
    still not perfect.
  </figcaption>

</figure>

Your spreadsheet should accomplish the following:

- Keeps track of the companies you've applied to, and the ones you're planning on applying to.
- Keeps track of the status of submitted applications.
- If you have multiple offers, it lets you keep track of the details for comparison
- Incentivizes you to continue chipping away it it. It definitely feels nice to go and toggle 3-4 rows to "submitted" at a time

I should note that with this approach, you ***do not*** want to apply to your dream company via online submission. Do you only want a 5% chance of getting a phone screen? Not really.

If done right, you can generate a handful of interviews for yourself with this approach. In an ideal world, you're also getting a handful of onsite interviews and racking up experience. The interviews should become easier and you should feel more comfortable in an interview setting. And, if you're lucky and skilled, you'll have multiple offers to bounce around each other, generating yourself leverage!

### Finding Companies

After going through all of the companies that you can recall off the top of your head (FAANG, Airbnb, Uber, Lyft, Robinhood, etc.), then the question becomes "How do I keep adding companies to this list?"

Here are some ideas I've used:

- Look at all the apps you use on your phone, include all the companies you find here. Note: a few of these may be your dream company(s), so save those for the "Focused Side".
- Any website that you navigate to, make it a habit to scroll to the footer and see if there is a "Jobs" or "Careers" link. If they have a role you're looking for, include them!
- Lists. "Top 100 companies to work for 2021", "Best 25 companies to work for in [CITY]", "50 Best Companies for Women" etc. Find any list you can get your hands on and scroll through all of them. Note down any that look remotely interesting, or that you could work at.
- Job Boards.
  - [AngelList](https://angel.co/jobs)
  - First workday of the month on HackerNews (ie [Ask HN: Who is Hiring? May 2021](https://news.ycombinator.com/item?id=27025922))
  - [RemoteOK](https://remoteok.io/)
  - [ProductHunt Jobs](https://www.producthunt.com/jobs)
  - [Indeed](https://www.indeed.com/)
  - If you're a student, there should be a career portal you can go find

The goal for adding everything to a list is that you have a massive backlog of companies that you can systematically go through and apply to every day. Have a 30m break? Awesome! Submit 2 applications. Watching some TV at night? Cool, work through a few applications each episode. Like playing video games? Make it a habit to submit 1 application after each win, 2 after each loss.

Turn it into a habit to ***feel good*** about applying. Toggle that row to "Applied" on your spreadsheet and know that you're playing the numbers game to the best of your abilities.

## The Focused Side

The "Focused Side" of the barbell is what I would imagine if someone social-engineered their way into an interview.

![Social Engineering Definition](/images/post-content/barbell/social-engineer.png)

So while not evil or fraudulent, the "Focused Side" approach definitely requires deliberate planning and execution.

Given Assumptions #4 and #5, we want to make the most out of applying to your dream companies. Remember, the most important part is landing an interview. If you've done the "Many Side" well, then you should feel good about the interview process and do well in the moment. Because the hardest part is landing the interview, then you should be able to communicate how awesome a fit you'd be at said company once you're in the room. It's far easier to communicate passion and excitement in person or on a video call than via resume or email.

### Actually doing the "Focused Side"

Cool, so all that we have left is Assumption #3. You need to show your passion.

How the heck do you do that? How can you possibly stand apart from everyone else?

Simple: _**Do something cool.**_

Come up with a new product, feature, tool — anything — that you'd like to see the company ship. If you want to work at Discord, come up with a feature that can be solved roughly with a Discord bot and build it. See if there is something you can do with their data or API. This is the part where being passionate comes into play, and why you're only doing this for a few companies. If you're passionate, you should be able to come up with some unique idea :smile:

This does not apply to only engineering. If you're applying for a design role, redesign a feature you are annoyed with. If you're applying for a product management role, write up a spec for something you'd like to see the company work on. If it is some completely other role, show them your Masters Thesis (if it applies of course), do a faux marketing campaign, update the copy on their landing page using GPT-3. Do something cool. ***Do the work as if you were working there already!*** You don't need to an exorbitant amount of time on this, maybe a handful of hours over the course of the week. The goal for this isn't to have the thing you make be absolutely perfect. ***The goal for this is to show that you're passionate about the company that you spent some of your free time critically thinking about how you'd bring value if you were to join.***

Now that you have something that you're proud of and actually want to see take effect there, then find the person at said company that would care about what you did, or at least be open to giving you feedback. This can be done in a few different ways. LinkedIn could work, but finding the specific team someone works on might be tricky, because LinkedIn search kind of sucks. You can see if the company department blogs, if they have them, have particular authors that stand out to you. Often times these are the engineers, designers, PMs, managers, leads, etc that work on the product. Normally their name and LinkedIn or Twitter handles are there. And the last ditch attempt, if it is a smaller company, is to see if they have a "Team" or "About Us" page on the website that might have the employees and their roles.

The goal of this step is to find someone at the company that is twofold:

1. They are a stakeholder in the work that you just did. It applies to their job and they are able to easily see the same value that you do in your own work
2. The person is contact-able. Twitter DM, LinkedIn message, email, by any means.

Once you identify this person, reach out to them and show off your work. Get their thoughts and ask them for feedback. ***It is important to note that in this interaction, you are not looking to get a referral, you simply want to interact with them and get feedback on your work.*** This can either be over DMs or email, but ideally you get them in a video call, or post-COVID times, you're able to set up a quick coffee chat with them. Whatever fits for their schedule, just be flexible and don't make it weird.

After you chat with them about the cool shit that they do at your favorite company and the cool shit that you did, take their feedback ***and implement it.*** Spend the next few days, the next week, whatever it may be, and make the changes to the thing you put together. This is imperative. This shows that you listened and iterated on the feedback.

Once you're satisfied with the changes, hit the same person up again. Tell them that you're implemented their feedback and would like to show them again.

Once you're in that conversation and its going well, at the end of the conversation you can ask them if their team has any open roles that would be a good fit for you. If they do (fuck yeah!) ask your contact what the best way to apply for that role would be. This is where you can ask to see if they're able to refer you, or to talk to the hiring manager about you.

Getting yourself a key stakeholder / decision maker on the team to be a fan of you is suuuper important. Recall back to Assumption #3. If there are 2 awesome candidates, but one clearly cares deeply about the company, enough so that they worked on something in their free time, sought out feedback from someone on the team, and implemented the feedback, then the decision to hire the passionate person is a no-brainer.

It is important to note that you should be as genuine and humble as possible interacting with your dream company(s). There should be some sort of reverence and respect that your interactions exude. While the "Focused Side" is methodical about its approach, you should not feel bad about doing this. You put in the work, you truly want to be there, and you're genuine. In a world where you're competing against a sea of other applicants, it is necessary to change the paradigm and set yourself apart from everyone else.

## Wrapping Up

I wanted to keep the scope of this article focused to ***landing many interviews*** at various companies and ***landing an interview at your dream company(s)***. I don't cover anything about negotiating or doing well in the interviews. There are plenty of resources already that exist that provide far better information than I could ever. If you have any resources that you would like me to include at the bottom of this article that you find useful, let me know and I'll include them here and credit you :smile:

If you've found success using this method, I'd love to know! (And if you want to be included in this article as well, I'm happy to put you here).

If you have comments, questions, or anything else (like typo fixes), feel free to DM me on Twitter at [@evan_frawley](https://twitter.com/evan_frawley) or [hit me up on LinkedIn](https://www.linkedin.com/in/evanfrawley/).

Good luck; have fun!


Job hunting sucks. Let's engineer your way into your dream job!

How to land a job at your dream company


About a year ago, I found Next.js and Vercel and immediately wanted to rebuild my personal site on it. Building it out was super fun! I followed the [Next.js tutorial](https://nextjs.org/learn/basics/create-nextjs-app) and had a blast learning the languages, not to mention the newfound power of using MDX to easily create blog posts and web pages &mdash; which before would have easily taken far more time wrapping everything in `<div>`s and formatting it all nicely.

However... the final result a year ago left much to be desired. I wasn't happy with how it looked and felt, which is probably why I only wrote one _**real**_ post over the past year.

![](/images/post-content/updated-site/old.png)

It was honestly pretty bad. I chose some whack color scheme, the `<code>` elements were styled poorly, the blog posts themselves did not have reader-friendly formatting, and, perhaps most egregiously, there was no light/dark mode toggle.

So I decided I would clean up my personal site and make it a place where I would be proud to publish random thoughts and articles in perpetuity. After all, if I am a full-stack (frontend leaning) engineer, my personal site better be goddamn beautiful.

A few weeks prior to revisiting it, I finally tried out TailwindCSS while hacking on a [side project](https://meld.so). The delay for trying out Tailwind came from an association of Tailwind to Boostrap. 5 years ago, I tried out Bootstrap and _**absolutely hated**_ it. Bootstrap did not interface well with React, and I was unable to customize my components with surgical precision. For at least a year up until this point, I had wrongfully classified TailwindCSS in the same bucket as Bootstrap &mdash; and boy was I wrong.

TailwindCSS made it so freakishly easy to whip up a new UI, with so meany great features coming right out of the box. Dark mode toggling, typography, lovely mobile responsiveness.

Within a few hours of hacking on my personal site, which was previously built with [theme-ui](https://theme-ui.com), I had a refreshed UI made with Tailwind and looking fly.

I'd like to take a moment to note as well that I was heavily influenced by [Lee Robinson's beautiful personal site](https://leerob.io) while building this updated site.

So alongside bringing the UI up to speed with TailwindCSS, I massaged the blog post typography to my liking, added in a new code block theme (Material Oceanic, which I use in Webstorm!)m abd whipped up and [About page](/about) that has a neat timeline about all the cool shit that I've done over the years :smile:

So now that this site is updated, I definitely want to start putting my thoughts and learnings down, so that I can spread the knowledge with yall!


A bit about how and why I updated this site.

A much-needed facelift


## The `zsh` aliases that'll turn you into a _"10x Engineer"_

As a software engineer, spending time in the command line has become second nature to me. Doing any work related to `git`? Command line. Running `whois` against a domain to see which asshole took the domain name that _I just came up with_. Command line. Running a local project, `ssh`-ing into a remote box, creating/moving/reading/deleting/renaming files, scraping data with a python script? All command line.

However, with nearly every developer using the command line, I only notice a small percentage of my peers customizing and tricking out their command line to maximize their efficiency. Often times I find myself running the same commands over and over, whether that's for debugging, checking the status of things, or simply my regular workflow. I feel like I can personally whiz my way around my instance of ITerm2 only because I've nailed down my aliases and keybinds.

Therefore, I wanted to share some of my favorite aliases and tricks that have boosted my efficiency over the years.

(First things first though -- I highly recommend using [`ohmyz.sh`](https://ohmyz.sh) and the `robbyrussel` theme.)

#### Navigation aliases

```bash
alias gg="cd ~/code" # goes to my code directory
alias ggo="cd ~/go/src/github.com" # goes to go github source path
alias ggg="cd ~/go/src/github.com/GH_USERNAME/REPO" # goes to a specific project repo path
```

#### Simple Git shortcuts

```bash
# This is the one that I far an away use the most!
# Go back to last branch
alias back='git checkout @{-1}'

# These are great as well
# Git log
alias log='git log'
# Git status
alias gs='git status'
# Git diff
alias gd='git diff'
# Go to staging branch
alias staging='git checkout staging'
# All git branches
alias allbranch='git branch -a'
# Local git branches
alias branch='git branch'
```

#### More complex Git shortcuts

```bash
# Squashes most recent commit up to and including given commit hash
# usage: FIRST: git lot -> find the oldest commit hash you want to include
#        squash COMMIT_HASH
function squash {
  git reset --soft $1; git commit -a --amend --no-edit;
}

# Amend a commit message
# usage: amend "some new commit message"
function amend {
  git commit --amend -m $1;
}

# Typical workflow that I'd have would be on a feature branch to, once the branch
# is ready to be committed to the main branch, I run `squash` and then `amend` with a message
# like `amend "Feature Branch: Feature Name"`
```

#### Docker Shortcuts

```bash
# Get container process
alias dps="docker ps"

# Get process included stopped containers
alias dpa="docker ps -a"

# Get container logs
# usage: dlogs my-container
function dlogs() { docker logs $1 }

# Remove all containers
function drmf() { docker rm -f $(docker ps -a -q); }
```

#### The meta stuff

```bash
# Open this file in VS Code
alias oz='code ~/.zshrc'
# Refreshes zsh profile
alias ref='source ~/.zshrc'
```

Whenever I want to edit my `.zshrc`, it's as easy as running `oz` in the CLI and as soon as I save the file, running `ref` will immediately apply the changes.

And.... Voilà! You now can pick and choose the ways that you can customize and trick out your CLI. Hopefully doing this over the years after making some changes you can cumulatively shave hours off of your development time :smile:

Notes: I was inspired to write this after seeing [this article](https://thorsten-hans.com/5-types-of-zsh-aliases) and learning a few tricks!


There are the handful of zsh aliases that have drastically improved my dev experience

ZSH aliases that will change your life


## This is the initial post of [evan.gg](https://evan.gg)

This personal site is built using:

-   [React](https://reactjs.org) (my perferred method of web dev)
-   [Next.js](https://nextjs.org/) (framework) & [Vercel](https://vercel.com/) (hosting)
-   [theme-ui](https://theme-ui.com) (theme-able, responsive, CSS-in-JS based UI library)
-   [mdx](https://mdxjs.com/) (for posts like this)
-   [next-mdx-enhanced](https://github.com/hashicorp/next-mdx-enhanced) (so I can do some advanced markdown)
-   [prettier](https://prettier.io/) (for my sanity)
-   [MDX Prism Syntax Highlighting](https://theme-ui.com/packages/prism/) (for dank syntax highlighting in my writings)
-   [MDX emoji plugin](https://mdxjs.com/advanced/plugins) (ability to do :smile: and :fire: on the site)
-   [Inter font](https://fonts.google.com/specimen/Inter) and [DankMono font](https://dank.sh) (my favorite fonts)
-   [Favicon.io](https://favicon.io) (generate the favicon)

If you're interested about how I built it, let me know and maybe I'll write about it! :grin:

The source code for this site can be found [here](https://github.com/evanfrawley/evan.gg).


Meta post describing the tech stack of evan.gg

Blog