Leonel Norat

Write tests that last! In this article from Builder Alexa De La Garza, learn how to future-proof your workflows, creating maintainable journey tests that adapt to change. #AutomationTesting #QualityEngineering #Playwrights

14

1 Comment

Join Kevin Morales, he'll be talking about HOF in Android and how to implement it to improve the performance of your apps. You'll see examples and a live demo at #DevFest #Miami🌴 #DevFest2024Miami 📱 #MobileDevFest 🤖🌴

4

💡 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

🎬 Time to React with today's Tech Tidbit ⚛️ In this edition of Tech Tidbits, Luis Felipe Zamora talks about making your React code more modular, cleaner, and easier to maintain with custom hooks. 🛠️ If you need to reuse logic across components, manage complex states or side effects, or extract specific logic into its own file, custom hooks are your answer. 🎥 Already using custom hooks? Share your tips and experiences with us! 💬 #TechTidbits #React #CustomHooks #WebDevelopment #CodeOptimization #FrontendTips

41

How We Streamlined Invoice.me’s Financial Operations with Microservices and Cloud-Native Architecture We had the opportunity to help Invoice.me, an online accounting platform for SMBs, in modernizing their legacy Ruby on Rails codebase. Their monolithic architecture was slowing down feature releases and complicating deployments due to code dependencies. On top of that, their on-premise infrastructure just couldn’t handle the rapid growth they were experiencing. ⚙ We refactored their entire application into a microservices architecture, splitting the codebase into independent, self-contained services, each with its own API and database schema. This modular approach allowed parallel development and independent deployments, significantly speeding up feature delivery. ⚙ We also migrated their platform to AWS using Kubernetes for container orchestration, ensuring elastic scalability—so Invoice.me can now easily adjust resources to meet growing user demand. ✅ The result? Faster development cycles, smoother deployments, and a scalable cloud infrastructure that’s ready to handle future growth! Read the full case study: https://bit.ly/3ZQCPxQ 

15

🔎 Discover the Top JavaScript Frameworks for Web Development in the latest blogpost written by Silvana Molina, Service Delivery Manager at Coderio. Learn how these powerful tools can boost your development speed, enhance productivity, and improve code quality 🌎 https://lnkd.in/deZAZ-G3 #Coderio #technology #softwaredevelopment #softwareoutsourcing #JavaScript #WebDevelopment

12

WhatsApp stands as a testament to FP's power in real-world applications. Brujo Benavides brings this practical perspective to #FnConf, where he'll demonstrate tools for maintaining large Erlang and Elixir codebases. Don't miss his session on Hank and Meandro! Learn more: https://lnkd.in/g3SZP3W9 #Erlang #Elixir #CodeQuality

5

WhatsApp stands as a testament to FP's power in real-world applications. Brujo Benavides brings this practical perspective to #FnConf, where he'll demonstrate tools for maintaining large Erlang and Elixir codebases. Don't miss his session on Hank and Meandro! Learn more: https://lnkd.in/g3SZP3W9 #Erlang #Elixir #CodeQuality

1

Check out our newest BLOG! "How to implement validation with captcha" by our own David Moreira! .NET Developers will find this very interesting and useful for their work with .NET and Blazor tech as we learn new things every day! https://lnkd.in/dPWvC3Wv #blazor #components #blazorise #dotnet #csharpdotnet #programming #opensource #development

22

FullStack development is not easy. It's pretty hard. This is the truth. You have to deal with deadlines. You have to master fundamentals. You have to build projects to learn. You have to learn advanced concepts. You have to develop complex features. So, remember this... Behind struggling, you have a brilliant future waiting for you. Trust in yourself.

1

👨‍💻 Ivan Xue built seamless test automation with Cypress + Azure DevOps. Ivan, Staff Software Engineer in Test @ Prospa and #CypressAmbassador, joined us to share how he successfully tackled the challenge of structuring an effective test pipeline. Discover: ✅ Why Prospa chose Cypress ✅ Why Prospa opted for Cypress Cloud ✅ Integrating Cypress tests with Azure CD pipelines ✅ ...and more! https://lnkd.in/ejX_mBfx

13

🌟 Excited to Share This Contribution of Celestial Systems Inc. to Ext JS 🌟 I’m thrilled about this upcoming webinar: "Do More with Less: Your Sencha Ext JS Application" 🗓️ Date: December 5, 2024 ⏰ Duration: 30 minutes This is a fantastic opportunity to explore how to modernize legacy Ext JS applications, integrate real-time analytics and AI, and craft custom themes for cohesive branding—all in just 30 minutes! I’m personally looking forward to the Live Demo showcasing the potential of modern Ext JS applications. If you’re passionate about taking your Ext JS skills to the next level, this is a session you won’t want to miss. Let’s grow and innovate together! Sencha #ExtJS #FrontEndDevelopment #WebDevelopment #extjs #SoftwareDevelopment #JavaScript #Sencha

10

Watched a portion of the old Brian Will video on why OOP is bad (https://lnkd.in/epvfRpPR), and bombed out fairly hard when he came out with the puzzling assertion that messages between objects properly speaking shouldn't include object references. Well, there goes your visitor pattern; there goes the UI staple of registering objects with some event bus for callbacks when particular events happen. Is there some source in the literature (Alan Kay, I guess) for this odd restriction? It seems like a basic misapprehension: sure, messages should transfer representations of internal state and not haphazardly leak references to the state itself (otherwise external parties can mutate it without going through the owning object's protocol), but it's also a pretty basic affordance of message-passing systems that the addresses of things that can receive messages are first-class things that can be passed around (compare URIs in REST, or channels in pi calculus). The other odd assertion was that permitting many objects in an arbitrary graph to hold a reference to an object and access its methods was as bad as having global shared state. It fairly obviously isn't: the ability to exercise the protocol for reading or updating a particular bit of state can get passed around to wherever it needs to be, but isn't immediately available to everything, and pretty much the whole point is that you're passing a pointer to the protocol, not the rights to inspect and modify the data structures it guards. It seems that Will wants to argue for a hierarchical flow of messages down a DAG-shaped stack of routines and subroutines with a single controlling root procedure, rather than a potentially cyclic call graph with objects fielding requests from all angles. In practice that's what your average Spring Boot service actually does of course: controller to service to persistence or external client layer, and back up again. But (and this is an argument for a future post) that's because the average Spring Boot service is fundamentally procedural code, with a bit of indirection between modules. Other topologies are possible, and appropriate for particular use cases. The most generous reading I can give of Will's argument is that OOP offers more flexibility than perhaps a majority of actually existing programs really need, and we'd be happier and less burdened by object bureaucracy if we wrote those programs in a more constrained idiom. I actually think that's kind of true, but haven't got to the bottom of what it means in practice just yet.

2

Just a few more hours before our webinar "Empowering Java Applications with NoSQL: A Hands-On Workshop" starts! ⏰ Join us as we discuss with Otavio Santana how NoSQL databases can advance your Java applications: https://lnkd.in/enCHHytD #NoSQL #JavaDeveloper #JavaApplications #FreeWorkshop #TechWebinar

13

💡 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

Everyone is excited about new changes in SwiftUI during #WWDC 2024. But many apps are still relying on UIKit. Read all notable changes in UIKit from this great summary by Jordan Morgan https://lnkd.in/g7f8ejGV

2