Thanks for making me realize how little I know about the PHP CLI, Ian!
Full of great information and ideas, but could benefit from a high-level look at processes, threads, signals, etc. at the top of the talk to help set some base terms.
While it started a little rough with technical difficulties, Nic eventually found his stride as he offered a lot of great advice. It wasn't until the chronic illness reveal, however, that everything made sense: that twist helped put everything he had previously mentioned into a new context, which was really impactful.
Great insights, and good job not letting the technical difficulties throw you off.
Really enjoyed it. Felt like it provided a good checklist and approach for analyzing attack surfaces and prioritizing responses. Really appreciate "giving permission" for not fixing everything - always good to remind devs that "good enough" is, in fact, good enough.
Might be value in spending more time on who potential attackers are? How does protecting from internal attacks differ from defending against script kiddies?
Thank you for sharing your knowledge, insights and experience Nic! ”Errors are your only honest friend. They let me know whats going wrong so I can fix them.” -Nic Hampton, Treehouse
nice work.
one bug in your example code!
Also, maybe address the question of why this additional step in testing is not overkill
Really great talk that is equally inspiring and terrifying.