Bruno Cardoso

🌟 Join us at #KubeCon + #CloudNativeCon North America 2024 🌟 I'm thrilled to be presenting "Scale Job Triggering with a Distributed Scheduler" alongside Artur Souza next week at KubeCon! 🚀 Imagine scheduling thousands—or even millions—of jobs, all triggered reliably and persistently, even in the face of downtime. In this session, we’ll dive deep into: 🔷 Why #Dapr needed a distributed Scheduler 🔷 Design decisions and architecture 🔷 Code and package walkthroughs 💡 This session is a must see if you're tackling job scheduling at scale and interested in how Dapr can simplify your distributed system design. 📅 When: Wednesday Nov 13 at 3:25pm (local time) 📍 Where: KubeCon North America, Salt Lake City, UT 🔗 Session Details: https://sched.co/1i7lq Come chat with us at the Diagrid booth during the conference! We’d love to answer your questions, hear about your projects, and see how #Catalyst & #Conductor can help with your use cases. 🔥 Looking forward to discussing #scalable job scheduling and #system #design with y'all! #KubeCon #DistributedSystems #Dapr #Kubernetes #TechTalk #CloudNative #go #SDLC

33

2 comentários

Are you using AWS Lambda? A new book is in the works by 🦁 Luciano Mammino and James Eastham for building efficient, sustainable and cost-effective serverless functions using AWS Lambda and Rust. https://rust-lambda.com/

27

6 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

👋 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

Two years ago, I posted a guide on DEVTO explaining when to use rem, em, or pixels in web development. I initially created this guide because I couldn’t find an easy explanation on the web, so I wrote it in Portuguese to help others who had the same doubts as I did. Today, while reviewing some of my old posts, I noticed that this particular post had reached 10k views. So, I decided to recreate the post in English to help more people with this basic topic. Here’s a quick explanation: Pixel (px): An absolute unit representing a fixed size on the screen. In CSS, a pixel is not the same as a physical pixel but rather a reference pixel based on a 96dpi display. Usage: Ideal for fine-tuning and elements that require fixed dimensions, such as borders and precise positioning. It does not adapt to zoom settings or changes in the root font size. REM (Root EM): A relative unit based on the root font size of the document. By default, 1rem is equal to 16px but can vary if the root font size is changed. Usage: Great for ensuring accessibility and adaptability. When the root font size changes, all elements sized with rem adjust proportionally. It helps maintain a responsive and adaptable design. EM: A relative unit based on the font size of the parent element. Its size can vary depending on the context in which it is used, meaning it can inherit the size from its parent. Usage: Useful for defining font sizes, spacing, and line heights that are relative to the parent element’s font size. This allows the layout to adjust dynamically based on the text size of the parent element. Usage Tips: px: Use for fine adjustments and elements that do not need scalability. rem: Use for most of your layout to ensure flexibility and ease of accessibility maintenance. em: Ideal for properties that need to be dynamic relative to the parent element, such as internal spacing and font sizes. If you want to read the complete post check here: https://lnkd.in/dkuyw4Rn

5

New edition on the Lodgify Tech Blog! 🚀 We're excited to share our latest blog post authored by Luiz: "Implementing Cache with the Decorator Pattern". In this article, Luiz explores how to leverage the Decorator Pattern to efficiently implement caching, enhancing both performance and scalability in your applications. Whether you’re an experienced developer or just getting started, Luiz’s insights and practical examples will be invaluable for your next project 😉. Check out the full post here: https://lnkd.in/d5pkvAXR Explore careers at Lodgify and join us on the innovation journey! https://lnkd.in/g46Ghnr #TechBlog #SoftwareDevelopment #Caching #DecoratorPattern #LodgifyTech #ProgrammingTips

27

Hey everyone! 🎉 I just published a new blog on Medium about Test-Driven Development (TDD). After years of coding and experimenting with TDD, I wanted to share my insights and challenges. I'd love for you to check it out and share your thoughts! 📚✨ #TDD #testdrivendevelopment #android

75

6 comentários

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

Are there any #informationarchitects or #ux designers in my network here that could consult with me on improving the IA of the Node.js Learn section? At the recent Collab Summit in Dublin, we discussed the need to refactor our linear journey. Matteo Collina got the ball rolling, which we are tracking at https://lnkd.in/g4UhiMVV My instincts as an once-proficient-now-amateur UX practitioner are as follows: - inventory the content - think through a card sort strategy, from maintainers, BUT ALSO, users - re-org easy wins - identify gaps, breakout issues - recruit writers to help fill in gaps - testing??? This is another great example of the multi-disciplinary work an open source project benefits from. It's not all code, and never was, as we have grown and found each other. https://lnkd.in/gNPUEVDB tries to make a strong case for this, and it's been fun to reflect on how to embody it. #opensource #nodejs #contentdesign #technicalwriting

17

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

Hey folks! 👋 Are you looking to boost your Ruby on Rails app’s performance and responsiveness? Look no further! I’ve just published a new article on Medium where I dive deep into the wonders of Event-Driven Architecture and how it can make your app more scalable, resilient, and real-time! 🌟 In this guide, you'll discover: ✅ Why Event-Driven Architecture is a game-changer ✅ A step-by-step walkthrough to implement it in Rails ✅ Real-world use cases that might just spark your next big idea. If you're ready to take your Rails app to the next level, you don’t want to miss this. Check it out and let me know what you think! https://lnkd.in/g2JdDvut Let’s make our apps better, one event at a time! 🚀 #RubyOnRails #EventDrivenArchitecture #WebDevelopment #TechInnovation

1

📝 Rewrite for the right reasons https://lnkd.in/d24FStGf

2

I really enjoyed the opportunity to share insights about a tool I had just learned in a short period. One memorable moment was when an audience member asked about the difference between Apache Flink and Apache Kafka. Both tools have impressive processing speeds, integrate well with databases and storage systems like PostgreSQL and BigQuery, and are scalable—making them powerful in the data processing landscape. What I was excited to clarify was the fundamental distinction in how each tool operates. While both offer strong cross-functional features, Apache Flink functions as an intelligent data pipeline, enabling developers to perform various transformations and analyses on incoming data. In contrast, Apache Kafka acts as a "dumb" data pipeline—it reliably transmits data as-is, ensuring that a "1" sent into Kafka will reach consumers unchanged. Both tools serve unique and impactful purposes in technology, having revolutionized the way we handle real-time data. Here’s to many more opportunities to speak and share knowledge!

22

1 comentário

Hi, AWS CDK is a very relevant topic nowadays. Important tool that I will focus more on in 2024. This is my study recommendation. Fabricio Veronez Vishnu Kvs Herbert Souza Pereira https://lnkd.in/dJuXwT8T

6

Zuplo was super easy for me to integrate with my web API using only a couple of steps: 1) I needed to forward traffic from Zuplo to my server. This was done with "one line", if I can even call it that, in the Zuplo portal. Given my path on Zuplo, I just had to pick an option in their UI to rewrite and tell it what URL to go to. So far, so good. We like easy. 2) I needed to lock down my server. I want Zuplo to be the "front door" to my web API, but I still have to expose my service so that Zuplo can access it! To do this, I added an API key that my server knows about and Zuplo is configured to use. This means that Zuplo is the only outside source that knows the "secret" to talking with my web API. While my service could technically be discovered and callers could try hitting routes, they'll all be very quickly rejected. 3) ... to be continued! This is where all the *extra* stuff can get added: - Auth - Rate limiting - Monetization - Analytics - Documentation ALL OF IT done through Zuplo. That makes my life MUCH easier 😄 Check out more Zuplo here: https://lnkd.in/giqBk786 Stay tuned for the video coming this Friday on how I modified my ASCII art API to work with Zuplo! This Saturday's newsletter will walk through in more detail. #zuplo #api #webdev #aspnetcore

15

A few months ago in Brazil, the CTO of a major national bank (CAIXA) made a controversial statement about the IT. He claimed they no longer needed these professionals for two main reasons: first, due to bureaucratic processes in corporate IT, which resulted in long timeframes for task completion; second, because the business team itself had started using AI to create solutions. The executive argued that standard IT took too long to get things done, while AI allowed for greater agility. In his view, the important thing is to release software as quickly as possible, seeing no issues if the releases have flaws. This stance is quite absurd and potentially dangerous even more in a financial context where security and quality matter. We shouldn't sacrifice quality for the sake of speed. While it's true that AIs should be used to assist and enhance the development process, we're still far from being able to completely replace human developers.

4

Rust on Rails? Maybe. But Rails 8 stole the show! It started with a bit of curiosity. As I'm using Rust a lot, very normal to dive into a bunch of contents, I came across something unexpected: Loco, a Rust framework inspired by Rails. Some even joked about calling it "Rust on Rails," which got a good chuckle out of me. It’s not the first framework trying to recreate the magic of Rails in a new language Laravel, AdonisJS, and a few others have attempted similar feats, some got good outcomes others not. Naturally, with my history of working extensively with Rails, I had to give it a shot. Honestly? My experience with Loco was mixed. A few bugs here and there, some promising features, but nothing that truly blew me away. It’s got potential, sure, but it’s still in the beginning. That’s when the thought hit me "what’s going on with Rails these days?" I’d been out of the Rails world for a few years, and I wasn’t exactly up-to-date. Little did I know, just few days prior, Rails 8 beta had been announced. Talk about perfect timing. Nostalgia hit hard as I watched DHH’s keynote. The new tools, the sleek features, and that signature Rails simplicity I was hooked again. I had to try it. So, I did what any developer would do: I fired up Rails 8 and built a quick CRUD app. And when I say quick, I mean really quick. It was like stepping back into a world where building high-quality, standard applications was fast and intuitive again. Rails has always promised speed to develop, and it still delivers. Revisiting Rails reminded me how much fun the Ruby ecosystem can be. For anyone thinking about future projects, personal or professional, Rails 8 is absolutely worth considering. For those curious about Rails World 2024 Opening Keynote with DHH, here’s the link https://lnkd.in/evANSeNU And if you want to check out the new features, the Rails 8 page is here: https://lnkd.in/ewCyZx5c

14