devrel travel looks glamorous from the outside, you see pics like this and think “damn, nice life” but here’s the thing, this job requires you to talk. a lot. workshops, talks, twitter spaces, 1:1s with devs, answering the same questions with the same energy every single time and it only works if you genuinely love it. like actually love explaining how things work to people because if you don’t, you’re just performing enthusiasm for a paycheck. and developers can smell that from a mile away the perks are real. the views are beautiful. but so is the energy it takes to stay “on” when you’re exhausted as uncle ben once told my friend spiderman - with great power comes great responsibility this has to be a passion. otherwise you’re just working to work.

ai isn't replacing engineers. it's exposing how much time we spent fighting friction instead of building. big difference.

your first pull request shouldn't impress anyone. it should exist.

the easiest way to stand out in tech right now: finish things. seriously. the bar is on the floor.

people think open source is about contributing. it's actually about learning how great engineers think. the code is the curriculum.

everyone wants leverage. nobody wants repetition. and that's the differentiator.

the best networking strategy is still being good at something.

most people need consistency, not motivation.

the more ai improves, the more i think judgment becomes the actual moat. writing code is easier. generating ideas is easier. research is easier. execution is faster. but deciding what's worth building? still hard. good taste is becoming more valuable, not less. that's the part nobody can automate for you.

the uncomfortable truth about long-term success: almost nobody gets outworked. they get outlasted. people love talking about intensity. 10 hour days. weekend grinds. productivity systems. but careers aren't built in a month. they're built by showing up for years. the compounding starts exactly where most people quit.

i think the best education in software is still an active open source project. not a course. not a bootcamp. not a certification. a real codebase. you get to see how good engineers structure systems. how they review code. how they make tradeoffs. how they think. most people read tutorials. the fastest learners read production code.

one thing i've noticed about strong engineers: they don't get emotionally attached to being right. they get attached to finding what's right. that's a completely different mindset. one protects the ego. the other improves the system. most career growth is just moving from the first to the second.

the merge button doesn't care about your imposter syndrome. just saying!

every builder eventually learns the same lesson. the work you're most proud of won't be the thing that went viral. it'll be the thing nobody noticed. the tool that saved you 30 minutes every day. the bug you finally fixed. the architecture decision that prevented future problems. the documentation that helped a stranger. the internet celebrates launches. builders remember improvements.

The internet rewards opinions. Reality rewards competence. Choose carefully.

One of the biggest lies I told myself early in my career was: "I'll contribute when I'm good enough." Good enough for what? Good enough according to whom? The truth is that open source doesn't care about your resume. It cares whether your patch improves the codebase. That's it. Nobody checks how many years of experience you have before reviewing your PR. Nobody asks whether you've completed enough courses. Nobody asks whether you feel confident. The code either makes things better or it doesn't. Everything else is noise.

the reason bear markets are valuable has nothing to do with price. bear markets remove spectators. that's it. when nobody is watching, you discover whether you actually enjoy the work. the likes disappear. the hype disappears. the validation disappears. the work remains. that's why some people come out of cycles transformed while others disappear. same market. different relationship with the work.

your dream job is hiding behind a pull request you haven't opened yet.

every serious builder eventually realizes: motivation is a bug.

the internet rewards opinions. reality rewards competence. choose carefully.

A lot of people say they want to contribute to open source. What they actually want is to feel qualified enough to contribute. Those are very different things.