Never Rewrite

We're joined by guest Austen Tucker to explore the concept of communication gaps in tech environments. The discussion emphasizes the importance of setting clear expectations and using pedagogical techniques to enhance collaboration.Show notes:https://www.thearcades.me/https://www.linkedin.com/newsletters/7312541452108972032/

In this conversation, Isaac Askew and Jeffrey Sherman explore the analogy of changing jobs to rewriting code, discussing the intentionality behind job changes, the impact of company culture on career growth, and the importance of aligning personal values with professional roles. They reflect on their own experiences with job transitions, the feelings of stagnation and underappreciation, and the challenges of resetting perceptions in a new role. The discussion also touches on the costs of employee turnover and the need for companies to recognize and retain valuable talent.

In this episode of 'Never Rewrite', Isaac Askew and Jeffrey Sherman delve into the nuances of providing constructive feedback in software development. They discuss the importance of framing feedback in a way that encourages open communication and psychological safety, particularly when dealing with legacy code and the developers who created it. The conversation emphasizes empathy for past developers, the significance of understanding context, and the need to separate the code from the individual who wrote it. They also explore how to give feedback on UX design, highlighting the importance of assuming positive intent and understanding the constraints that may have influenced design decisions.

Isaac Askew and Jeffrey Sherman explore the complexities of legacy code and tech debt through the analogy of construction in old houses. They discuss how unexpected issues can arise when making changes, the importance of communication between engineers and product managers, and the need for thorough investigation before committing to projects. The discussion emphasizes the significance of understanding costs and efforts involved in engineering tasks, and how to effectively convey this information to stakeholders.

Today we discuss the cultural implications of testing and release practices in software development, emphasizing that these issues are often rooted in organizational culture rather than technical challenges. We explore the transition from startup mentality to a more structured approach as businesses grow, the fragility of early successes, and the importance of quality over speed in releases. The discussion also highlights the role of leadership in fostering a culture of accountability and continuous improvement, as well as the need for developers to take ownership of their code.

In this episode, Day Martin, founder of Swayday, shares her journey from creating a standing desk company to developing motion gaming experiences aimed at improving educational outcomes for children with ADHD. The conversation explores the iterative process of game development and the importance of feedback. Day notably reuses instead of rewrites the gaming code of her pilot gaming project to pivot towards an idea with better traction.Show NotesSwayday: https://swayday.com/Times Tables: AR Space Game: https://apps.apple.com/az/app/times-tables-ar-space-game/id6743813232

Isaac and Jeffrey discuss the challenges faced in recovering value from failed projects, particularly focusing on a specific project that was halted due to legal concerns. They explore the importance of A-B testing, the role of legal feedback, and the lessons learned from the experience. The discussion emphasizes the need for quick iterations, optimizing processes for future projects, and maintaining a positive team attitude in the face of setbacks.

Isaac Askew and Jeffrey Sherman discuss the significance of making incremental changes visible in software development. They emphasize the importance of metrics in measuring performance, system reliability, and user behavior. The discussion covers A-B testing, decision-making based on data, and real-world applications of metrics in projects, highlighting how these practices can lead to better outcomes and improved communication within teams.

Isaac Askew and Jeffrey Sherman discuss the ongoing debate between end-to-end tests and unit tests in software development. The discussion delves into the implications of the testing pyramid, the potential future of testing with AI, and the evolving role of product teams in the testing process. They emphasize the need for a balanced approach to testing, cautioning against over-reliance on end-to-end tests while recognizing their value in certain scenarios.

Spriha Tucker, Field CTO at BuildKite and former founder of Aviator, dives deep into CI/CD practices. She discusses the pivotal role of feedback loops in agile development to enhance code quality and align products with user needs. Spriha highlights innovative rapid prototyping strategies and the necessity of authentic customer relationships. The conversation also covers the importance of data visualization in improving developer experiences and scaling organizational success, emphasizing that it's all about delivering real value through effective collaboration.