Oscar M. Cortez Martínez

💡 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

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

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

💡 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

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

The latest article from Qubika's Platform Engineering Studio highlights our expertise in building high performance Ruby on Rails applications - and how you can boost application performance using materialized views in Rails. The article by one of our full stack senior developers, Ignacio Siri, dives deep into: 👉 What materialized views are and how they differ from regular views. 👉 When to use them for maximum impact. 👉 A practical example of aggregating sales data with SearchCraft. 👉 Setting up, using, and refreshing materialized views seamlessly. Read the full article here: https://lnkd.in/e2Af73Tw #RubyOnRails

23

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

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

📰 #ThrowbackThursday ☀️ This summer, enjoy a few poolside reads 🏊📖 Every Thursday, read our best articles by the SensioLabs Tech team on Medium & dev.to We start with Nicolas Valverde's article telling you a true love story 💖 between PHPStorm & Docker 👉 https://bit.ly/3rs0hlO #dev #php #symfony

18

As devoted JavaScript and Vercel fans 🙌 , we watched the annual Next.js Conf, where founder Guillermo Rauch shared exciting updates to simplify #webdevelopment complexity. If you missed it, here are the highlights: 🔹 Community Growth. With over 4,000 pull requests and 570 new contributors, Next.js now sees 7 million weekly downloads. The community is active across YouTube, TikTok, and X, sharing valuable insights. 🔹 Vision for Next.js - Make it Work: Quick setup for seamless application launches. - Make it Right: Reliability and iterative improvements, with Turbopack now stable. - Make it Fast: Enhanced performance and faster build times. 🔹 Turbopack Introduction. This new bundling engine speeds up cold starts and incremental builds, reducing compile time by up to 90%. 🔹 Data Fetching & #Caching Enhancements.  New caching APIs include: - use cache API. Efficiently caches any #React-rendered data (not just JSON). Default in-memory but configurable for custom setups. - Component level caching. Apply use cache at the page, component, or function level for targeted control. - Self-hosting enhancements. #Nextjs 15 adds customizable cache handlers, efficient image optimization, and #Nodejs middleware support. 🔹 Accessible Caching Options. Next.js now offers event and time driven revalidation tools, simplifying caching and setting up for better handling of dynamic and static content. We’ve captured some main points, but check out the full conference (link in comments)👇 if you’d like more detail. Rest assured, we’re following the latest in #web and #mobile development to keep our clients ahead of the curve.

9

1 Comment

🎬 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

🚀 New Article Alert! 🚀 It’s been a while since my last post, but I'm excited to share my new article!, "Taking the Helm as Engineering Manager: Leading an Established Engineering Team". I dive into key strategies for stepping into established teams. You'll reach out REAL situations that I lived, thoughts and tips. Whether you're already an Engineering Manager or looking to step up, these insights might help guide your path toward effective leadership. Check it out in ♦️ Personal Website: https://lnkd.in/ddiTvbq8 ♦️ Medium Link: https://lnkd.in/dWN3zGTq Subscribe to my Newsletter 👉 👉 👉 https://lnkd.in/dNePvQJV ♻️Reshare if you think it can contribute and a reaction/feedback is always a gift 🎁 #leadership #productivity #trust #management #learning #growth #team #help #engineeringleadership #people #goal #stakeholders #strengths

6

The lack of cooperation between delivery teams can be challenging. How can we, as designers, developers, QA’s, BA’s, or delivery leads, improve this? Monica Morales gave a ⚡lightning talk⚡ about bridging this gap at the #DotNetNorth meet-up last night, focusing on how UX Designers and Developers can work better together. Ultimately, we all share the same goal: delivering value to our users while meeting business objectives. We also find joy in solving problems. So, why not work together more effectively? When we collaborate, great things happen! Here are some tips to keep this relationship strong: ❓Communicate and ask questions (a lot of questions... the more, the better). 💬 Show others what you’re working on and ask for feedback (feedback is a chance to learn and improve). ✊ Show mutual respect and value everyone’s input. 🥅 Discuss user goals and needs together. 🛑 Try to understand design, business, and technical constraints. 🔬 Test solutions together. 📝 Hold cross-team workshops. Are there any other tips you think are important for cross-team collaboration? Comment below! 👇 Thank you to all speakers and #DotNetNorth for the fantastic and inspiring event! #Wowtech #WomenInTech #DiversityMatters #ManchesterTech #Inspire #Empower #Support #Encourage #TechCommunity #WomenEmpowerment #TechGoals #Innovation #CareerGrowth #WomenInUX #WomenInDev #Innovation #UXTips #DevTips #FrontEndTips #CVTips

23

1 Comment

During my management training sessions with Joaquin Raya Barberis in cohort 2: The manager's tools are People, Process, Product, and Technology. They are ordered from high impact to low impact which means if you're improving the process, don't expect crazy high ROI. An interesting article by meta about creating a Nudges process to "notify" developers to review PRs helped them achieve ~10% improvement. It's good and huge at their scale but this is not solving the root problem IMO. https://lnkd.in/dYZb7hBQ For a "slow" PR review process, the core problem should solved by using the "People" tool and the "Process" together. It should be fixed by developing a mindset of extreme ownership and accountability across teams.

6

Fully Local RAG 101 with Llama 3 + Ollama + LlamaIndex This article by Pavan Kumar is a great handbook for creating a fully local RAG pipeline with LlamaIndex (with a HyDE layer). It is lower-level than our “5 lines of code” Quickstart, giving you a better understanding of our lower-level components: text splitters, nodes/documents, Qdrant integration, response synthesizer, and more. https://lnkd.in/gfMpSnij

783

8 Comments