Screaming in the Cloud - Google Is Deprecating This Podcast with Cody Ogden

Episode Date: December 4, 2019

About Cody OgdenA product designer at heart, Cody has been crafting experiences for the web since he was ten years old. He’s best known for his open source website and its cheeky Twitter ac...count, Killed by Google, which Fast Company called “an informational fever dream,” and one netizen praised as “an ignorant meme.” His project tracks news of Google’s product decisions until they are laid to rest in the Google Graveyard.Cody works remotely as a software engineer at Cannabiz Media. He's a fan of hard cider, winters in Minnesota, and sees himself moving into a product design role at some point in the future.LinksTwitter: @killedbygoogleLinkedIn URL: https://linkedin.com/in/codyogdenPersonal site: https://codyogden.comCompany site: https://killedbygoogle.com

Transcript
Discussion (0)
Starting point is 00:00:00 Hello and welcome to Screaming in the Cloud with your host, cloud economist 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. to help you solve common problems and build faster. They themselves are free, though occasionally some of the products they stand up are not, but it's a great way to click button, wind up receiving a technical solution
Starting point is 00:00:51 that's implemented that ideally solves a problem you have. Visit snark.cloud slash AWS solutions. Again, that is snark.cloud slash AWS solutions. And my thanks to AWS for their generous sponsorship of this episode. And this episode is sponsored by Influx Data. Influx is most well known for InfluxDB, which is a time series database that you use if you need a time series database. Think Amazon Timestream, except actually available for sale and has paying customers.
Starting point is 00:01:24 To check out what they're doing, both with their SaaS offering as well as their on-premise offerings that you can use yourself because they're open source, visit influxdata.com. My thanks to them for sponsoring this ridiculous podcast. Welcome to Screaming in the Cloud. I'm Corey Quinn. I'm joined this week by Cody Ogden, who, among other things, is the mortuary assistant at Killed by Google. That is killedbygoogle.com. Cody, welcome to the show. Thanks for having me, Corey. Well, thank you for what you do. For those who have never heard of it,
Starting point is 00:01:57 though, let's start at the beginning. What is Killed by Google? Killed by Google is an open source project that tracks just kind of the status of Google's product history and keeps track of current products and products in the future that may end up being deprecated or killed. It really drove home to me that when I first pulled the site up
Starting point is 00:02:18 months and months ago, where it has this counted list of all the various services that Google has announced an end-of-life date for. And maybe one or two are questionable on this, but the last time I counted, it was over 180, wasn't it? Yeah, I think we're up to 190 now. Which means that Google has announced more products that they are end-of-lifing than AWS has launched, period. Seems to be true. It's always interesting because Google has sort of built up this reputation now where whenever they announce an update on fill in a service here,
Starting point is 00:02:52 the immediate response from the entire universe is, ah, crap, they're turning that one off too. And whenever I make that observation on Twitter, I don't know if you've seen any of it, but I periodically get well actually to death by a whole bunch of Google fans. And, oh, that's not true. It's only consumer stuff that gets turned off. It's for the better, yada, yada, yada.
Starting point is 00:03:15 There's always the same lines that get trotted out. But I don't necessarily agree with the criticism in that it's building an expectation that when Google releases something, its days are inherently limited. So fun and jokes and poking large companies with sticks aside, where do you tend to fall on the Google has announced a thing? How long is it for this world spectrum? That's a great question. I think for me personally, I've grown much more skeptical about adopting, especially a piece of something that really helps me do something in my life, there's no guarantee it's going to be available to me down the road. The problem that I've always had is it does definitely color my opinion of the company. The notable starting point for a lot of this in most people's consciousness was Google Reader.
Starting point is 00:04:22 It was for those who weren't around then or weren't paying attention or simply have better things to worry about than shaking your fist angrily at something years old now, Google Reader burst onto the scene and more or less eviscerated an entire nascent industry of RSS aggregators because it did it so much better than the rest of these, and it was free. You could just shove all your various RSS feeds into Google Reader, and it was free. You could just shove all your various RSS feeds into Google Reader, and it was glorious. In the meantime, it also wound up eviscerating a decent portion of the market
Starting point is 00:04:52 for companies that were already playing in this space, but these things happen, and it was amazing, and I recommended it to people left and right, and I used it more or less for my entire news outlet. That was where all of the, I guess, things I cared about would show up. I would muscle memory, type it into any browser I was in idly when I was waiting for something else to show up. And then they announced that they were end of life-ing it. And there's some, I heard different stories about why. Some said that it was because it was running
Starting point is 00:05:23 on a bunch of legacy systems that once this was removed, they could finally turn them all off. Cool. The other was that they were building Google Plus as their new social network and wanted to clear the way with anything else that vaguely resembled a social network. Awesome. And so they announced this about six months in advance or so, and people built a few replacements that are mostly there. I use Feedly. Everyone else is using something different, but it's not the same. And that was the first indication I really had brought to my attention that suddenly this thing that I'd built my workflows around, I think that this thing that I built my digital life around wasn't guaranteed to be there in coming years. So anything I started using online should have a backup plan. And I started going
Starting point is 00:06:07 down that path pretty easily. And okay, now as a result, anything that I tend to use for the most part, I have at least an alternative, if not as good, will at least get the job done. And I do credit Google with helping teach that lesson, though I don't think that's the lesson they were trying to teach the world. What are your thoughts? Yeah, I mean, I think my experience was very similar. I was a Google Reader user myself. When it disappeared, I was, you know, very upset. I had invested a lot of time in really fine-tuning, you know, my setup in that one piece of software. And when that service just wasn't available to me anymore, I had to go searching out for alternatives. I mean, for me, as a developer, I really leaned into things that are more self-hosted. So I spun up my own kind of RSS aggregator that was like open source and
Starting point is 00:07:01 you could self-host yourself. And I've been using that kind of ever since just because I didn't want to take the chance that relying on another company that could be acquired or go under or just have their product shut down or make a pivot would affect me again with my fine-tuned set of news things that I want to have access to in the future. It's one of those stories where the, I think the old Bader-Meinhof effect is the term for it, where once you see something, you hear a new term or learn a new concept, suddenly you start seeing it everywhere. And, or the easy non-technical example would be, oh, if you're considering buying a particular make and model of car, suddenly you see them on the road everywhere when before you never noticed them. And once this started happening, I started seeing more and more products that Google had released or acquired suddenly being turned off with little to no warning.
Starting point is 00:07:54 And some of these mattered way less than others. One that I thought somewhat recently was interesting was their Hire by Google product. Do you care to tell that story? Sure. I mean, Hire was a pretty interesting product from an external standpoint. recently was interesting was their hire by Google product. Do you care to tell that story? Sure. I mean, hire was a pretty interesting product from an external standpoint. I mean, they'd really paired it. I mean, they're rightfully set to create products that are focused on enterprise users, especially for that small to medium business range, who can't afford to invest in those like large applicant tracking systems that are kind of
Starting point is 00:08:25 already available and they they were they were ready to disrupt that industry so they launched hired back in i'm gonna say like 2017 or 2018 maybe um and they quickly got a lot of the kind of early tech companies, the small startup tech companies on board, which of course creates word of mouth. And then they decided to shut it down. They announced a one year for their SLA. They announced that they would shut it down a year
Starting point is 00:08:57 from the 1st of September. So next year, 2020, it'll be going away. And I think that puts a lot of weird tastes in the mouth of people who may have been considering or still use Google's G Suite platform because those were heavily integrated pieces of software because they really combined G Suite into Hire to make it a product that really worked proactively
Starting point is 00:09:24 for that hiring process. And now they're forcing all these companies to, you know, find an alternative, figure something else out, go back to spreadsheets possibly. Yeah. And it was, it was not cheap either. This required some work for companies to integrate with. And once you went through the pain and hassle of doing this, suddenly whenever someone randomly would search your company name and then careers, boom, right there were all your job postings at the top of Google's organic search results, which is incredibly powerful for how most people look for jobs these days, but also kind of damning in that you're telling me that you can effectively get top placement above ads and still not find a way to make money out of this thing.
Starting point is 00:10:06 And it seems like it really cuts against a lot of their own stated value propositions. And then in turn, you have these companies who have paid the money for this, who've invested in it. And that really sort of takes the wind out of the counter argument of Google launches and kills consumer things all the time. And that's fine. But you absolutely can trust Google Cloud and anything enterprise-y
Starting point is 00:10:28 because it's always going to be here. Well, that's sort of a thing that was aimed solely at companies and look where we are. Yeah, I mean, I agree. And I mean, I think it's important to also realize that like the people who follow Google product launches they're probably not your average consumer they're probably more tech minded or they work in the industry or they work adjacent to the industry these are people that are going to be eventually making the decisions about what
Starting point is 00:10:56 platforms to adopt what what services to to buy into And building that reputation, especially at the enterprise level, but also at that kind of prosumer level, kind of, I don't know, it just feels like that opportunity is just being missed to build a decent reputation there. It is because you have to increasingly disambiguate between what is the product name that starts with the word Google that I can trust and build a business around versus what product starting with the word Google would I be a complete moron to trust will still be here five years from now? And the answer to that always presupposes that someone has an in-depth knowledge of Google's organizational structure. I don't. Yeah, same. It was interesting. I was preparing for this.
Starting point is 00:11:46 I was reading back through their letter to investors when they did their IPO. I found it really funny. One thing that they called out was that they want to think long-term, but then they quantified long-term as three to five years. And I found that interesting because the people who've kind of looked through this list and like run some interesting, you know, calculations on the data, you know, they found that the kind of average for those products is about four years. So I mean, if long term is four years, like I just think there's a disconnect between what Google might consider long term, as far as the tech world and what the rest of the world considers long term. I frequently said that multi-cloud is a stupid best practice, and I stand by that.
Starting point is 00:12:34 However, if your customers are in multiple clouds and you're a platform, you probably want to be where your customers are unless you enjoy turning down money. An example of that is InfluxData. InfluxData are the manufacturers of InfluxDB, a time series database that you'll use if you need a time series database. Check them out at InfluxDB.com. Personally, if I take a look over at the AWS side and do a comparison here, there's a very clear differentiating line where AWS will announce something that is absolutely ridiculous. It's
Starting point is 00:13:13 Looney Tunes come to life. And I may think it's ridiculous. I may think it has no market. I may not understand its target market, but I would not hesitate to build a business on top of it simply because they don't turn things off full stop. And on the consumer side, sure, the Amazon Fire Phone. For the longest time, I would be getting boxes shipped to me by Amazon Prime, and they had the Fire Phone tape on it. And it was always this moment of sheer terror. Oh no, has someone sent me a Fire Phone? I don't want one of those before they blissfully killed the thing they don't do that over in the aws world they'll call something classic like ec2 classic or elb classic which means it's not getting new features but you can still use it and simple db was one of their first products you can still use that you probably don't want to, but you can.
Starting point is 00:14:08 So as a result, based on the 10 years and change of history with them releasing products, I wouldn't hesitate to believe that anything under the AWS umbrella is going to be something I can trust with my business. I don't have that certainty with Google in the least. Yeah, I think, yeah, I just think that timeline is such a weird disconnect for even consumers, but enterprise too, like that cloud computing as well. That timeline of what is actually long-term is either not clear to people in their pitch, or it's just fundamentally a culture difference between what they consider long-term
Starting point is 00:14:45 versus what everyone else would expect long-term to be. Oh yeah. And reputation matters so much in this space. People don't realize this, but AWS and GCP have the same equivalent contractual requirements around notice before deprecating a product. And that's fascinating when you're trying to do an apples to apples comparison, but here in the real world, they certainly don't have the same mindshare equivalent thereof. I know theoretically, yes, Amazon could decide to turn off AWS in a year, but they're not doing that. I don't have, I don't see any future where they would. Yeah. I mean, I, I can't speak enough to AWS to really speak well to it,
Starting point is 00:15:26 but there's definitely a difference in how the reputation between those two really plays out. Conversely, if you were to sit here and ask me, do I think that GCP is going to be turned off when Google loses interest? My response to that is, of course, no. I don't believe that's true. I think they're going to be in this for the long haul. But imagine for a second that suddenly they did. Suddenly there's an announcement later today after we're done recording where they're announcing a three-year sunset period where GCP is getting turned off. Customers would be up in arms and screaming on Twitter because that's what customers do. But the response would be, it was a Google product. What did you expect?
Starting point is 00:16:12 And that right there is the problem. Wholeheartedly agree. Like that is the exact reaction would be, what did you expect? Just look at the history. Look at how they've treated their products in the past. Look at how they just cut them out. They said, we're done. We're bored with it.
Starting point is 00:16:26 We don't want to do this anymore. And yeah, I mean, the reaction from all spheres would be the same thing. It's, you know, it's no surprise almost at this point. At the time of this recording, they recently announced that they were acquiring Fitbit, which, okay, great. Fitbit has been sort of struggling for a while, but you want to place any bets as to how long Fitbit is going to be around? If someone's listening to this podcast in three years, will the term Fitbit mean anything to them? Yeah. I mean, it's funny. I mean, if we look at the history of hardware acquisitions from them, like Nest, and I think before that
Starting point is 00:17:08 they had to revolve, which were all kind of Internet of Things acquisitions, that history doesn't look bright. Or at least the future doesn't look bright for Fitbit, both as a brand and as a product. And I mean, for consumers, I mean, they may end up with hardware that just doesn't work anymore. And there was a similar story years ago where Sony installed a rootkit on various CDs, audio CDs that people would buy that would effectively subvert their computers to make sure they weren't copying these things. And that caused a massive kerfuffle. And I went a decade after that without buying Sony equipment. And whenever I talked to people about
Starting point is 00:17:56 that, they looked at me like I was nuts because, well, that was clearly a radically different division of Sony than the one that makes cameras and laptops. And I agree with them. They're right. However, the reason that companies do these acquisitions and have all these different divisions is that one division that has a particular product line generates good feelings toward that. And companies want those good feelings to convey to other aspects. It's not just good feelings that do this. I almost wonder as a result if there would be a consumer brand for Google and an enterprise brand for Google that they could launch to start differentiating this
Starting point is 00:18:34 and get away from some of the user pain that folks have had every time something like Inbox gets turned off. I mean, I definitely think that they have, at least Google has kind of already started this with how they've structured alphabet. You're starting to see a lot less. I mean, recently they announced touringbird.com. It was like a travel informational point of interest site that tried to help like get you deals and information about you know places of interest they just announced that it was torn down i mean i had never heard of this before i didn't even know it was a google
Starting point is 00:19:12 brand apparently it was you know under this umbrella of something called area 120 which is another company that's under the umbrella of alphabetphabet, not of Google. But now that technology is being absorbed into Google. So I mean, yeah, I mean, it's kind of interesting the way they're structuring things now is almost to obfuscate the impact or that kind of, or protect or kind of create a barrier for that reputation so that they can't just keep contributing to that one brand that's most well-known. One thing that's strange to me is that I don't see people getting confused by Amazon doing the exact same thing, where they have early versions of Echoes
Starting point is 00:19:57 and a bunch of devices that they put out and then wind up replacing and sunsetting, as they do with many consumer electronics. The only time I've ever heard someone talk about, well, what does that mean for AWS, inherently comes down to someone trying to defend Google and making that point. But I see zero customer confusion about that. I think the interesting thing that might contribute to that is just the approach to the customer experience that Amazon does versus Google does too. I mean, even at a consumer level, you know, Amazon is really focused on making sure they have great customer service. You can reach a real person and actually talk to them
Starting point is 00:20:38 at Amazon. Not necessarily AWS, unless you want to pay a lot of money, but as just a normal everyday buying an Echo customer, I can get a hold of somebody at Amazon. At Google, I mean, it's not been my experience with any Google product I've ever owned, and especially not with any of their software services. It's always an empty form that never gets a reply or a help article is all you can really find that doesn't actually solve your problem. So I think that there might be that, at least at a consumer level, this kind of perceived idea that Amazon really does have that approach to customer service that makes the product more valuable because they provide that. Whereas Google, it's like, here's a product. That's all we got for you.
Starting point is 00:21:29 It also feels like Google has so much of their revenue coming from ads that anything that doesn't directly lead to ad sales means that it's just a hobby project for them, that they don't really see any downside to turning off on a whim when the person who championed it moved on or got promoted. It really does feel like there's something systemically strange with the culture. It's funny that you mentioned that because I've read accounts from people who claim to be ex-Googlers on sites like Hacker News, on other people who've recounted these same stories that it's, they feel like part of the issue with, especially the consumer product shutdown is that the promotion cycle internally is so focused on launching and not maintaining. So you launch a product and you get a promotion and you launch
Starting point is 00:22:18 product and you get a promotion. So the person who kind of is supposed to be like the lead advocate for whatever the product is, like once they get that promotion, they move on. There's no one else to take that helm. And, you know, this has been recounted in multiple different places that I've read online. But it's, yeah, I mean, it could definitely be at least partly driven by that kind of internal promotion culture. Yeah, it's really one of those unfortunate areas. I mean, we saw this at Google Next, where they're talking about things from all across the enterprise side of the business. And then they put the Google Voice logo up on the slide and the entire room just falls silent. And they mentioned the rolling into G Suite
Starting point is 00:23:00 and there was a little bit of like scattered applause, like, oh, we thought we'd get a better response to that. Yeah, because we thought you were about to kill it on stage in front of everyone. It's at this point, whenever Google brings up a service that's been seemingly neglected for a long time, it's never good news. I'm cautiously optimistic about this. Yeah, I mean, I think Google Voice was absolutely a great example of that. There was it. It got left behind.
Starting point is 00:23:27 I mean, it had one of the oldest iOS updates on an Apple user. So it had one of the oldest iOS updates, had some really old design technique on it. It had been updated for like almost a year or so before they finally gave it a refresh. And then it just went dormant again and didn't receive any updates and then yeah when they rolled it into G Suite people were like honestly surprised like the the momentum behind that pivot almost with with Google Voice it kind of coincided with them bringing Project Fi out of Project Fi and turning it into Google Fi. And it felt like Google had ignored Google Voice for so long.
Starting point is 00:24:12 And that's typically their MO. They ignore the app until they're just like, finally, yeah, let's just be done with it and kill it. And I think that there's an opportunity there, though, where they can start being more transparent with roadmaps around the products that they put out. Because that's not only going to make sense to the pro consumer levels who kind of work in industry and understand the product lifecycle, but also really be more transparent with consumers so they can make more informed choices.
Starting point is 00:24:40 And that's really what it comes down to, is just telling customers what to expect and then meeting those expectations. Now the expectation is they release something, who knows if it'll still be here in a week. In fact, a lot of that iOS refresh update wasn't even intentional. They were using internal certificates to do a few things with research groups that Apple didn't allow and revoked the certificate. So they had to rebuild their applications to get them up and working again with the latest version of Xcode, which forced compatibility with modern iOS devices. So suddenly everything, the Google Docs suite of applications, suddenly were fitting the screen
Starting point is 00:25:16 on some of the newer iPads. And the fact that that's what it takes to get them to update their stuff when it's just push the button and republish it is nuts to me it feels like google has been engaged in an ongoing war against its own users for far too long well i mean it's not even necessarily that they're like anti-user it's just like it feels like there's not a a culture emphasis on maintenance is just as important as new product. You know, maintaining a good product that we know people use isn't as important as creating something new or launching something new or getting something new out there to try to see what hits the wall and sticks. And I think that's a really, I mean, it's a difficult thing because, you know, like you said earlier, the majority of their revenue is coming from advertising.
Starting point is 00:26:11 And they have the privilege of almost not having to care because it doesn't undermine their bottom line. It must be nice. But at some point, public sentiment starts to turn against them. And this is the biggest damage that they're doing. I mean, a lot of their uptake and their cool factor came from people who were early adopters who were driving their friends and family to use these things.
Starting point is 00:26:38 So in some cases, some extreme cases, you start seeing things such as you get your parents on board with something, you get your non-technical relatives on board with other things, and suddenly Google takes it away, Inbox being a good example of this. What are the odds that you're going to recommend a Google product again to those folks? Because suddenly you're the jerk who got them into a thing that's now being turned off and ripped away from out from under them. It's not a great feeling to be one of Google's most devout fans when it increasingly makes you look like an idiot to your social
Starting point is 00:27:09 circles for having believed in them. Yeah. And I mean, I think that goes back again to that, that messaging piece towards, you know, whoever's using their product. You know, I said earlier, you know, that's the techies, the people who are around the tech industry and who are interested in new technology that want to try the new stuff and want to really dig in and figure out how it works and what it can really do for them, right? But if they don't have a clear message on, hey, this is just an experiment, which I don't think it's really going to be long-term, they're going to make those recommendations to other people, get them involved, just like you said, and then it's on them when something, when they kill it. And that's the interesting part, is at some point, it feels like we're all
Starting point is 00:27:52 being Google's beta testers, for lack of a better term. They're even blurring the line now between, well, if you're not paying for it, you can't expect it to be around next month. Well, yeah, except the messaging has always been, this is great. You should use it. And then suddenly it's not. But I mean, if we look at the history of even their most successful projects, like Gmail, I mean, Gmail was in quote unquote beta for years and it was never guaranteed to be an actual thing right now today. But how's that, I think the bigger question was, has that impression of what beta is changed
Starting point is 00:28:28 throughout the years? And I think that, and also is Google driving that impression of what beta actually means? Funny you mentioned Gmail. About a year or so ago, there was an announcement about G Suite now was going to have a price hike from $5 per month per user to six. And the internet lost its collective minds over this, but I was thrilled because I'd rather
Starting point is 00:28:49 you charge me more for a service that costs you money to run than turning it off out from under me. Can you imagine having to replace Gmail for effectively every company that's been using it? And the hell of it is, I'm not entirely sure I'd put it past google at this point to try it yeah i mean i think that yeah i mean it's uh yeah it was crazy like the first time they've raised that price for you know basically since g suite's inception um and it it's almost like counter to the argument a lot of people make about some of these google products that get killed is well i mean you weren't paying for it right like that somehow makes it okay yeah but you can't have it both ways like you can't um not you can't pay you know always have the same price and never see
Starting point is 00:29:37 that price increase even though you're getting a lot more valuable value now out of the services that they're offering you and as part of g suite so i I mean, it's, I don't know, it's so, it's such a silly, such a silly thing to think about because people do bring up the argument all the time. Well, name me something that people paid for that Google killed and are people paid. Yeah. People, sorry. Name me something that people paid for that Google ended up killing.
Starting point is 00:30:07 And you can just go down the list and you can find things that people paid pretty significant amounts of money to get their hands on. And then Google turned around and shut it down. Or like the Google Maps API changes where, surprise, your bill is now going to be 14 times what it was before for the same usage pattern. That tends to break the implicit contract you have with customers. Yeah, absolutely. As we record this, it is November 4th, 2019. What do you think the next service to die is going to be? I get this question a lot. I never like to speculate too much because, I mean, at the end of the day, I want to be an optimist about it. Like I want the products that they create, they can really be foundationally changing for people, um, and really improve their lives through technology to be great to work out for them.
Starting point is 00:31:00 But I, I, at this point, I, I'm not even sure. You also don't want to give them ideas. That too. I think that could be a very good take on it. So have you gotten any feedback on the killedbygoogle.com site? Feedback from? Oh, the entire internet. Let's start there.
Starting point is 00:31:17 I imagine Google would not go on record unless it was with a cease and desist, but what are they going to do? It's all true. Yeah, I mean, there's been tons of feedback it's i think i first described the feedback is that people kind of take away what they want from killed by google they either are you know awestruck i can't believe google has killed this many things some people visit they want to just take a trip down memory lane it's
Starting point is 00:31:44 nothing they can do. These are cool things that I got to use at one point. Some people look at this and they're like, yeah, this is why we need better policies like internally for our company about data retention. Like how can we export things that people are doing on Google's platforms to make sure we have an archive for our company or for our team or whatever. And then some people have a lot of criticism. I mean, they're like, well, I mean, like I said before, well, people didn't pay for these products. So, you know, it's Google's right to just shut them down when they want to.
Starting point is 00:32:15 And I mean, I accept that criticism. I think it's important more that we have that discussion about adopting technology into our lives that may not last forever and what that looks like for people from the consumer level to the enterprise level. Yeah. It's easy to turn this into a roasting Google story, but in practice, it does inspire longer-term thinking around some of these things. I think that there's a strong balance that needs to be struck. There are a lot of services that people found near and dear to their hearts that aren't there anymore. They had to massively shift their own workflows in a timeline not of their own choosing.
Starting point is 00:32:53 And that stuff leaves scars. Now, I have to ask, I know it's hosted on GitHub, but are there any Google services that could be killed that suddenly you have to redo how killedbygoogle.com is hosted? Yes, potentially. So Kill Guide Google is hosted on Netlify at the moment, and they use a quote-unquote multi-cloud platform, which as far as I can see, they're using at least Google Cloud Platform for a lot of the static sites that they host. So, I mean, my site is literally hosted on a Google server, which I find kind of funny and ironic,
Starting point is 00:33:33 but at least I've Netlify to back me up and move me over to AWS if I ever need to. It's a transition. I have the sneaking suspicion in some cases, not a question of if, but when. Yeah, no, I can't say I disagree. So other than killedbygoogle.com, where can people find you if they want to hear what you have to say about this and other topics? Well, they can find me on Twitter at killedbygoogle. They can also find me on my own personal website, codyogden.com.
Starting point is 00:34:03 And we'll throw links to both of those in the show notes. Cody, thank you so much for taking the time to speak with me today. Yeah, absolutely. Thank you for having me. Of course. Cody Ogden, mortuary assistant at Killed by Google. I'm Corey Quinn, and this is Screaming in the Cloud. If you've enjoyed this episode, please leave it a five-star review on iTunes. If you've hated this episode, please leave it a five-star review on iTunes. If you've hated this episode, please leave it a 5-star review on iTunes. sold. This has been a HumblePod production. Stay humble.

There aren't comments yet for this episode. Click on any sentence in the transcript to leave a comment.