Felipe Cecagno

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

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

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

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

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

Cillers Podcast World Class Hackathons Episode 12 OUT NOW: Meet Matheus Guimaraes, Senior Developer Advocate at Amazon Web Services (AWS) Matheus boasts over 20 years of experience in the industry, ranging from developer to CTO and everything in between. In this episode, we talked about how participating in top-tier hackathons not only broadens your understanding of game-changing technology but also deepens your self-awareness. According to Matheus, there's no better path to self-knowledge and personal growth than through hackathons. Participating in these events can also ignite new motivation and aspirations within yourself. 😍 Episode Link: https://lnkd.in/d5kKYGYd Enjoy!

18

1 Comment

🎉 Exciting news! I've just released EasyAssets, a Flutter package that takes the headache out of asset management! 🚀 Ever found yourself drowning in a sea of asset strings, desperately wishing for a life raft? That was me, until I realized – why not build the raft myself? 🏊‍♂️💡 EasyAssets automatically generates a Dart class with type-safe constants for all your assets. No more typos, no more string gymnastics – just smooth sailing! ⛵ Why I built it: 1️⃣ Couldn't find a library that did exactly what I needed 2️⃣ Wanted to simplify asset management for Flutter devs everywhere 3️⃣ Thought it'd be fun (spoiler: it was!) But this is just the beginning! On the horizon: 🔮 Build runner integration 🔮 Customizable output folder 🔮 And more! I'm all for open-source collaboration, so if you're itching to contribute or just want to check it out, hop on board! 🏴‍☠️ GitHub: https://lnkd.in/gTWb5DGK pub.dev: https://lnkd.in/gHQ5ThuV Let's make Flutter development a breeze, one asset at a time! 💨🌈 #Flutter #OpenSource #DartLang #MobileAppDevelopment

3

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

🚀 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

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

The manual is out; automation is in. I'm incredibly proud of our team and their fantastic work on fully automating our API documentation process. Special shoutout to Luís Santos Henriques and Diogo Correia for leading this project. By combining tools like TypeScript, OpenAPI and Fastify, we've built a system that significantly improves our development workflow through automated documentation updates and code autocomplete features. This approach allows our developers to author service-to-service communication much faster and without errors. By leveraging OpenAPI, JSON Schemas, and TypeScript, our team has developed a seamless process to maintain our frontend and backend microservices that boost efficiency, ensure accuracy, and greatly enhance developer experience! Check out Luís's article to learn more about this impactful approach: https://lnkd.in/dunVe_Ff #DeveloperEfficiency #Automation #Pipedrive

64

7 Comments

👋 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

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

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

Some conversations here about tools and technologies seems a bit short term to me. A couple of years ago people would complain about GraphQL (there's a bigger reason why the sudden hype against GraphQL started, but I'll won't cover it today...) A popular point was around GraphQL Codegen as being hard to setup and slow. But at The Guild Software we think long term... Since than, GraphQL Codegen been worked on and improved daily (continuously for almost 10 years now....) Presets for client and server were introduced to make it extremely easy to setup. And with the latest release by Eddy Nguyen, the new server present is now: * ~50% faster in medium-large codebases * Supports Apollo Federation much better My ask of you all is to keep bringing us real feedback If you say GraphQL is bad/hard - tell us exactly why, and please make sure you use the latest and greatest of our tools before you do....

19

3 Comments

Just got a peak at Caio's new book. My review: it's a handy guide for beginner and intermediate Bubble devs. 3 things that will help you level up 👇 1. References to all of Bubble's capabilities Bubble has a lot of functionalities and it's hard to keep track of them. This book can be a nice indexed list for your reference. 2. A guide for responsiveness design It can be complicated for beginners to grasp. The way it's presented here makes this way easier to understand and implement. 3. Understanding and implementing Databases Databases can be a pretty foreign concept, especially for non-technical Bubblers. The Database section in here simplifies it. I've added it to Atomic Fusion's resources section. Adding a link in the comments. #nocodedevelopment #nocodelowcode #webdevelopment #uiux #designer #bubble #software #tech #webdesign #webapp #freelancer #founder #saas #startup #nocode

36

4 Comments