Ronald Poillot Cartes

TDD is an excellent methodology to build software. To me one of the biggest advantages is that I need to know what I want. I can easily get lost in the code: building something and later realize that it is similar to what I want but what is similar is not the same. With writing the tests first I realize that I don't even know what I want, so I can take a step back, think, and then go for it. It saves me a lot of headache and time. #TDD

1

💡 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

Hello everyone, how are you? Today, Tiago Nascimento Souza and I had the opportunity to speak to the platform engineering community about our journey in building our IDP. This journey started in 2015 and we have continued to evolve up to the present day. If you couldn't attend the webinar, here is the YouTube link: https://lnkd.in/dF4mpHgF #platformengineering #devops Sicredi Platform Engineering

77

Drawing insights from my conversation with Thiago Bomfim, an experienced software engineer who made the leap from Brazil to Portugal, here are the 10 most crucial tips for developers considering a move to Portugal. Read more 👉 https://lttr.ai/ASUEe #RichCulturalHeritage #ExperiencedSoftwareEngineer #InternationalCareer #LifeChangingDecision #AttractiveDestination #DrawingInsights

5

What does it mean to be a VP of Engineering, managing 80 people? How do you approach goal setting, professional growth, managing technical debt and increasing velocity? We are covering all of this in the interview with Greg Stewart, a VP of Eng at Flo Health. Listen it all here:

11

Leading technical teams requires a delicate balance between achieving results and fostering a culture of learning. This article explores strategies for new managers to encourage experimentation and transform mistakes into valuable stepping stones for growth. Ready to unlock the innovative potential of your technical team? Read the full article here: https://lnkd.in/d_xzsYTR #leadership #technicalteams #innovation #experimentation #learning

32

2 commentaren

The Value of Design Documentation in Microservices Teams 🛠️ When developing microservices in Go, designing is just the first step. The real magic happens when you defend and validate that design with your team. 👥 Team Collaboration: When teams gather to review and challenge design decisions, it strengthens the architecture and ensures no critical element is missed. A design that has passed through multiple perspectives is one that’s more robust and future-proof. 📄 Documentation Matters: Once the design is validated, creating clear documentation is essential. This documentation will not only capture key design decisions but also serve as a guide for new team members joining the project. It answers the “why” behind each decision and ensures that as the system evolves, everyone is aligned. 💡 Good design is the foundation; good documentation is the bridge to future development success. #GoLang #Microservices #TeamCollaboration #SoftwareArchitecture #DesignDocumentation #TechLeadership

2

Value of the good feedback to your reports is extremely important. So, let’s dive into story of engineering manager Bob! You all gonna be familiar with his feelings and situation: https://lnkd.in/gFszHd3s

35

I don't remember who said this (if you know, comment, and I'll give credit): "The system architectures are results of companies organization... The system design represents companies' relationships, communication's way, etc...." Businesses can justify the complexity but it is more about the company organization. The system reflects the team dysfunctions (comm, exchanges, isolation, etc)

2

4 commentaren

Good Read from Maarten Dalmijn 📖!!! Key Takeaway: 1- Set reasonable sprint goal 2- Sprint is flexible. Drag in work as necessary 3- Instead of pushing in work based on capacity, pull in work based on the flow of work. !! 4- Actively manage your flow of work https://lnkd.in/g7KjGm7z

12

This is why I hate PMs great way to (probably) waste time on urgent jobs: I have attached a 663-word text for translation into Dutch for your consideration. This would be for the client’s booking app.   Ideally we would like to receive the translation back by 12 noon GMT tomorrow, Friday 1st November.   Please can you let me know if you would be available and what rate would apply. As we don’t have a very high budget for this job, I thought I’d better ask. === so in short you want: 663 words for a booking app (the part of the client's business that insures money coming in) , in less than 24 hours, and you want it for peanuts probably.... (but on that first mail you are not letting me what the budget is - so you hope for something really low) ====

6

10 commentaren

Data Contracts Live Inside Sprints Now Reviews Beat Perfect Docs... Weekly data reviews outperform static contracts. Here's what works: Contract-as-Code Reality ↳ Embed contracts directly in CI/CD pipelines ↳ Deploy dbt tests as living contract checks Two-Way SLAs Work ↳ Both producers and consumers set measurable expectations ↳ Review adherence in sprint retros, not quarterly Sprint-Level Feedback ↳ 15-min weekly contract health checks ↳ Fix small issues before they break pipelines Measure What Matters ↳ Track prevented incidents, not doc updates ↳ Count days between contract violations Real Team Ownership ↳ Rotate contract review leads monthly ↳ Share fixes in team learning sessions Contracts work best when treated as sprint deliverables, not shelf documents. As data scales, embedded contract testing will replace static agreements. "Quality isn't checked; it's built-in sprint by sprint." - W. Edwards Deming. When was the last time you reviewed a data contract in your sprint retro? Share your sprint-level contract wins in the comments. Repost ♻️ to promote better data practices. Follow Siddhartha Vemuganti, and tap the 🔔 for data engineering insights! #DataEngineering #DataOps

Have you ever sent a Pull Request but people seem to ignore it? Or perhaps when you start reviewing a PR your feel overwhelmed? These symptoms speak of a recurrent problem in most teams about the quality of our Pull Requests. In this article, I'll explore practical tips to help you prepare PRs that your team will want to review and that ultimately will help you raise the quality of your codebase. https://lnkd.in/gHygJPNp

6

🎥 Simplify video integration with the Vonage Video API! Choose default UI for ease or mediaStreams for granular control. Whatever your preference, we've got you covered. In this post, Javier Molina Sanz explores seamless integration options tailored to your needs. #mycompany https://lnkd.in/eb_qfeTn

1

Engineering levels in the organization - always a topic for holy wars. In this video we will try to describe difference between different levels of ICs from my humble point of view :) https://lnkd.in/g34My-WP Enjoy!

56

1 commentaar

💡 Last week, during a consultation with a CTO of a custom software development company, we tackled an important question: How can we increase the quality of delivery in teams made up mostly of junior engineers❓ It’s a broad topic, and we could easily write a book on it! However, I offered two general high-level options: 1️⃣ Hire experienced engineers who will ensure the quality. 2️⃣ Let your junior engineers take ownership of quality by: ▶ Explaining the "why" behind their tasks. ▶ Gradually giving them more ownership and responsibility. ▶ Involving them in decision-making. Of course, tools for quality checks help, but from my experience, unless your engineers truly feel ownership over quality and leadership supports this mindset, it won’t work sustainably. Now I’m curious, what other options or approaches would you suggest to improve delivery quality in junior-heavy teams? I’d love to hear your thoughts! #engineeringmanagement #techleadership #mentoring

7