Xin-Kuan (Leo) Yeh’s Post

What if your platform wasn’t just functional but a developer favorite? In his The New Stack blog, Justin Reock shares 6 steps to shift from reactive fixes to proactive impact. ✨ Root out real pain points. ✨ Develop Systems Thinking. ✨ Drive developer love with a product mindset. Curious? See how: https://lnkd.in/gzpYmadk

🧠 I've had the opportunity to learn so much over the last year, deeply embedding into Platform Engineering communities and learning about their successes and challenges. So many recognizable patterns have emerged: ➕ Our metrics tell the wrong story when we are not continuously monitoring our systems, forcing us into teleological patterns of analysis rather than proactive understanding ➕ Systems Thinking is more important than ever, #Deming knew that only 4% of an organization's productivity is a result of the worker, while 96% is related to the underlying productivity systems ➕ Throwing more tools just leads to tool sprawl and head first into Ashby's Law, we have to think about foundational tools that align with sociotechnical challenges and culture. Read more about it in my newest contribution to The New Stack! #PlatformEngineering #DevEx #DevOps

“Platform engineering teams should consider themselves product owners, with developers as their customers. They should conduct discovery to understand developers’ needs and then reach out to end users to help them become successful with the resources provided. This requires marketing, communication and customer support skills, which are often lacking in very technical teams. The key here is a product-oriented mindset and culture, which allows platform engineering teams to focus on creating value for their end users (developers) by listening to user feedback and continuously iterating and improving their product (the developer platform).”

🔧 A messy codebase can create a chaotic mindset. Here are ways to ensure your product development brings mental calm: 🔧    Refactor Regularly: Regularly refactoring code helps keep it clean and maintainable. It’s easier to work with a well-structured codebase.    Adopt Coding Standards: Implementing and adhering to coding standards ensures consistency, making the code easier to read and understand.    Automate Testing: Automated tests catch issues early, giving you confidence that changes won’t break existing functionality.    Use Version Control: Version control systems like Git help track changes, making it easier to manage and collaborate on code.    Document Thoroughly: Good documentation provides clarity. It helps team members understand the codebase and reduces onboarding time for new developers.    Review Code Regularly: Regular code reviews promote best practices and catch potential issues early, leading to higher-quality code.    Prioritize Clean Architecture: Investing in a clean and scalable architecture upfront pays off in the long run. It reduces technical debt and makes future development smoother.    Encourage Continuous Learning: Stay updated with the latest development practices and tools. Continuous learning fosters innovation and efficiency. By implementing these practices, we can transform chaotic codebases into well-oiled machines, leading to a more productive and mentally calm development environment. #CleanCode #Productivity #SoftwareDevelopment #BestPractices #EngineeringLeadership

Here's another blog post. This one highlights two Git merging workflow strategies, and argues for Trunk-Based Development. What's your engineering team using today, and why are you still using GitFlow? https://lnkd.in/gJDt3wpx

Code Rewriting No More. Painful. Oftentimes avoidable. Costly. Did you know that developers spend roughly a third of their time rewriting code, many times because of poor product specification? Read more here and share your thoughts 👇 #developers #product #productmanagment

How to Avoid the Refactoring Trap as a Product Manager 🤬 ✅ Refactoring should solve a problem for users—not just cleaner code. It is done as part of a feature delivery. 📏 Refactoring must improve a measurable metric (typically internal, such as delivery speed, or enabler for a new feature). 💯 Technical debt is the natural state of any software. - "All code becomes legacy code the moment it is written." Inspired from 👉 Good Refactoring vs Bad Refactoring https://lnkd.in/eihXufQt

I recently came across an insightful article by Adam Ard that addresses some of the key challenges in the software development process. Adam offers specific solutions that I found to be very practical. For those navigating the delicate balance between product and engineering teams, this might be a valuable read. You can check it out here: https://lnkd.in/dP_zJwtk

Product Mindset Key to Platform Engineering Success “Build it, and they will come” is not a viable strategy for ensuring developers will adopt your platform. To avoid your platform’s untimely demise, you have to treat your platform like a product and sell it to your customers: Your developers. The lighthouse team approach is valuable because it helps platform teams avoid boiling the ocean while also ensuring your platform provides real value every step of the way. #product #platformEngineering

Build Platform Engineering as a Product for Dev Adoption... Adopting a platform engineering strategy is only the start of the process. Turning it into a valuable product that your developers will adopt and support is a critical part of the journey.