Yue Huei Ong

Super excited to be back at the SingaporeJS meet-up next Tuesday, 13 August! I asked Erik Nguyen if I should present a new talk, and he said why not. So, here it is—I’ll be sharing some tips and tricks for frontend debugging using DevTools. With this being a fresh talk, I'll be spending the National Day 🇸🇬 long weekend preparing the slides. Majulah Singapura! Happy 59th birthday, Singapore 🇸🇬! As a web developer, you've likely relied on console.log countless times—but what if there’s a more efficient way to debug? Many of us tend to overlook the full range of powerful features that browser DevTools offer beyond basic logging. In this session, we'll uncover some of the hidden gems within DevTools, introducing techniques and features that can completely change how you debug. We’ll go through everything from debugging hidden elements to using tools like Visual Coverage, Animation Timeline, Performance panels, and more. Expect around 20 tips to take your debugging skills to the next level and make your workflow smoother. A lot of these DevTools features get missed because we assume they’re just common knowledge. Think of this session as an information buffet—I'll present a variety of tools for you to explore. Let's dive in with curiosity and see how we can rethink our debugging approach! Looking forward to seeing you all next week. This is an in-person event at the Rakuten Asia Pte Ltd office in CapitaGreen. RSVP here: https://lnkd.in/gjY5KpgW

47

5件のコメント

Inspired by Yangshun Tay's post, I always been a firm believer in writing more code is one of best ways to level yourself as software engineer. The more you code, the more you: - Solidify your understanding of core concepts. Each line you write reinforces the fundamentals, making them second nature. - Develop your problem-solving muscles. Coding is a constant dance with challenges, and each solution strengthens your critical thinking. - Build a portfolio of practical experience. Hands-on projects showcase your skills and fuel your passion for the craft. Always coding for fun

289

15件のコメント

My recorded talk at JavaScript Bangkok 2.0.0 is now live! If you want to dive deeper into DevTools, check it out 👉 https://lnkd.in/gmHQS7m9 The video quality is excellent—I can hear myself so clearly! Watching it again has been a great way to reflect and think about how I can improve for the next time. Frontend debugging is a skill that gets better with regular practice, but many developers do not take full advantage of what DevTools can offer. Just like mastering your code editor boosts productivity, getting comfortable with DevTools can do the same. Some of my favourite features are: - LogPoints - Changing program behaviour on the fly - Overriding web content and HTTP response headers locally - Debugging disappear elements These tools have been game changers for me, and I hope they will help you too!

28

Today, I am sharing how to get Email and Password authentication in Our Android App using Firebase. 1.When initializing your Activity, check to see if the user is currently signed in public override fun onStart() {     super.onStart()     // Check if user is signed in (non-null) and update UI accordingly.     val currentUser = auth.currentUser     if (currentUser != null) {         reload()     } } 2.Create a new account by passing the new user's email address and password to createUserWithEmailAndPassword: auth.createUserWithEmailAndPassword(email, password)     .addOnCompleteListener(this) { task ->         if (task.isSuccessful) {             // Sign in success, update UI with the signed-in user's information             Log.d(TAG, "createUserWithEmail:success")             val user = auth.currentUser             updateUI(user)         } else {             // If sign in fails, display a message to the user.             Log.w(TAG, "createUserWithEmail:failure", task.exception)             Toast.makeText(                 baseContext,                 "Authentication failed.",                 Toast.LENGTH_SHORT,             ).show()             updateUI(null)         }     } 3.Donot forget to add Dependency in your gradle.kts dependencies {     // Import the BoM for the Firebase platform     implementation(platform("com.google.firebase:firebase-bom:32.8.1"))     // Add the dependency for the Firebase Authentication library     // When using the BoM, you don't specify versions in Firebase library dependencies     implementation("com.google.firebase:firebase-auth") } #firebase,#android

10

PM: we need to release it today Dev: but this is an early-stage proof of concept PM: WE NEED TO RELEASE IT TODAY! Dev: ok... PoC: ~~~~~~~~~~~~~~~~~~~~~~~~~ Rome wasn’t built in a day, & so aren’t bleeding edge applications! When it comes to AI Deployments, it could look a lot like this That’s because even if it’s enterprise grade plugn-play or even a chatbot It cannot have all the intelligence since day 1 So running behind perfection at PoC stage is going to render it ir”responsible” (pun intended) Is the suggestion compromising on the accuracy of the application? Absolutely not! Quite the opposite That said, having a flexible infrastructure, that supports not just AI, but any enabler in the tech stack is key! So it’s crucial to build architectures that can incorporate any disruptive efforts. ~ Start SMALL not PERFECT ~ FAIL & ITERATE quickly ~ Think SCALE ~ Repeat This could be the mantra for exponential growth in this highly *alive* era of transformation. #ai #resposibleai #llms #genai #enterprise

12

I completed the first and second modules (System Design + Networking) of the iOS Lead Essentials program 🧑‍💻! Here's a summary of what I learned so far 👇 - The fundamentals of good system design and architecture. How to think, design, and draw diagrams like a software architect. - Networking best practices to develop, maintain, and test a clean networking layer in iOS apps with key frameworks such as URLSession, URLProtocol, Decodable, and third-party code. Also, how to work effectively with backend teams. Click to see more: https://lnkd.in/gscKGNiD

30

1件のコメント

I completed the fifth module (Main Composition) of the iOS Lead Essentials program 🎊! Here's a summary of what I learned so far 👇 - The fundamentals of good system design and architecture. How to think, design, and draw diagrams like a software architect. - Networking best practices to develop, maintain, and test a clean networking layer in iOS apps with key frameworks such as URLSession, URLProtocol, Decodable, and third-party code. Also, how to work effectively with backend teams. - Persistence best practices to effectively develop, maintain, and test a clean persistence layer in iOS apps using URLCache, CoreData, FileManager, Codable, and other key persistence frameworks. - UI, UX, and Presentation best practices, and how to develop, maintain, and test a clean UI and Presentation layer in iOS apps. How to use MVC, MVVM, MVP, and their variants, prototyping techniques, localizing apps, working effectively with designers, and how to create reusable UI/Presentation components. - Composition best practices - how to compose modules to form a fully functional app. Also, how to validate high-level acceptance criteria with automated tests at every level (Unit, Integration, Snapshot, UI...), how to use the Combine framework and how to develop, maintain, and test-drive a clean Composition layer in iOS apps. Click to see more: https://lnkd.in/gXkYjHep

34

2件のコメント

Disclaimer: by no means I advocate abandoning JDK platform – I think JDK platform and ecosystem is very productive and robust modern platform that should be widely adopted. Rant: I have been enjoying development with Kotlin for the  past 5 years and I recently attended SeaJUG meeting where Java dev advocate  Billy Korando of ORACLE was presenting on new features in Java and JDK 23. Billy is a good presenter and I feel bad for him: he has to cheerfully present the sad state of Java (language) development. I think Java stewards just stuck in the past and do not get it! WTF they spend time adding useless features: Jwebserver – why spend any time on something that cannot be used for any real work – the excuse is that some professors and students are too stupid to use tomcat or jetty; Single File Source Code – another useless feature, the script cannot pull libraries and integrate with my corporate private repository of artifacts, or even public ones I think that Java leadership just do not get it: to succeed Java ecosystem MUST embrace build toolchain and code repositories. IMO it should adopt Maven because of its simplicity and declarative nature (it could sure benefit from simplified syntax) With Maven we can compile and run any code while enjoying dependencies resolution with mvn exec:java -Dexec.mainClass="com.mycompany.ComplexAndUsefulCode" The strength of Python, Node, Go ecosystems is that they made it super easy to pull down libraries, but official Java tries to be standalone – so silly! Language itself is laughable, it tries to keep up with modern languages but cannot implement features properly. Text blocks – seems like useful thing, but it is does not support interpolation! Wtf, so we are back to relying on archaic, badly readable formatting. Java String html = """      <html>          <body>              <p>Hello, %s</p>          </body>      </html>      """.formatted(strA); Good languages: val name = “John” val html = """      <html>          <body>              <p>Hello, ${name}</p>          </body>      </html>      """ Records… bad incomplete copies of data classes from Kotlin and Scala, do not even have copy constructors and methods, rely on POSITIONAL (bug prone) parametrization. The list goes on and on. I think at this time Java as a language is doing more disservice than helping JVM ecosystem. #Java #JDK

6

11件のコメント

𝐉𝐚𝐯𝐚 𝐓𝐡𝐫𝐞𝐚𝐝𝐬: 𝐏𝐥𝐚𝐭𝐟𝐨𝐫𝐦 𝐓𝐡𝐫𝐞𝐚𝐝𝐬 𝐯𝐬. 𝐕𝐢𝐫𝐭𝐮𝐚𝐥 𝐓𝐡𝐫𝐞𝐚𝐝𝐬 Hello, everyone! Today, let's dive into the world of Java threads. We'll explore the differences between Platform Threads and the Virtual Threads. 𝗣𝗹𝗮𝘁𝗳𝗼𝗿𝗺 𝗧𝗵𝗿𝗲𝗮𝗱𝘀 : traditional threads that directly map to native operating system threads. They are managed by the OS, making use of fixed memory allocations for each thread's stack . 𝐌𝐞𝐦𝐨𝐫𝐲 𝐔𝐬𝐞 : Each thread uses a chunk of memory called a stack. This can be quite large (hundreds of KB to a few MB). You can adjust this size, but it’s still pretty big. 𝐌𝐚𝐧𝐚𝐠𝐞𝐝 𝐛𝐲 𝐎𝐒 : The operating system (OS) manages these threads. It handles when each thread runs and switches between them. 𝐑𝐞𝐬𝐨𝐮𝐫𝐜𝐞 𝐇𝐞𝐚𝐯𝐲: Because they use a lot of memory, creating thousands of these threads can eat up your system’s resources quickly. 𝐁𝐥𝐨𝐜𝐤𝐢𝐧𝐠 : If a thread is waiting for something (like reading a file), it stops doing anything else. This can waste a lot of time if many threads are just waiting around. 𝐁𝐞𝐬𝐭 𝐟𝐨𝐫 : Tasks that need heavy CPU work where you don’t need a ton of threads. 𝗩𝗶𝗿𝘁𝘂𝗮𝗹 𝗧𝗵𝗿𝗲𝗮𝗱𝘀 : The Newcomer Virtual Threads are a new feature in Java. They’re designed to be much 𝐥𝐢𝐠𝐡𝐭𝐞𝐫 and 𝐦𝐨𝐫𝐞 𝐞𝐟𝐟𝐢𝐜𝐢𝐞𝐧𝐭. Here’s how they work: 𝐒𝐦𝐚𝐥𝐥 𝐌𝐞𝐦𝐨𝐫𝐲 𝐔𝐬𝐞 : Virtual Threads start with a tiny amount of memory and grow as needed, which is much more efficient. 𝐌𝐚𝐧𝐚𝐠𝐞𝐝 𝐛𝐲 𝐉𝐕𝐌: Instead of the OS, the Java Virtual Machine (JVM) handles these threads. This makes switching between threads faster and less resource-intensive. 𝐒𝐮𝐩𝐞𝐫 𝐒𝐜𝐚𝐥𝐚𝐛𝐥𝐞: You can create millions of virtual threads without running out of memory, which is fantastic for handling lots of tasks at once. 𝐍𝐨𝐧-𝐛𝐥𝐨𝐜𝐤𝐢𝐧𝐠: When a virtual thread is waiting, it doesn’t waste resources. The JVM pauses it and resumes it later without blocking other threads. 𝐁𝐞𝐬𝐭 𝐟𝐨𝐫: Tasks that need to wait a lot, like web servers handling many connections. 𝐑𝐞𝐚𝐥-𝐖𝐨𝐫𝐥𝐝 𝐄𝐱𝐚𝐦𝐩𝐥𝐞 Let’s say you’re building a server that handles lots of users at the same time: 𝐏𝐥𝐚𝐭𝐟𝐨𝐫𝐦 𝐓𝐡𝐫𝐞𝐚𝐝𝐬: If you 𝐜𝐫𝐞𝐚𝐭𝐞 𝟏𝟎,𝟎𝟎𝟎 𝐭𝐡𝐫𝐞𝐚𝐝𝐬, you might need around 𝟏𝟎 𝐆𝐁 𝐨𝐟 𝐦𝐞𝐦𝐨𝐫𝐲. 𝐕𝐢𝐫𝐭𝐮𝐚𝐥 𝐓𝐡𝐫𝐞𝐚𝐝𝐬: The same number might only need 𝐚𝐫𝐨𝐮𝐧𝐝 𝟒𝟎 𝐌𝐁 to start, growing as needed. 𝐂𝐨𝐧𝐜𝐥𝐮𝐬𝐢𝐨𝐧 𝐕𝐢𝐫𝐭𝐮𝐚𝐥 𝐓𝐡𝐫𝐞𝐚𝐝𝐬 are a huge leap forward for Java, making it possible to handle many tasks more efficiently. While Platform Threads are still useful for certain types of tasks, Virtual Threads offer a 𝐥𝐢𝐠𝐡𝐭𝐰𝐞𝐢𝐠𝐡𝐭, 𝐬𝐜𝐚𝐥𝐚𝐛𝐥𝐞 𝐬𝐨𝐥𝐮𝐭𝐢𝐨𝐧 𝐟𝐨𝐫 𝐦𝐨𝐝𝐞𝐫𝐧 𝐚𝐩𝐩𝐥𝐢𝐜𝐚𝐭𝐢𝐨𝐧𝐬 𝐧𝐞𝐞𝐝𝐢𝐧𝐠 𝐭𝐨 𝐡𝐚𝐧𝐝𝐥𝐞 𝐦𝐚𝐧𝐲 𝐜𝐨𝐧𝐜𝐮𝐫𝐫𝐞𝐧𝐭 𝐭𝐚𝐬𝐤𝐬. So, if you’re developing in Java, give Virtual Threads a try. They could make your applications run faster and use resources more efficiently. #java

14

1件のコメント

🚀 Diving into Packages in Golang! 🛠️ I just explored one of the key concepts in Go—packages! It’s been super fun to learn how to organize code better and keep things modular. 💡 I created my own package (helpers) and used it to define a custom HelperType struct, which I then accessed in my main Go file. It’s amazing how packages make code more reusable and maintainable! Looking forward to exploring more advanced features in Go. If you’ve worked with Go packages, I’d love to hear how you structure your projects! Let’s connect and share ideas. #GoLang #GoPackages #CodingJourney #LearningInPublic #SoftwareDevelopment #Programming Golang Jobs Golang Dev

2

Recommended books for cracking Technical Interview

3

Firebase vs. Supabase: Why I ditched Firebase and moved my backend to Supabase I’m currently building a production-level app with Supabase, I was initially skeptical about moving away from Firebase, but my client's main requirement was to avoid using Firebase due to its cost and the risk of becoming too dependent on the Google ecosystem. Once you get dependent on it, there is no going back, So we decided to use Supabase and the experience has been phenomenal! Supabase offers everything I love about Firebase but with the added benefits of SQL. The migration process was straightforward, and now I have more flexibility and control over my backend. The real-time features and seamless authentication make it perfect for my projects. Additionally, the ability to write complex queries and use familiar SQL tools has significantly improved our data management. The performance improvements and scalability options have also been impressive. Supabase’s detailed documentation and active community support have made the transition smooth and enjoyable Have you used Supabase before? If yes, what was your experience?

7

2件のコメント

🚀 How Facebook Scaled Memcache to Handle Billions of Users 📈 I have been reading the book by Alex Xu called System Design Interview an Insider’s Guide, and he recommended reading the paper published by Facebook (Meta now :D) to understand how Facebook handled most of the common caching issues. In the world of high-scale systems, efficient caching is crucial for maintaining performance and responsiveness. My latest article on Medium dives deep into how Facebook optimized and scaled Memcached to handle the demands of billions of users. 🔍 What you’ll learn: - The role of consistent hashing in load balancing - Techniques to reduce latency and prevent cold cache misses - Strategies for failover and maintaining data consistency - How Facebook minimized network congestion and optimized traffic 💡 Scaling is not just about adding more hardware; it’s about building smart systems that adapt to changes and grow alongside the user base. Check out the full article here: https://lnkd.in/eXk4DQmd #Scaling #DistributedSystems #Caching #FacebookEngineering #TechLeadership #Memcached #SystemDesign #CloudComputing #HighPerformanceComputing #SoftwareEngineering

12

2件のコメント

I completed the fourth module (UI + Presentation) of the iOS Lead Essentials program 🥳! Here's a summary of what I learned so far 👇 - The fundamentals of good system design and architecture. How to think, design, and draw diagrams like a software architect. - Networking best practices to develop, maintain, and test a clean networking layer in iOS apps with key frameworks such as URLSession, URLProtocol, Decodable, and third-party code. Also, how to work effectively with backend teams. - Persistence best practices to effectively develop, maintain, and test a clean persistence layer in iOS apps using URLCache, CoreData, FileManager, Codable, and other key persistence frameworks. - UI, UX, and Presentation best practices, and how to develop, maintain, and test a clean UI and Presentation layer in iOS apps. How to use MVC, MVVM, MVP, and their variants, prototyping techniques, localizing apps, working effectively with designers, and how to create reusable UI/Presentation components. Click to see more: https://lnkd.in/gWmfPgQC

33

3件のコメント

Trying to run some examples for Kotlin coroutines, but can't build my project. I'm using the latest Check it out: https://lnkd.in/gXrEdFr7 Join the conversation! #gradle #kotlin #kotlincoroutines

1

I want to build a pair programming community. The pair programming sessions are really helping you with coding skills, because it forces you to write lines of code when you are a driver. It can also help your technical interview processes because you will have one or two interviewers while you are coding there. If you merely code quietly with no one around, then look, now you have a better option. You will keep talking, thinking out loud, and learn during a pair programming session. If you take turns with a group of people while problem solving and coding, you can make more professional connections. I made many friends through coding. I have a meetup group for mob programming. I have a few hours after work. I want to contribute to this (probably existing) community. As a start, please feel free to join a calendar I made with my free Calendly account (thank you). https://lnkd.in/g9gwpk5K Also, please spread words for me because I think I will get the benefit of pair programming to do better at any Leetcode interview.

29

6件のコメント

I can personally vouch for some of these. Thanks to this author for some great resources making life of engineers easier ! Alex Xu

15