Ryan Peterman

It's ultra low profile and ergonomic.

And I couldn't find anything like it on the market.

So that's why we built it.

I'll put a link to the keyboard in the description.

You can take a look and learn more about the project there.

We could definitely use your support.

Also, if you have any feedback for me about the show, I'd love to hear it.

Comments on YouTube have led to guests coming on like Ilya Grigorik and David Fowler.

I wasn't aware of them until someone dropped a comment.

Also, feedback in the comments helped me learn to reduce the number of cliffhangers in the intros.

So your comments definitely make a difference.

Please keep letting me know what you'd like to see more of in the show, and I'll see you in the next episode.

This is Mark Brooker.

He's a distinguished engineer at AWS, and I interviewed him for technical learnings from his career.

3,000 cloud system postmortems.

I wanted to ask you, what makes a good postmortem?

You had a tweet that said that there are cases where caches are bad.

I prefer to see the teams around me avoiding caching where possible.

We also discussed how software engineering is changing.

What is important given that code is kind of flowing like water now?