Eric, John, and Oscar record together again to discuss the April 2019 issue on the new frontend fundamentals, php[tek], and quite a lot more about web browsers than anyone anticipated.

The very first thing you need to do when something goes wrong is to get a good handle on the situation and find out what’s wrong. Many users first instincts are to get frustrated and say, “This is broken!” and expect you to figure it out. While there can be lots of places to look, narrowing down the possible causes can help greatly.

Over the past two months we’ve been building PHP Easy Math a purposely simple example library to demonstrate how to build a reusable package for the PHP ecosystem. We’re going to cover triaging and managing issues users may open as well as pull requests to your library.

Everyone on your team should have a good idea of the actual problem or feature they are working on before any code is written. Once the issue itself is ready to go, the work can begin. Every company will be slightly different in how they want to handle actual commits, but this month I will […]

Issues and issue tracking are central to your team’s communications about what’s getting worked on and needs fixing. Having a clear and agreed upon standard for working with them will keep your team focused and productive while minimizing misunderstanding.