Pinned
Mike Chen
Mike Chen
@chenmike.com
👨💻 CTO and Co-Founder of Motivo 🏠 Dad of 2 💼 Prev: Airbnb, Wealthfront, Google mikechen.io
348 followers258 following225 posts
Mike Chen reposted
Just got off a call with THE Mike Chen. Can confirm, not a coffee chat dud. hahaha JKJK Great "meeting" you finally!! PS my parents shut the air off upstairs and i'm DYING. @chenmike.com #careerswitcher #techcommunity
Mike Chen reposted
Loved the convos this past week on nickyt.live with @chenmike.com. Here’s a short where Mike talks about using AI in his development workflow. Thanks again for hanging! youtube.com/shorts/f06d2...
Mike Chen reposted
And we're live! Come hang with @chenmike.com and me as we discuss their path from individual contributor, to engineering manager to CTO!
Excited to chat with @nickyt.online tomorrow about my journey from IC -> manager -> CTO Planning to talk about all the adjustments I had to make along the way to be successful in each new role Hope you can join us!
Looking forward to chatting with @mikechen.io this Wednesday. Come hang as we dig in to going from an individual contributor (IC), to engineering manager to CTO! https://buff.ly/3PozAaf
Mike Chen reposted
Was very excited to see this amazing piece of work by @samwho.dev come together It's always so impressive to see people take a pretty academic topic like Turing machines and make them so accessible. Awesome visualizations and writing. Well done!
What does it mean for something to be Turing complete? I answer this question, and more, through a series of fully interactive Turing machine simulations! Play, pause, step forwards and backwards, and even write your own Turing machine programs in my latest blog post. samwho.dev/turing-machi...
Mike Chen reposted
Same to @nickyt.online, had a great time chatting today, one of the nicest people in the community! Love his streams, brings in lots of different people about interesting web dev topics. Check it out when you get the chance nickyt.live
Had a great coffee chat with @mikechen.io today. Thanks for hanging and the great convo! ☕ If you aren't already, go give him a follow!
This is such a unique way to learn about history — an interactive map showing historical borders, battles, and people of note One of the most interesting things I've seen on the internet in awhile www.oldmapsonline.org/en/history/r...
terriblesoftware.org/2024/12/04/t... Great read for new managers or anyone thinking about becoming one. Sums it up well: "Success for you is as simple as asking yourself two questions: 1. Is my team shipping? 2. Are they happy? If the answer is “yes” to both, don’t worry; you’re crushing it. 🎉"
Mike Chen reposted
This is a really great starter pack - I found a few people from the old site I didn’t have yet. go.bsky.app/3b9A8JY
TL;DR to this thread, > 2/3s of the responses say they're still using Client-Side Rendering at work, despite so much conversation around Server-Side Rendering and React Server Components A really good reminder that what gets talked about most in tech circles doesn't always reflect market realities
What kind of React app do you get paid to work on (not hobby projects)? - CSR, no SSR - Isomorphic SSR - RSC Again, if you don’t use React at a paid gig, don’t reply. If you maintain multiple, reply with the one that makes the most money (the product, not yourself)
Mike Chen reposted
Josh's courses are on the shortlist I feel comfortable recommending to all frontend engineers. I've been doing this 14 years and I still learned a bunch from both courses. Even if you're a senior engineer and know everything (unlikely), you'll learn a lot about how to mentor and teach effectively.
🏠 I’m having an Open House! This has become a bit of a tradition for me. Every Black Friday, I select a couple of lessons from my courses and make them public for a few days. This way, potential students can test-drive the content and see if it’s a good fit for them! The doors have just opened. 😄
I always tell new engineers to be cautious when using AI for code gen. Even worse than sneaking trash into your code, it hampers your learning. IMO it's hard to learn how to code if you're not typing code into your IDE. I highly encourage asking the AI questions though, that's an amazing use case.
AI arguments? Is this really a hot take? Learning to code in 2025 and beyond, I guess I will say this until someone can change my mind.
5/5 How to do what you love and make good money sive.rs/balance A bit of a philosophical one. Companies can take advantage of the fact that programming is fun, and try to get you to find your meaning at work. This article encourages separating your creativity from your job.
3/5 Speed matters: Why working quickly is more important than it seems jsomers.net/blog/speed-m... Optimizing for speed and efficiency early in my career was a game-changer. I could experiment more, close more tickets, and learn faster. One of the best investments I've ever made.
4/5 Choose Boring Technology mcfunley.com/choose-borin... Cutting-edge tools introduce risk, and need strong justification. If you're new, it's unlikely you'll make decisions about what tools your team uses, but you should understand how they make these decisions. It'll be your turn someday.
2/5 The Trimodal Nature of Software Engineering Salaries blog.pragmaticengineer.com/software-eng... Title says "in the Netherlands and Europe" but applies everywhere. This article will really help you understand the tech job market, which is critical for knowing whether you're being paid fairly.
2/5 (cont) Note: there's an updated version of this article, but paywalled. newsletter.pragmaticengineer.com/p/trimodal-n... The free version gets the main points across, but this newsletter is well worth the subscription.
1/5 Salary Negotiation: Make More Money, Be More Valued www.kalzumeus.com/2012/01/23/s... Long read but worth it. It highlights how companies approach salary totally differently than employees, and what to do about it It also has strong tactical advice on how to approach your salary conversation.
Loved this write-up of the debugging process for a complex problem: 1. Develop hypotheses about the issue's root cause 2. Eliminate potential issues one at a time by making changes/copying working examples and seeing if the issue persists Worth a read if you're working on your debugging skills!
😱 Not so short JS horror story: githero.app was performing really badly when using the back button in the browser. The whole app was refreshing. Initially I thought I was doing something wrong but quickly saw that it could only be that the routing library was not listening to the popstate event.
Any time you ask someone for help, they're wondering: • How much work will this be? • Will this person respect my time? • Am I going to have to hold their hand? They ask these questions even if they like helping people! Show them you're willing to help yourself first.
I be getting so tight when someone is like “if you know of any roles that would be good for me, reach out” You dont want a job. LOL cuz why do other ppl have to do the work for you?
Hard agree. For our small engineering team, our application asked only for resumes (no cover letters), but if someone took the time to write a thoughtful email alongside their resume, I read every word. It really set them apart if they did even a halfway decent job with it.
Ive been involved in hiring at several of the companies I’ve worked at. At one company, I saw all of the direct applications, I was the first person to review them. The quality was *terrible*. Most people put zero effort into their application. A tiny bit of effort can go a long way. 🧵
Mike Chen reposted
You are up to date.