Mohd Zaid’s Post

Goals

🎉 Exciting Milestone: Reached Town Hall 13 in Clash of Clans! 🏰 Today, I'm thrilled to share that I've reached Town Hall 13 in Clash of Clans, and believe it or not, this journey has taught me invaluable lessons about being an engineer. Here are some insights that directly translate to my professional growth: Strategic Planning: Just like in software development, advancing in Clash of Clans requires meticulous planning and strategic thinking. Prioritizing upgrades, managing resources, and anticipating challenges mirror the project management skills needed in engineering. Continuous Improvement: Reaching higher levels demands constant learning and improvement. This resonates with the iterative nature of software engineering, where continuous integration, testing, and deployment are key to delivering robust solutions. Team Collaboration: Success in the game is often driven by the strength of your clan. Similarly, in software engineering, collaboration and teamwork are crucial. Sharing knowledge, supporting peers, and leveraging collective strengths lead to outstanding outcomes. Adaptability: In both Clash of Clans and software development, the landscape is ever-changing. Being adaptable and quick to pivot when facing new challenges is a vital trait. It fosters innovation and resilience in dynamic environments. Problem-Solving: Every raid and defense in Clash of Clans involves critical problem-solving skills. In software engineering, debugging and optimizing code require a similar analytical approach to overcome obstacles and achieve success. Reaching Town Hall 13 is more than just a gaming achievement; it symbolizes growth, perseverance, and the continuous pursuit of excellence. I’m excited to bring these insights into my professional journey as an engineer and to continue pushing the boundaries of what’s possible. Let's keep leveling up, both in games and in our careers! 💪🚀 #SoftwareEngineering #StrategicPlanning #ContinuousImprovement #TeamCollaboration #Adaptability #ProblemSolving #CareerGrowth #Tech #ClashOfClans #GamingToGrowth

🎉 𝗘𝘅𝗰𝗶𝘁𝗶𝗻𝗴 𝗠𝗶𝗹𝗲𝘀𝘁𝗼𝗻𝗲: 𝗥𝗲𝗮𝗰𝗵𝗲𝗱 𝗧𝗼𝘄𝗻 𝗛𝗮𝗹𝗹 𝟭𝟯 𝗶𝗻 𝗖𝗹𝗮𝘀𝗵 𝗼𝗳 𝗖𝗹𝗮𝗻𝘀! 🏰 Today, I'm thrilled to share that I've reached Town Hall 13 in Clash of Clans, and believe it or not, this journey has taught me invaluable lessons about being an engineer. Here are some insights that directly translate to my professional growth: Strategic Planning: Just like in software development, advancing in Clash of Clans requires meticulous planning and strategic thinking. Prioritizing upgrades, managing resources, and anticipating challenges mirror the project management skills needed in engineering. Continuous Improvement: Reaching higher levels demands constant learning and improvement. This resonates with the iterative nature of software engineering, where continuous integration, testing, and deployment are key to delivering robust solutions. Team Collaboration: Success in the game is often driven by the strength of your clan. Similarly, in software engineering, collaboration and teamwork are crucial. Sharing knowledge, supporting peers, and leveraging collective strengths lead to outstanding outcomes. Adaptability: In both Clash of Clans and software development, the landscape is ever-changing. Being adaptable and quick to pivot when facing new challenges is a vital trait. It fosters innovation and resilience in dynamic environments. Problem-Solving: Every raid and defense in Clash of Clans involves critical problem-solving skills. In software engineering, debugging and optimizing code require a similar analytical approach to overcome obstacles and achieve success. Reaching Town Hall 13 is more than just a gaming achievement; it’s a reflection of the skills and lessons that are applicable to real-world engineering challenges. #SoftwareEngineering #StrategicPlanning #ContinuousImprovement #TeamCollaboration #Adaptability #ProblemSolving #ClashOfClans #ProfessionalGrowth

At NOVA, we believe progress starts with reflection. That’s why we’re launching a Substack—a space where we’ll share the lessons we’ve learned, the challenges we’ve tackled, and the innovations we’ve explored in the built environment. 💡 On our Substack, you’ll find: Stories from real projects (big and small). Honest reflections on what worked—and what didn’t. Fresh ideas to spark innovation. Insights into how we approach problem-solving and product development. We’re committed to sharing not just our successes but also the lessons we learn from failure. 🔗 Ready to dive in? Check out our introduction post below ⬇️ Whether you’re in the industry or just curious about how the spaces around us come to life, we hope you’ll find something valuable. #Innovation #BuiltEnvironment #ProductDevelopment #Substack #NOVA

Exciting Milestone 🎉: Reached Town Hall 12 in Clash of Clans! I'm thrilled to announce that I've reached Town Hall 12 in Clash of Clans! This journey has surprisingly imparted invaluable lessons that align closely with my engineering career. Here are some key insights: 📝Strategic Planning : Advancing in Clash of Clans demands meticulous planning and strategic thinking, much like software development. Prioritizing upgrades, managing resources, and anticipating challenges are essential skills in both realms. 📈Continuous Improvement : Just as reaching higher levels in the game requires constant learning, software engineering thrives on continuous integration, testing, and deployment. The iterative nature of both fields ensures the delivery of robust solutions. 🙎♂️Team Collaboration : Success in Clash of Clans is often driven by the strength of your clan. Similarly, in software engineering, collaboration and teamwork are crucial. Sharing knowledge, supporting peers, and leveraging collective strengths lead to outstanding outcomes. 🅰️Adaptability : Both the game and software development landscapes are ever-changing. Being adaptable and quick to pivot when facing new challenges fosters innovation and resilience in dynamic environments. 🧑🏫Problem-Solving : Every raid and defense in Clash of Clans involves critical problem-solving skills. Similarly, debugging and optimizing code in software engineering require an analytical approach to overcome obstacles and achieve success. Reaching Town Hall 12 is more than just a gaming achievement; it symbolizes growth, perseverance, and the continuous pursuit of excellence. I'm excited to bring these insights into my professional journey as an engineer and to continue pushing the boundaries of what's possible. Let's keep leveling up, both in games and in our careers📈!

Building software is like building a cathedral. I recently started a new project with a team of about 12 developers. Early on, I suggested dividing the team into squads — one focused on product/features and the other on infrastructure. That’s when a question came up: could this division lead to a lack of unity and a loss of the overall vision for the project? This made me think about two concepts from the book The Pragmatic Programmer. First, the authors compare software development to building a cathedral, which requires a balance between art and engineering, but most importantly, a clear and shared vision of the final goal. Second, the idea of orthogonality, which in the context of teams, means allowing squads to work independently without losing alignment with the bigger picture. And that’s my challenge: how do you ensure team independence while maintaining a unified vision for the project? How have you tackled this?

#MythBster Friday with Systems Engineering #Myth :“Systems engineering slows down development.” Oh, how I love this one! Because, of course, who needs things like clear requirements, risk management, or functional interfaces, right? Let’s just wing it and hope the system works like magic! Sarcasm aside, this myth is like saying roadmaps slow down your vacation. Sure, you could skip planning, start driving, and “figure it out as you go”… but don’t be surprised when you end up stranded in the middle of nowhere, miles from your actual destination. #Busted: Systems engineering doesn’t slow development—it accelerates success. Here’s why: • It catches issues early. (Would you rather find a critical flaw on day 10 or in production?) • It aligns teams to a shared vision. (So the software guys don’t build something incompatible with the hardware folks!) • It saves you from the “we’ll fix it later” trap, which costs exponentially more than “fix it now.” So yes, systems engineering might feel like a slow start. But ask yourself: Is it better to spend 10% of your time planning the system upfront, or 50% of your time cleaning up the mess later? #ProTip: If systems engineering seems slow, you’re probably doing it wrong. #SystemsEngineering #DevelopmentMyths #PlanSmart #EfficiencyOverChaos #QualityMatters

Ever feel like you’re looking at a chair wedged between a balcony and a building? Welcome to the world of software engineering! Just like that chair, we’re constantly balancing innovation and stability, speed and quality, creativity and practicality. Every line of code, every design decision, and every project deadline tests our ability to juggle competing demands. Here are 3 strategies that help me stay balanced: 1. Encourage continuous learning to balance innovation with stability. 2. Use Agile practices to manage speed and quality through iterative development. 3. Foster clear communication to align priorities and make informed decisions. And remember, unlike that precarious chair, our projects are designed to stay balanced and not fall apart…hopefully! 😄 #SoftwareEngineering #TechLife #Innovation #Balance #EngineeringChallenges

As developers, we deal with practical challenges every day. Often, we’re so focused on the technical part of development that we forget the real purpose of our jobs. It’s not solving technical issues; it’s building products for human beings. What we do is very technical at its core, but the consequences of our decisions are very human: they strongly affect people’s lives, their access to information, and their participation in society.

Lessons from The Phoenix Project: My Week-Long Journey Through a Transformational Read This past week, I embarked on a journey through The Phoenix Project by Gene Kim, Kevin Behr, and George Spafford. It wasn’t just another book on my shelf; it became a companion during my daily metro rides and weekend relaxation. Between my commute to and from the office, I managed to squeeze in 30-40 pages each day. On the weekend, I devoured over 100 pages, captivated by the lessons and the narrative woven into the story. Reading in the metro has become a daily ritual for me. With the city buzzing around me, the moments I spent with The Phoenix Project felt like I was stepping into a different world—a world that, strangely enough, mirrored the challenges we face in the tech industry today. The book’s narrative is not just a story; it’s a powerful metaphor for the struggles and transformations many of us experience in our professional lives. Want to dive deeper? Read more on my Newsletter https://lnkd.in/dXQk5Md8 If you’re interested in diving into this insightful book, you can grab your copy of The Phoenix Project and other books that I’m reading here (https://lnkd.in/d8WrjY2Z). It's a read that might just change the way you see your work and your role in your organization. (Note: This is an affiliate link, and I may earn a small commission at no extra cost to you if you choose to purchase through it.)