Bryan Finster retweeted
My laminated quick-reference card lists every engineer's individual defect rate and lines of code. Accountability isn't some fuzzy concept; it's a DATA point on my desk. scaledagiledevops.com/tags/g…
Bryan Finster retweeted
My build engineering team takes 6-8 weeks to provision a new environment, following a 200-step manual checklist signed off by three directors. Some call it 'lead time,' I call it a GUARANTEE of consistency. You can't rush... scaledagiledevops.com/tags/g…
Bryan Finster retweeted
My QA team consistently hits 3.7 defects per thousand lines of code. Been that way for eight quarters. That's not just stability; it's a testament to a PERFECTLY refined process. You'll understand when your metrics are this predictable.
Bryan Finster retweeted
Just joined this platform. My Convoy Commander suggested I "build a personal brand." I told him I already have one... It's called a 47-page deployment checklist and a laminated quick-reference card.
Bryan Finster retweeted
Most developers know TDD, but many teams are better served by starting with BDD.
Let me explain why. 🧵👇
Bryan Finster retweeted
In this month's Engineering Room episode, I explore the innovative Army Software Factory with Matt Flautt (CTO) and Jeff Day (Chief of Platform).
Listen HERE:
Apple - apple.co/43s2e0h
Spotify - spoti.fi/3VqZVIV
Audible - bit.ly/TERaudible
Just saw Book of Mormon and now have the song 🎵Hasa Diga @elonmusk🎵 stuck in my head.
Bryan Finster retweeted
Mr. President, Ukraine did not “start” this war. Russia launched an unprovoked and brutal invasion claiming hundreds of thousands of lives. The Road to Peace must be built on the Truth.🇺🇸🇺🇦
“Russia Invades Ukraine in Largest European Attack Since WWII” @FoxNews (February 24, 2022) foxnews.com/world/russian-in…
@LEGO_Group your website is broken. I’m seeing this in Safari and Chrome.
Tucker Carlson is lying about American soldiers firing missiles youtube.com/shorts/HrhgNA_Fh… via @YouTube
Tucker being yet another Russian agent? I’m shocked!
So Trump’s going to “drain the swamp” by creating another cabinet post with a SADMF.com worthy troll acronym that’s focused on “government efficiency” that requires two of his cronies to lead it. Sounds legit.
I see comments from people whining about AI use in the arts. I can only assume they aren’t good artists. AI is a tool, just like a camera. The real photographers didn’t die because of cheap cameras. Better tools help skilled people. They don’t replace skill.
What are the chances? It was great hanging out with you @VaughnVernon!
While in NYC this past weekend, I had a serendipitous opportunity to meet @BryanFinster in person. We were even staying at the same hotel. We talked mostly about CI/CD at scale and AI for developers. Bryan said I'm missing out by not trying Claude, which I have intended to do, but time escapes me.
Here we are together.
Bourbon Driven Development
If you can safely code while unsafe to drive, you probably have a good test suite.
The problem Democrats have is they keep making battle plans and expecting their opponents to follow their plan. That never ends well.
HEY MAGA:
In case you missed it, now YOUR guy is the old AF candidate, and he's been found liable for sexual assault, he rambles in public like a deranged fool, his name is all over Jeffrey Epstein's call logs, and he's a convicted felon.
AND HIS OPPONENT IS AN EXPERIENCED PROSECUTOR.
Looking forward to the debate.
Bryan Finster retweeted
This strange tweet got >25k retweets. The author sounds confident, and he uses lots of hex and jargon. There are red flags though... like what's up with the DEI stuff, and who says "stack trace dump"? Let's take a closer look... 🧵1/n
Bryan Finster retweeted
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.
Bryan Finster retweeted
Facing challenges with traditional agile frameworks?
@BryanFinster shows how true agility comes from engineering systems to reduce delivery friction. Improve every aspect of your organization!
Read more: infoq.com/articles/replace-p…
My post: linkedin.com/posts/romanorot…


















