*NO LONGER* Dev Relations @PayPal Best at: Actionable feedback Passion: Finding root cause Live to: Make an impact at ⚖️ Mantra: Experience is EVERYTHING
Here, in Arizona, the snakes expose themselves. I like to tell my husband that I like to avoid the questions you mention above, it’s giving too much space to them already. Just be grateful that you don’t have to be them or live with them. You get the choice to remove yourself from their negative behavior…some are not as lucky 😔 regardless! I have no idea why you’d even be dealing with this, you’re such an amazing person.
Honestly. I don’t care what side of a fence you sit on or what beliefs you have, but us adults have got to step it up for our children. The @CITYOFMESA school district has received 4 different threats alone this week and I just had to share number 5. Instead of fighting about why this is happening, go ask your kids if they’re okay tonight.
🚀 We’re excited to introduce Strategic SiteBuilders! Ready to build your dream website? Connect with us for cutting-edge design and development. https://t.co/fHoC9jLWbG
#WebsiteLaunch#WebDesign
What themes are folks using with Wordpress these day? Looking for the best template to use as a foundation, e.g. Theme: https://t.co/bi2XPzQNPh
Note: I hear bootstrap doesn't play nice with wordpress...Is this wrong???
Which one of my devs got me :)
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.
@KevinBlancoZ@LeadDevRel I’d personally do doc hacks every quarter (less cost to the business) and if budget is available a hackathon 1 - 2 times/year.