Screaming in the Cloud - Drawing from the Depths of Experience with Deirdré Straughan

Episode Date: January 25, 2022

About DeirdréFor over 35 years, Deirdré Straughan has been helping technologies grow and thrive through marketing and community. Her product experience spans consumer apps and devices, cloud services and technologies, and kernel features. Her toolkit includes words, websites, blogs, communities, events, video, social, marketing, and more. She has written and edited technical books and blog posts, filmed and produced videos, and organized meetups, conferences, and conference talks. She just started a new gig heading up open source community at Intel. You can find her @deirdres on Twitter, and she also shares her opinions on beginningwithi.comLinks:“Marketing Your Tech Talent”: https://youtu.be/9pGSIE7grSsPersonal Webpage: https://beginningwithi.comTwitter: https://twitter.com/deirdres

Hello, and welcome to Screaming in the Cloud, with your host, Chief Cloud Economist at the Duckbill Group, Corey Quinn. This weekly show features conversations with people doing interesting work in the world of cloud, thoughtful commentary on the state of the technical world, and ridiculous titles for which Corey refuses to apologize. This is Screaming in the Cloud. This episode is sponsored in part by LaunchDarkly. Take a look at what it takes to get your code into production.

I'm going to just guess that it's awful because it's always awful. No one loves their deployment process. What if launching new features didn't require you to do a full-on code and possibly infrastructure deploy? What if you could test on a small subset of users and then roll it back immediately if results aren't what you expect? LaunchDarkly does exactly this. To learn more, visit launchdarkly.com and tell them Corey sent you and watch for the

wince. This episode is sponsored in part by our friends at rising cloud which i hadn't heard of before but they're doing something vaguely interesting here they are using ai which is usually where my eyes glaze over and i lose attention but they're using it to help developers be more efficient by reducing repetitive tasks so the idea being that you can run stateless things without having to worry about scaling placement etc, etc. and the rest. They claim significant cost savings and they're able to wind up taking what you're running as it is in AWS with no changes and run it inside of their data centers that span multiple regions. I'm somewhat skeptical, but their customers seem to really like them. So that's one of those areas where I really have a hard time being too snarky about it, because when you solve a customer's

problem and they get out there in public and say, we're solving a problem, it's very hard to snark about that. Multis Medical, Construx.ai, and Stacks have seen significant results by using them, and it's worth exploring. So if you're looking for a smarter, faster, cheaper alternative to EC2, Lambda, or Batch, consider checking them out. Visit risingcloud.com slash benefits. That's risingcloud.com slash benefits. And be sure to tell them that I sent you, because watching people wince when you mention my name is one of the guilty pleasures of listening to this podcast.

Welcome to Screaming in the Cloud. I'm Corey Quinn. One of the best parts about running this podcast has been that I can go through old notes of conferences I've went to and the people whose talks I've seen, the folks who have done interesting things back when I had no idea what I was doing, as if I do now. And these are people I deeply admire. And now I people I deeply admire. And now I have an excuse to reach out to them and drag them onto this show

to basically tell them that until they blush. And today is no exception for that. Deirdre Strawn has had a career that has spanned three decades, I believe, if I'm remembering correctly. A bit more even. Indeed. And you've been in, I want to say marketing,

but I'm scared to frame it that way, not because that's. And you've been in, I want to say marketing, but I'm scared to frame it that way, not because that's not what you've been doing, but because so few people do marketing to technical audiences well, that the way you do it is so otherworldly good compared to what is out there that it almost certainly gives the wrong impression. So first things first, thank you for joining me. Very happy to. Thank you for having me. I'm very happy to. Thank you for having me. It's always a delight to talk with you. So what is it you'd say it is you do exactly? Because I'm doing a very weak job of explaining it in a way that is easy for folks who have never

heard of you before, which is a failing, to contextualize. Well, there's one. I was until recently working for AWS and went to the went to an internal conference once at which they said it was a marketing conference. They said, as the marketing organization, our job is to educate. Now, you can discuss whether or not we think AWS does that well, but I deeply agree with that statement that as marketers, our job is to educate people. The classical marketing is to educate people about the benefits of your product. Here's why ours is better. The Kathy Sierra approach to that, which I think is very, very wise, is don't market your product by telling people how wonderful the product is. Tell them how they can kick ass with it. How do you wind up disambiguating between that and, let's just say, it's almost a trope at

this point where someone will talk about something, be it a product, be it an entire Web3 thing, whatever. And when someone comes back and says, well, I don't think that's a great idea, the response is, oh, no, no. You just need to be educated properly about it or do your own research, that sort of thing. And that is, to be clear, not anything I have ever seen you say, do, or imply. But that almost feels like the wrong direction to take that in, of educating folks. Well, yeah, I mean, the way it's used in those terms, it sounds condescending. In my earliest, earlier part of my career, I was dealing with consumer software. So this was in the early days of CD recording.

We were among the pioneering CD recording products. And the idea was to make it, my Italian boss saw this market coming because he was doing recording CDs as a service. Like you were a law firm that needed to store a lot of data and he would cut a CD for you and you would store that. And, you know, this was on a refrigerator size thing with a command line interface, very difficult to use, very easy to waste these hundred dollar blank CDs. But he was following the market and he saw that, you know, there was going to be these half height CD-ROM drives. And he said, well, what we need to go with that is software that is actually

usable by the consumer. And that's what we did. We created that software. And so in that case, there were things customers still had to know about CD-R, but my approach was that, you know, I do the documentation. I have to explain this stuff, but I should have to explain less and less. More and more of that should be driven into the interface and just be so obvious and intuitive that nobody ever has to read a manual. So education can be any of those things. You know, your software can be educating the customer while they're using it. I wish that that were one of those things we could point out and say, well, yeah, years later, it's blindingly obvious to everyone, except for the part where it's not. Where every once in a while on Twitter, I will go and try a new service that some cloud company launches or something else I've heard about.

And I will effectively screenshot and then live tweet my experiences with it. And very often, I'll get accused of people saying, ah, you're pretending to be dumb and not understanding that that's how that interface works. No, I'm not. It turns out that the failure mode of bad interfaces and of not getting this right is not that people look at it and say, ah, that product is crap. It's that, oh, I'm dumb and no one ever told me about it. That's why I'm so adamant about this. Because if I'm looking at an interface and I get something wrong,

it is extremely unlikely that I'm the only person who ever has. And it goes beyond interfaces. It goes out to marketing as well, with poor messaging around a product. When I say marketing, I'm talking the traditional sense of telling a story and here's a press release. Great, You've told me what it does. You told me about big customers and the rest, but you haven't told me what painful problem do I have that it solves

and why should I care about it? Almost like that's the foregone conclusion. No, no. We're much more interested in making sure that they get the company name and history right in the about us at the bottom of the press release. And it's missing the forest for the trees in many respects. It's on some level, it suffers a similar problem of sales where you have an entire field that is judged based upon some of the worst examples out there. And on the technical side of the world, again, all these roles are technical, but the more traditional, I write code for a living types, there's almost a condescension or a dismissiveness that is brought toward people who work in sales or in marketing or honestly anything that doesn't spend all their time staring into an IDE for a living. You know, the people who get to do something that makes them happy as opposed to this misery

that the coder types that we sometimes find ourselves trapped into. How have you seen that? Yeah, and it's also condescension towards customers. I have seen so many engineers who will throw something out there and say, this is the most beautiful, sexy, amazing thing I've ever done. And there have been a few occasions when I've looked at it and gone, yes, I can see how from a technical point of view, that's beautiful and amazing and sexy,

but no customer is ever going to use it, either because they don't need it or because they won't understand it. There's no way in that context to have that make sense. And so, yeah, you can do beautiful, brilliant engineering, but if you never sell it, no one ever uses it, what's the point? One of the ways that I've always found to tell a story that resonates, and it sometimes takes people by surprise when they're doing a sponsorship of something I do or whatnot. And they're sitting there talking about how awesome everything is. And, hey, let's do a webinar together. It's cool. We can do that.

But I'd rather talk to one of your customers because you can say anything you want about your product. And I can sit here and make fun of it because I have deep-seated personality problems and that's great. But when a customer says, I have this problem and this is the thing that I pay money for to fix that problem, it is much harder for people to dismiss that because it's, you're voting with your dollars. You're not saying this because if your product succeeds, you get to go buy a car or something. No, someone instead of saying this because I had a painful point, not only am I willing to pay money to make this painful thing go away, but then I want to go out in public and talk about that. That is an incredibly hard thing to refute, bordering on the impossible in some circumstances. That's what always moved me. If you have a customer telling stories about how great something is, I will listen. If you have

your own internal employees talking about how great something is, I will listen. If you have your own internal employees talking about how great something is, I have some snark for you. And that is another thing AWS gets right, is they work very hard to get the customer in front of the audience. Although, with a new technology service, et cetera, there is a point before you may have those customers in which the other kind of talk, where you have a highly technical engineer speaking to a highly technical audience and saying, here's our shiny new thing and here's what you can do with it.

Then you get the customers who will come along later and say, yes, we did thing with the shiny new thing and it was great. An engineer talking about what they did is not always to be overlooked. Your career trajectory has been fascinating to me in a variety of different ways. You were at Sun Microsystems, and I guess personally, I just hope that when you decide to write your memoirs, you title it The Sun Also Crashes.

That's such a great title. I haven't seen anything use it yet, and I hope I live to see someone doing that. And then you were at Oracle for 10 months. Wonder how that happened for those who aren't aware. There was an acquisition story. And then you went to Oracle for 10 months. Wonder how that happened for those who aren't aware. There was an acquisition story. And then you went to spend three and a half years at running educational programs and community at Joyent back before community architect, which is what you were at the time,

was really a thing. Community was just the people that showed up to talk about the technology that you've done. You were one of the first people that I can think of in this industry when I've been paying attention who treated it as something more than that. How did you get there? So my early career, I was living in Italy because I was married to an Italian at the time. And I had already been working in tech before I left the United States and enjoyed it and wanted to continue it. But there was not much happening in tech in Italy then. And I just got very, very lucky. I fell

in with this Italian software entrepreneur, absolute madman. And he was extremely unusual in Italy in those days. He was basically doing a Silicon Valley style software startup in Milan and self-funded, partly funded by his wealthy girlfriend. You know, we were small, scrappy, all of that. And so he decided that he could make better software to do CD recording as the CD-ROM drives were becoming cheaper and he could foresee that there would be a consumer market for them. What era was this? Because I remember back when I was in school, basically throughout failing out of college, burning a bunch of CDRs to play there, and every single tool I ever used was crap.

You're right. This was a problem. So we started on that software in 91. Yeah. You know, his goal was, I'm going to make the leading CD recording software for the Windows market. Hired a bunch of smart engineers, of which there are plenty in Italy, and started building this thing. I had done a project for him documenting another OCR, optical character recognition product, and he said, how would you like to write a book together about CD recording? And I was like, okay, sure.

So we wrote this book, and it was like okay sure so we wrote this book and you know it's like basically me reading and him explaining to me the various color book specs from phillips and sony that explain you right down to the pits and lands how cd recording works and then me translating it into layman's terms and so the book got published in january of 1993 by random house it's one of the first books if not the first book in the world to actually be published with a cd included so you're ultimately the person who's responsible indirectly for hey you could send cds out and then the sea of aol mailers showing up it was basically the mini frisbee uh plague lasted a decade or so for the rest of us yeah and this was all marketing.

For him, the whole idea of writing a book was a marketing ploy. Because on the CD, we included a trial version of the software. And that was all he wanted to put on there. But I thought, well, let's take this a step further. And this was, I had been also doing a little bit of work in journalism just to scrape by in Italy. I was actually an Italian computer journalist. And I was getting sent to conferences, including the launch of Adobe PDF. Like, they sent me to Scotland to learn about PDFs.

Okay. But then it wasn't quite ready at the time, so I ended up using FrameMaker instead. But I made an entire hypertext version of that book and put it on that CD, which was launched in early 93, when the internet was barely becoming a thing. So we launched the book, sold the book. Turned out the CD had been manufactured wrong and did not work. Oh dear. And I was just dying. And the publisher said, well, you know, if you can get hold of the readers, the people, you know, cause they were getting complaints. They said, if you can reach the readers somehow and let them know there's a number they can call and we'll send them a replacement disk. We had put our CompuServe email address in the book.

It's like, yo, hey, we'd love to hear from you. Write to us. Were those a long string of numbers as a username? Yeah. You could reach it via external email at the time, I believe. And we didn't really expect that many people would bother, but because there was this problem, we were getting a lot of contacts. And so I was like, I was determined I was going to solve this situation. And I was interacting with them. And those were my first experiences with interacting

with customers, especially online. And we did have a solution. We were able to defuse the situation, get it fixed. So that was when I realized it was very powerful because I could communicate very quickly with people anywhere in the world and quickly over whatever the modem speed was at that time, 1,800 baud or something. And so I had already been using CompuServe when I was in college. And so I was interested in how do you communicate with people in this new medium? And I started applying that to my work. And then I went and applied it everywhere. It's like, okay, well, there's this new thing coming, you know, called the internet. Well, how can I use that? Publishing paper manual seems kind of stupid in this day and age. So I can update them much more quickly if I have it on a website. So by that time, the company had been acquired by Adaptec. Adaptec had a website,

which was mostly about their cables and things. And so I just kind of made a section of the website. It was like, here is all about CDR. And it got to where it was driving 70% of the traffic to Adaptec, even though our products were a small percentage of the revenue. And at the same time, I was interacting with customers on the Usenet and by email. And then later mailing lists and the rest. And now it's, we take it for granted, but it used to be that so much of this was unidirectional, where at an absolute high level, the best you could hope for in some cases is, I really have something to say to this author. I'm going to write a letter and mail it to the

publisher and hope that they forward it. And you never really know if it's going to wind up landing or not. Now it's, I'm going to jump on Twitter and tell this person what I think. And whether that's a good or bad change, it has changed the world. And it's no longer unidirectional where your customers are silent masses anymore, regardless of what you wind up doing or selling. I mean, I sell consulting services. Yeah, I deal with customers a lot. We have high bandwidth conversations. But I also do an annual charity t-shirt drive. And I get a lot of feedback and a lot of challenges with deliveries and the rest toward the end of the year. And that is something else we have to deal with. It's not what it used

to be of just mail a self-addressed envelope to somewhere and hope for the best, and we'll blame the post office if it doesn't work. The world changed, and it's strange that happens in your own lifetime. Yeah, and there were people who saw it coming. Early on, I became aware of the Cluetrain Manifesto because a customer wrote to me and said, I think you're the best example I see out there of people actually living this. And the clue train manifesto said, the internet is going to change how companies interact with customers. You are going to have to be part of a conversation rather than just, we talk to you and tell you what's what. And I was already embracing that. And then it has had profound implications. It's in some ways a democratization of companies and their products, because people can suddenly be very vociferous about what they think about your product and what they want improved and

features they'd like added and so forth. And I never said the customer is always right, but the customer should always be treated politely. And so I just developed this. It was me, but it was a persona, which was true to me, where I am out here, I'm interacting with people. I am extremely forthcoming and honest. That you are, which is always appreciated, to be clear. I have a keen appreciation for folks who I know, beyond the shadow of a doubt, will tell me where I stand with them. I've never been a fan of folks who will, oh, I can't stand that guy. Oh, great, here he comes. Hi!

No, there is something very refreshing about the way that you approach honesty and that you've always had that. And it manifests in different forms. You are one of those people where if you say something in public, be it in writing, be it on stage, be it in your work, you believe it. There has never been a shadow of doubt in my mind that someone could pay you to say something or advocate for something in which you do not believe. Nice. Yeah, it's just partly because I've never been good at lying. It just makes me so deeply uncomfortable that I can't do it. That's what a good liar would say. Let's be very clear here. Like, what's the old joke? Like, if you're going to be good at one thing, be good at lying because then you're good at everything. No, it's a terrible way to go through life. Yeah, and the

earned trust thing was part of my portfolio from very early on, which was hilarious because in those days, as now, there were people whose knee-jerk reaction was, if you're out here representing a company, you automatically must be lying to me or about to lie to me or have lied to me. But because I had been so out there and so honest, I had dozens of supporters who would pile in and say, no, no, no, that's not who she is. And so it was, uh, yeah, it was interesting. I had my trolls, but I also had lots of defenders. The real thing that I've seen as well. Sometimes is when someone is accused of something like that, people will chime in. Look, I get this myself. People like

you. I don't generally have that problem, but people will chime in with like, I don't like Corey, but no, he's generally right about these things. Like, okay, great. It's like the backhanded compliment and I'll take what I can get. I want to fast forward in time a little bit from the era of mailing books and CDs, the CDs in them,

and then having to talk to people via other ways to get them in CompuServe to 2013 when you gave a talk at one of, no, I'm not going to say one of, it is the best community conference of which I am aware, Monktoberfest, as put on by our friends at RedMonk. It was called Marketing Your Tech Talent. And it's one of those videos that's worth the watch. If you're listening to this and you haven't seen it, you absolutely should fix that. Tell me about it. Where did the talk come from? As you can see in the talk, it was stuff I had been doing. It actually started earlier than that.

When I joined Sun Microsystems as a contractor in 2007, my remit was to try to get Sun engineers to communicate. Sun had done this big push around blogging. They'd encouraged everybody, open up your own blog. Here's our blogging platform. You can say whatever you want. And there were like 3,000 blogs, about half of which were just moribund. They had put out one or two posts

and then nothing ever again. And for some reason, I don't know who decided, but they decided that engineers had goals around this and engineering teams had to start producing content in this way, which was a strange idea. But so I was brought on. It's like, you know, help these engineers communicate, help them with logging and somehow find a way to get them doing it. And so I did a whole bunch of things from like running competitions to just going and talking to people. But we finally got to where Dan Maslowski, who was the manager who

hired me in, he said, well, we've got this conference. It was the SNEA, the Storage Networking Industries Association Conference. We're a big sponsor. We've got like 10 talks. And why don't you just go, I know, I'm going to buy you a video camera, go record this thing. And I'd used a video camera a little bit, but, you know, it's like never in this context. So it's like, okay, let's figure out, you know, what kind of mic do I need? And so I went off to the conference with my video blogging rig and videoed all those talks. And then the idea was like, okay, we'll put them up on, you know, Sun had its own video channels and things. We'll put it out there and this information will then

be available to more people. It'll help the engineers communicate what they're doing. And the funny part was I run into with Sun, the professional video people wanted nothing to do with it. Like your stuff is not high enough quality. You don't meet our branding guidelines. You cannot put this on the Sun channels. Okay, fine. So I started putting it on YouTube, which in those days meant splitting it into 10 minute segments because that was all they would give you. And so it was like everything I was doing was guerrilla marketing because I was always in the teeth of somebody in the corporation who wanted to, it's like, oh, we're not going to put out video unless it can be slickly produced in the studio. And we're only going to do that for VPs, not for engineers. Oh yeah. The little

people, as it were. This talk in many ways, I don't know if I've ever told you this story or not, but it did shape how I approached building out my entire approach to the sponsorship side of the business that I have, how I approach communicating with people. It's where, in many ways, the newsletter has taken its ethos. One of the things that you mentioned in that talk was, first, you were, I believe, the first time that I ever saw someone explicitly comparing the technical talent slash dev rel, which is not a term I would call it, but all right, to the Hollywood model,

where you have this idea that there's an agent that winds up handling these folks. They're freelancers. They're named talent. Those are the ones that have the draw. That's what people want. So you have to develop this. And okay, well, why is it important to develop this?

Because you absolutely need to have your technical people writing technical content, not folks who are divorced from that entire side of the world, because it doesn't resonate. It doesn't land. This is, I think, what DevRel has sort of been turned into. What is DevRel? Well, it's special marketing, because engineers need special handling to handle these things. No, I think it's everyone needs to be marketed to in a way that has authenticity, that meets them where they are. And that's a little harder to do with people who spend their lives writing code than it would be someone who is in a more accessible profession. But I don't think that a lot of it's being done right. This was the first encouragement that I'd gotten

early on that maybe I am onto something here. Because here's someone I deeply respect saying a lot of the same things from a slightly different angle. Like I was never doing this as part of a large technology company, but it was still, there's something here. And for better or worse, I think I've demonstrated by now

that there is some validity there. But back then it was transformational. Well, thank you. It still kind of is in many respects. This is all new to someone. Yeah, I felt, you know, I'd been putting engineers in front of the public and found it was powerful. And engineers want to hear from other engineers. And especially for companies like Sun and Oracle and Joyent, we're selling technology to other technologists.

So there's a limited market for white papers because VPs and CEOs want to read those. But really, your main market is other technologists, and that's who you need to talk to. And talk to them in their own way, in their own language. They weren't even comfortable with slickly produced videos. Neither being on the camera nor watching it. Yeah, at some point, it's what I was like, I look too good. It's like, oh, yeah, it's, oh, you're going to do a whole video production thing. Great.

Okay, well, the makeup artist can be like, what do you mean makeup? And it's. Oh, it was worse. Sun wasted so much money because you would get an engineer and put him in the studio under all these lights with these great big cameras, and they would just freeze. And he was like, well, hurry up, hurry up. We've got half an hour of studio time. You'll get your thing, say it.

Yeah, whereas I would take them in some back conference room and just set up a camera and And it's like, well, hurry up, hurry up. We've got half an hour of studio time. You'll get your thing, say it. And it's like, eh. Whereas I would take them in some back conference room and just set up a camera and be sitting in a chair opposite. It's like, relax. Tell me what you want to tell me. If we have to do 10 takes, it's fine. Yeah, video quality wasn't great, but the content was great. It seems like there's a new security breach every day.

Are you confident that an old SSH key or a shared admin account isn't going to come back and bite you? If not, check out Teleport. Teleport is the easiest, most secure way to access all of your infrastructure. The open source teleport access plane consolidates everything you need for secure access to your Linux and Windows servers. And I assure you, there is no third option there. Kubernetes clusters, databases, and internal applications like AWS Management Console, Yankins, GitLab, Grafana, Jupyter Notebooks, and more. Teleport's unique approach is not only more secure, it also improves developer productivity. To learn more, visit goteleport.com. And no, that's not me telling you to go away. It isTeleport.com. And no, that's not me telling you to go away.

It is GoTeleport.com. Speaking of content, one more topic I want to cover a little bit here is you recently left your job at AWS. And even if you had not told me that, I would have known. Because your blog has undergone something of a renaissance, beginningwithi.com, for those who want to follow along. And of course, we'll put links to this in the show notes. You've been suddenly talking about a lot of different things. And I want to be clear, I don't recall any of these posts being one of those,

I just left a company, I'm going to set them on fire now. It's been about a variety of different topics, though, that have been very top of mind for folks. You talk about things like equal work for equal pay. You talk about remote work versus cost of commuting a fair bit. And as of this recording, you almost recently wound up talking specifically about problematic employers in tech. But what you're talking about is also something that was happened during the days of the Sun acquisition through Oracle. So people are thinking like, wait a minute, is she sub-tweeting what happened today? No. These things rhyme and they repeat. I'm super

thrilled whenever I see this in my RSS reader, just because it is so like, oh good, I'm going to read something now that I'm going to enjoy. So let me put this in distraction-free mode and really dig into it because your writing is a joy. What is it that has inspired you to bring that back to life? Is it just having a whole bunch of free time? And well, I'm not writing marketing stocks anymore, so I guess I'm going to write blog posts instead? My blog, if you looked at a calendar over the years, it sort of comes and goes depending what else is going on in my life. I actually was starting to do a little bit more writing and I even did a few little TikTok videos before I quit AWS and starting to think about, you know, some of

the more ancient history parts of my career. It's partly just because of what's been going on in the world. Brendan and I moved to Australia a year ago and it was something that had been planned for a long time, we did not actually expect that we would be able to move our jobs the way we did. And then, you know, with pandemic, everything changed. That actually accelerated our departure timeline because we've been planning initially to let our son stay in his school in California until he finished elementary, but then he wasn't in school. So there seemed no point, whereas in Australia, he could be in a classroom. And so, you know, the whole world is changing and the working world is

changing. But also, you know, we all started working from home. I've been working from home mostly since 1993. And I was working very remotely because I was working from Italy for a California company. And because I was one of remotely because I was working from Italy for a California company. And because I was one of the first people doing it, the people in California did not know what to make of me. And I would get people just completely ignore any emails I sent. It was like as if I did not exist because they had never seen me in person. So I would just go to California four times a year and spend a few weeks. And then I would get the FaceTime. And after that, it was easy to interact on any way I needed to. It feels like it's almost the worst kind of remote because you have most people in an office,

and then you have a few outliers. And that tends to, in my experience at least, lead to a really weird team dynamics where you have almost a second class of folks who aren't taken nearly as seriously. That's why when we started our company here, it was everyone is going to be remote all the time. We were distributed. There is no central office because as soon as you do that, that's where things are disastrous. My business partner and I live a couple states apart.

Yeah, and I think that's the fairest way to do it in companies that have already existed, where they do have headquarters and there's... Yeah, you can't suddenly sell your office space and all 300,000 employees are now working from home. That's a harder thing to do. Yeah. But I think it's interesting that the argument is being framed as, oh, people work better in the office, people learn more in the office. And we've even had the argument trotted out here that people should be forced back to the office because the businesses in the central business district depend on that. It's like, well, what about the businesses that have since, you know, in the meantime sprung up in the more suburban centers?

You know, you've got some thriving little cafes out there now. Are we supposed to just screw them over? It's ultimately people making economic arguments that have nothing to do with the well-being of employees. And the pandemic at least has, I think, a lot of people have come to realize that life is just too short to put up with a lot of bullshit. And that, by and large, commuting is bullshit. It's a wasted time. It's not great for the environment. And again, I'm not sitting here saying the entire world should do a particular thing. I don't think that there's one size fits everyone solutions possible in this

space. Some companies, it makes sense for the people involved to be in the same room. In some cases, it's not even optional. For others, there's no value to it, but getting there is hard. And again, different places need to figure out what's right for them. But it's also, the world is changing and trying to pretend that it hasn't. It just feels regressive. And I don't think that that's going to align with where the industry and where people are going, especially in a full remote situation we've had with a global pandemic. Some wit on Twitter recently opined that it's never been easier for a company to change jobs. You just have to wait for the new laptop to show up, and then you just join a different Zoom link and you're in your new job. It's like, you know, you're not that far from wrong here.

There's no like, well, where's the office? No, it is my day-to-day looks remarkably similar regardless of where I work. That means something. I was one of the early beneficiaries as well of this work-life balance that I could take my kid to school in the morning and then work and then pick her up from school in the afternoon and spend time with her. And then California would be waking up for meetings. So after dinner, I'd be having meetings. Yeah, sometimes it was a pain, but it was workable and it gave me more flexibility. Now, whereas the times I had to commute to an office tended to be hellish. I think part of the reason the blog has had a lot more activity is I've just been in sort of a more reflective phase.

I've gotten to this very privileged position where I suddenly realized I actually have enough money to retire on. I have a husband who is extremely supportive of whatever I want to do. And I'm in a country that has a public health care system, if it doesn't completely crumble under COVID in the next few weeks. Hopefully we'll get this published before that happens. Yes. And so I don't have to work. It's like up to this point in my career, I have always desperately needed that

next job. I don't think I have ever been in the position of having competing offers. You know, there's people who talk about, you know, you can always go find a better offer. It's like, no, when you're a weirdo like me and you're a middle-aged woman, it's not that easy. People saying that invariably. So what is your formal job? Like, oh, SDE3. Like, okay, great. So that means like they're not just, they don't need to hire you. They need to hire so many of you that they need to start segregating them with Roman numerals. Great. Maybe that doesn't apply to everyone. Maybe that particular skill set right now is having its moment in the sun, but there's a lot of other folks who don't neatly fit into those boxes.

There's something to be said for empathy that, because this is my lived experience, does not mean it is yours. And trying to walk a mile in someone else's shoes is almost increasingly, especially in the world of social media, a bit of a lost skill. I mean, it's partly that recruiters are not always the sharpest tools in the shed and or they're very, they're very young. They're very new to it all. It's just people like to go for what's easy. And like, for example, me at the moment, it's easy to put me in that product marketing manager box. It's like, oh, I need somebody to fill that slot. You look like that person. Let's talk. Whereas before, people would just look at

my resume and go, I don't know what she is. I really think the fact that you've never had competing offers just shows an extreme lack of vision from a number of companies around what marketing effectively to a technical audience can really be. It's nice to see that what you have been advocating for and doing the work for for your entire career is really coming into its own now. Yeah, we'll see what happens next. It's been interesting. Yeah. I had never had so much attention from recruiters as when I got AWS on my resume. And then even more once it said product marketing manager, because, okay, you've got the fang and you've got a title we recognize. Let's talk to you.

Exactly. Oh, yeah. You fit in that box finally, because it's always been one of those, you know, like, what is it you actually do? There's a reason that I've built what I do now into the last job I'll ever have, because I don't even know where to begin describing me to what I do and how I do it. Even at cocktail parties, there's nothing I can say that doesn't sound completely surreal. I make fun of Amazon for a living. It's true, but it also sounds psychotic, and here we are. Well, it's absolutely brilliant marketing, and it's working very well for you. The realization that I had was that if this whole thing collapsed and I had to get a job again, what would I be doing? It probably isn't engineering. It's almost certainly much

more closely aligned with marketing. I just hope I never have to find out, because honestly, I'm having way too much fun. Yeah, and that's another thing I think is changing. I think more and more of us are realizing working for other people has its limitations. You know, it can be fun. It can be exciting depending on the company and the team and so on. But you're very much beholden to the culture of the company or the team or whatever. I grew up in Asia as a child of American expats. So I'm what is called a third culture kid,

which means I'm not totally American, even though my parents were. I'm not. I grew up in Thailand, but I'm not Thai. I grew up in India, but I'm not Indian. You're something in between. And your tribe is actually other people like you, even if they don't share the specific countries. Like one of my best friends in Milan was a woman who had grown up in Brazil and France. It's like, you know, no countries in common, but we understood that experience. And something I've been meaning to write about for a long time is that third culture kids tend to be really good at adapting to any culture, which can include corporate cultures. So every time I go into a new company, I'm treating that as a new cultural experience. It's like Ericsson was fascinating. It's this very old Swedish telecom with this wild old history and a footprint in something like 190 countries. That makes it amazingly unique and fascinating.

The thing I tripped over was I did not know anything about Swedish culture because they give cultural training to the people who are actually going to be moving to Sweden. But not the people working elsewhere, even though you're at, yeah, it's like, well, dealing with New Yorkers is sort of its own skill or dealing with Israelis, which is great. They have great folks, but it's a fun culture of management by screaming, in my experience, back when I had family living out there. It was great. One of my favorite people at AWS is Israeli. Exactly. And you have to understand some cultural context here and how to handle it, even if you're not sitting in the same place. Yeah, we're getting better as an industry, bit by bit, brick by brick. I just hope that we'll wind up getting there within my lifetime, at least. I really want to thank you for taking the time to come on the show.

If people want to learn more, where can they find you? Well, as you said, my website, beginningwithi.com. And I am on Twitter as Deirdre S. That's D-E-I-R-D-R-E-S. And we will, of course, include links to that in the show notes. So yeah, I'm pretty out there, pretty easy to find, and happy to chat with people. Which I highly recommend. Thank you again for being so generous with your time, not just now, but over the course of your entire career. Well, I'm at a point where sometimes I can help people, and I really like to do that. The reason I ever aspired to high corporate office, which I

now clearly I'm not ever going to make, but was because I wanted to be in a position to make a difference. And so even if all the difference I'm making is a small one, it's still important to me to try to do that. Thank you again. I really do appreciate your time. Okay. Well, it's great talking to you as always. Likewise. Deirdre Strawn, currently gloriously unemployed. I'm cloud economist Corey Quinn, and this is Screaming in the Cloud. If you've enjoyed this podcast, please leave a five-star review on your podcast platform of choice. Whereas if you hated this podcast, please leave a five-star review on your podcast platform of choice, along with an angry, insulting comment that you mail to me on a CDR

that doesn't read. If your AWS bill keeps rising and your blood pressure is doing the same, then you need the Duck Bill Group. We help companies fix their AWS bill by making it smaller and less horrifying. The Duck Bill Group works for you, not AWS. We tailor recommendations to your business, and we get to the point. Visit duckbillgroup.com to get started. this has been a humble pod production stay humble