Code Reviews At Disy - Where We Were And What We Wanted
A software team's journey from inconsistent practices to establishing a formal, team-wide code review process, including their goals and principles.
A software team's journey from inconsistent practices to establishing a formal, team-wide code review process, including their goals and principles.
The author reflects on the global reach of their book 'Intermediate Python', which has been read in 181 countries and used for training.
Laravel 5.3 introduces Mailables, a cleaner way to send emails using dedicated PHP classes instead of complex closures.
Explains why creating custom open source licenses harms collaboration and adoption, advocating for standardized licenses.
An introduction to threat modeling, a security technique for identifying assets, attack vectors, and attackers to build better system defenses.
A developer shares insights from reading the entire Python standard library, advising it's not necessary for proficiency and recommending community learning.
Discusses the philosophy that removing unnecessary features improves software by reducing complexity and cognitive load for users.
A tech consultant explains why clear, professional writing is a critical skill in IT, covering grammar, context, and documentation.
A GitHub employee shares a curated list of recommended books for hackers, geeks, and open source developers on technology and business.
A developer shares three powerful mindset principles from a Thoughtbot podcast: strong opinions loosely held, nothing is set in stone, and rejecting 'because we've always done it'.
A talk arguing for the importance of code comments, debunking common arguments against them and providing a framework for effective commenting.
A guide on how to ask clear, specific, and well-researched coding questions to get faster and better answers from experts.
A product manager shares twelve key responsibilities and daily activities based on their experience at GitHub, focusing on accountability, team leadership, and user advocacy.
Mike Ash announces a hiatus from regular blog posts to focus on completing his book, 'The Complete Friday Q&A: Volume II'.
The author explains their decision to publish their book 'Laravel: Up and Running' with O'Reilly instead of self-publishing.
A comprehensive talk and demo covering JUnit 5 features, architecture, migration from JUnit 4, and advanced testing techniques.
Explains the benefits of using language-agnostic automation scripts in software projects to simplify onboarding and CI/CD processes.
A software engineer discusses the concept of defect prevention, analyzing root causes of bugs and suggesting process improvements to avoid recurrence.
A developer recounts a massive, poorly-scoped code review and the strategies used to salvage it, emphasizing best practices.
Explores the terminology and lifecycle of software bug reports, discussing the tester's role and team dynamics in defect management.