Explore

Top 7 software bloggers to follow

This blog highlights the top 7 bloggers in the field of software engineering and product development. These bloggers provide valuable insights and ideas on software design, processes, and methodologies. The list includes Martin Fowler, known for his expertise in software patterns; Kent Beck, the creator of Extreme Programming and Test Driven Development; Paul Graham, co-founder of Y Combinator and an expert on startups and entrepreneurship; Jeff Atwood, co-founder of Stack Overflow; Andy Hunt, founder of the Pragmatic Programmer series; Joel Spolsky, a blogger who offers both sensible and surprising perspectives; and Steve Yegge, known for his entertaining content. Following these bloggers can help software engineers improve their skills and gain knowledge from the best in the field.

Building High-Performing Engineering Teams: Lessons from a Manager

This article discusses the insights and lessons learned from a top-tier engineer on building and leading successful engineering teams. It emphasizes the importance of team dynamics, workload management, performance evaluation, minimizing context switching, and leveraging diverse expertise. By prioritizing these factors, managers can create an environment that fosters collaboration, productivity, and success, ultimately leading to exceptional results.

Code Reviews 101

The goal is to increase code quality through effective collaboration and a proactive learning environment. Code reviews are important because they improve code quality, reduce incidents, promote team collaboration, identify issues with SOLID principles, and leverage cross-functional skills. Code reviews also benefit individuals by encouraging learning from peers, improving attention to detail, increasing productivity, and promoting technical discussions. When done right, code reviews save time in the long run. They also improve product quality by reducing code issues and promoting testable code. Code reviews are related to Agile as they share knowledge, improve estimates, and promote early feedback. Guidelines for code reviews include submitting small amounts of code, providing context to reviewers, including screenshots or mock-ups for UI changes, involving senior engineers or subject matter experts, and actively participating in code reviews. When asked to code review, it is important to provide constructive criticism, address the request promptly, communicate availability, notify the author when finished, look for tests, and involve a lead or senior engineer in case of disagreements.

Challenges Faced by Engineering Leaders in Scaling Teams

Engineering leaders face several challenges when scaling their teams. One key area of focus is providing effective feedback and recognition to team members, which fosters growth and improvement. Building strong relationships and collaboration between engineering and product teams is also crucial. Remote work presents unique challenges, such as lack of trust and engagement, which can be addressed through proactive communication and trust-building. Hiring qualified senior engineers is another challenge, but implementing a rigorous hiring process can help overcome this. By addressing these challenges, engineering leaders can create successful and high-performing teams and a positive work environment.

How do you do CI/CD?