Fabien Pelletier

I had an interesting discussion with folks from the Chrome and Firefox teams about React Server Components and how they affect the web performance at the Toronto Web Perf Meetup yesterday. The DCL event seems to happen when the last bit of HTML reaches the browser, which can be seconds later. Until that happens, no module or deferred scripts are going to be invoked. Having the browser paint the page before all suspended components load is definitely a good feature, but it doesn't change the fact that we need to deliver all data as fast as possible. All the deferred or module scripts won't load until DCL happens. Have this in mind when you're suspending your components. It's easy to think "it will reach the browser whenever it does" since the users will be able to interact with the website before that, but don't adopt that mindset.

25

The October Montreal.rb talk will be on how to "Tame Complex Queries with Database Views", given by David Cornu, a Staff Software Developer at Patch. Date/Time: Wednesday, October 2, 2024 at 7pm Location: Anticafe Montreal (294 Saint-Catherine St W, Montreal, Quebec, Canada) RSVP link: https://lnkd.in/er8Hz24N Description: PostgreSQL views are a useful tool to make query logic reusable and maintainable. This talk will cover their pros and cons, a couple of real-world use cases, and how to use them in Rails apps using the Scenic gem. Speaker: David is a staff software developer at Patch (a climate tech startup). He cracked open Why’s Poignant Guide to Ruby in 2009 and has been in and out of Rails apps since. #montrealrb #montreal #ruby #rails #talk #presentation #softwareengineering #softwaredevelopment #programming #community

1

🎤*tap, tap, tap* Is this thing on?? If you're letting fear get in the way of using metrics to extend your management style, you're missing out on chances to better support your ICs. Check out my talk to learn how my team and I employed them safely, leveling up our 1-1 conversations around job satisfaction, burnout prevention, self-advocacy, and healthier team dynamics. ✨✨ https://lnkd.in/dPyJjRjx

37

2 Comments

What countries have an 8-4 hour working time overlap with the US and a huge pool of Fullstack Engineers? 👇👇👇 🇧🇷 Brazil: 180,000 software engineers -> EST: 8 hours overlap -> PST: 5 hours overlap 🇦🇷 Argentina: 48,000 software engineers -> EST: 7 hours overlap -> PST: 4 hours overlap 🇲🇽 Mexico: 40,000 software engineers -> EST: 8 hours overlap -> PST: 6 hours overlap 🇨🇴 Colombia: 32,000 software engineers -> EST: 8 hours overlap -> PST: 6 hours overlap 🇨🇱 Chile: 18,000 software engineers -> EST: 7 hours overlap -> PST: 4 hours overlap ---------------------------------------------------------------------------- 💬 Drop a comment and I’ll shoot you a report on US startups hiring full-stack devs—where, how, and the $$$! ---------------------------------------------------------------------------- P.S. If you want to learn more about how YC, A16z, and other startups are climbing to the top, consider following me.

4

2 Comments

Hey recruitiers / hiring managers... adding this kind of info to your posts sure would be swell for everyone involved since "engineering manager" and "software manager" mean such different things in different organizations. Even with descriptions and required skills this info clarifies what matters and how much. A job requires Java for example. If you say technical is 5 stars someone that isn't strong in code isn't (or shouldn't) apply. If you say technical is 1 star, someone that wants to stay in code while managing isn't going to apply. And importantly for both visa versa. More context can only help you be more likely to get candidates that match your expectations. Take a look at the 5 different types of Engineering Manager and then specify it and mention the blog (no clue who the blog poster is btw, no affiliation) or use the idea of the different areas to stress. eg: The Delivery Engineering Manager Technical 🌟 Team 🌟🌟 Process 🌟🌟🌟🌟🌟 Product 🌟 https://lnkd.in/eSj2i9yj

3

🌟 Join us at #KubeCon + #CloudNativeCon North America 2024 🌟 I'm thrilled to be presenting "Scale Job Triggering with a Distributed Scheduler" alongside Artur Souza next week at KubeCon! 🚀 Imagine scheduling thousands—or even millions—of jobs, all triggered reliably and persistently, even in the face of downtime. In this session, we’ll dive deep into: 🔷 Why #Dapr needed a distributed Scheduler 🔷 Design decisions and architecture 🔷 Code and package walkthroughs 💡 This session is a must see if you're tackling job scheduling at scale and interested in how Dapr can simplify your distributed system design. 📅 When: Wednesday Nov 13 at 3:25pm (local time) 📍 Where: KubeCon North America, Salt Lake City, UT 🔗 Session Details: https://sched.co/1i7lq Come chat with us at the Diagrid booth during the conference! We’d love to answer your questions, hear about your projects, and see how #Catalyst & #Conductor can help with your use cases. 🔥 Looking forward to discussing #scalable job scheduling and #system #design with y'all! #KubeCon #DistributedSystems #Dapr #Kubernetes #TechTalk #CloudNative #go #SDLC

33

2 Comments

Amazon Q Developer Tips: No.2 IDE Layout by Ricardo Sueiras 💡 Tip 2 for Amazon Q Developer users: Improve your coding flow in VSCode by dragging the Amazon Q chat icon to the right. Access project files and chat simultaneously for a smoother experience. Stay tuned for more tips! #AmazonQ #VSCode #CodingTips 💻✨ https://buff.ly/4gegWxq #aws #cloudcomputing #devto

3

🧵 The Hidden Developer Growth Secret I Learned From Early Shopify Days (It's not about the tech stack...until it is.) In 2006, I was a young dev in Ottawa running IT services. One coffee chat with Aydin Mirzaee changed my entire perspective on building software. Here's what actually matters: Code Isn't Your Ceiling From: "I need to master the latest framework!" To: "Wait, these founders are teaching me how to think about problems" Learning how successful devs approached problems > memorizing syntax The Real 10x Move From: "Must learn every new tech!" To: "Must understand why this feature matters" Watching early Shopify's obsession with merchant problems taught me more than any architecture doc. Community Compounds From: "I'll just learn online" To: "These local devs are sharing real-world battle stories" Truth: Building alongside others beats watching tutorials. Growth Is Messy From: "Need perfect code!" To: "Need to solve real problems" Plot twist: Those local meetups taught me how to balance technical debt with business needs. Mindset > Stack From: "Ruby vs PHP vs Node?" To: "How are we measuring user impact?" The tech stack debate doesn't matter as much as understanding your users. The Hidden Truth: While everyone's chasing certifications... Real engineering wisdom comes from: Seeing decisions play out Watching products evolve Understanding user impact Building alongside others Sharing real failures What I really learned: Technical skills are table stakes Problem understanding is rare Community beats credentials Impact over implementation Measure what matters Want real growth? Join local dev communities Ask about failure stories Learn decision contexts Share your struggles Build relationships Because while everyone's copying FAANG architectures... Understanding why decisions were made matters more than the decisions themselves. What unexpected lesson changed how you build? Share this with a dev who needs to think bigger 👇 #DeveloperLife #WebDev #Engineering #StartupLife P.S. Great code starts with great problem understanding and the actual need. Everything else is just implementation details.

4

3 Comments

Good news for Scala 2 - maintenance will be "continued indefinitely". https://lnkd.in/dDWMA8Hr This means no pressure on teams to retool and to migrate their Scala 2.13 apps. (I expect most teams to be on 2.13 as that is required to support recent Java JDKs, and I expect most teams to be deploying on recent JDK versions for security reasons.)

5

2 Comments

💎 What's better than a spring day? A spring day where you learn how to avoid using JavaScript in Ruby on Rails apps. If you're in Montreal, I'll be giving a talk tomorrow at 6pm on Ruby Hotwire: Drive, Frames, and Streams tomorrow at Potloc. https://lnkd.in/emc9KrM8 #RubyOnRails #Hotwire #NoJavaScript #WebDevelopment #TechTalk #MontrealTech #RailsDevelopers #RubyHotwire #SoftwareDevelopment #CodingTips

6

Kafka-compatible data streaming should not be expensive or complicated. WarpStream is used in diverse production environments. Create your free account and get $400 in credits that never expire at https://lnkd.in/g_nUnb7x

11

2 Comments

Finally Breaking My Silence (Why I Decided to Start Sharing My Journey) After 20+ years in tech, from selling ice cream in Rio's favelas to building distributed systems at Microsoft and AWS, I realized something: I've been too quiet. Why I never shared before: - Too focused on building - Imposter syndrome - "Others know more" - Always next challenge But yesterday something hit me: The kid selling ice cream in Rio would have killed for the knowledge I have today. So I made a decision: Starting today, I'll share: - Real engineering lessons - System design insights - Cloud architecture decisions - Raw truth about tech career No sugar coating. No buzzwords. Just hard-earned lessons from: - Building Azure's notification system - Scaling AWS services - Getting patents - Leading global teams - Starting from zero What you'll get: 1. Deep technical insights - Distributed systems - Cloud architecture - Real scaling problems - Performance optimization 2. Career real talk - From favela to big tech - Breaking barriers - Growth mindset - Actual challenges 3. Startup insights - Early decisions - Technical debt - Team building - Real trade-offs Why now? Because somewhere there's a kid like I was Thinking tech is impossible Thinking dreams are too big Needing to know it's possible Follow along if you want: - Zero fluff - Deep technical knowledge - Real experiences - Practical insights PS: Yes, I'll share the ice cream selling strategies too. Some of them still work in system design 😉 Special thanks to Thiago Caserta and Marcelo Cauduro for pushing me out of my comfort zone. Sometimes you need great co-founders to remind you that your journey matters.

177

25 Comments

Learn how to utilize the slash commands in GitHub Copilot for Visual Studio with ease! Check out Bruno Capuano's latest video tutorial, focusing on how /AskVS enhances your coding experience by facilitating code refactoring and providing helpful suggestions. https://lnkd.in/gRDrzvNU #github #copilot #ai #msftadvocate

10

2 Comments

A few days ago, I started working on a prefetch implementation based on the recommendations from Unified Streaming’s documentation: https://lnkd.in/dKhQ6phN. Here’s the code: https://lnkd.in/dhwWeWdX (NGINX + Lua and a web server written in go for testing purposes) I haven’t tested it in production yet, but I would appreciate hearing from anyone with experience implementing something similar. If that’s you, could you please share your results? #videostreaming #livestreaming #videoengineering

31

Let's talk about hiring "10x engineers" 🤠 🚀 . The search for unicorn-like figures is always a top of mind for hiring, and there’s a seductive trap many fall into: the allure of the "artisan coder." Artisan coders are craftsmen of the code world, creating bespoke solutions that all too often prioritize their own personal aesthetics over team efficiency. While their craftsmanship is often excellent, it can introduce complex dynamics within teams . Psychologically speaking these individuals may exhibit a superiority complex, believing that their methods and outputs are beyond the standard approaches most developers use. This isn't just about preference—it's a manifestation of personal rigidity that can lead to increased conflicts within teams. Their insistence on niche and rarified methods can alienate colleagues and stifle collaboration, crucial for agile and harmonious project development and maintainability. Furthermore, they often show a reluctance to adopt widely-used tools and frameworks (usually touting arbitrary non-business-centric performance objectives) isn’t just a technical choice—it raises the cost of development. I call it the "I'm special" trap: esoteric choices should only be considered in rare situations, where they align with business objectives. Most of the time, it's simply overkill. Further, tools (IDEs, web frameworks, workflow engines) are not merely facilitative; they are foundational for ensuring that everyone in the team can work together seamlessly and efficiently. The consequences are tangible: projects may face delays, suffer from scalability issues (usually because others are less-productive trying to contribute), and incur higher costs due to the need for specialized maintenance or even complete rewrites of the artisan’s code. Don't get me wrong: I love artisans - and some do produce industry moving masterpieces - but most do not. So beware and be on your toes. Your 10x can easily minus 5x with the wrong hire and you find yourself mired in a technical swamp. Stay safe out there. 🤘

23

8 Comments