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.
@adamdotdev what if that could also have a benefit for the company and other stakeholders?
eg.?
PAAS with AgencyOS/PM tool integrated
(not-so-tech platform for inclusivity)
This is a reminder that if you work in a country with very strong worker protection laws, and your employer announces mass layoffs, there is a fair chance you are protected.
Before signing anything: pay for an employment lawyer to get their opinion.
Very relevant in Berlin now.
@VillageOneCoop @darkhorseberlin Super interested in understanding motivations and insights about this project! We learned a thing or 2 about collabs, over the past 15+y, and that's how we know that we didn't even scratch the surface.
Happy to see this project popping up, and looking forward to knowing more! ♥️
@ShopifyDevs is there a suggested "official approach" on how to org Shopify Development workflow using git and git flow?
Any read you can recommend on the subject?
This statement seriously undermines my trust in Google as steward for the web platform. When did we go from "never break the web" to "yes we will break the web often and you should be prepared for it"?!