Lung Sin Kwee

Week 2: Scaling Memcache at Facebook To accelerate your career as a high-growth engineer, it’s essential to immerse yourself in cutting-edge research articles and engineering blogs from reputable companies. This practice not only broadens your knowledge base but also keeps you updated with the latest industry trends and technological advancements. 🔗 Link: https://lnkd.in/gFtcV-fv Facebook’s blog has taught me a lot about how they handle the challenges of scaling Memcache to support their massive user base. They share details about their system's design, the technologies they use, and how they solve complex problems. For example, they implement strategies like sharding to distribute load and redundancy to ensure high availability. Learning about these techniques has given me a better understanding of how to build and maintain large-scale distributed systems. Reading blogs and articles from companies like Facebook, Google, and Netflix is great because they share their experiences and solutions. This helps you learn best practices in software engineering and system design. They often share stories about how they built their systems and solved tough problems, which can be very useful for your own work. To become a better engineer, I recommend spending some time each week reading these resources. Start with topics that interest you or are related to your job. Then, slowly explore new areas and technologies. Take notes, try out what you learn in your projects, and discuss your findings with colleagues or mentors. In short, keeping up with engineering blogs and research articles is a great way to improve your skills and advance your career. My journey recently included learning about scaling Memcache at Facebook, and it has laid a strong foundation for my continuous growth. I encourage all aspiring engineers to make this a habit and include it in their professional routine. #Engineering #CareerGrowth #TechInsights #ContinuousLearning

9

This is my second anniversary working at RisingWave. I started there as an intern working with the mentorship of ZHI LIU, where I got to deliver cutting-edge work such as implementing SqlSmith for RisingWave in Rust, and streaming query optimization. From there I started deep-diving into the RisingWave Kernel under the leadership of Eric Fu, working on features such as Backfilling, and new deployment modes, closely collaborating with fellow engineers, and having strong cross-collaboration with other teams (cloud, docs, product) as well. In these two years, I'm always amazed by my fellow engineers working on the Database Kernel. They are extremely strong engineers with both breadth and depth, have high ownership and accountability, making them a delight to work with. The same qualities are consistent across HR/Ops, Cloud, Product, Performance and Reliability, and Documentation teams. In my opinion, the #streamprocessing market is still nascent, where many are still using batch OLAP / OLTP systems to do adhoc computation, instead of leveraging streaming databases to do incremental computation. We are beginning to see a bigger shift in the market, where many move from just doing stream ingestion, and start to explore streamlined systems such as RisingWave to do stream processing, in view of cost-savings and greater performance. Moving forward, I'm doubling down on user-experience and developer-experience in RisingWave to continue driving adoption and improve our engineering efficiency. Looking forward to the rest of 2024 and beyond! #streamprocessing #database #sql #streaming #kafka #rust #risingwave

107

8 Comments

📢 Excited to share my latest Medium article on solving Leetcode's "121. Best Time to Buy and Sell Stock" problem in Go (Golang)! 🚀 In this article, I dive deep into various solutions, discussing their advantages and disadvantages. From brute force to optimized integer operations, I cover it all. If you're preparing for coding interviews or just looking to enhance your algorithm skills, this piece is a must-read! Check it out on Medium and let's connect over some great coding insights! 💻 #Leetcode #Golang #CodingInterview #Algorithms #Programming

5

GPT-4oi getting huge fanfare. I'm not surprised as I had been grinding away using cot to solve logic problems. as Andrew ng said "you already have gpt 5 if you use agents." so gpt 4oi to me seems not so impressive maybe - it just shows me people were too lazy to learn how to use the prior models to solve logic problems. 4oi streams boatloads of planning into oblivion before you get an answer, if you had taken the other models and given them time to think you could have been getting similar results this whole time. examples? surely! a common logic problems is solving the counting of r in the word strawberry. all of the models fail to count the number of rs. they say 2 not 3 rs are in stRawbeRRy. but if you use Chain of Thought, the models get this logic question right. here is Claude below. I saw so many people complain about this very publically and just never read the docs to see how to solve logic problems. ----------- Certainly! Let's use the "Chain of Thought" (CoT) approach to count the number of 'r's in the word "strawberry": First, let's write out the word: strawberry Now, let's go through each letter one by one: s - not an r t - not an r r - this is an r (count: 1) a - not an r w - not an r b - not an r e - not an r r - this is an r (count: 2) r - this is an r (count: 3) y - not an r After going through all the letters, we've counted 3 r's. Therefore, the word "strawberry" contains 3 r's.

2

Interviews can be a rollercoaster of hard work, hope, and sometimes a bit more of luck. Recently, I interviewed with ByteDance, and here's how it went: • Passed the OA with challenging coding questions. • In Round 1, I solved two hard coding problems with an efficient approach in 40 minutes and moved on to Round 2 with positive feedback. • In Round 2, I received encouraging feedback on my OS, Networking, and Linux knowledge. • During the behavioral round, I felt confident and connected as we discussed various situational questions. Was put on hold for two weeks, later informed that at this moment they cant offer me a role(because of reorg). It’s tough when you pour your heart into something and still fall short. Despite the positive feedback, it just wasn’t my moment this time. This experience reminded me that while I can control my preparation, some things are beyond my control. If you or your team is hiring, please reach out to me. Hoping for a bit more luck in my next interview! :) #tech #interview #womenintech #jobs #interviewexperience #2025 #career #software #SRE #DevOps #internationalstudents #faang #ByteDance #luck #interview #openforwork #techcareer #fulltimeopportunity #openToWork #softwaredevelopement #opentowork #layoffs2024 #amazon #meta #apple #atlassian #rubrik #hft #GHC24 #WE24

186

7 Comments

Project #Convo for @supabase open source hackathon. It experiments with a fun concept that use LLM as role play characters in various scenarios for English learners to practice conversations. Had fun building with Supabase anonymous signin, oauth, and database features. And big thanks to my school mate Keith for helping with the TSS feature! In #Convo, you can browse various scenarios, have conversations with different roles and try to achieve set goals and target words. Turn on the mic and speak to the agent. See your performance evaluation. Sign in to Google to save your conversations and resume it later anytime in any device. And just simply enjoy a focused distraction-free conversation. #Convo is designed to be simple, easy to use, fully responsive, support both light and dark mode. Try it out here: https://convo.website

12

How to write a killer Software Engineering résumé? By Terrence Kuo An in-depth analysis of the résumé that got me interviews at Google, Facebook, Amazon, Microsoft, Apple, and more. This résumé got me interviews at Google, Facebook, Amazon, Microsoft, and Apple.I obtained these interviews by sending my résumé to the résumé black hole, also known as applying online. Applying online is the most common way people go about applying for a job and therefore the least effective way to land an interview due to competition. Yet that is exactly how I obtained all my interviews. How did I accomplish this? In this article, I will go through a line-by-line analysis of my résumé for the following purposes: explaining the choices that I made in creating my résumé why I believe this résumé worked to help me land those interviews, and how you can create an even better résumé! I decided to write this article because I struggled a lot with landing interviews when I first started looking for a job. It would have been extremely helpful for me to have a real-life example résumé to look at. This article is organized into the following sections: The All Too Familiar Way of Not Landing an Interview - a short anecdote of my frustrations when I first started applying for jobs Evaluating the Options: Moving Forward - a reflection on different strategies to improve the odds of landing interviews Learning How to Write a Killer Résumé By Example - the step-by-step analysis of my résumé with each of the following sections corresponding to my résumé: 1.The Essentials from a Glance 2.Who Are You 3.Contact Information 4.Education 5.Employment 6.Personal Projects 7.Skills

113

1 Comment