podcast May 28, 2021

Podcast 342: You’re just as likely to ruin a successful product as make it better

Working from home? We chat about being your own operations department and battling scope creep solo.

Ben Popper Director of Content

We chat with Mike Brevoort, Platform Architect at Slack, about the power of platforms and what developers can do to automate workflows and processes that used to be shared across multiple teams, but now often fall to individuals working remotely and asynchronously.

Episode Notes

You can check out our piece how developers can be their own operations department here.

Our piece on preventing scope creep while working from home is here.

You can follow Mike on Twitter here and learn more about building apps for Slack here.

This week’s lifeboat badge goes to averroes for helping us to : Check if integer == null

TRANSCRIPT

Tags: api, futureofwork, platform, slack, the stack overflow podcast, workflow automation

se-stackoverflow May 5, 2023

Building golden paths for developers (Ep. 567)

The home team talks with Luca Galante of Humanitec about how platform engineering is more art than science, how self-service platforms empower developers with “golden paths,” and why he’s excited, not anxious, about AI tools (at least for now).

Eira May Senior Content Marketer

so-for-teams March 1, 2023

New pricing for Stack Overflow for Teams

Although a lot has changed since Stack Overflow launched in 2008, one thing has not: Stack Overflow continues to help people find the answers they need, when they need them. Our platform supports millions of the world's most active developers and technologists who visit every month to ask questions, learn, and share technical knowledge.

Joy Liuzzo

partner-content January 11, 2023

Taming multiple design systems with a single plugin (Ep. 526)

We chat about how their design system is evolving into a platform, how AI keeps their brand consistent, and why a design system doesn’t have to solve every use case.

Ryan Donovan

2 Comments

I’m confused – the title says Podcast 342, but the linked podcast says Podcast 344?
342 title: You’re just as likely to ruin a successful product as make it better;
344 title: WFH? Developers learn to be their own operations department.

Yes, I’m confused by this too. I’m also ‘amused’ that there seems to be lots of podcasts etc where the people taking part seem difficult to contact. One person in the linked podcast above even mentions contacting them on twitter, but they rarely use it. There’s sometimes never any ‘proper’ contact information these days, only social media addresses.
And if there’s anything wrong with the podcast, like above, you can’t contact them to put it right. Once the podcast is put up on a site, the organisation behind it is like a ghost ship that sails onwards.