rebuy’s Post

Developer productivity is elusive, don't bother with it, here are some reasons why: * What makes a developer or team productive changes from team to team, from quarter to quarter, even from individual to individual. Trying to impose accurate metrics is futile. * Providing incentives for productivity metrics forces developers to focus on gaming them, which certainly will not improve the quality of their output * Provided you have done your hiring correctly and your company culture supports it, all developers want to be productive and get into the flow. They love it, they don't need to be goaded into action with leadership imposed metrics. So what can leaders measure instead? 🚀 𝐅𝐨𝐜𝐮𝐬 𝐨𝐧 𝐜𝐫𝐞𝐚𝐭𝐢𝐧𝐠 𝐭𝐡𝐞 𝐜𝐨𝐧𝐝𝐢𝐭𝐢𝐨𝐧𝐬 𝐟𝐨𝐫 𝐭𝐡𝐞𝐦 𝐭𝐨 𝐠𝐞𝐭 𝐢𝐧 𝐚𝐧𝐝 𝐦𝐚𝐢𝐧𝐭𝐚𝐢𝐧 𝐟𝐥𝐨𝐰 𝐬𝐭𝐚𝐭𝐞, that is, optimize all the things that create friction and waste time, measure what does NOT make developers productive and improve that. Here are some ideas on how to do it (not an exhaustive list by any means): 👉 Have engineering principles that state that all engineering teams must see each other as users and customers. Every team understands and embraces user experience and prioritizes making their colleagues do the least amount of work to get their job done. --> Ask developers how hard is it for them to get their job done across teams or departments, or due to corporate processes. Write down the principles and hold all teams accountable to them. 👉 Pick or create tools provide instant feedback and are easy to use, over tools that have a lot of bells and whistles but are too tedious to use. --> Measure time it takes for a user to get familiar with a tool and number of steps to perform the job with it and continuously reduce it 👉 Improve feedback loops - creativity, quality and quantity of output are directly correlated with how quickly a developer can see the result of their changes. I totally recommend Brett Victor's talk for a dramatic example of this --> https://lnkd.in/e5SU8QVm More about this here: https://lnkd.in/eqN7QmKd #developerexperience #devex #developerproductivity

In a recent conversation with a founder we’re helping hire top technical talent for, the question came up: “How do you identify a 10x developer?” It got me thinking—there’s a lot of myth around the idea of the 10x developer. Many assume it’s the person who writes the most code or completes the most tasks. But the truth is, real 10x developers don’t just focus on output—they focus on impact. A true 10x developer: • Design systems that reduce failure before it happens. • Writes clear, maintainable code that others can easily work with. • Guides their team to improve and make better decisions, all while keeping an eye on the bigger picture. It’s not about being the fastest or doing the most—it’s about creating long-term, sustainable success for the team. These are the developers who make everything run smoother, even when you don’t notice. As leaders, it’s important to nurture these 10x developers: • Give them the space to think strategically, not just execute tasks. • Encourage them to share their knowledge and leadership with the team. • Recognize their contributions to building maintainable systems, even when the results aren’t always immediately visible. • Provide growth opportunities that go beyond just technical skills—nurture their leadership abilities. When you foster this type of talent, your entire team becomes more effective, and the long-term value they bring far exceeds the typical metrics of productivity. #LeadershipInTech #10xDeveloper #SoftwareDevelopment #Teamwork #EngineeringExcellence #TechLeadership #NurturingTalent

Navigating the world of tech leads feels a bit like trying to find your way through an IKEA store—full of twists, turns, and the occasional existential crisis. The role is a unique blend of tech wizardry and leadership finesse, and if you’ve ever pondered what makes a great tech lead tick, the latest article on Ironhack’s blog offers some fascinating insights. Here’s the lowdown on what it means to be a tech lead: - Mind the Gap: A tech lead doesn’t just sit around answering technical questions; they’re basically the sherpas of their software team, paving the way through rocky terrains of architecture and design. Clearing programming hurdles? Totally their jam. - Team Dynamics: Unlike traditional managers, tech leads don’t drown in admin tasks. They focus on guiding tech decisions while supporting and developing team members. Think of them as the difference between a drill sergeant and a life coach—both have their roles, but one definitely has more pep talks. - It’s Not All About the Code: Sure, tech leads need solid technical skills, but they also have to navigate the art of communication and team dynamics. It’s like being a conductor of a symphony orchestra—ensure everyone plays in harmony, even if some strings get a little out of tune now and then. - The Path Ahead: The article also dives into how aspiring tech leads can set their sights on this coveted role. It’s not about being a coding rock star; it’s about pulling your team towards a shared vision, problem-solving with finesse, and honing interpersonal skills that will make you the go-to person for guidance. If you've ever thought about stepping up your professional game, the tech lead position could be the goalpost. Grab a coffee, read the article, and see if you’re ready to embark on this exciting journey. Who knows, you might just find your calling! https://lnkd.in/ezSDX7su

The Top 5 Challenges Businesses Encounter in Software Development Let's be honest – creating successful software isn't a walk in the park. Whether you're a startup or an established company, you're bound to face some significant hurdles. 1️⃣ Feature Overload: Constant additions elongate the development process, leading to escalating costs and turning your dream app into a financial burden. 2️⃣ Talent Acquisition Struggle: Recruiting skilled developers often feels like an elusive quest, and assembling and retaining an optimal team can seem insurmountable. 3️⃣ Technological Complexity: Selecting the appropriate tools amidst a plethora of emerging trends can make your project feel unstable. 4️⃣ Communication Breakdowns: Teams may become isolated, fostering misunderstandings and hindering alignment. 5️⃣ Bug Nightmare: Bugs and minor issues lurk everywhere, posing a threat to your launch and tarnishing your reputation. But fear not – Eastplayers is here to tackle these software development challenges head-on! We excel at managing scope, nurturing talent, navigating technology trends, bridging communication gaps, and squashing bugs. Are you prepared to develop exceptional software stress-free? Let's talk! 😃 Drop your most significant development challenge in the comments below! #softwaredevelopment #softwaresolutions #eastplayers

Thank you to Forbes for including me in this great piece on the skills and traits that make developers invaluable. All too often I see the role of the developer being diminished, but a great engineering team can transform a company (and not just in tech). My contribution to what to look for in your hires? I believe that customer empathy and understanding are the greatest skills that anyone developing products brings to their work. This is often overlooked in a world centered on functions and data, but the fine details of every choice made in building software can make a product better- or worse-suited to the users’ needs. When you find developers who are passionate about solving problems, you’ll make better products. https://lnkd.in/d8s5XW9a

🍪 #Developers Are Smart People  – Why not just trust them? Sometimes, we add too many controls to our workflows to ensure "quality." Things like 𝗮𝘂𝘁𝗼𝗺𝗮𝘁𝗲𝗱 𝘁𝗲𝘀𝘁𝘀, 𝗮𝘂𝗱𝗶𝘁𝘀, 𝗮𝗻𝗱 𝗿𝗲𝘃𝗶𝗲𝘄𝘀 𝗮𝗿𝗲 𝗰𝗿𝘂𝗰𝗶𝗮𝗹. The issue is 𝘄𝗵𝗲𝗻 and 𝗵𝗼𝘄 we 𝗶𝗺𝗽𝗹𝗲𝗺𝗲𝗻𝘁 them. Developers are intelligent and capable of things machines can't do. Yet, we often create workflows 𝗯𝗮𝘀𝗲𝗱 𝗼𝗻 𝗱𝗼𝘂𝗯𝘁, not trust. I've seen this mistake in many organizations. 𝗪𝗵𝗲𝗻 𝗾𝘂𝗮𝗹𝗶𝘁𝘆 𝗱𝗿𝗼𝗽𝘀, 𝘄𝗲 𝗮𝗱𝗱 𝗺𝗼𝗿𝗲 𝗰𝗼𝗻𝘁𝗿𝗼𝗹𝘀. But is this the right approach? 🍪 𝗨𝗻𝗱𝗲𝗿𝘀𝘁𝗮𝗻𝗱𝗶𝗻𝗴 𝘁𝗵𝗲 𝗣𝗿𝗼𝗯𝗹𝗲𝗺 I learned the hard way that it wasn't. It made things worse. Take 𝗰𝗼𝗱𝗲 𝗿𝗲𝘃𝗶𝗲𝘄𝘀, for example. They should provide feedback for developers. But we often rely on tickets and pull requests after changes are made instead of talking directly to the right colleague at our IDE. Asynchronous code reviews can remove developers' responsibility. They lose context and don't build a sense of ownership. "It's now someone else's responsibility." 🍪 𝗧𝗵𝗲 𝗕𝗲𝘁𝘁𝗲𝗿 𝗔𝗽𝗽𝗿𝗼𝗮𝗰𝗵 I prefer accessible communication between colleagues as work happens. This is natural and effective. Instead of delaying communication, 𝘁𝗿𝘂𝘀𝘁 𝘆𝗼𝘂𝗿 𝗱𝗲𝘃𝗲𝗹𝗼𝗽𝗲𝗿𝘀 𝘁𝗼 𝗸𝗻𝗼𝘄 𝘄𝗵𝗲𝗻 𝗮 𝗿𝗲𝘃𝗶𝗲𝘄 𝗶𝘀 𝗻𝗲𝗲𝗱𝗲𝗱. Quick opinions from a fellow developer are more effective. Developers should always have the time to help each other with a quick review. It is easy when you practice the idea of small batch sizes. Not every change needs to be reviewed anyway. 𝗗𝗼𝗻'𝘁 𝗴𝗼 𝗳𝗼𝗿 𝗶𝘀𝗼𝗹𝗮𝘁𝗶𝗼𝗻 and the idea of "A remote developer needs to have 6 hours of focus time". naahh...  🤣 👉 Instead, we 𝗻𝗲𝗲𝗱 𝘀𝗲𝘃𝗲𝗿𝗮𝗹 𝗵𝗼𝘂𝗿𝘀 𝗼𝗳 𝗰𝗼𝗹𝗹𝗮𝗯𝗼𝗿𝗮𝘁𝗶𝗼𝗻 𝘁𝗶𝗺𝗲 as a team, no matter where we sit. 🍪 𝗠𝘆 𝗔𝗱𝘃𝗶𝗰𝗲 To my younger self and all tech leads: 𝗧𝗿𝘂𝘀𝘁 𝘆𝗼𝘂𝗿 𝘀𝗺𝗮𝗿𝘁 𝗱𝗲𝘃𝗲𝗹𝗼𝗽𝗲𝗿𝘀 🍀. A culture of trust beats any artificial workflow. Click on "𝗦𝘂𝗯𝘀𝗰𝗿𝗶𝗯𝗲 𝘁𝗼 𝗺𝘆 𝗡𝗲𝘄𝘀𝗹𝗲𝘁𝘁𝗲𝗿" for more Engineering Cookies 🍪 ♻️ Fellow #developer, Please share and let us know your opinion :) 👇 Have a great weekend everyone! Adrian #softwareengineering #tech #cto  

Hello Connection! Who are 10x Developers? "In the ever-evolving tech landscape, the term '10x Developer' often comes up. While it suggests a developer who is ten times more productive than their peers, it's essential to recognize that productivity in software development is more than just individual output. A truly effective developer combines deep technical knowledge with strong problem-solving abilities and excellent collaboration skills. They thrive in team environments, leveraging their expertise to uplift others and drive collective success. Let’s celebrate not only the extraordinary individuals but also the power of teamwork in creating impactful solutions. After all, innovation often happens when great minds come together! Keeplee Akash Pandey Chandan Kumar Anjan Sen What qualities do you think make a developer truly exceptional? #10xDeveloper #SoftwareDevelopment #Teamwork #Innovation #Devlopers #webdevlopers"

The Secret Sauce to Building a Development Team (Hint: It's Not Just About Coding Skills) Building a high-performing development team is important for success. But it takes more than just hiring talented developers and throwing them together. I've learned that creating a high-performing development team is both an art and a science. Here are some key insights I've gained over the years: 1. Shared Vision and Goals: Ensure every team member understands the big picture: • the company's mission, • values, • and strategic goals.    Align individual goals with team objectives to create a sense of purpose and shared ownership. 2. Clear Communication and Collaboration: Implement open communication channels where everyone feels comfortable sharing ideas, asking questions, and providing feedback. Encourage collaboration through: • regular team meetings, • brainstorming sessions, • and knowledge-sharing initiatives. 3. Trust and Psychological Safety: Create a safe space where team members can take risks, make mistakes, and learn from them without fear of judgment or blame. Encourage vulnerability and open communication about challenges and roadblocks. Celebrate both successes and failures as learning opportunities. 4. Empowerment and Autonomy: Give your team members the autonomy and resources they need to make decisions and solve problems independently. Trust their expertise and encourage them to take ownership of their work. Provide opportunities for growth and development to help them reach their full potential. 5. Continuous Feedback and Recognition: Establish a culture of regular feedback, both positive and constructive. Recognize and reward individual and team achievements to boost morale and motivation. Create a feedback loop where team members feel heard and valued. A high-performing team isn't built overnight. It requires consistent effort, patience, and a willingness to adapt your leadership style to the team's needs. --- Interested in building products smarter and faster? 👇 Follow Samir Sakanovic If you need my help to build your MVP, DM me "MVP".

Too many times, I have found myself discussing team structures and hiring strategies in my career. Should we hire full-stack people or strong specialists? From my experience, there is no silver bullet, so both directions can form strong teams, but we need to acknowledge that both strategies have pros and cons. One extremely costly obstacle to the team's success, though, is when tech professionals struggle to understand the user's journey holistically due to limitations in their tech knowledge and skillset. Modern web applications are quite demanding beasts since they tend to pay huge attention to User Experience, of course, for very good reasons. This is exactly where things tend to go south because a seamless and intuitive User Experience is usually accomplished by combining a heck of things and technologies. Tech people who are not limited by their hard skills are the ones who can see the whole picture, understand the application's high goals, work closely with business stakeholders, and ultimately can even guide the business people into delivering something useful. Why? Because they can see the whole map from the top of the tower and not from the first floor. It is a matter of perspective to be able to see the whole puzzle and grasp how various pieces fit together. Don't let your hard skills limits prevent you from becoming such an impactful tech professional 😉 https://lnkd.in/dsxD9Gbj #webdevelopment #careerdevelopment #software #leadership #management #engineering

Imagine this: Your star developer who knows everything about the codebase gets nicked by a headhunter and leaves. The other two juniors are stuck because they had always depended on the senior to make all the decisions. He had known every detail, after all. I wouldn’t want to find myself in this situation as a CEO. To avoid it, embrace the TEAM OWNERSHIP mindset. Let me explain: When building an MVP, it’s useful to have one or two star developers who feel true responsibility and OWNERSHIP for your product. However, once you’ve found your product-market fit and need to grow, your team will grow too. That’s when star developers become bottlenecks, because no decision can be made without them. Team Ownership can help. It means that everybody in your team feels responsible for your product. It means that knowledge is shared. It means that your team is empowered to make decisions even without a key person. The key to achieving the Team Ownership mindset are the star developers themselves. They must embrace a new role and become Dev Leads. Dev Leads help newcomers feel at home, get quickly acquainted with the tech and feel a sense of ownership for their work delivered. Keep on thing in mind, though: The MVP is like their child, and nobody lets others do weird stuff to their children. It’s your job to ensure your Dev Leads understand why Team Ownership is vital for the company’s survival. How do you implement the Team Ownership mindset in your own teams? Any tips to navigate the common pitfalls I’ve mentioned?