Screaming in the Cloud - Serverless Evangelism with Farrah Campbell

Episode Date: March 18, 2020

About Farrah CampbellAfter 10 years of working in healthcare management, a serendipitous 20-minute car ride with Kara Swisher inspired Farrah to make the jump into technology. She has worked at multiple startups in many different capacities, eventually working her way to being the Ecosystems Director for Stackery in Portland, Oregon.As the Stackery Ecosystems Director, Farrah has managed the Stackery relationship with AWS including Stackery as an Advanced Technology Partner, achieving the AWS DevOps Competency, a launch partner for Lambda Layers and is an AWS Serverless Hero. Farrah has cultivated the serverless community as an organizer of Portland Serverless Days, the Portland Serverless Meetup, along with numerous serverless workshops and the Portland tech community events from Techfest to bringing multiple luminaries to Portland.Links Referenced AD: DigitalOceanAD: DataStaxPortland Serverless DaysPortland Serverless Meetup Twitter: @FarrahC32LinkedIn: https://www.linkedin.com/in/farrahcampbell/Email: [e-mail] site: https://medium.com/@FarrahC32Company site: www.stackery.io

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. And this is important to me. No billing surprises. With simple, predictable pricing that's flat across 12 global data center regions and a UX developers around the world love, you can control your cloud infrastructure costs and have more time for your team to focus on growing your business.

See what businesses are building on DigitalOcean and get started for free at do.co slash screaming. That's do.co slash screaming. And my thanks to DigitalOcean for their continuing support of this ridiculous podcast. Welcome to Screaming in the Cloud. I'm Corey Quinn. I'm joined this week by Farah Campbell, Ecosystems Director at Stackery. Farah, welcome to the show. Hey, thanks, Corey. Thanks for having me. So let's start at the beginning with what is an Ecosystems Director?

Well, my job basically is to connect with people across AWS, the serverless ecosystem, so that we can increase more serverless adoption, making connections with partners, customers, community members, and then strategic partners like AWS. So it sounds like you're viewing this as something that is distinct from, effectively, community. Where's the dividing line? That's a good question. I think right now it encompasses both. I mean, it's a new technology. Well, it's not necessarily so new now. But I think that I feel like I kind of represent the entire community, but also our customers and our partners are part of that community.

I need to be wherever they're at, focusing on making sure that we're in this together. So one thing you mentioned a minute ago was that you're focusing on serverless and then in almost the same breath, you tied it back to AWS. Do you view serverless as being primarily AWS driven? Is that your area of focus? Is that just shorthand because AWS is such a, I guess, gargantuan presence in the market that it's easier to contextualize it there. I mean, where do you stand on that? Well, I guess I should like back up a little bit and say, you know, working at Stackery, Stackery is definitely everything we do is built on top of AWS. We speed up the application development delivery, helping teams to securely deploy and build these serverless applications. At this moment, we do not have any,

we don't have a system that works with Azure or Cloud Run. And so when I talk about serverless, I guess I talk about the people that are right in front of me. Oh, I'm right there with you. You may want to back away from that. I want to charge directly into it. And the reason that I fix AWS bills is where the big expensive problems are. When I'm doing serverless development work on a bunch of different ridiculous things that I then throw up on Twitter for mockery, I find that I'm always tripping over AWS things in the wild. When I just Google

serverless and then whatever I want to do, URL shortener, for example, I'm not seeing a whole lot of options that aren't built on top of AWS. For better or for worse, in my experience, that is where the community tends to circle around. Even when I step outside of my, I guess, bubble, I'm still seeing that AWS is definitely carrying the torch in this space. Yeah, I think so. But there's a lot of good people that are doing good work at Microsoft and Google that actually I wish I could work more with. We're just not there yet. Oh, of course. I'd even take it a step further and invoke the great Satan. In this case, the Oracle folks, when they wound up acquiring a lot of the iron.io people,

they had a fantastic technology and a fantastic story, and it's just overshadowed by Oracle's business practices. So for better or worse, I don't get to play with that stuff in any meaningful way. Yeah, it's always about the, when I talk about companies and I like, I guess, throwing muck, it's never about the individual people. It's about the corporate cultures by and large. I sometimes do a poor job of articulating that, but, oh, I work at a company he hates, therefore he must hate me is never accurate. It tends to not, separating the person from the employer is challenging at times, but I sometimes feel like I stumble over doing that well.

I think you do a pretty good job. I've never felt like you were targeting a specific person. I mean, I think that when you have, it's always to give them like happy birthday videos or something cool. Yeah. The only exception to that rule that I have is Larry Ell have, it's always to give them like happy birthday videos or something cool. Yeah, the only exception to that rule that I have is Larry Ellison because he's not people. He just thinks he's people and he has no friends or people who love him to take offense on his behalf. So therefore, it's a free target and it's never punching down. Funny thing about Larry Ellison in my past insurance life when I was a broker here in Portland, Oregon. His ex-wife, Barb Ellison, who owns a, it's called Wild Turkey Farm, which is like a horse

studying ranch. And she was one of my clients. That is amazing. And thank you for naming her because it is Larry Ellison. I would have to ask you which ex-wife. There are three to choose from. But I digress. Sorry, this is not a dump on Larry

episode, though it somehow turned into that. But all right, moving on. So how did you get to the place you are? I don't think I've ever been talking to companies who are looking to hire and they say, you know, what we really need is an ecosystems director. That feels like a role that emerges rather than something that is actively recruited for. And maybe that's just because I'm not looking in the right places, but how did you get where you are? Well, how did I get where I am? Well, Nate created this role for me here at Stackery. I had known him from the community. I've worked at a number of startups here in Portland. In fact, actually, I got my start because when I moved to Portland, I knew I wanted to do something different. And I was trying to get a job. It took me about, well, for a year, I applied, got no responses.

I ended up volunteering at a conference called TechFest Northwest. And I ended up being the speaker handler. Well, my first job was to pick up Kara Swisher. I didn't have any idea who she was. And they just told me she was a very important person. Anyhow, I was super incredibly nervous that entire time. But it was actually pretty amazing because I had the opportunity to talk to her. And she actually inspired me to quit my full-time job and take this startup that had got in front of my face, which was four hours a week. That is a heck of an origin story.

I feel like Kara, based on my impression or whatever I met her myself, would argue that everyone's important. But she's one of those inspirational people that I really love just seeing almost everything one of those inspirational people that I really love just seeing almost everything that she does. Even when I don't agree with her, I find, I just love the way that she frames and does things. Yeah. She's pretty awesome. I mean, she even sent me the, uh, the Steve jobs commencement address and told me to watch that. And then

she's like, next time I hear from you, I want to know what you've done to try to get into tech. And like, it was like the next day I had this offer. It was pretty crazy. And I'm incredibly thankful to her for that. She's not that lady behind the glasses that everybody thinks. No, it's, it's very clear just from following her on Twitter that she has a definite personality that she does not bother to hide, which from my personal perspective is just something that I adore. I spent my first part of my career trying and failing to hide my personality as anyone who'd ever met me can attest. And finally, this thing turned into me embracing my crappy excuse for a personality. And here we are. I scream into microphones about cloud computing. I mean, I would say you have a pretty good personality, Corey. I really love that picture

with the motorcycle helmet on the horse. Yes. The dating profile photo I had when I met my wife. So she knew exactly what she was getting into 11 years ago now. I mean, that takes a lot of personality. That was an experience. Let's put it that way. It's been, uh, I tend to be of nothing else, refreshingly direct. So something else has happened recently that I wanted to get your thoughts on, or as much as you can tell us, you've become an AWS serverless hero and hero, of course, is the name of their program, which I've always found to be kind of weird. It feels like hero or entrepreneur or a few other things are things other people call you calling yourself. That sounds weird. Thought leader is similar in that space, but I'm curious as to what it was like

to first become a hero. Secondly, what is the, what is the hero? What does being a hero mean? So what does a being hero mean? Um, actually like like serial heroes are early adopters, spirited pioneers of the serverless ecosystem. I think that the announcement of me being a serverless hero was pretty, I thought it was impactful because it shows that, you know, I guess experts in the field, that it requires more than just the ability to code. It requires the ability to have communication and to lead with empathy. And I think it's important that they're helping to change the way that we're looking at leaders in our industry. I love the terminology, if for no other reason than I heard that they had an AWS Heroes program, and I immediately set out to become an AWS villain instead. And I've mostly gotten there. If you look at some of the things that I've celebrated, even on this podcast, I've had a couple of, as I term them, code terrorists who have shown up and demonstrated horrifying architectures and patterns to achieve reasonable outcomes. But by and large, I find that the folks in the HERO program tend to be, at least from

the outside, never having been one myself, those are the folks that we hear an awful lot from in their respective subject areas. They more or less are the torchbearers for the rest of us who are stumbling our way more or less blindly through a lot of these things. And when, when you have people who can be held up and, and demonstrated as this is one possible way to do it, here's someone willing to tell stories about this, it becomes incredibly compelling. And for whatever reason, those are folks who can tell stories with a greater degree of honesty and transparency than you'll often get from either a marketing apparatus or a developer advocacy or developer relations program because none of these folks work for AWS.

They're all community members or work at other companies in the space. But no one is carrying a quota from Amazon of you must get at least X people to sign up or you're not a hero anymore. No, in fact, I haven't seen any requirements at all, to be honest. I mean, I wasn't setting out to be a hero. I never, ever imagined that I actually would, just because if you looked at everybody's profiles, everybody's written books or had all these open source contributions, tons of medium posts, and it just had a lot more experience than me when it comes to building applications. I guess it reminds me of having that serverless mindset and focusing on what matters. And I feel like that's kind of what my career has been since I've gotten to

tech. My life was always had to be like that. I had to focus on what mattered just because I was a single mom. But it's pretty powerful when you can start to translate that into your work and see growth and affect change. Can you tell me a little bit more about that? I mean, having a single child right now with my spouse and I, that seems like an impossible amount of work. I can't fathom what it would be like having to do that alone. But how does that map directly into the work side? From very early on, I was the queen of making poor decisions when I was younger.

I ended up divorced and had two kids and I was 24 and on my own in a place I didn't have any family near me. And I guess like my relationships were suffering too with my family, but I had two little guys to take care of. And so when it came down to it, like everything I did, the time that I had, I needed to be focusing on something that mattered. And so like I even think about that even like to, you know, day to day being a single mom, if I have a number of things to do, if I can like outsource like housework or picking up groceries, whatever it is, like, you know, time is important. You know, we didn't make sure that

we didn't have a lot of TV, wanted to make sure that, you know, we had a lot of face to face time in those moments that I did have that time with the boys. And I think taking that and like applying that into like your work life, there's a lot of stuff that happens in our day-to-day that just noise. And if I take the time out of, you know, if I take that time to focus on that, I'm now wasting time on things that don't matter and things that actually might like take me to a place that's actually not productive. I guess that's how I would say it translates from like being a mom, being like, you know, applying that mindset of focusing on what matters in your life and then translating that over to your work. Did any of that make sense or am I just rambling?

No, it absolutely does. There's a tremendous amount of, I guess, gatekeeping in the infrastructure space of, oh, you've only been doing this for a couple of years. Well, unless you were doing this back in the Solaris days of big iron and the rest, well, you're not really involved in the infrastructure world, which is first, nonsense. And secondly, not hugely relevant most days when you're talking about getting something out the door. That's sort of the entire premise of serverless is the stuff that everyone has to learn. Well, a lot of that is now handled for you. It's sure there are times where it's very useful to have specialist insight into how

a lot of those subsystems work, but you maybe don't need that to build a quick API that does something that demonstrates business value. No. In fact, for somebody, I mean, for me, I mean, I created a web hook. I authenticated with Google and I was having to look for specific information through my emails that would drop into a Google sheet. And then I could then act on that. I've then built like a language translator app with my coworker, Danielle. Um, I just created my own website, uh, you know, built all on top of AWS services using like route 53 cloud front, uh, certificate manager S3 and like using the Lambda function to deploy that. Like, and I'm doing this stuff by reading these tutorials and in all honesty, I have

really no idea what these things are doing. Like route 53. Um, I have really no idea what these things are doing. Like Route 53. I maintain it's a database. I'm told it's not, but I don't even care. So, but I can get these things all up and working. So one of the things that I hope to help people do is just take a step and like forget about all the things that you know we can we'll bring that we'll bring that back later but like forget all the things that you think you know and then just go try it and like see what happens like you'd be amazed that like

with all the information that they must have after building systems how they can apply it into building new systems what they would be able to do. This episode is sponsored in part by DataStax. The NoSQL event of the year is DataStax Accelerate in San Diego this May from the 11th through the 13th. I've given a talk previously called The Myth of Multicloud, and it's time for me to revisit that with a SQL, which is funny given that it's a no SQL conference, but there you have it. To learn more, visit datastacks.com. That's D-A-T-A-S-T-A-X.com. And I hope to see you in San Diego this May. I think part of the key to this whole, I guess,

unlocking the power of serverless is it's not even that old. So if you've been using these technologies for 20 minutes, congratulations. You're one of the elder statespeople who has been using this for a long time. It's hard to remember sometimes, but 15 years ago, there was no such thing as cloud in any real sense. So everyone who's been doing this since the beginning, well, yeah, they don't necessarily need to be that old to get there. No, you don't. And I'm like shouting this from the rooftops because there's like a moment right now to come up and level up all of your skills. Like that's what everybody is doing. Everybody else is going to be doing it, you know, in the next couple of years, three to five years later. And if you do it now, it sets you up in a pretty good place. You just have to be doing it in the next couple of years, three to five years later.

And if you do it now, it sets you up in a pretty good place. You just have to be willing to put in the work. Oh, yeah. And there's always time to go back and learn the underlying things that you need when you need them. Like, well, sure, using Lambda and API Gateway, and that's fine for you right now, but that's not going to be economical in scale once you wind up with 8 million users in a typical month. Oh, heaven, seems to me that might come with some other benefits where, huh, I can afford the time or the resources to delve more deeply into that arena when I need to. But optimizing in advance of something like that, you're almost never going to have that happen. Why bother? Yeah. And I think a lot of times you hear about like people just try to like want to

rework the same things that they've already done or just having a like a preconceived idea about why something won't work and they've tried it in the past or uh they had used it for some part of the application that didn't work or maybe they were on a completely different team like that doesn't matter like doesn't mean it doesn't work for anything else ever again. There could be all kinds of factors that, you know, uh, were a part of the reason why it didn't work at that time. Um, but anyhow, uh, I think, uh, I think a can do attitude can, can enable a lot specifically for developers, uh, working in a serverless, uh, uh, ecosystem. Something I've learned about serverless is that I've been using it for a couple of years for different things.

And I was working on a system the other day, and my immediate response was, this is awful. Whoever wrote this obviously had no idea how best practices are supposed to work. There's at least 16 errors I can see on this. What moron did this? And of course, I whipped out get blame and of course the answer was me and at which point I just quietly fixed it up and there was no need for me to bring that story up any further

but it always seems like no matter what the tool is and how perfect it can be you can always either first learn new things about it and makes the person you were yesterday look a little bit less bright than the person you are today. And secondly, any tool can be used or misused. I mean, look at me using route 53 as a database. It's a recurring joke for a reason in that it's something you can do, but probably shouldn't, but it could actually be forced into service as the, as I wind up

evolving that joke forward, you, You can misuse anything, and that doesn't mean the tool itself is bad. It just means the architecture is more than a little bizarre. I at least try to provide a positive example whenever I bring that up these days, and sometimes I forget to do it, but every once in a while I pay off my guilt for an entire generation of people listening to this who have now built CMDBs inside of DNS, but I at least hope that people are taking the right lesson from these things. Yeah, no, I actually kind of like this, this conversation kind of like, kind of made me think about my role a little bit. Because I started thinking about like,

when we think about somebody that's like evangelizing, or even like the hero program, when we think about evangelizing a new technology we we tend to think about like the cool tricks uh the new features uh the integrations but i actually like think about like evangelism is is much more about that it's you know you have to gain trust from the people that you're talking to you have to inspire them them and then support them, make them want to follow and to be a part of what you're doing. Part of what I think is so interesting about all of this

is that everyone winds up in their own silos. And we see this with communities in a lot of different ways, but look at what you're doing. You said at one point you were the queen of poor decisions. Well, now you're currently an organizer for Portland Serverless Days. You help run the Portland Serverless Meetup. You do a bunch of serverless workshops and you were doing a bunch of other tech fest things as well. That's an awful lot of volunteer work, which doesn't, I guess, directly tie back to, for most companies anyway, I don't know how Stackery is structured internally,

but it doesn't confer any direct benefit immediately to the company. That's, you're effectively giving an awful lot of yourself to the community. Yeah. I mean, I, I don't know that I know how to do it any other way, to be honest. When I talk about bad decisions, this is like, I was like the queen of negativity and everything around me is like something wasn't going right. You know, it was, I was the queen of negativity and everything around me is like something wasn't going right. You know, it was I was the queen of blame and victimizing myself. And it's been pretty amazing to see like what my life has been like when I stopped that, you know, and I was like, again, like that happened when I entered into tech. And I'm like, I'm only focusing on what matters here.

And it's it's amazing how like what a better place I am with my career, what a better place I am with how I feel about myself, with my friends, with my kids. It's the idea of bringing your whole self to work. Yeah. For good or for better or for worse, I bring my whole self to work. Given that you're involved in all these different things and talking to all these different folks about various aspects of it, I have to ask, what do you think right now is being the most misunderstood about serverless? Serverless, it's a lot more than Lambda or Knative. It's a mindset. It's an innovation strategy for enterprises.

But I also think that the technical aspects of serverless are important. But I think that there's like this like a paradigm shift in engineering and the work that has generated so many tech careers is now hidden behind this glowing, growing menu of cloud services. And I feel like that there's like this host of fears and then like a focus on negativity instead of a focus of, you know, how to be involved and, you know, to start modernizing these systems. fantastic approach for greenfield development of new experiments. The other is that the exact opposite, where this is perfect for modernizing legacy things. And I go back and forth as to which it's better fit for. I guess starting to come away with the idea that it may very well may be perfect for both use cases, depending upon other constraints. I think that is totally true. And it doesn't have to be one or the other. It can be used with containers. It can be used with on-prem solutions. I don't even know the old ways, actually, of building all these applications, to be honest with you. But serverless is not like an end-for-all. Everything has to be serverless. It's something that I think that companies are striving to get to. And it's, again, like I see it more of like the way you're building applications.

Out of curiosity, is Jamstack tied closely to the serverless movement? I keep hearing things about it and I thought it was something one company was doing and now I'm not entirely even sure what it is. Have you come across that at all? So Jamstack is, I think it's like marketers that I think that a lot of them are using serverless. I actually haven't been a part of any of their meetups, but we did actually host one here at Stackery, I think like a year ago. And I know a lot of great people in the space like, you know, Jason, I think he works at like Netlify now. I can't remember what his last name is, but he lives in Portland. But I think that marketers are leveraging the power of serverless.

I mean, if I think about it from how Stackery is using it, I can run my own A-B tests by adding in new functions to a usage event for trigger that our team built out. I don't need to bother anybody from our engineering team to get that done. Yeah. A lot of times I'll start to see people arguing against the use of managed services or SaaS platforms of, oh, that's not real serverless. I'm trying to solve a business problem here, not strain for ideological purity. And I tend to get relatively fed up relatively quickly with folks who tend to let the, I guess, religious movement that they're

trying to embrace, for better or worse, overtake the actual business value the entire thing is designed to deliver for customers. Totally. Totally. I see like, it's like a technological goal, you know, like for all these vendors to start deliver hosting and computer power to their customers. Maybe one day we'll call it something else because the name just doesn't make sense. That's the problem is it's easy to sit here and cast aspersions on various names of things. I mean, Lord knows I do that enough with AWS launches. But naming things, it turns out, is super hard. It turns out also that naming things is super important when you're setting up your environments, when you're installing certificate tokens on your computer, because you need to be able to figure out what those are later. And default and dev and then one that just has a number isn't helpful.

These are all things that I learned the last week, so I thought I would share. And typos, of course, are always fun and things that matter. Computers, extraordinarily literal to a fault. Naming this seems to be a completely hard thing in technology, period. No matter if it's setting up your environments, keeping your tokens, knowing what AWS accounts you're building and naming the services. So what is Route 53, by the way? Managed DNS. That's all it is. It's effectively the internet's phone book, how it converts www.twitterforpets.com into an IP address. One, two, three, four. How does one use that for a, I can't stop thinking about you using it as a database

and because like nowhere in there, nowhere when I was setting anything up in there, did it look like it could be used for that? Ah, great question. You can use text records or TXT records that you have arbitrary strings up to, I want to say 4K. I haven't tested the limits of my database lately. And then you can just query it with a standard DNS query

and it returns the value. You teach your code to ask the question through DNS, take the response, and do something with it. And you've built, fundamentally, what is a database in its purest sense. Now, people are going to send me letters over that description, but I'll take it. And it's not the best service for the job. I mean, if you want to use a key value store that can scale as

designed for this, something like DynamoDB makes an awful lot of sense. But you can misuse DNS this way. Well, we did talk about people misusing technologies earlier. And I don't think that's going to stop anytime soon. And I don't think the current generation of serverless proponents and detractors invented the concept for better or worse. Well, maybe Alex DeBree can help you. We can get that migrated to DynamoDB. I heard he's really good with it. Absolutely. There's got to be some sort of weird failover between DynamoDB and Route 53 simultaneously.

So if people want to wind up hearing more about what you have to say, where can they find you? You can find me on Twitter. I am at FarrahC32. You can find me on LinkedIn and then you can always find me by email. I'm just Farrah at Stackery.io.

Excellent. Farrah, thank you so much for taking the time to speak with me today. I appreciate it. Yes, thank you so much for taking the time to speak with me today. I appreciate it. Yes, thank you so much for having me, Corey. I appreciate it. It's been a lot of fun. And I just repeated what you said.

No, that's fine. That's called being a thought leader. When people repeat what you say, you've made it. Awesome. Farrah Campbell, Ecosystems Director at Stackery. I am Corey Quinn, and this is Screaming in the Cloud. If you've enjoyed this podcast, please leave an excellent review on Apple Podcasts. If you've hated this podcast, please leave an even better review on Apple Podcasts,

but at least make the review entertaining. This has been this week's episode of Screaming in the Cloud. You can also find more Corey at Screaminginthecloud.com or wherever fine snark is sold. This has been a humble pod production stay humble