A guide to establishing a productive Git workflow for development teams, covering branch strategies and best practices.
A developer shares personal insights on the benefits and challenges of pair programming, from overcoming initial anxiety to improved focus and debugging.
Explores the critical partnership between Engineering Managers and Product Managers, comparing it to a marriage for effective team alignment and decision-making.
A developer argues that well-run business meetings are crucial for software teams, distinguishing them from wasteful gatherings.
A software team shares their adapted Git workflow for managing a monolithic codebase with multiple independent development teams.
A developer shares a painful freelance project case study, detailing scope creep, poor management, and burnout, with lessons on client relationships and project ownership.
Argues that code reviews should be a team effort, not a single person's responsibility, to improve quality, share knowledge, and build ownership.
A detailed look at Disy's structured code review process, including their 'code buddy' system and principles for effective peer reviews.
A software team's journey from inconsistent practices to establishing a formal, team-wide code review process, including their goals and principles.
A software engineer discusses the concept of defect prevention, analyzing root causes of bugs and suggesting process improvements to avoid recurrence.
A junior front-end developer shares lessons on teamwork, communication, and tools for integrating into a new tech team.
A UI engineer shares key lessons from working at IBM Design, covering enthusiasm, iteration, and initiative in a tech design environment.
Explores why developers find Git difficult, contrasting individual vs. team workflows and the mindset shift needed to appreciate it.
Practical advice for software teams to reduce merge conflicts and improve collaboration using version control best practices.
A blueprint for product management focusing on building trust, establishing velocity, and strategically killing scope to align product and engineering teams.
Advocates for establishing a 'Git-iquette'—a set of etiquette rules for using Git in team projects to improve code history clarity and collaboration.
A guide to providing constructive and respectful feedback during code reviews, using examples from Linus Torvalds and a more positive approach.
A senior developer shares his 20-year philosophy on client-focused work, team consistency, and uncompromising code quality practices.
Laravel Forge introduces Circles for team server access and a new Forge Plus plan with unlimited servers and team management features.
A satirical critique of source control, arguing for USB drives, to highlight flawed reasoning in tech outage reactions.
