Paul Shaw’s Post

Why thinking outside the box is important 🤔 Thinking outside the box helps you to solve challenging problems. 📌 𝐉𝐨𝐢𝐧 𝐎𝐮𝐫 𝐓𝐞𝐥𝐞𝐠𝐫𝐚𝐦 𝐠𝐫𝐨𝐮𝐩 𝐟𝐨𝐫 𝐬𝐭𝐮𝐝𝐲 𝐦𝐚𝐭𝐞𝐫𝐢𝐚𝐥 https://lnkd.in/gpD_UYdm 𝐈𝐧𝐭𝐞𝐫𝐯𝐢𝐞𝐰 𝐏𝐫𝐞𝐩𝐚𝐫𝐚𝐭𝐢𝐨𝐧 https://lnkd.in/giibiJ9x It allows you to look beyond a defined scope of relevance to find answers that would not exist otherwise. The agile methodology for example came from looking beyond established software development procedures. Thinking outside the box focuses more on creative problem-solving and challenging assumptions. It involves questioning assumptions, challenging traditional norms, and reframing problems with a broader understanding. Follow - Yogesh Talele #think #outsidethebox #success #hardwork

Building a process is an iterative process. We will always find bugs or ways to improve it. The more patience you have, The better we can make it. #simplifyyourworkflow #makelifeeasier #processworkflow

Have we tried the alternative? No. Then we cannot judge. Often teams cannot see the problems of their way of working because they have only known that way of working. Or they see the problems but feel that is endemic to software development because they don’t know better. Interestingly, those teams believe they are high-performing. Compared to what? When we don’t know the alternative. The thing is, once we experience high-performance we won’t even say we are. We continuously question our ways of working. Hmm 🤔 this could be better. This seems off. This doesn’t feel right. Isn’t there a better way? #lean

Want to save money and boost productivity? Focus on quality from the start! 🌟 Neglecting internal quality leads to a rapid buildup of clutter that slows down feature development. Even the best teams produce clutter, but by maintaining high internal quality, they can keep it under control. High internal quality keeps clutter to a minimum, allowing a team to add features with less effort, time, and cost. 🚀 #SoftwareQuality #TechDebt #DeveloperProductivity #SoftwareEngineering

Measuring Productivity. Before we can talk (meaningfully) about measuring a thing, we need to define said thing. So what is "productivity" in software product development? What is it NOT? #productdevelopment #mondaythoughts

End to end testing is not just testing at the end of the development of the flow. Many people think you cannot end to end test before the whole flow is ready. You need to follow closely the development and learn how the flow is feeling, how it reacts, what the flaws are. Even if 30% of the flow is ready you can already start with end to end testing. It is all about providing early feedback about the flow you are building. It is important business is involved already in the early buildup. Shifting left is all in the mind of the people. #qualityassurance #shiftleft #endtoend

Software companies stress about having more features or different features to separate themselves from the competitors. Here’s the thing though. Imagine you have two programs that look similar and do exactly the same thing. But one takes 5 seconds to load and a minute to do whatever it is that it’s doing. And the other loads in 50 milliseconds and take another 200 to do the thing. Which one would you choose? Which one you think is nicer to use? Performance is a great differentiator. It’s the killer feature. It’s what can trample all your competitors. Neglect it at your own risk. #softwaredevelopment #softwareengineering #productmanagement #performance

Feeling overwhelmed by trying to make everything perfect? Consider emphasizing Action over Analysis! ⚡️ It’s easy to get caught in the cycle of overthinking, especially in software development. But actions speak louder than words! Instead of sitting around, burying yourself in analysis, how about rolling up your sleeves and diving into the project? Taking steps—no matter how small—can lead to progress! Each action you take generates new information to analyze, develop, and create. It’s less about having perfect details upfront, and more about learning through doing. So let’s embrace progress over perfection! Remember, each moment spent overthinking is a moment of potential lost. Get out there and take action! #Koorus #ActionOverAnalysis #GetThingsDone

Changing Change Itself...

Gathering context around the implementation before jumping into the code is crucial. It saves your: • Time • Effort • Credibility If you jump into implementation without fully understanding the context of what you are implementing, you risk jeopardizing your credibility within the team. Implementing things prematurely may lead to redoing the work. Therefore, be cautious: • Ask questions. • Read documentation and discussions. • Share your thoughts before beginning the implementation. #softwareengineering #softwaredevelopment