Luiz Guilherme da Silva Junior

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

🎤*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

Driver is You and Passenger is You as well! = Guilherme da Silveira, 29, of Revere, and Priscila Barbosa, 35, of Saugus, pleaded guilty to one count each of conspiracy to commit wire fraud. Barbosa also pleaded guilty to one count of aggravated identity theft. U.S. Senior District Court Judge Mark L. Wolf scheduled sentencings for both defendants on Aug. 4, 2022. In May 2021, da Silveira and Barbosa were charged along with 17 co-defendants with conspiracy to commit wire fraud by using stolen identities and falsified documents to create fraudulent driver accounts for rent or sale to individuals who might not otherwise qualify to drive for the rideshare or delivery services. According to the charging documents, the defendants allegedly used victims’ identifying information to apply for driver accounts with the rideshare and delivery companies – enabling them to pass the companies’ required background checks and create driver accounts in victims’ names. The defendants allegedly obtained victims’ names, dates of birth, driver’s license information and or Social Security numbers from co-conspirators and other sources, including sites on the Dark Net. The defendants and co-conspirators also obtained driver’s license images directly from victims, by photographing victims’ licenses while completing an alcohol delivery through one of the services or while exchanging information with victims following vehicle accidents, some of which defendants or co-conspirators intentionally caused in order to obtain license information. As a result of the scheme, Internal Revenue Service Forms 1099 were generated in victims’ names for income that conspirators earned from the rideshare and delivery companies. In connection with the scheme, Barbosa and da Silveira obtained driver’s licenses and Social Security numbers that they and their co-conspirators procured from the DarkNet and other sources. They then used these stolen identifiers to create and apply for numerous fraudulent accounts with the rideshare and delivery companies and supplied these identifiers to other co-conspirators who also created fraudulent accounts. To circumvent facial recognition technology utilized by rideshare and delivery companies as a security measure, Barbosa edited victims’ driver’s license images to display photos of the drivers renting or buying the fraudulent accounts. Barbosa and da Silveira each received over approximately $791,000 and $570,000, respectively, from the scheme in the form of rental payments from individuals driving under these accounts and payments from the companies generated with these accounts. Way to go Uber and Lyft - good job on the background check process!! = Somebody may be driving Uber or Lyft with your identity. Wouldn't it be a fun case: Driver is You and Passenger is You as well! Looks like: Schrodinger's Car

27

6 Comments

Measuring engineering work by just counting issues, PRs or story points is like measuring how much it rained by counting the puddles. 🌧️ Sure, it gives a rough idea, but you're probably way off. Learn more about how Jellyfish has advanced this representation of engineering with their Work Allocation model.

9

🚨 Navigating the X Ban in Brazil: A Technical Perspective 🚨 (message me if you are interested in implementing software to continue your business.) As many of you may know, the recent ban of X (formerly Twitter) in Brazil has sparked significant challenges, particularly within the programming and tech community. This platform, which many of us rely on for real-time updates, networking, and knowledge sharing, is now inaccessible in a critical market. **Adaptability in the Face of Change** Adaptability is a necessity. While the sudden loss of access to X presents real difficulties, it also offers an opportunity for us to innovate and explore alternative solutions. 🔧 Technical Solutions to Stay Connected Alternative Platforms: Exploring other social platforms like [LinkedIn, Mastodon, etc.] to stay connected with the community and receive updates. Custom APIs and Aggregators: Implementing custom APIs to pull in data from various sources, ensuring that I don’t miss out on critical industry news and insights. This includes setting up RSS feeds and using Zapier to automate the aggregation of relevant content. Communication Tools: Using encrypted messaging services and VPNs to maintain communication with peers and clients who are also affected by this ban (while respecting the laws and being careful not to advise VPN usage for the Brazilians themselves as it is labeled as illegal). ⚙️ Problem-Solving in Action In this case, I'm ensuring that my productivity and ability to deliver quality work remain unaffected or the effects minimalized. This situation underscores the importance of being resourceful and having a toolkit of technical skills ready to deploy when traditional methods are no longer available. 🤝 Supporting the Community It's crucial that we stand together and share knowledge during times like these. I’d love to hear how others are navigating this disruption. What tools or strategies are you finding effective? Let’s keep the conversation going and find ways to overcome these challenges together. If you are interested in the technical workarounds, message me and we can go over your options as companies and individuals.

3

1 Comment

What does agility mean as an architectural characteristic? This is a very important question I learned how to better answer thanks to Neal Ford and his amazing course about Architecture for Modern Engineering Practices.

7

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

💡 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

Five years ago, we started MuukTest with a question: Could we make "Great Software Testing and Automation" easier? My cofounder Renan Ugalde & I each have 20+ years of Software Development & QA experience. We've seen Bad Software Testing and Great Software Testing - way too much of the former, not enough of the latter: Bad Software Testing:  - Nonexistent professional testing team, expecting "developers to do all their own testing" (which 'works' until it doesn't) - Wild, non-disciplined, exploratory testing that doesn't help  - Testing that's treated as a second-class citizen in an engineering org, not as a partner - Reactive, under-resourced testing teams  - Testing with deficient coverage and no automation at all - Testing that's treated as the last step in an assembly line - Massive teams of testers, treated like a boiler room - Testing that slows engineering down I spent years of my life in Software QA and Testing roles like this… where I spent my Christmas holidays frantically, manually running regression tests across an entire application that *had* to be released yesterday. This is bad Software Testing. It is stressful for everyone and doesn't lead to good outcomes. Great Software Testing is:  - Proactive - A mix of (smart, disciplined, strategic) manual exploration and automation - Partner to engineering - Happens throughout the engineering cycle - Performed and coordinated by small teams of testing experts  - Employs amazing tools - Helps engineering move faster - Delivers insights, not more work Since 5 years ago, we have always believed that 'Great, Fast, Efficient Software Testing' will be made possible by AI. Bad testing happens because of bad ideas and bad tools, but with AI helping with a lot of the heavy lifting of test automation and maintenance, 'Great, Fast, Efficient Software Testing' is possible for more teams. Proud of our work in AI, making Great Software Testing possible for ANY software team. Great Software Testing means better software, faster development, happier customers, and better outcomes for all. 

25

Test Driven Development & Developer Advocacy - Interview With Guilherme Ferreira You're not a real developer unless you do TDD. Gui Ferreira is a TDD expert -- but no, not even he would tell you this. In our chat together, we covered a lot of ground. It was great to sit down with a fellow Dometrain course author to go over: - His career journey - Developer advocacy - Test-driven development - And MUCH more! Huge thanks to Gui for the talk, and I'd love to do more in the future! 👇Check the comments for the video link!👇

39

3 Comments

It’s crunch time for major initiatives, especially those involving new or existing design systems. Whether you’re working on digital transformation or AI feature development, aligning creative, product, and tech goals is a massive challenge. With over a decade of experience consulting for product and technology teams, I’ve seen what makes projects succeed—or struggle. A critical factor is evaluating the scope and timeline of change upfront. Some important questions to ask yourself ● Do my deadlines align with my current burn rate? Assess your team’s velocity now. You still have a few sprints to gather the right data and set achievable goals. If acceleration is needed, now’s the time to act. ● How do my goals align with my service architecture? For example, does your customer management system have the endpoints to support an upgraded loyalty program? Even if every endpoint isn’t mapped, having a plan for system transitions and scalability is crucial. ● How are my updated designs being implemented? Pixel-perfect implementation from Figma to production isn’t easy. Identifying changes to components and documenting them requires experience and clear processes. Luckily, I know a guy who can help 😉.

12

1 Comment

👋 Hey API developers, this one's for you! 👇 Senior Software Engineer Filipe Freire is breaking down the basics of Kong Inc.’s Insomnia live + Q&A this May. 📆 May 14 Here's a sneak peek of what’s on the menu: - 🎨 Bringing concepts to life - 🛠️ Crafting and prototyping APIs - 📨 Sending requests  - 🗂️ Keeping workspaces organized  - 🔄 Running tests  - 🐛 Debugging - 🤝 Collaborating Your free API Development and Testing 101 course is now open for registration! #KongPin #InsomniaREST #APIMocking #APIDevelopment #DevOps

10

10 tips You Dev need to know before working to Portugal with Thiago Bomfim ▸ https://lttr.ai/ARyu1 #RichCulturalHeritage #ExperiencedSoftwareEngineer #InternationalCareer #LifeChangingDecision #AttractiveDestination #DrawingInsights

6

2 Comments

Yet another excellent post from Marty Cagan about “founder style leadership” addressing two important notions: the product sense, which is built by the founders, and the need to know how to coach people to acquire this product sense subsequently in order to scale

1

💡 [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

💡 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