Gustavo Campos

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 comentários

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

🎤*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 comentários

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 comentários

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

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 comentários

Red flag: Teams who throw headcount at problems ☠ More is not necessarily better. And sometimes, more is actively counter-productive. Like the technical founders who hire "bee-dee" for the first time without clearly identifying the objectives, the process, and what success looks like. Just some vague notion of growth or expansion. Walk into that situation and you're almost guaranteed to fail, no matter how good you are. Then they'll fire you, blame you for the lack of results and go looking for a new person again. Cycle repeats. Or the leaders who paper over engineering inefficiencies by hiring more and more engineers and brute forcing their way through the roadmap (if there even is a roadmap), at the expense of an effective workflow, product feedback loops and quality code. Green flag: every job in the organization is either building, improving or operating a system ✔ Any well-run business is simply a set of interconnected systems which are operated by people. In a startup, those systems may be very immature, or prone to constant change. But they should still exist. The role of leadership is to create and prove those systems, and then delegate them. Ideally, that means every function is founder-led in the early stages. But if you do need someone to build, say, your marketing engine completely from scratch, it needs to be explicit that the job is to create and systematize the marketing process for the organization. That's not a job for a mid-level marketer. It's playing with fire to bring in someone like that and expect them to "figure it out". Occasionally they will. But mostly they won't. If you're going to delegate the leadership function, you need to hire a leader. If you won't do that, build the system first and then delegate it. But never mix the two. You'll thank me later. #recruiting #hiring #crypto #web3

9

5 comentários

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

Great talk by 🦁 Luciano Mammino about writing Lambda Functions in Rust. I strongly believe there is a good future for Rust, and it's good to see it working in Lambda too! Also I just learned Luciano and James Eastham are writing a book on it!

41

9 comentários

🚀 Mastering Fork Maintenance in Open Source Projects 🚀 Maintaining forks of open-source projects can be challenging, but Joaquim Rocha shares some invaluable tips to make it easier. From using atomic commits to contributing changes back upstream, his guide covers essential practices for smooth fork maintenance. 🔹 Atomic Commits: Keep your git history clean and conflicts minimal by making each commit focused on a single update. 🔹 Identify Fixes: Use conventions to tag your commits, making it easier to manage and squash fixes. 🔹 Avoid Evil Merges: Ensure merge commits don't introduce changes to maintain a clean history. 🔹 Rebase Often: Regular rebasing reduces conflicts and keeps your fork up-to-date with upstream changes. 🔹 Contribute Back: Simplify maintenance by contributing your changes back to the original project. Check out Joaquim's full guide for more insights! 🌟 #OpenSource #Git #ForkMaintenance #DeveloperTips

4

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

WARNING ⚠ : Are you about to design or work on a microservices project? If so, you really need to read this first. I will be publishing a series of articles about the dark side of microservices projects, and how some tiny design mistakes can grow into huge problems 🌋. My point of views are up for debate. I'm not saying I'm right, rather I'm showcasing some of the problems I went through. If you have an opposing opinion please share it with me as these discussions can help both of us learn more 📚.

6

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

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 comentários

1. Gradle Inc. Gradle is like a magic builder for your software projects. Think of building a house - you need to assemble bricks, wood, and other materials. Gradle does this for software. It takes your code, puts all the pieces together, and turns it into a working app or software. It's super fast and can handle big projects with ease, making sure everything is in the right place. 2. Phabricator Phabricator is like an all-in-one project hub for software development. Think of it as a digital workshop where your team can plan, build, and manage projects together. It helps you track tasks, review code, and collaborate in one place. This makes sure everyone stays on the same page, work moves smoothly, and projects are completed efficiently. 3. Gitea Gitea is like a digital storage locker for your code, but with teamwork in mind. Imagine working on a project with friends. You all need to keep track of who did what and make sure you're not messing up each other's work. Gitea helps you do that by letting you save your code, track changes, and collaborate seamlessly. Plus, it’s lightweight and super easy to set up! 4. Huginn Huginn is like your personal internet assistant. Imagine having a smart robot that watches the internet for you and takes action when something happens. Huginn can send you alerts, gather information, and even perform tasks automatically. Whether it’s monitoring news, tracking emails, or managing social media, Huginn makes your online life easier by doing the repetitive work for you. 5. Tabnine TabNine is like an intelligent assistant for coding. Let's say you’re writing a long essay, and someone whispers the next sentence to you. That’s what TabNine does for coding. It predicts what you’re about to type next and offers suggestions, helping you code faster and with fewer mistakes. It’s like having a smart friend who knows exactly what you need. 6. Ansible by Red Hat Ansible is like a remote control for your IT tasks. Imagine having to cook dinner for 100 people in different kitchens. Ansible helps you control all the stoves from one place. It automates tasks like setting up servers, deploying apps, or managing systems, so you don’t have to do it manually. It’s super efficient, reliable, and saves a ton of time. Follow For More 🤖

6

2 comentários

The Open/Closed Principle (OCP) is probably the most debated and sometimes misunderstood among the SOLID principles. I've made my share of mistakes when applying it! I have had several discussions about OCP within our team and the tech community. Here are a few common misuses I’ve observed: Misunderstanding Change: Many believe OCP means that code can’t be changed at all, which isn’t true. Struggling with Extensions: While we make code open for new features, we often struggle to keep it closed for modifications, leading to over-engineering for potential extensions that may never be needed. Ignoring the Principle: Sometimes, we neglect OCP entirely by constantly modifying core classes instead of extending them. Overusing Design Patterns: We can fall into the trap of overusing design patterns like the decorator or observer, even when simpler solutions would work just fine. Too Many Interfaces: Adding unnecessary interfaces that make things complicated. #SoftwareDevelopment #SOLIDPrinciples #OCP #Programming #BestPractices #CodeQuality

7

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 comentários