Plato ’s Post

🚀 Unlock the Full Potential of Your Next Project with Yohdev! 🚀 Are you planning a full stack engineering project but feeling overwhelmed by where to start? 🤔 You’re not alone! We’ve just released a new video where Andrew from Yohdev breaks down the entire full stack engineering process to make it easy and efficient for you. In this video, you’ll discover: 🔍 How to effectively work with a full stack engineering firm 🛠 The agile development process for faster, smarter delivery ⚡ Tips to save costs while maximizing project success 👉 Whether you’re in marketing, product management, or a startup founder looking to streamline your next web or app project, this video has the insights you need! Check it out and learn how to create a powerful MVP that aligns with your users’ needs and ensures a higher rate of success. 🌟 🎥 Watch the Video Here #FullStackEngineering #AgileDevelopment #TechConsulting #ProjectManagement #BusinessGrowth #MVP #Yohdev #Leadership #Innovation #TechTips

Team Topologies has become one of the most influential books shaping organizational strategies in large companies today. Its principles, like leveraging cognitive load to justify team structures and platform engineering, are echoed in countless presentations, whitepapers, and executive discussions. But is the concept of cognitive load being misused in our industry? And what are the implications when foundational ideas are misunderstood—or oversimplified? In my blog post, I take a closer look at the assumptions behind Team Topologies and what they mean for how we work in tech. If you're curious about the science—or lack thereof—behind these popular ideas, check it out: https://lnkd.in/epvPWCnP #SoftwareEngineering #TeamTopologies #DevOps #PlatformEngineering #CriticalThinking

Platform engineering represents a significant shift. The era of guerrilla tactics—where platform and operations teams would create skunkworks projects, sneak them into production, and later justify their value to expand—has come to an end.

🚀 Unlocking the Secrets to High-Performing Software Engineering Teams 🚀 In the fast-paced world of tech, building a high-performing software engineering team is crucial for innovation and success. Multiverse’s latest blog delves into the strategies and benefits of cultivating such teams. From enhancing collaboration to driving productivity, this article provides valuable insights for anyone looking to elevate their software development efforts. Discover the key elements that make a top-tier engineering team and how they can propel your organisation forward. Don't miss out on these game-changing tips! 👉 Link to the article - https://lnkd.in/eXzT_cS8 #SoftwareEngineering #HighPerformanceTeams #TechInnovation #Leadership #TeamBuilding

DORA metrics are a great start, but they're not the whole story. Engineering leaders need actionable insights beyond deployment frequency or lead times. Metrics like time to first commit, idle time waiting for CI/CD, and time spent resolving merge conflicts can uncover hidden bottlenecks and boost developer productivity. Check out this Forbes article featuring Debosmit Ray (debo) CEO of DevZero, on why DORA alone isn’t enough and how broader, developer-centric metrics can transform engineering teams. 👉 Read it here: https://hubs.la/Q032NLL40

There seems, in the weirdly laggy global "conversation" on LinkedIn, to be a discussion happening about if Engineering Leaders (tm) should code. I thought I'd weigh in. It seems like all of the discussion is centered around the code that leaders produce, but I think on a good and mature team, the code that leaders write should be irrelevant to the shipping of the product. I still think they should do it. I think it's very _very_ hard to keep up to date on what is happening in a codebase without contributing to it. Writing code is what forces you to pull on the threads, to follow chains of logic into other places in the code. I think we all understand this intuitively: if you're evaluating a new framework or library, you build a to-do list app with it, you don't just read the docs. Writing code is important because it helps you to understand what the challenges your team faces are, and to help you provide better high-level technical guidance, informed by the situation on the ground. It helps you understand the strengths and weaknesses of members of your team far more than just reading PRs does, and as teams grow, the leaders should not be a gating function for individual PRs anyway. In short, I think Engineering Leaders should (must?) write code, but that code itself is irrelevant. The same way you want your representative to live in your district, your Engineering Leadership should be writing code so that they understand the needs of the people they lead.

Demystifying Platform Engineering: Beyond the Buzz   Dear friends! Let's talk about this new buzz in tech - Platform Engineering.   I know, I know. Another tech term to learn, right? But hear me out, this one's actually seems to be working!!   So, what's Platform Engineering all about?   Think of it as your tech team's best friend. It's here to:   - Remove complexities for platform users/Developers (Make life easier for everyone using tech tools) - Provide self-service capabilities so developers help themselves without bugging devops/cloud team all the time   It's built on three simple ideas:   - The base or Underlying Platform: Where everything runs (like Kubernetes or good old servers) - The toolbox or Platform Capabilities: All the cool tools we love to use (tools like Argo CD, cost optimization, Crossplane) - The front door or Platform Interface: How developers actually use all this stuff (GUI, CLI, or API for user interaction)   Why should you care? Well, tech's getting super complicated these days. Platform Engineering is like having a really smart friend who sets up everything for you, so you can focus on the fun part - actually building cool stuff!   It's not perfect yet, and we're all still figuring it out. But I think it's going to make a big difference in how we work.   So, what do you think? Has your company tried anything like this? Did it help? Let's chat about it!     -------------------------------------------------------------------------   Enjoyed this insight? If so:   👤 Connect/Follow for more content ♻ Repost this to help others find it 💾 Save this post for easy access later   Your engagement fuels more content like this. Let's learn and grow together!

Why scaling engineering teams is hard? And how to scale them beyond the initial 10 engineers 👇 ⭕️ Small teams > Big teams → The scientific study (Reference: https://lnkd.in/ghnaFv7M) clearly shows that 5-person teams are a lot more efficient than 20-person teams. → Smaller teams are more efficient because of a smaller cognitive load (which increases exponentially as you add more people to the team). → Single team size should be between 4 and 8 engineers (two pizzas rule). → Once your team approaches the 8-person limit, you need to think about how to split that team into two. ⭕️ Slowly introducing (micro)services → Microservices is a way to divide teams, not code !!!!!!!!!!!! → Microservices structure usually represents teams' structure within the organization. → There is a great quote by Melvin. E. C. "Any organization that designs a system will produce a design whose structure is a copy of the organization's communication structure". ⭕️ Decoupled (async) teams is the name of the game → Your job as a manager of IT teams is to ensure loose coupling between the teams. → Loosely coupled teams = Loosely coupled (micro)services. → Divide teams into functional teams, where they are separated into their own bounded contexts. ⭕️ Introduce "Enabling" teams to work with functional teams. → Enabling teams are a group of highly specialized experts that work with multiple functional teams and provide their expertise (as well as coaching). -------------------------------------- 🚀 Starting or scaling your tech? ❇️ I will make sure it is successful. 🧑💻 Schedule a call with me: https://lnkd.in/dCSXwWp5

Keeping up with technology can be difficult for a tech leader. Your day doesn't necessarily involve writing code or even working at the architectural level anymore, yet it's important to be aware of emerging technologies and be able to use them when and if they are fit for solving the challenges you have. For me, following engineers sharing their knowledge doesn't always provide the level of understanding I require. Personally, I noticed I learn by doing stuff, so I often spend time working on personal projects to explore new technologies. I'd rather face the project as if I was about to start a new company, often I even create Lean Canvas for them, and then I spend some time writing some code to put together a PoC. These PoCs are never completed, that was not the point, but I learned how to use the technology and frequently I end up adding it to projects I work on later on. #keeplearning #doers