DK Day! I’m giving away 3 DK Metcalf jerseys if he goes over 100 yards receiving vs his old squad. If he does that and the Steelers WIN I’ll give away 5 jerseys! I’ll you have to do is follow me and repost. It’s that simple. Let’s have the best day of all-time!
🔥 We are live!
I'm beyond excited to announce the early access of:
The Road to Next 🎉 🎊 🥳
A comprehensive, self-paced video course for full-stack web developers, featuring React 19 and Next 15.
Learn more in the replies 👇
3 random people who 🔁 will get a license 👌
Here’s the thing folks. I’ve been coding 32 years. When something like this happens it’s an organizational failure. Yes, some human wrote a bad line. Someone can “git blame” and point to a human and it’s awful. But it’s the testing, the Cl/CD, the A/B testing, the metered rollouts, an oh shit button to roll it back, the code coverage, the static analysis tools, the code reviews, the organizational health, and on and on. It’s always one line of code but it’s NEVER one person. Implying inclusion policies caused a bug is simplistic, reductive, and racist. Engineering is a team sport. Inclusion makes for good teams. Good engineering practices makes for good software. Engineering practices failed to find a bug multiple times, regardless of the seniority of the human who checked that code in. Solving the larger system thinking SDLC matters more than the null pointer check. This isn’t a “git gud C++ is hard” issue and it damn well isn’t an DEI one.