One of the topics of seemingly perennial discussion among programmers is whether object-relational mapping (often abbreviated to ORM) is evil or not. Opinions seem to run the gamut from "I use and love it" to "I tried it once and never will again." And you often encounter at least a few "what are you talking about?"s.
I've given the talk "Banishing Loops with Functional PHP" (or "Functional Programming, it just depends on how I titled it) at least three times. But it's still, mostly a talk. You can watch a talk I've given many times right here:
Recently (at the end of 2017), OWASP updated its Top 10 list. For the unfamiliar, let me briefly explain what that means: the industry standard of basic-web-security education has altered. Though it's never been a complete security education, the OWASP Top Ten is where almost all standards for web-developer security education begin. So when it changes, that's kind of important.
Let's get it out of the way early: PHP is a strange and ugly language. It's not exceptionally fast. It's not beautiful syntactically. It's not formulated around a clear opinion about good software development practices. And it's still what I write a lot of software in. The obvious question is: why? Why use PHP today?
Like many people, I love the idea of doing positive work for the world. I do both little and big volunteer work, on a recurring and one-off basis. But the point here isn't how much praise I deserve (lots 😝), but what's it been like for me working with Code for Fort Collins. Code for Fort Collins is a member of Code for America's brigade program, and I've been involved for a few years. Here I'm going to examine what I've learned from my involvement.
It's easy to think about programming as an exercise of computers, or of languages and design. But at its heart programming is just about people. I bring this up because it's so easy to lose sight of the fact that people are who you're really programming for, and I just need a reminder sometimes. Maybe you do too.