Back to Vol 18, Issue 4

PHP Architect · Vol 18, Issue 4 · April 2019

Education Station: What Went Wrong

by Chris Tankersley

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.

The full article is in PHP Architect Vol 18, Issue 4. Subscribe to read it and every new issue.

Subscribe
Chris Tankersley

About the author

Chris Tankersley

Chris Tankersley is a husband, father, author, speaker, podcast host, and PHP developer. He works for InQuest, a network security company out of Washington, DC, but lives in Northwest Ohio. Chris has worked with many different frameworks and languages throughout his twelve years of programming but spends most of his day working in PHP and Python. He is the author of Docker for Developers and works with companies and developers for integrating containers into their workflows.

Our Partners

Collaborating with industry leaders to bring you the best PHP resources and expertise

Interested in partnering? Get in touch →