
🏹👨🏻💻
2.9K posts

🏹👨🏻💻
@BrianNotABroMan
🎮🐧☕️🧗🏻🎲💻 He/Him
Current Location: The Present Katılım Şubat 2010
279 Takip Edilen82 Takipçiler

@SoundTransit @SoundTransit is the 2 line still running eastbound across the lake? Hard to tell from the alerts
English

Link riders: Expect significant delays due to power system damage near UW Station. Get the latest updates by signing up for service alerts: soundtransit.org/ride-with-us/s…

English
🏹👨🏻💻 retweetledi

We're committed to making gaming accessible for all 💚
This month, we recognize the Gaming & Disability Community with a partnership to create an Adaptive Joystick, a curated games collection, a Special Olympics collaboration, and more: xbx.lv/3TOKmJF
English

@shanselman @PointerExpert Well more accounts to ignore on the interne. Sad that racism in tech is such a thing still. He can gtfo with that noise.
English

@PointerExpert He was not
Zach Vorhies / Google Whistleblower@Perpetualmaniac
For people looking for a conspiracy, the replacement language for C++, Rust, is compromised by a cabal of woke tards that are doing strange things. It's possible this could be a plot to move mission-critical code to Rust. It's the only other language Linux is allowing, other than C. But who knows.
English

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.
English

@shanselman Coding conventions, team culture around quality vs speed, post mortem / growth mindset etc. Bugs WILL happen. It’s how you handle them, learn from them, and move forward productively
English

WTF? You couldn’t just analyze the code could ya
Zach Vorhies / Google Whistleblower@Perpetualmaniac
@ianmiles C++ is hard. Maybe they have a DEI engineer that did this but for mission-critical software like this Crowdstrike should have set up automated testing using address sanitizer and thread sanitizer that runs on every code update. github.com/google/sanitiz… clang.llvm.org/docs/ThreadSan…
English

@JezCorden Honestly I’d love an anthem 2 if they gave it love. Great combat. Semi interesting setup that never got going.
English

@offbrand_studio Very cool start to a studio and glad to see @PirateSoftware onboard. Recently started watching his shorts and seems like y’all have the right mindset in hard industry. Excited to see what next!
English

@JezCorden Yessss Jez. It’s weird. It’s wholesome. It’s perfect. And obviously Senshi is best
English
🏹👨🏻💻 retweetledi

Together we create a more inclusive gaming world.
It’s Pride Month, and we’re celebrating the LGBTQIA+ community by working with the @TrevorProject, sharing a curated game collection, and more: xbx.lv/3R6ugK1
English
🏹👨🏻💻 retweetledi

🌟 Dive into the latest Microsoft GDK updates! "Record this" feature now integrated in the user library API in XAppCapture, buffering in PlayFab Telemetry, GDK tool enhancements, and more. #GameDev #Microsoft
youtu.be/2PTJyxYPm5g?fe…

YouTube
English

@davidfowl Steelseries sensei but I’m left handed and need an ambidextrous one
English












