Pierluigi Cau

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 Comments

The world-class engineering team at RevenueCat just shared a ton of insight into the engineering strategy that's allowed them to scale to support >32,000 apps and handle 1.2 billion API requests per day. Among other valuable and ready-to-implement tips around hiring practices and allocating reactive teams to manage those outside-of-the-roadmap enterprise requests, they called out another key action to deliver on their strategy: 💡 "Continue using Rootly for incident management: We will ensure the practice of writing blameless post-mortems and make use of Rootly for incident management." We're so proud to work with teams like RevenueCat who are defining new ways of working and achieving operational excellence within their engineering orgs. Kudos to them on the transparency as well — this rising tide lifts all boats 🛥️ Check out their full strategy here: https://lnkd.in/gNwGhr-A

17

1 Comment

If you haven't seen the new oxc-transformer release, you should check it out: https://lnkd.in/e_2KYHWq This morning I released a new version of hohoro (a minimal JS/TS build tool for libraries supporting incremental builds) with a new experimental export and binary that uses oxc under the hood! This means you no longer need to install or configure swc and also tsc for library builds! Check out hohoro here: https://hohoro.vercel.app/ and give it a try in your next project! The coolest part of this - is that all you need for: - Building your library (.ts/.tsx/.jsx/etc ➡️ ESNext JS) - Generating types (.d.ts files) - Incremental builds (only building changed files) Is to: - Install `[email protected]` - Add the script: "build": "hohoro-experimental" And that's it!

5

1 Comment

DVA is not associated with this job posting Senior Product Designer, Source Code at GitLab https://lnkd.in/g8DAzQHu What youll do Design intuitive and scalable solutions that enhance collaboration for teams working across various industries, including game development, automotive, healthcare, and more. Work closely with a cross-functional team to bring our strategic pillars to life: Easy administration for large teams: Enable efficient and intuitive scaling of Source Code Management for large teams. High performance with large binary files: Streamline collaboration for developers and contributors, ensuring seamless management of large binary files. Streamlined workflows for large repositories: Enhance the management and collaboration within large repositories, including monorepos. #jobopportunity #jobsearch #jobs #job #hiring #jobseekers #jobvacancy #recruitment #nowhiring #jobsearching #jobinterview #jobopening #jobseeker #jobhunt #career #hiringnow #jobalert #recruiting #employment #jobshiring #careers #jobhunting #work #vacancy #jobvacancies #applynow #jobfair #jobopportunities #workfromhome #jobposting

1

Unified schema yet distributed ownership and implementation. sweet music to the ears. https://lnkd.in/gGUqV7NR

3

Caching can make or break the experience. I’ve seen sites soar with the right strategy and struggle when caching is overlooked. It’s not just about speed; it’s about keeping readers happy and your site running smoothly. https://lnkd.in/eUgqYRzG

2

Winston Hearn, Frontend Observability Expert and Hazel Weakly, Web Developer and SRE, are back for Episode 2 of Ask the Experts! In this installment, they dive into the key questions you can be asking about your #frontend with #distributedtracing. Watch it today: https://lnkd.in/gRCb-VsW

15

We hear it often - "Everything is a trade-off." But what does this mean in #SoftwareArchitecture? Sadukie talks about many of the considerations we have as architects and the trade-offs involved! Check it out: https://lnkd.in/gSSvPcbf #SoftwareDevelopment #TechTraining

2

We hear it often - "Everything is a trade-off." But what does this mean in #SoftwareArchitecture? Sadukie talks about many of the considerations we have as architects and the trade-offs involved! Check it out: https://lnkd.in/gSSvPcbf #SoftwareDevelopment #TechTraining

3

We've recently shipped our Kafka-API compatibility layer that enables amazing integrations such as the one with SingleStore! When using SingleStore’s Kafka pipeline, which allows for fast, exactly once processing to ingest data, Dekaf serves as the intermediary between SingleStore and Estuary Flow. Here’s how it works: 1. Pipeline setup. SingleStore’s Kafka Pipeline is configured to communicate with Dekaf just as it would with a Kafka broker. Estuary Flow acts as the data producer, streaming data into topics that Dekaf exposes to SingleStore. 2. Topic management. In Estuary Flow, each capture is organized into logical topics, similar to Kafka partitions. SingleStore subscribes to these topics through Dekaf, ensuring data is consumed in real time. 3. Schema handling. Dekaf also handles schema management through integration with schema registries. It ensures SingleStore receives data with the correct structure, minimizing the need for manual schema mapping. 4. Data delivery. As changes happen in source databases (like MongoDB or PostgreSQL), Estuary Flow captures these changes and streams them via Dekaf to SingleStore. This provides a near real-time view of the data in SingleStore — perfect for applications requiring up-to-date information for analytics or operational purposes. By using Dekaf, SingleStore users can integrate real-time data pipelines from a variety of sources, leveraging the power of Estuary Flow while maintaining the simplicity of Kafka-like operations. Check it out the full article here: https://lnkd.in/d5Q4Zzt4

10

State of the Frontend in 2024! https://lnkd.in/gQ9-YwMS TL;DR: 1. React and Next.js are here to stay. 2. Redux and Redux Toolkit is still kinda popular. 3. Vercel, Github Actions, Node.js , Typescript and Tailwind css lead in their spaces. 4. GraphQL is waning in popularity 5. Dedicated QA teams are shrinking, devs expand their roles further into testing. 6. ChatGPT and Copilot are popular choices for AI tools, but Sonnet 3.5 is viewed as a better code generation model. Curious to see how much of a spike Cursor (uses Sonnet 3.5) will enjoy! These are just some items that really caught my attention, more details in the report...

16

1 Comment

Want to master Event-Driven Architecture? Our series continues with Nathan Neikirk breaking down the crucial differences between Pub/Sub and Streaming APIs. Discover how to leverage the right tool for the job and optimize your event processing. Read part 2 below: ☁ Part 1: Introduction to Event Driven Architecture (vs. Point to Point) ☑ Part 2: Classifying Event-Driven Architectures- https://lnkd.in/gUYQJYCN ☁ Part 3: Event Driven Architecture in Salesforce ☁ Part 4: Should YOU implement Event Driven Architectures?

23

2 Comments

Output vs outcome is a choice that affects many layers of measurement. In all cases I can think of, output is easier to measure but is the least informative metric.

10

[TECH] API vs SDK: could you tell the main difference in a short sentence? ​​​🧐​ In our tech world, API and SDK are essential concepts and tools, but they are often misunderstood and their aim swapped. But guess what, API and SDK are not the same and actually serve different purposes. Let's define them in a simpler way: ​​​🌉​ 𝗔𝗣𝗜 - 𝗔𝗽𝗽𝗹𝗶𝗰𝗮𝘁𝗶𝗼𝗻 𝗣𝗿𝗼𝗴𝗿𝗮𝗺𝗺𝗶𝗻𝗴 𝗜𝗻𝘁𝗲𝗿𝗳𝗮𝗰𝗲: imagine it as a bridge that allows different software to communicate with each other. Better, it’s like a menu that tells you what services or data you can use. And then you pick the one that suits your objective, to see what you wish. For example, at Visioglobe, developers can use an API to call a specific action, such as the integration of real-time information into a map; this way enabling dynamic features. ​​​🧰​ 𝗦𝗗𝗞 - 𝗦𝗼𝗳𝘁𝘄𝗮𝗿𝗲 𝗗𝗲𝘃𝗲𝗹𝗼𝗽𝗺𝗲𝗻𝘁 𝗞𝗶𝘁: see it as a toolkit that includes everything you need to build applications. It could be APIs, libraries, documentation, and sometimes sample code. For instance, Visioglobe’s SDK for mobile (Andoid & iOS) provides developers with all the components required to build and fully customize interactive indoor maps directly within their apps. In short ​​​⚡​ API is a specific connection, while SDK is a full toolbox.

14

🔍 Dive deep into iOS system library reversing with #Radare2! In Part 2 of our blog series, Francesco Tamagni reveals how to find cross references within a single library in the dyld shared cache. #ReverseEngineering https://loom.ly/Sj4_its

43

I've worked in similar environments and deploying to production several times a day takes a lot of the risk out of delivery. As mentioned here it's predicated on separating the concepts of deployment from release using techniques like feature flags and branch by abstraction.

8