Juan Cruz Basso

💡 Lead your remote/distributed teams with empathy (my own experience): Working with remote or distributed teams can be a challenge for Engineering Managers. Keeping your teammates aligned across different time zones, countries, or cultures requires excellent organization, best practices, and a lot of emotional intelligence. One thing I’ve learned is that beyond technology and processes, the human factor is probably the most important to manage. You’ll need to resolve conflicts, build trust, and boost productivity, but you won’t be able to do it without empathy—I can assure you of that. A few quick practices that have helped me are: ▶ Clear goals: Ensure everyone is following the same direction. Keep the goals visible to the team (e.g., JIRA board, Slack, etc.), and provide friendly reminders if you have stand-ups with them. ▶ Good communication and cadence: Schedule regular check-ins. Make sure the team feels heard. ▶ Flexibility and cultural differences: Be flexible with schedules and learn how to communicate with different cultures, as not everyone works in the same way. Practice deep listening with your teammates and set clear expectations. Learn what is "normal" for them and find a balance to create a good fit within your team. ▶ Foster a safe environment: Create open discussion spaces for the whole team, plus 1:1 meetings. A meeting I’ve been using a lot, which often gets overlooked, is the retrospective. But for your team to participate and share their true feelings, they need to feel comfortable. What has been your experience leading distributed teams? I’d love to hear other points of view, thoughts, and reflections! Remember, I’m creating more content related to engineering management at https://daniheredia.com/ So sharing it is always more than welcome 🙇‍♂️ #leadership #engineeringManager #remoteTeams #empathy #distributedTeams #distributedTeams #emotionalIntelligence #diversity #cultures #newsletter #team #teamWork

12

Want to come and work with me? We're hiring for a mid-level, a senior and a tech lead software engineer here in Manchester. We are a Scala shop so experience there would be great, but we're also honestly open to smart people with experience in other languages. * Mid-level https://lnkd.in/etE2_err * Senior https://lnkd.in/ehdGirbx * Lead https://lnkd.in/emh_R3Gx Update 2024-04-29: sorry, no visa sponsorship available for these roles. No agencies. Look, I mean it. I know there are arguments both ways but it's not my decision and if you think telling me how good your agency is will change anything, you misunderstand how enterprise companies work.

198

34 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

💡 [TIP] How do you handle unexpected news as an Engineering Manager? In day-to-day work, you and your teams sometimes receive unexpected news that can shake the team's motivation. As Engineering Manager, how are you handling this? Here is how I’m approaching these situations in case it helps you reinforce your own mindset: 1️⃣ Understand this reality: companies evolve. One day, your best teammate might leave. Another day, you might decide to move on. And on another day, the company might make changes. That’s just how it works. 2️⃣ So, I ask myself this question: What opportunities can my teams and I find in this situation? 3️⃣ If you're following step number 3️⃣ , I can ensure you that you'll find at least 1 opportunity to grow. 4️⃣ Communicate this to your teams and remain open to deeply listening to their thoughts and proposals. 5️⃣ Create your own plan to seize the opportunity. The ideal world doesn’t exist. And perhaps it doesn’t because “ideal” means something different to everyone. 🙂 This may sound obvious, but when we receive unexpected news, we tend to ask ourselves why and try to understand it, investing energy in something that probably isn’t up to us. This leads to frustration and exhaustion when it’s unnecessary. I choose to keep fighting to protect my #energy and #motivation. What about you? More content related to engineering management at https://lnkd.in/dNePvQJV #team #growth #engineeringmanager #manager #productivity

10

Finding great devs shouldn’t be this hard. -Freelancers? Hard to keep ‘em locked in. -Dev shops? Tough to manage. -Overseas hires? Time zones get tricky. Meet Revelo: 400,000+ pre-vetted engineers based in Latin America 🇲🇽🇧🇷 fluent in English, working in your time zone, and fully focused on your team. No hoops, no hassles—just the talent you need, ready to start in days. Get your shortlist, skip the drama. Revelo’s got your team covered. 🚀✨ #EngineeringLeaders #RemoteTalent #ProductManagement #HireSmarter #DevTeams #SoftwareEngineering #TechTalent #Nearshoring

34

Super excited to share the latest models from Llama team. It comes with 3 model sizes (405B, 70B and 8B) models. On top of that it comes up Trust & Safety models Llama-Guard-3 and Prompt Guard. New Features 🛣 Longer context: 128k ⚒ Tool calling: It comes with brave_search and wolframe_alpha tool integration and ability to use zero shot learning to create custom tools. 🌎 Multilingual: Supports 7 additional languages on top of English Check out the resources 1. Llama 3.1 Prompt Format (https://lnkd.in/gvgKTkjW) 2. Llama Recipes to help you get started using the latest models. (https://lnkd.in/gvKNfvuZ) 3. Models are live on HuggingFace (https://lnkd.in/gV735VDk) 4. You can download the models directly here (https://lnkd.in/gXMVzhqN)

22

1 Comment

💡 Continuous Feedback is key to Building Stronger Teams: As an Engineering Manager, I’ve learned that one of the most powerful tools we have it’s feedback. I think feedback fosters team growth and engagement. I'm not speaking only about annual reviews. It’s about making feedback a part of your day-to-day management style. What have I discovered over the years? 🔄 Real-time feedback builds trust: sharing it openly and regularly, it creates a culture of transparency opening the door for honest conversations. 🌱 Not only focussed in performance: empower growth in your teams, if they're growing, the performance and results will do it consequently. 📈 Small corrections prevent big issues or problems, giving us time to adjust our team's direction. 💬 Two-way street: be open to receiving feedback, not only from your manager but also from your team. I regularly ask my team, "What can I do better?". You can also create a quarterly feedback form to gather their input So, you'll create a team culture in which engagement, better problem-solving, and a stronger sense of ownership will make the difference 🚀 What has been your experience on this? I’d love to hear other points of view, thoughts, and reflections! Remember, I’m creating more content related to engineering management at https://lnkd.in/drVtNeji ♻ So sharing it is always more than welcome 🙇‍♂️ #leadership #engineeringManager #teamGrowth #feedbackCulture #empathy #feedback #emotionalIntelligence #diversity #cultures #newsletter #team #teamWork

2

Want proof that Trino is spreading far and wide? How about an open source project req_trino to help you write client applications in Elixir from the Erlang ecosystem. Thanks to André Luís Anastácio you can now learn more at  https://lnkd.in/gi9JPE2b

18

Insightful talk "The Myth of the Modular Monolith" by Eileen M. U. is now available! Check this out - https://lnkd.in/dK_3_mZu Eileen delves into the appealing yet often flawed concept of a modularized Rails monolith. She highlights that while this approach might seem like a perfect solution, it frequently fails to address deeper architectural, operational, and organizational issues. I couldn't agree more. A modular monolith isn't a silver bullet, but it does help steer us in the right direction. I think there are two architectural concepts that should be strictly followed to achieve the goal of manageable modular monolith. 1. Modules and their boundaries. Thanks to Shopify, we have a tool for that in the Ruby world. Packwerk gem allows us to define modules and plays like an analyzer that highlights dependency violations between your modules. You can read retrospective about this tool here - https://lnkd.in/dtWCRPjr 2. Module interface. A robust module facet is needed to hide all internals from external users and provide a reliable and concise interface. Unfortunately, Ruby lacks a built-in mechanism for this. There was an attempt with packwerk at some point, but it didn’t get off the ground. Nevertheless, modular monolith unlikely to be truly manageable and comfortable to work with without module interfaces. The closest example of modules and interfaces is Java/Kotlin. In this world we just can't build an application if we break the module interface and try to use things hidden from external use. When we start working with interfaces, we inevitably have to deal with interface types and signatures. Interfaces cannot really be relied upon without signatures. Fortunately, in Ruby, we have RBS and Sorbet. RBS will eventually become the default option for signatures. By the way, RubyMine already works well with RBS/Sorbet and highlights signature mismatches in your code preventing bugs in production. So take a look. Regarding large existing Rails applications that self-move towards a mash of code. Well, there really don't seem to be any easy solutions here. Being huge, a Rails application is cramped, leaving no easy solutions from a technical point of view. Indeed, it seems that only gradual refactoring and changing the culture and priorities within the product can improve the situation. However, I think it's potentially possible to implement an approach in Rails that will force developers to build a reasonable architecture and not mix things up. This will inevitably lead to a slowdown of Rails development velocity, which contradicts the main feature of the framework and is unlikely to ever be implemented. After all, only a few Rails applications survive to the point where we have to solve architectural problems rather than business problems. Tell me about your experience with packwerk and modularisation in the comments! Interesting to see your thoughts! #RailsWorld #Rails #Ruby

4

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

WhatsApp stands as a testament to FP's power in real-world applications. Brujo Benavides brings this practical perspective to #FnConf, where he'll demonstrate tools for maintaining large Erlang and Elixir codebases. Don't miss his session on Hank and Meandro! Learn more: https://lnkd.in/g3SZP3W9 #Erlang #Elixir #CodeQuality

5

WhatsApp stands as a testament to FP's power in real-world applications. Brujo Benavides brings this practical perspective to #FnConf, where he'll demonstrate tools for maintaining large Erlang and Elixir codebases. Don't miss his session on Hank and Meandro! Learn more: https://lnkd.in/g3SZP3W9 #Erlang #Elixir #CodeQuality

1

We asked #developers which programming language they prefer, and the results were close! Our Developer Relations Engineer, Alejandro Duarte, shares the results and explains their meaning. See what he has to say. 👇

24

1 Comment

In my career, I’ve never seen any evidence suggesting a connection between formal degrees and being a good programmer. By “programmer,” I mean developer, engineer, or whatever term you use for people who create software. Whenever I see folks pushing this narrative—which is a thing in Spain—I am genuinely puzzled. I used to think that, as the discipline matured, a formal degree might eventually become recommendable in the distant future. But with the self-teaching possibilities introduced by LLMs, I’m incredibly skeptical. There will always be a market for exceptional courses and teachers, but I doubt universities, as we know them, will be the answer in the future.

118

152 Comments

✍🏽 We have a new article on our blog! This time, José Alejandro Sulbarán Armas, lead front-end developer at Leniolabs_, shares his expertise as a technical interviewer, focusing on the key soft-skills that will attract the interviewer’s attention. 🔗👇🏽 Read the full article: https://lnkd.in/d2_D5Cw4 #technicalinterview #interviewtips #softskills

7

Here's my 2024 LinkedIn Rewind, by Coauthor: Elite status + technical architecture were 2024's twin peaks - but the real story was in the daily engineering challenges that got us there. Turns out you can evolve as a leader while keeping your hands dirty with code. E quem diria? 😅 Key achievements that actually mattered: • Earned FY24 IS Elite Advocate certification (porque sim!) • Achieved Technology Architect Associate certification • Led engineering teams through complex project deliveries • Maintained technical depth while expanding architectural scope Three posts that captured our engineering reality: "FY24 IS Elite Advocate" Because leadership impact starts with technical credibility https://lnkd.in/dDYU7F7T "Technology Architect Associate" Expanding architectural expertise while staying close to code https://lnkd.in/dQg-JqpF "Integration Tests > Pelé > Unit Tests" Sometimes controversial takes are just practical engineering truth 🤣 https://lnkd.in/d5ywda3W Looking ahead: 2025 will be about scaling architectural impact while keeping hands dirty with code - because the best solutions come from living in both worlds. To every engineer balancing technical depth with growing impact: stay practical, keep coding, and remember - integration tests really are better than the Pelé movie 😅 -- Get your 2024 LinkedIn Rewind! Go to coauthor [dot] studio in your browser

6

🚀 Java 21 Virtual Threads at Netflix: A New Era of Performance Challenges Netflix's JVM Ecosystem team recently embraced Java 21, including generational ZGC and virtual threads, aiming for performance boosts in high-concurrency microservices. While virtual threads offer remarkable advantages by suspending and resuming without blocking OS threads, a deeper dive into production revealed unexpected quirks in real-world usage. 🔍 The Issue: Netflix microservices using virtual threads encountered intermittent timeouts and hung instances, leading to unresponsive services. Thread diagnostics showed Tomcat constantly creating virtual threads without available OS threads to execute them, causing socket issues and piling up in a "closeWait" state. 🔑 Root Cause: Netflix's engineering team discovered that virtual threads performing blocking operations within synchronized blocks remain "pinned" to OS threads. This locks resources until all OS threads are occupied, effectively freezing virtual threads waiting for processing. 💡 Solution & Takeaways: After thorough analysis using thread and heap dumps, the team identified specific locking behavior patterns contributing to this issue. Virtual threads’ unique mechanics necessitate careful tuning for high-concurrency services, particularly with blocking calls and thread contention. The team’s experience underlines that, while virtual threads unlock new potential, adapting existing services to harness their full potential can reveal complex interactions in multithreaded environments. 👩‍💻 Insight for Developers: Virtual threads are a game-changer, but mastering their interaction with traditional synchronization and locks is essential to avoid pitfalls. This journey highlights the importance of evolving debugging strategies to match next-gen Java features. 📖 Full Article on Netflix Tech Blog: Dive into the in-depth journey and technical insights by Vadim Filanovsky, Mike Huang, Danny Thomas, and Martin Chalupa on Netflix’s adoption of virtual threads and how they tackled the challenges along the way. https://lnkd.in/daYsmHik #Netflix #Tech

3

1 Comment