Quoc Viet Ha的动态

?? New Blog Post Alert! ?? In my latest blog, I dive into the power of creating value and coding with purpose, inspired by the lessons in the book "The Lean Startup". If you're interested in discovering how to drive impactful projects and stay focused on what matters, give it a quick read! I've been building on these lessons from the book since being at Nimble Approach to enable me to create value fast and encourage faster feedback loops in various client projects. ?? Check it out here: https://lnkd.in/e2qWF4-9 I'd love to hear your thoughts and any lessons you've learned about building meaningful work. ?? #TheLeanStartup #DevCommunity #software #developer #engineer #tech #blog

?? Creating Value and Coding with Purpose - Lessons from The Lean Startup ?? After reading The Lean Startup, I’m reminded of how crucial it is to build with purpose. It’s easy to get lost in complex code and shiny features, but are we solving real problems for our users? The book’s approach to focusing on quick iterations, validated learning, and real feedback makes a world of difference in ensuring our work truly serves a need. Some key takeaways that resonated with me: ?? Start small with an MVP and iterate based on real feedback. ?? Track meaningful metrics, not just vanity stats. ?? Keep user feedback at the core to avoid overbuilding. These insights keep us grounded, coding not just for functionality but for impact. Thanks for sharing Hasib???? Ahmed! #softwaredevelopment #codingwithpurpose #leanstartup #techinnovation

Building Tech Products from Scratch vs. Working on Existing Projects: Which is more important ? . . ?? Let's understand from a Software Engineer's perspective... One of the most argued topics in the tech world has to do with whether to build from scratch or to better an existing project. While either way presents one with valuable learning curves, creating from scratch contributes uniquely to habit formation. You will learn the entire cycle of product ideation, design, architecture, coding, testing, and deployment when you build from scratch. The kind of comprehensive experience gained therein not only sharpens your technical skills but also strengthens your problem-solving abilities. You will gain the ability to foresee obstacles, come up with creative solutions, and make critical decisions that will set the course for the product's future. Working on an existing project teaches one how to navigate complex codebases, improve legacy systems, and work with already established frameworks. These skills are rather important in maintaining and evolving products that users are already depending on. It builds a mindset of innovation and ownership, wherein one gets into the habit of making something from scratch. One begins to consider more than the present, to visualize what could turn into reality and fulfill it. In that way, this empowers one to be creators, not just contributors; in an industry motored by fast-changing innovation, this kind of mindset is very valuable. While this is so in their own importance, do not belittle the strength of starting from scratch. True innovation begins right there. #TechInnovation #ProductDevelopment #CareerGrowth #TechLeadership #InnovationMindset #softwareDevelopment

One of my favourite processes for reviewing and giving #feedback on how a team works together, a piece of work, an event, or pretty much anything really, comes from the world of #agile software development; a sprint retrospective. It’s fast, gives everyone a voice, and can actually be pretty fun. Google it for the ins and outs but in a nutshell: Get everyone together to discuss a thing. Divide a board into 4 sections; ?? - what went well ?? - what went not so well ?? - ideas ?? - shout outs Give everyone post-it notes and set a timer for 5-10 minutes Everyone adds their post-it notes to each section of the board during that time The group discusses each post-it note on the board Some feedback will lead to an action item that gets captured and built into your #businessprocess Even if you’re not developing software in your #StartUp - I’d recommend giving this framework a go if you want to keep improving (and who doesn’t want that?!).

I sometimes feel out of place as a software engineer. And thinking about why I started programming kinda makes that clear to me. At 14, I poured countless hours into building from scratch: - My personal blog - A social network - A browser game But I knew nothing about product development. All I had was an interest in tech and a bunch of ideas in my head. Software is the ultimate way to unleash your inner builder: - Easy to dive into - Totally free - Accessible to all! How many of you started like that? People don't fall in love with technology just for the technology itself. They fall in love with the possibilities it unlocks: - Creating innovative projects - Using technology to make a positive impact - Solving challenging problems And yet, most of us end up working for soul-sucking feature factories. You can’t hide your true nature for long. Your passion for creation is like a dormant volcano, ready to erupt at any moment. I reached a breaking point and started questioning my life choices. Maybe I should move to UX? Or try product management? Maybe not, feature factories are sucking their souls too. Shall I just leave tech then? Something changed when I read the article on "product engineers" from Gergely Orosz of The Pragmatic Engineer What are product engineers? They: - Dive into product discovery, propose enhancements. - Align choices for optimal UX and business impact. - Thrive on seeing their work impact real lives. - Grasp the why behind product development. - Embrace the big picture for wise decisions. - Value quick feedback loops. - Harness an entrepreneurial mindset. They thrive in empowered product teams or go solo, building their own products like Pieter Levels and Marc Lou. If you are someone who: - Is sick of being treated as a code monkey - Aims to make a difference in the world - Loves to help others with technology => Join me on a journey to discover: - The role of product engineers - Foster collaboration between all people working in tech (check out my podcast, Invisible Algorithms) - Mastering essential soft skills and technical tools for solo or team innovation and product engineering I'm not alone in this thinking. I know there are more like-minded people out there. What’s your story? Let me know in the comments???

The 20-80 Rule: Why Done is Better than Perfect ????? Let’s be honest: How often have we delayed a release in software development because we were chasing perfection? ?? We’ve all been there. We want flawless code, a seamless user interface, or the “perfect” solution. But here’s the hard truth: Perfection is the enemy of progress. The Pareto Principle tells us that 80% of the value comes from 20% of the work. Focus on delivering the core features and learn from real-world feedback. What it shouldn’t be: 1. Fear of starting too early ?? If you hesitate because something isn’t “perfect,” you’re holding up progress. Just start and improve later! 2. Searching for the perfect solution ?? There’s rarely a perfect solution. A better strategy is to start small and improve step by step. 3. Stalling over minor details ??? You can spend forever tweaking details, but it’s often better to focus on the big stuff first and deal with the small things later. The Right Approach: 1. Focus on what’s important ? Identify what brings the most value and do that first. Small optimizations can wait. 2. Learn from experience ?? Once your solution is out, you’ll get feedback that helps you identify real problems and fix them. 3. Do first, then improve ?? Don’t wait for perfection—get your product out there and improve it gradually. ?? Why this works: ?? Iteration beats perfection: The best software products we know today weren’t perfect at the start. Think of giants like Google, Amazon, or your favorite app. They were built through continuous updates and learning from users. ?? Progress over perfection: The key is to keep moving forward. Don’t let the fear of releasing an imperfect product hold you back. Progress is better than perfection. ? Speed matters: In today’s fast-paced development world, speed is crucial. Get it out there. Make it work. Then refine it. ?? Remember: Done is better than perfect. ? Progress, not perfection, leads to success. ?? Great products are born from iteration, not isolation. ?? ?? What do you think? Have you ever caught yourself spending too much time perfecting a feature? Let’s discuss! ???? #softwareengineering #coding #programming #ParetoPrinciple #IterationOverPerfection #AgileDevelopment

In my experience, the "move fast and break things" approach? Yeah, not so great in software development ?? Think of it like building a house...on quicksand. Rushing the foundation is gonna lead to a whole lot of expensive repairs later on (and a very unhappy homeowner ??). Too often, managers confuse agile with unrealistic speed expectations. This leads to a vicious cycle: engineers get burnt out trying to keep up, code quality suffers, and the whole project risks failure. And who gets the blame? The engineers! ?? Let's change this narrative! Time to ditch the burnout and build awesome products instead. Here's the secret sauce: 1. Realistic Planning:?Arbitrary deadlines? No thanks! Let's involve engineers in setting achievable goals. 2. Celebrate Quality:?Testing and refactoring are the VIPs of the process, not things you squeeze in at the end. ? 3. Open Communication:?Red flags need to fly early! Transparency saves the day. ?? 4. Sustainable Pace FTW:?Let's reward teams for building amazing, well-crafted products, not just hitting deadlines with messy code. ?? Startups and big companies, listen up: rushing development leads to: 1. Technical debt pileup:?Code gets messy FAST, slowing you down later. ?? 2. Endless refactoring:?Like playing whack-a-mole with bugs. ?? 3. Glitchy products:?Nobody likes a buggy app, and it hurts your reputation. ?? 4. Missed features:?Too busy fixing stuff to build the cool things people?actually?want. ?? Let's build a better way! Invest in your engineers, and you'll invest in the long-term success of your products. ?? Any other fun tips to prevent burnout? Do share in the comments! ?? #softwaredevelopment #startups #agile #tech #productdevelopment #codinglife #worklifebalance #coderproblems #letsShopdev

The magic of software development lies in our constant drive to explore the how and why of things. Whether it's debugging code at 2 AM, brainstorming the next big feature, or simply refactoring old functions, it all starts with a spark of curiosity. Here are a few mindset shifts that have had a huge impact on my development journey: 1. Debugging is Discovery ?? – Every bug is an opportunity to learn something new about your code. 2. Code is Communication ?? – Clean code isn't just for machines; it's for other developers who’ll work on it after us. 3. Never Stop Learning ?? – Tech moves fast, and staying curious keeps us growing alongside it. No matter how advanced the tools get or how quickly frameworks evolve, the developer mindset stays rooted in growth, adaptability, and grit. ?? What mindset or practices have transformed your development journey? Let’s share our insights and keep learning together! ?? #Innovation

If you have ever worked with me, you'll know that I like to speak in memes. What better way to share some great PM learnings than with memes? I was in a recent interview where they asked about how to balance tech debt vs new features, an age old problem that we all face. I always love making sure that the system is built well the first time, but understand that things get messed up and need to be fixed over time. So there has to be a balance in everything. Additionally, this article covers documentation. Who reads it all? I know that I've been victim to getting handed long PRDs and cumbersome knowledge bases to learn the product. It isn't fun sitting and reading long documents, so how does one best find the happy middle ground of lengthy documentation vs no documentation?

In the world of tech, development isn’t just about code—it’s about evolving ideas, solving real-world problems, and pushing boundaries every day. Whether it’s through late-night debugging, collaborating with a team of like-minded innovators, or diving into a new framework, tech development is a journey of relentless growth and discovery. ?? For every problem, there’s a creative solution waiting to be unlocked, and the path to mastery is paved with moments of curiosity, persistence, and continuous learning. Let’s share insights, learn from our failures, and celebrate each win, big or small. Because in tech, every line of code, every product shipped, and every project completed brings us one step closer to transforming the world. #TechDevelopment,?#Innovation,?#SoftwareEngineering,?#Agile,?#DigitalTransformation?#FutureOfWork