/Kevin Sookocheff

What Complex Systems Can Teach Us About Building Software tl;dr: To build successful complex software systems: (1) Define a set of quality architecture principles that the organization believes in and that are systematically enforced. (2) Develop quality information aggregation systems that allow leaders to determine which components of the system are following the rules. (2) Experiment widely and encourage diversity in how we build teams and how we build software. Kevin explains how he arrives at these conclusions.

featured in #401


Project Management For Software Engineers tl;dr: Kevin discusses the 5 phases of managing an engineering project, according to Project Management Institute: (1) Initiation: Identifying and interviewing stakeholders, developing scope statement and getting approval. (2) Planning: Creating comms, project and risk management plan. (3) Execution: Schedule accountability check-ins, adjust to feedback from delivering stepping stones. (4) Monitoring and Control: Regular status reports. (5) Closure: Confirm project is done, document lessons learned, celebrate success.

featured in #396


The Zero Bug Policy tl;dr: All bugs should be treated equally. Benefits are that it sensitizes the team to having bugs, reduces development time (devs have to re-learn the issue and context of bug which takes time), improves feature estimations, velocity and customer happiness.

featured in #135