![Code[ish] microphone logo mark](https://www2.assets.heroku.com/assets/podcast/codeish/codeish-microphone-mark-dark-f97b5b85f5deaa3222c37cae7ec34604dfd0258617bd6a4cfe223e0c0dc72c69.svg)
![Code[ish] logotype](https://www3.assets.heroku.com/assets/podcast/codeish/codeish-logotype-white-b7612fc8c65c2a6bc93473e2584e4141591e6093b37b2c32613d738a16a004a2.svg)
![Code[ish] logo](http://heroku-www-files.s3.amazonaws.com/podcasts/uploads/610d8a9b-b983-4670-ad93-88fdf7a929f8/codeish-cover-art.png)
112. Managing Public Key Infrastructure within an Enterprise
Robert Blumen
Lead DevOps Engineer, Salesforce
The episode focuses on managing a certificate authority (CA) within an enterprise. The internal CA is compared on many points to PKI on the public internet. →
111. Gift Cards for Small Businesses
Chris Castle
Director, Developer Advocacy, Heroku
James Dong
Owner, Last Minute Gear
How much can a day of coding help others? James Dong created a platform to help small businesses impacted by the COVID-19 pandemic sell gift cards online. Learn how this platform, built on Heroku, provided a way for residents to support... →
About Code[ish]
A podcast brought to you by the developer advocate team at Heroku, exploring code, technology, tools, tips, and the life of the developer.
Looking for more podcasts? Tune in to the Salesforce Developer podcast to hear short and insightful stories for developers, from developers.
110. Scaling a Bernie Meme
Nick Sawhney, Greg Nokes, Dan Mehlman, Michael Rose, and Jack Ziesing
Having a goofy meme project go viral can be an exhilarating feeling. It can also cause your heart to drop, as you've suddenly been saddled with new responsibilities around uptime and scaling resources. Nick Sawhney shares his experiences... →
109. Meditation for the Curious Skeptic
Andrew Lenards and Chris Castle
Meditation can take many forms. While it may conjure up cliched images of people sitting on cushions and chanting, in actually, many different groups, from the Harvard Business Review to medical professionals, are exploring the ways in which... →
108. Building Community with the Wicked CoolKit
Julián Duque, Lynn Fisher, and Chris Castle
Back in the day, the web felt smaller and people used simpler ways to connect with others. Those with niche interests still found each other despite the absence of mega social platforms. Lynn Fisher, Chief Creative Officer at &yet, shares... →
I Was There: Stories of Production Incidents II
Ifat Ribon, Chris Ostrowski, and Corey Martin
Growing your monthly active user count is the goal for every startup. But can your popularity actually work against you? In this installment of I Was There, Ifat Ribon and Christopher Ostrowski share their experiences tracking down... →
107. How to Write Seriously Good Software
Marco Faella and Rick Newman
Writing legible, functionable code is the aspiration for many programmers. Defining what that actually means is another matter altogether. Our guest, Marco Faella, has written a book on the subject. We'll explore the characteristics good... →
106. Growing a Self-Funded Company
Alli McGee, Lewis Buckley, and Greg Nokes
Most companies talk about building for the customer—but when you’re a self-funded company like BiggerPockets, building a product that users pay for can be the difference between success and shutting down. Guests Alli McGee and Lewis Buckley... →
105. Event Sourcing and CQRS
Andrzej Ludwikowski and Robert Blumen
Organizing data into a sequence of CRUD operations have a long history in software. But with newer and never-ending data streams, different models are emerging. Guest Andrzej Ludwikowski, a software architect at SoftwareMill joins host... →
104. The Evolution of Service Meshes
Luke Kysow and Robert Blumen
As microservices and container orchestration have grown in popularity, reusable layers of logic, such as authentication and rate limiting, have been pulled out into separate entities known as a service mesh. Luke Kysow, a software engineer... →
103. Chaos Engineering
Mikolaj Pawlikowski and Rick Newman
Chaos engineering is a way of testing your software predicated on the fact that something in your system, at some point, will break. By intentionally causing disruptions--for example, dropping network connections--and observing how your... →