Category Archives: _Micropost ๐Ÿช

Tiny, short thought. Less polished.

Tips for going to conferences alone

Going to a conference alone can be an intimidating experience, but it’s completely doable (I’ve done it many times). Here are my tips:

Optional: Look people up ahead of time and reach out

If you can, try to research ahead of time people who will be attending the conference and reach out online with a LinkedIn or Twitter message. This might give you a nice head start.

Be friendly, open, and seek out others in your situation

You might be surprised how many other solo attendees are at conferences or conventions. These will be the easiest people to meet as your ‘first friends’ โ€” don’t be afraid to approach and say hello!

Set a goal: Don’t eat dinner alone

If a conference doesn’t include dinner, set an explicit goal for yourself to not have dinner alone.

Actively try to meet people throughout the day, specifically seeking out other solo attendees who might want to get dinner later.

Exchange contact info with people you enjoyed meeting, and float the idea of possibly getting dinner if they don’t already have plans.

Detach politely from uninteresting people

Don’t spend excessively long around people you don’t connect with.

After meeting someone, if you don’t find them very interesting and would prefer to keep mingling, it’s completely acceptable to do so. You can say something like “Well it was great to meet you โ€” I think I’d like to mingle around a bit more. Have a great conference.”

Just try to make one new friend

Don’t set the bar too high for what would make it a successful event for you. For me, if I make even one solid new friend or connection, I consider it a win.

Just try to have one takeaway from talks

This is unrelated to going solo, but like the above tip, I set the bar pretty low for what I aim to get out of talks. If I get even one solid insight, thought, or takeaway, I consider it a win. You’d be surprised how hard it is to get one solid takeaway from some talks.

Volunteer

Volunteering can be a great way to automatically meet people (organizers, other volunteers) and get in contact with well known people in the community.

Make it easy for others to strike up a conversation

You can do yourself a favor by wearing slightly more interesting clothing or accessories than you typically might. For example, for me it might be wearing a shirt for my favorite band. Or maybe something topical for the conference/convention. The goal is to give people something easy to comment one which you can talk about, and help get a conversation going, or keep one going if you run out of things to talk about.

You are the first advocate for your art

As an artist, it’s easy to become disheartened when you make something, publish it, and find that no one really cares.

A mindset that can help you overcome this and avoid becoming jaded is viewing yourself as the first and most passionate advocate for your art.

Your art, with its great potential, can’t speak or advocate for its greatness by itself. It needs someone to do this for it.

And you, as the artist, play this role. Ultimately, no one is going to be a stronger advocate for it than you. At least, at first.

How to build traction for your creative endeavor

Core cycle:

  • Try hard at something (bonus if it’s hard)
  • Share it, enthusiastically, in public
  • Repeat every week*

Bonus: Find likeminded peers and become good friends with them.

*A week strikes a good balance between consistency and workload.


Plus:

  • If it’s not working, shake it up somehow
    • Try different content
    • Try a different format
    • Try a different venue
    • Intentionally try to improve at the craft
    • Imitate people 1-2 steps above you
    • Artistically steal for everything except the key area of creativity & innovation

This advice comes from a decade+ at failing to build traction for my endeavors, with small pockets of success here and there:

  • Then Tragedy Struck (instrumental metal) โ€” Little traction
  • comfort (wave / trap music) โ€” Medium/little traction
  • timestamps.me โ€” Little traction
  • offlinemark (2012-2019) โ€” Little traction (Twitter)
  • offlinemark (2019-2023) โ€” Medium traction (Blog, Twitter)
  • offlinemark (2024+) โ€” High traction (Youtube)

7 steps towards learning something

Here’s my rough mental model around learning things in the world of computer programming:

  1. Never heard of it before
  2. Heard of it, but don’t know what it is
  3. Know what it is conceptually, but not how it works
  4. Know how it works, but never implemented it
  5. Have implemented it, but just for fun, not in production
  6. Implemented something in production
  7. Applied concept creatively in a novel fashion (mastery)

Find your own bugs

Audio version: https://podcasters.spotify.com/offlinemark/episodes/Find-your-own-bugs-e2i15vc

Contributing to open source is a popular recommendation for junior developers, but what do you actually do?

Fixing bugs is a natural first step, and people might say to look a the bug tracker and find a simple bug to fix. However, my advice would be to find your own bugs.

In 2019, I had some free time and really wanted to contribute to the LLVM project in some way. Working on the actual compiler seemed scary, but LLDB, the debugger, seemed more approachable.

I went to the LLVM Dev Meeting, met some LLDB devs, and got super excited to contribute. I went home, found a random bug on the bug trackers, took a look for all of 30 minutes, then … gave up. Fixing some one else’s random string formatting bug simply wasn’t interesting enough to motivate me to contribute.

3 months later I was doing some C++ dev for fun. I was debugging my code and ran into a really, really strange crash in the debugger. It was so strange that I looked into it further and it turned out to be a bug in LLDB’s handling of the “return” command for returning back to the caller of the current function. The command didn’t correctly handle returning from assembly stubs that don’t follow the standard stack layout/ABI, and caused memory corruption in the debugged process which eventually led to a crash.

This was totally different. I had found a super juicy bug and dedicated a couple weeks to doing a root cause analysis and working with the LLDB devs to create a patch, which was accepted.

So if you want to contribute to open source, I would agree with the common advice to fix some bug, but would recommend finding your own โ€” it will be way more rewarding, fulfilling, and a better story to tell.

https://twitter.com/offlinemark/status/1778483168611610940
https://twitter.com/offlinemark/status/1208491737099882496

Why I use 5 different git clients

What if I told you you didn’t have to use just one git client? I use 5, and here’s why:

  1. Command line – Sometimes it’s the simplest fastest way to do something.
  2. Lazygit – Ultra-fast workflow for many git tasks, especially rebasing, reordering, rewriting commits. Quickly doing fixup commits and amending into arbitrary commits feels magical. Custom patches are even more magical.
  3. Fork (Mac app) – Great branch GUI view. Nice drag and drop staging workflow.
  4. Sublime Merge – Good for code review, can easily switch between the diff and commit message just by scrolling, no clicks.
  5. Gitk – Great blame navigator.

One you try one of these GUIs, you’ll never go back to git add -p.

Toxic minimalism

If you’ve ever had a painful move due to having too much stuff, you might have had the urge to become a minimalist to avoid an unpleasant experience like that again.

There’s a lot of good things about minimalism and the philosophy of needing less. In addition to being easier to move, it’s better for the environment, and less costly to have & maintain less things.

But watch out โ€” it’s easy to go too far in the other direction and let the minimalism take on a toxic quality, where you don’t even acquire things that you really would find helpful, and would improve the quality of your life.

If you’re in that position, I’d just remind you that it’s ok to acquire a bunch of stuff, learn what is really valuable to you, then trim things down later. Sometimes to go narrow, you first need to go wide.

It’s worth writing, even if someone else covered the topic already

It’s worth writing, even if someone else on the internet has covered the topic already, because:

  1. Writing helps you understand the topic better
  2. Your tone, communication style, or perspective might appeal more to some readers than the original source
  3. It helps build your public body of work, which makes you luckier

And writing is just an example โ€” replace it with whatever form of self-expression you’d like.

Learning kernel development on hard mode

When I started self-studying kernel development via MIT 6.828 (2018)’s open source materials (JOS OS), I thought I was making my life easier by not starting from scratch. Doing this allowed me to get going very quickly with a base skeleton for an OS, as well as a fully functioning build system and helper Makefile command for debugging with qemu.

That was great, but I’ve realized that there are also many ways I’m doing this on hard mode:

  • Doing it in only 2-3 hours a week
    • This is not really enough time to develop an OS, and is particularly hard for debugging, where it can be helpful to have significant context built up for longer sessions.
  • Live-streaming almost all of it
    • This can be very distracting and make me go at a slower pace than usual, since I try to engage with viewers and answer questons. On the other hand, explaining things helps solidify my understanding.
  • Working with a 6 year old code-base, but using a newer toolchain โ€” which means fighting bitrot
    • There have been multiple cases where the codebase actually got in my way and produced very hard to debug bugs. Also, when I transition labs, it introduces a bunch of foreign code that I don’t understand. It can be difficult to tell if I truly have something broken, or if the new code is in an intermediate state that is meant to yield issues like crashes or assertion failures.