Min Chen’s Post

I've only got 939 commits across 26 fully-functional public projects (as well as several additional non-public, proprietary projects) to GitHub this year spanning the entirety of full stack engineering and showcasing a wide variety of technical proficiency. I can totally see why you wouldn't want to hire that because he doesn't have a special piece of paper. Like I've said, it's your loss. Those without contractual protection of some form from me, be that 1099, W2, or C2C are competing with me. Hope you're in for it. I don't have 9 layers of corporate dalliance to pass through with 4 different teams. I can get your ideas to market faster and I can make them better than you can, because the entire industry is stuck in 1995 and I woke up in the future space year 2023. There's a massive paradigm shift coming so soon, akin to the invention of the internet. Remain clung to your archaic processes at your own peril.

Interesting thread on ycombinator news around the habits of great software engineers. The top post by onion2k resonates IMO…tldr; -people-focused approach, -constant thought of the end user…”is this making their life easier?” -obsess over making their code fail elegantly, -ensure systems are strongly robust, -thinks about failure states deeply, -able to make tradeoffs…”hey, this is good enough” rather than making it perfect at the cost of time, -maintaining the balance of what’s needed vs what’s interesting. What do you think? #softwareengineers #greathabits #ycombinator

If you missed the last article of my newsletter "Code Your Future", you can still read it today! The article was "Making the Leap: Tips for Securing Your First Software Engineering Role" 🔥 You can subscribe today and read it! https://lnkd.in/dB6fvCxD #careerchange #job #jobs #softwareengineering #firstjob

Check out this insightful article on code review practices from Google, essential reading for all software engineers. Share your thoughts after giving it a read! #CodeReview #GoogleEngineering #SoftwareDevelopment #TechInsights https://lnkd.in/g46pWCpu

👉 Behind #QConSF is a collective of distinguished senior software leaders who carefully curate the QCon topics based on the crucial trends and essential best practices you need to know about. This Oct 2-6, the conference will contain 12 tracks. If you’re a senior software developer, software architect, or tech team lead, you won’t want to miss out. Explore the full list of tracks that you can learn from at QCon San Francisco 2023 covering frontend development, deep-tech, JVM, languages of Infra, staff plus engineering, and more. Link in bio. 🔗 #SoftwareConference #SoftwareDevelopment #SoftwareArchitecture #EmergingTrends #TechConference

Why most engineers aren't 10x engineers 🧵: 1. No domain expertise - The example L7 above has a deep understanding of Java's runtime + Google's existing pipelines. This allows him to solve problems few others can 2. No influence - Not all 10x engineers have impact purely through code. Some lead major initiatives by influencing large groups of engineers to build what matters most There's limited numbers of roles for people who can lead initiatives of large enough scope for (2) (1) however is permissionless and fully in your control (although hard) If (1) appeals to you, consider working on an infra team. This is much more common on those teams in my experience There's generally more opportunities to learn and demonstrate deep technical expertise in infrastructure ~ Ryan Peterman, staff software engineer at Instagram (via the 𝕏 platform) Most engineers can be 10x engineers. Just gotta find someone 10x worse than you. This is one example, every capable engineers can be “10x” in some scenarios that they are familiar with. The 10x concept is irrelevant and most of the time inaccurate. If L7 at Google is using garbage collector logs to fix performance issues, how bad is the average developer at Google?

🚀 I want to be one of the best Software Engineers. What should I do? 🤔 Do I need to learn the best system design? 🏗️ Do I need to solve as many LeetCode problems? 💻 Do I need to master powerful system architecture? 🛠️ Do I need to dive deep into high-level algorithms? 🤯 ....................................................... 💡 NO, start by building "SIMPLE" products! 🛠️ #SoftwareEngineering #CareerAdvice #ProductDevelopment 🚀

As a Principal Software Engineer, here is a list of the top 10 reasons why you should not be writing code: .

What makes a great software engineer? There are plenty of opinions on this topic. Most common answers suggest the following: able to produce maintainable working software, team player, keeping up-to-date with new technologies… A study from the University of Washington (“What Makes a Great Software Engineer?”) has uncovered 53 attributes of a great programmer. This is the result of almost sixty interviews with experienced engineers at Microsoft. What makes a Microsoft software engineer great isn’t necessarily what makes a great software engineer. However most of these attributes are worth discussing.The study classifies the 53 attributes into 4 groups and emphasizes the most interesting ones in each group https://lnkd.in/gZT2VQuw

When I was prepping for my Microsoft Interview with my job, I challenged myself to solve 1 problem daily for 100 Days, without any excuse. And it did wonders for me. These 100 Leetcode Questions can help you Build consistency, and get you stronger at problem-solving. 💪 Credit: Bosscoder Academy Check them out here- https://bit.ly/3TpivjO They have helped 1000+ software engineers get into top companies by helping them learn DSA, System Design, and Full Stack Development. Share it with your colleagues. And, if you do plan to take the challenge, write Challenge Accepted in the comments below! #leetcode #challenge #collab