The [REFACTORED] Podcast

Refactored 148: "DevOps: The Third Silo"

Wherein the guys think wheelwrights are making a comeback!

Show Notes

• The guys discuss the evolution of DevOps
  • Still a philosophy.
  • Still not a job title.
  • But also, now definitely a job title.
  • Danger zone: Did we just create a new silo? That would be… not great.
• Why do people elect .NET for web dev? The guys are baffled.
• Comment: “Serverless sounds cool in theory, but now we’ve got a thousand different functions running everywhere, and I have no clue how to monitor or debug half of them. Did we just trade one set of problems for another?”
• Comment: “I’ve been managing a dev team for a while, but now everyone wants to use AI tools to ‘help code faster.’ How do I keep productivity up without turning my team into a bunch of over-reliant AI button-pushers?”
• … and much more!

automation career cloud code devops microsoft-sucks school tooling workflow

Refactored 147: "Pro Consoles: Nothing to See Here"

Wherein Chris gives 0.1% and Frank goes full boomer desktop.

Show Notes

• Chris becomes a camera snob while Frank warns against combination appliances.
• Nothing CEO Carl Pei issues Return-To-Office mandate; publishes on LinkedIn.
  • It’s impassioned
  • It sounds logical
  • It’s unsubstantiated
  • TLDR: GTFO
• Are smartphones commoditized? Are “Pro” consoles worth it? The guys debate.
• The guys wonder what “innovation” will come next to steal the limelight from LLMs.
• … and much more!

business-strategy culture gaming gear hardware product-design remote-work

Refactored 146: "Procedural Justice"

Wherein Frank goes full Enya and Chris can't build a single boat.

Show Notes

• Chris has a new GPT power use case. It’s not new, and it’s not his, but he pretends like it is.
• The guys avoid a longer-form discussion about popular game dev algos, like Perlin Noise and Voronoi Diagrams.
• Frank brings up Pandora (yeah, it’s still a thing) and the guys talk ML “filter bubbles” and job security.
• The guys debate inconsistent messages coming out after a recent Columbus, Ohio data breach [1] [2].
  • TLDR: City officials lied. Then they retaliated against the whistleblower. Then they sued him. Then they lied some more.
  • …….. jerks
  • Maybe sometime the guys will share what they really think. ;)
• Streaming may revive a new wave of interactive fiction - Frank unpacks an example while Chris gets eaten by a giant spider.
• … and much more!

algorithm artificial-intelligence breach gaming law security workflow