Event Producer at @wpsessions. Organizer behind @wordsesh, @woosesh, and @loopconf. Father to 3 boys (one with #T1D). Husband to @kjrichards. I love #OSS, #Lego, #woodworking, and good #movies. (Also it's pronounced "risen" as in, "He is risen.")
I see and post 12:34 a lot. No, I don't know why, either.
| Personal | https://rzen.net |
| WPSessions | https://wpsessions.com |
| Gravatar | https://gravatar.com/rzen |
| Location | Grandville, MI, USA |
12:34!
Back home, finally, after a very long day of travel from London. #LoopConf was a blast! And now I'm ready to be in my own bed
This is excellent. 👌🏼
“Open source, the thing that drives the world, the thing Harvard says has an economic value of $8.8 trillion.
Most of it is one person.
And […] not one of those single person projects have the proper amount of resources they need. If you want to talk about possible risks to your supply chain, a single maintainer that’s grossly underpaid and overworked.”
Yuuup. Baffling how so many companies depend on open source software without funding it, ever.
The Register recently published a story titled Putin on the code: DoD reportedly relies on utility written by Russian dev. They should be ashamed of this story. This poor open source developer is getting beat up now to score some internet points. It’s very upsetting. But anyway, let’s look at some receipts. If you’re not real smrt, it seems like pointing out an open source project is written by one person in a country you don’t like is a bad thing. It could be. But it also could be the software running THE WHOLE F*CKING PLANET is written by one person. In a country. But we have no idea which country. It’s not the same person mind you, but it’s one person.
4 years of Securing Laravel! 🎂
🎉 120 Security Tips
🕵️ 37 In Depth articles
Thank you all for the support over the years!
I think many people misunderstand the purpose of code review. The purpose of code review is not for the reviewer to find bugs, and certainly not for them to ensure that the code is bug-free. Anyone who depends on code review to find bugs is living in a fool's paradise. As everyone should know by now, it is not in general possible to find bugs by examining the code.
The primary purpose of code review is to find code that will be _hard to maintain_. The reviewer looks at the code and tries to understand what it is doing and how. If they can't, that means it will be hard to maintain in the future, and should be fixed now, while the original author is still familiar with it.
OK, preaching to the choir here, but…
Our brains and bodies are simply not wired to handle the 24/7 horrors going on in the world right now.
I am not going to judge you based on how much you do or don’t talk about current events here.
Because I do know that the folks I follow here - they care, even if they’re not talking about it.
So if you’re feeling guilty/awkward/whatever about posting a good thing, or what you had for dinner, or something you made - please, don’t.
We need good stuff.
a 2661 byte program I wrote just won the "Sur Prize" at the International Obfuscated C Code Competition. You can probably guess what it is once I mention that @foone might enjoy it
Lea Verou, PhD
Stephen Rees-Carter 
Mark Dominus
Play Ball and Fight Fascists
deater
Jeremy Felt