Screaming in the Cloud - At the Cutting Edge & Node with Nader Dabit

Episode Date: August 12, 2021

About NaderCurrently working to help build the decentralized future at Edge and Node.Previously led Developer Advocacy for Front End Web and Mobile at Amazon Web Services.Specializing in GraphQL, cross platform, & cloud enabled web & mobile application developmentDeveloping applications & reference architectures using a combination of GraphQL & serverless technologies built on AWS4 years experience training fortune 500 companies on web & mobile application development, with the last two focused on React and React Native Training (clients include Microsoft, Amazon, US Army Corps of Engineers, Visa, ClassPass, American Express, Indeed, & Warner Bros).Mobile consultant specializing in cross platform web & mobile application developmentAuthor of React Native in Action (Manning Publications)Author of Full Stack Serverless (O'Reilly Publications)International speakerCreator of React Native ElementsCreator of JAMstack CMS & JAMStack ECommerceLinks:Edge & Node: https://edgeandnode.comJs.la: https://js.laTwitter: https://twitter.com/dabit3Youtube: https://www.youtube.com/naderdabit

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. Your company might be stuck in the middle of a DevOps evolution without even realizing it. Lucky you.

Does your company culture discourage risk? Are you willing to admit it? Does your team have clear responsibilities? Depends on who you ask. Are you struggling to get buy-in on DevOps practices? Well, download the 2021 State of DevOps Report brought to you annually by Puppet since 2011 to explore the trends and blockers keeping mid-evolution firms stuck in the middle of their DevOps evolution because they fail to evolve or die like dinosaurs.

The significance of organizational buy-in, and oh, it is significant indeed, and why team identities and interaction models matter. Not to mention whether the use of automation and cloud translate to DevOps success. All that and more awaits you. Visit www.puppet.com to download your copy of the report now. Up next, we've got the latest hit from Veeam.

It's climbing charts everywhere, and soon it's going to climb right into your heart. Here it is. Well, dang. Ransomware had my data all jacked up, if only I had secure backup. Then I met you, BAME, AWS Backup Dream Team, yeah. Welcome to Screaming in the Cloud, I'm Corey Quinn. I'm joined this week by Nader Dabit, who, until recently, was a senior developer advocate at AWS, and now is heading to a new company that, as of the time of this recording, you haven't started the job yet,

but you'll be doing developer relations at Edge and Node. That's right. First, congratulations. Career mobility is great. Secondly, welcome to the show. Thank you, thank you. And thirdly, what is Edge and Node? So, yeah, this is actually the first time I've even spoken to anyone about this. So this is very early stuff.

So it's exciting to even be acknowledging it. But yeah, thank you for having me here. And I'm a big fan of yours. And I know we've met a few times in person. So it's always fun to keep up with the ideas that you throw out there. Yeah, Edge & Node is basically a new company. It just started in February of 2021. And it's in the decentralized finance or Web3 world as well. And the general idea that they're trying to accomplish is to kind of facilitate companies and people that are looking

to build applications in this space. It's kind of a fairly new space compared to kind of the traditional web space, which would be things like what I'm doing at AWS now, even as we speak. But the general idea is that they want to facilitate companies building out decentralized applications in general and any types of applications that are kind of falling into that same category. I'm in a weird spot because I think that a lot

of the technology around the distributed financial stuff, by which we of course mean blockchain, cryptocurrency, etc., is goofy. There are challenges with it across the board, etc., etc., etc. However, I'm deeply envious of the passion that the people who are really into that space exude around it. And maybe I'm just old and bitter and twisted, but man, I wish I could get that excited about anything. Well, I mean, I'm leaving probably the best job I've ever had in my entire life by far. I'm leaving the most comfortable situation I've ever been in in my entire life as well. I have a great team that I work with.

I've been here for a little over three years. The stuff that we're doing is amazing. So for me to actually leave this position, you know, says a lot to me or the idea that I would even leave kind of says a lot to me and everyone I've told so far, which is like a few people like my wife and a few family members. And of course, some people at work, they're also kind of shocked by it. But I think that I've really enjoyed what I've been doing. But after a little over three years, I've kind of gotten a little bit, I'm kind of the type of person that is always like looking for the next new thing to do and something to kind of like

challenge me. And the more I've kind of looked into the space and also the team that I'm joining, and also the more that I look at maybe some of the challenges that we're seeing in the world in general, that kind of the idea that some of these technologies are aimed to solve, especially if you look at what's happening in countries in the last few years, like Lebanon, where you cannot take money out of the bank and they're having massive inflation, Venezuela and other parts of the world like Turkey and Nigeria as well. There is a problem that needs to be solved. And a lot of the solutions, in my opinion, kind of lie in these decentralized financial applications. It's still in the early days, though. So I think it's a really cool opportunity to kind of get in on something and learn it and learn the ecosystem

and maybe even help some people while I'm doing it. Really, really passionate about the team I'm going to be working with. And I'm kind of really excited about it. So yeah, it's kind of an interesting part of my career. Like if I looked at the job that I have now at AWS five years ago, I would have done anything to have it, right? It was like, it is such a great role. So for me to actually leave this is kind of like mind bending even to myself. So it's kind of a weird and interesting time in my career, but it's also really, I'm really excited.

I look forward to hearing how it treats you. But that's a forward looking conversation and almost one for another day. Let's look back a bit. You've been at AWS for almost four years, and you've been a senior developer advocate around Amplify, which means that you and I haven't spent a whole lot of time interacting because everyone says, oh, front end and thus JavaScript by extension are easy beginner. That's baby stuff. Yeah. The hell with everything

about that. It is dark magic that every time I try to understand, I come away more confused than I was when I started. And in anything remotely resembling a professional context, I have the good sense to pay professionals rather than try to unpack it myself. I wind up tying myself in knots. The few times I have dabbled with it, you've been around and have reached out to help

with things that I get stuck on. And I'm gratified in many cases that you're looking at this going, huh, that's interesting, which is engineer's talk for what the hell is this? And it makes me, oh good, I'm not alone. This stuff really is confusing. But you've had something of a meteoric rise as far as a known voice in space in the front-end world. Tell me about that. Yeah, it's been really exciting to kind of have had all this stuff happen over the last few years. And it means a lot to me. And I'm really always extremely grateful for where I am.

I mean, I don't really know. I mean, I joined AWS in January of 2018. Before that, I was doing consulting in my own company for about a year and a half in a company called React Native Training. And I think that my community involvement started really maybe in 2016-ish when I started funding my own trips to go to conferences. So in Mississippi, the first company that I was working at when I started getting interested in conferences and stuff wasn't really going to pay for me to do that type of stuff. So I started just finding events outside of Mississippi because

there isn't anything. And that's where I live in Mississippi. There's like no tech here, right? So I started going to these events and I started becoming like really inspired by the people that I saw that were working at these companies like Google and Facebook and Amazon and even startups that were having really successful careers. And they were very, very inspired and excited about what they were doing. And they were speaking and I was like, wow, this seems like so, so awesome because I could just see how great all that stuff was. At least it was for me. I started thinking, okay, if I want to, I want to become involved in these communities, like what do I need to do? And, you know, I started doing the things that I thought would kind of get me to that point. And it was more like instead of,

I don't really want to like be known. I just want to like become friends with these people and get to know them and have these opportunities come up for me maybe. So I started doing writing. So I wrote my first blog post. It was talking about something like webpack configuration or something like that, 2016. That was my very first blog post and I put it out there and it actually did really well. It has over a million views at this point and it probably doesn't even work, but people still do it. But having that initial blog post and putting it out there and having people read it and like it really spurred my continued content creation, you could call that, even though I hate the word content creation or the phrase. So I just started doing more of that.

So I started writing. I started contributing to answers on Stack Overflow and stuff when I could. And then I started an actual meetup here in Mississippi. And I started speaking at the meetup myself because there was no one here to speak at first. And one thing kind of led to another. And then I would say, you know, over time, I started speaking at conferences. When I joined AWS, people started to kind of like take me a little more seriously because when you're working, I guess, at a company that people don't know and you have that on your Twitter profile, for some reason, people just are less likely to follow you.

Or at least I noticed that when I joined AWS, people were more likely to follow me. So, I mean, I don't know, it just happened over time and it's been really exciting. And I think the thing that I like the most about what's happened is all the relationships that I've built and all of the people that I've become friends with. Like I'm friends with so many people and almost all of my friends now, I could say pretty much came from the tech world outside of my hometown of Mississippi or Jackson, Mississippi, you know? I grew up in a small town in Maine. I have somewhat similar origin stories, except I never actually amounted to anything useful or good. I just went funny and obnoxious instead.

And my road to tech was by starting off as a grumpy Unix admin and over time evolving into a DevOps person, SRE person, managing the same teams, and then doing whatever the hell it is that I do now. What I find interesting is that if I were talking to someone who wanted to get into tech today, I would suggest radically different things. The path that I walked is well and truly closed. So instead, what I see is this world of being able to get into tech through boot camps, through having more established paths for beginners. Self-study is just as valid, too. And I would suggest the first language someone pick up, even though I don't understand it,

to be JavaScript, because it is very clear that that is the future of technology in many respects. And I'm not saying that because I love JavaScript. I don't. I don't like it, if I'm being honest. But it is the most accessible language that is broadly being taught. And the number of people in a position to learn it

absolutely dwarf the existing tech sector. I have a very hard time seeing a future where JavaScript is not the lingua franca of just about everything that requires coding. Is that overstating it? No, I agree. I agree 100%. I mean, the way that I look at it is unless you kind of have a clear, clear understanding about where you want to go into tech and it does not align with what JavaScript has to offer, then you might as well choose JavaScript to start off with. Like you mentioned, it's just about the numbers. With JavaScript, it's kind of like the highest language that people are actually hiring for. Like if you look at all the different charts

and all the different studies and all that stuff recently, but you can also do the most with it. So if you've learned JavaScript and you become, if you want to say, oh, I don't want to do front end, I want to do back end, you can do that. You can build mobile apps, you can build desktop apps. You can pretty much do anything. So I think it's a really great way to kind of like learn programming and also kind of find the path that you want to have at the same time without having to learn an entire language and ecosystem and then throw all that knowledge away to learn something else because that's not going to align with like where you want to go. So yeah, I agree completely. And I know that I'm going to get letters for this, but I think that's a good thing. It would be kind of nice on some level if I had at least a working knowledge of a language that could be simply and commonly used for

simultaneously front-end, back-end tooling, et cetera. The Node ecosystem is vast. Instead, bad Python is my lingua franca, and there are ways you can theoretically transpile it into front-end, and the working consensus is, oh my god, never do this. And that's okay. I feel like on some level I'm from a different era, and the direction that I go in is radically different than where I would if I were starting out today. That's okay. It's a big industry. There's room for all kinds. If you don't agree with what I'm saying, that's fine too. Because again, there are so many paths and so many ways to get there that there's plenty of room for everyone. The pie is getting bigger. And that's what I think

it's important to focus on rather than trying to maximize the amount of the existing pie you can claim for yourself. And that's something that you've been doing for a long time. You entered tech, what is it, 11, 12 years ago now? Yeah, it was in 2012, so I guess about nine years ago. And since then, you've had a number of roles that were effectively pure development. But additionally, there's a constant and recurring theme that you wound up sort of smacking into, going from senior web developer, front-end web developer, software developer, web application developer. That's when it starts to shift. Software developer, software developer. Then at React Native Training, you were a founder and trainer. And then you went to AWS and did senior developer advocate work.

And you have shifted in many respects away from the person that writes the production code to the person that teaches other people to write code. And that is a massive and fundamental shift that often goes unnoticed. Yeah, I would say that going back a lot, I guess, when I started learning how to code, I was 29 or 30. And I tried to find a job shortly after in Mississippi. And I'm not coming from like a traditional background either. I don't have a diploma even from high school. I don't have a college degree or anything like that. So I was kind of like coming from a very, very non-traditional background, right? In Mississippi, there just wasn't anything here. So I started applying for roles all over the place, like

Southeast United States, didn't get any opportunities there, started hitting the East Coast and the West Coast, hired someone to spruce up my resume. I did have some stuff to put on there just from me playing around on GitHub and just learning. And also I did build out an e-commerce site that was actually working and stuff like that. But the general thing that I was just looking for was my foot in the door. And the first opportunity that I got was in LA. So the LA opportunity was a contract. It wasn't even a full-time role, but I took it and I just moved to Los Angeles over the weekend because I had to be there on Monday. And when I got to LA, I was like put into this real developer role, right? Like with real developers.

And it was a complete, complete like shock in every way for me. But it was probably the most exciting thing that ever happened to me in my life because I was, I kind of was like enjoying coding. And then I was like now put into this space where I was around a bunch of really, really good coders. And they were just coming to work in this warehouse

wearing like flip-flops. And there was like free snacks and free drinks. And there were just coming to work in this warehouse wearing like flip flops, and there was like free snacks and free drinks. And there was a dog in like a beanbag chair, stuff that was completely wild and new to me, right? So like, I became really excited. And then when I was in LA, the developers that I was working with started taking me and introducing me to like the community of JavaScript,

I guess, or really the coding community in LA, but it was really mainly JavaScript is what we were kind of like working in. So when I first went to my first meetup, I was just completely blown away because not only was it just probably one of the better meetups in the world, because I've been to a bunch of them since then, but it was also my very first one. I didn't even know these things existed. So I'm going into this like really gritty part of like downtown LA into this huge warehouse with them. And I don't know what to expect. And we walk in and there's waiters walking around with food.

There's free drinks. There's alcoholic and non-alcoholic beverages. There's this huge stage set up with like hundreds of chairs. Everyone's like walking around, like talking about coding and stuff. People from Google were there trying to hire people. To me, it was just something that I'd never imagined that I thought was just so cool. And then I sit down and people are just going one by one, teaching people things that they've learned in their free time.

They're taking time out of their day. This is their free time to teach other people about how to do things. And I was just completely, really in love with that idea from that moment on. So I got introduced to these meetups. And ever since that happened, I moved back to Mississippi about a year later. And being here, there just wasn't anything here.

There was no meetups. There was no conferences, of course. And I really missed that. So I kind of started getting into ways that I could do the same thing, but have it here in Mississippi. So I first started a meetup here. We ran the meetup for a little over four years, I think three and a half to four years, maybe where we would have bi-weekly meetups where we would do pretty much the same thing we did in LA. It was js.la was the meetup. It still happens.

And I actually got to go back there and speak at Google maybe a year and a half ago, which was really meaningful for me. And then after the meetup, I also started a local coding school, which never really took off, but I did it for about two years and we never really made, in fact, we lost money because most of the classes were free. It is a school. If it loses money, you're doing it right until you apparently round the bend somewhere and have an endowment for your school that's in the billions, or you just pivot to Pura for profit, and suddenly you start making trade-offs on behalf of your students. It's a mess.

Yeah, exactly. Yeah. I was just actually really hoping to break even and be able to have this community resource here in Mississippi because there wasn't any. But there just wasn't enough people interested in learning how to code that, or maybe I wasn't as good of a marketer as I could have been. Maybe not enough people knew about it, but I was doing everything I could to kind of get the word out. And we would have between one to six people maybe show up to these classes that were between like one to eight hours long. And we would teach people how to write code. We would teach them how to

build apps with Angular. And towards the end, I was doing React because that was a thing. And from then on, I really enjoyed that. Like, I really enjoyed the experience of being in LA and having someone teach me. And I learned so much. I kind of like always was wanting to give that back and also, you know, be involved in those types of events. So, yeah, I've kind of always enjoyed the teaching aspect and the learning aspect. I really love installing, upgrading, and fixing security agents in my cloud estate. Why do I say that? Because I sell things for a company that deploys

an agent. There's no other reason. Because let's face it, agents can be a real headache. Well, Orca Security now gives you a single tool to detect basically every risk in your cloud environment that's as easy to install and maintain as a smartphone app. It is agentless, or my intro would have gotten me in trouble here, but it can still see deep into your AWS workloads while guaranteeing 100% coverage. With Orca Security, there are no overlooked assets, no DevOps headaches, and believe me, you will hear from those people if you cause them headaches, and no performance hits on live environment. Connect your first cloud account in minutes and see for yourself at orca.security.

That's orca as in whale, dot security as in that thing your company claims to care about, but doesn't until right after it really should have. Oh, I loved my time in LA. It was a fun place to be. There were a lot of interesting things that happened, and there are days I sincerely miss that. But, you know, life happens. Things go on. We drift in different directions. One of my personal breakthrough moments was, I was contracting for another company, and they sent me to various places to do various things. And they were effectively DevOps or sysadmin style bodies for hire. And it was the skills that you would accept. And one day, Puppet, at the time called Puppet Labs, reached out to them with a very weird ask, which is, great, we want someone who's obviously checks all the technically capable boxes to come and be a traveling trainer to teach people how to use Puppet. Which, you know, these days is borderline considered negligence, but at the time it was a good approach. And it really taught me how to, first, dive into things and understand them myself. And two, how to explain them in different ways and

reach people who all have different learning styles. And hands down, I thought that becoming a network engineer for a brief time was one of the best things I ever did to advance my career. Yeah, it doesn't hold a candle to learning to teach other people about complex things, because if they don't understand what you're talking about, it's your failure, not theirs. Right. Yeah, I agree. I agree completely. So did you find that a lucrative career at the time? It was a four-month contract. I found it very lucrative in the sense of, I mean, I was on salary for the consulting company. It's not something that I would set out to do as an independent consultant without significant forethought. It was rough. I was on the road every week for four straight months. I was on a first name basis with different air crews in different cities. And it was very wearying. And it was also the problem that I

ran into, at least for my proclivities, is you're teaching a different group of folks in a different city every week, but it's the exact same curriculum, which is set by a different group. And like the first one, you're terrified to give it because, oh my God, I'm going to mess it up. And you somehow muddle your way through. And on the second one, you're like, I've got it. And your third one, oh no, I don't got it because something goes wrong.

And by the eighth, it's repetitive and it's the same thing. And you can use the same jokes and make people laugh and have all kinds of fun conversations, but it's a weird problem. I mean, this was exacerbated by the fact that the training at the time was a couple thousand dollars. It was three days. A lot of people who were taking the class were angry at Puppet because they saw, rightly or wrongly, that this was automation software that was coming to take their job away, and they were nervous and scared and didn't want to deal with that. And I'm the representation of that company in front of them.

And oh, by the way, if I get negative enough ratings, I'm fired. So good luck. Send us a postcard when you get there. And it was how I learned to speak publicly off the cuff. Because you do a demo, the demo breaks because it's a demo. And you have to tell a story while fixing the demo. But it became repetitive at some point, to the point where now the class doesn't exercise,

great, and someone has a problem, and without even getting up from the front of the room, it's, yeah, you dropped, you forgot a comma, and they look at you like you're a wizard from the future. It's, no, just at that point, there's always one person who forgets a comma. You start seeing these things. I really enjoyed that,

and I enjoyed meeting people and telling stories with them. And it was a great experience. I miss a lot of it. And I try and recapture it with the other stuff that I do now. But it was absolutely a watershed moment in my career. Yeah, I would say that I was doing like something similar when I was doing my React training for like a little over a year. And the thing that I like about AWS is what I'm doing now is that I'm kind of teaching different things. I'm teaching the same like ideas, but I'm teaching them applied in a bunch of different ways.

So I don't really get too bored. But when I was doing React Native training, I was kind of like you were teaching the exact same thing over and over and over. And it did start getting to the point where I was just unhappy with myself because I was like not learning anything myself. And even though I like teaching, I also like also enjoyed learning. So when I'm not pushing myself,

I seem to get really antsy. Oh yeah. It's one of those evolve or die moments where it's, at least the way I see the world, you have to be able to effectively understand multiple points of view. You have to be able to recognize frustration when you see it and not take it personally. It requires so many things that we call soft skills, but oh my God, are they hard as hell. Yeah, yeah, absolutely. People, skills, or whatever you want to call it. I don't really know what we should call it, but it's one of those things that for me didn't come naturally and it just came with practice. So like speaking at events, like you said, going to meetups and just interacting with people in the developer community, being on podcasts and hosting my own podcast at one point.

Yeah. Over time, you just get better at it. There are people born with very talented skills. They just are really pleasant people. But for some people like myself and a lot of other people, I'm sure it's one of those things that you have to kind of like practice and become aware, you know, keep looking at yourself and like identifying areas where you can improve and be very, like you said, not take anything personally. Like if someone, if they call you out on something, like acknowledge that they're probably right and

look back into yourself and see what you can do to improve. One of the common myths that we see across the board is that you have a sizable audience on Twitter. And I say that as somewhat, we're roughly equivalent. And it's one of those, I take a look at that and it's weird. It's not something that you ever, I think, come to accept. Like you say like, wow, he has a lot of followers. And I realized, wait, I have like roughly the same number. Oh, wow. I have a lot of followers. Man, is it weird talking to an audience that is several times the size of the town I grew up in. But it feels almost like you've always been there, that you have emerged fully formed from the forehead of some god, but you've only been in tech for roughly a decade. Please don't take this the wrong way. You're a smidgen older than that.

And your LinkedIn doesn't talk about what you did before that. It's very focused on the existing tech narrative, which, oh, from a business perspective, makes sense. But let's unpack that a bit. What were you doing before you learned to first write code and later teach it? So this is like a really important part of, I would say, my story whenever I really get into this, because I think a lot of people have a similar path or they're maybe wanting to become on a similar path that I'm on now. And just kind of hearing other people's stories and how they've done it is really encouraging to a lot of people. So I do like to share this and kind of go into the details before I became a developer. So like I mentioned, I dropped out of high school because I didn't ever get a diploma.

In Mississippi, you can actually get your GED and then go into community college. So I did that. Hey, you have more educational credentials than I do. I don't even have a GED. Oh, really? Wow. I did not know that. I would have never guessed that.

Sidebar, yeah. I was expelled from two boarding schools, wound up getting a diploma from some random homeschooling organization, let me test out of it, found out years later they weren't accredited, and then failed out of college. But on paper, I have an eighth grade education, and no one can ever take that away from me. Me and you have a lot in common, it seems like. Sure seems like it. So yeah, basically I was kind of a fuck up from the age of like, I don't know, 18 until 29.

And I had my good and bad moments without going into all the details. But during that time, I just didn't know what I wanted to do with my life. My father has a clothing store here in Mississippi, and he sells like men's suits and kind of like what you would say is like a part of town that's kind of like the lower income part of town and stuff. And I worked there often. Whenever I couldn't find a job anywhere else, my dad would always like, let me come in and work for him. So I did have that as kind of like a fallback mechanism. So I would even consider that like a privilege almost, right? Because a lot of people,

you lose your job, you're kind of out in the street, right? But during the time between the age of 18 and 29, I was kind of doing all kinds of stuff. I was trying different things. I worked at restaurants for a few years early on, and then later on in my career, everything from a host to a bartender, to a waiter, to a manager, even. Looking back on the restaurant business, I actually don't like it. I have so much respect for anyone that is in it. And I have a lot of respect for waiters and stuff because I understand what they've gone through. So I did that. I tried working in retail for my dad. I also tried working in retail for other people, like shoe stores and stuff like that as a salesperson. I got my real estate license. And I got my real estate license in 2007-ish, like right before the bust of 2008. Oh, yes. Everyone was getting into real estate.

And if you weren't, people looked at you like you were nuts. Oh, I remember those days. So I got my real estate license. And six months later, the bust happened. And I was a failure big time in that endeavor. If I'd stuck around, who knows, right? But it didn't work out for better or for worse. So yeah, I tried all kinds of stuff, honestly. And I was never really like good at anything. I never really succeeded in anything. So one of the times when I was working with my dad in his store, we basically wanted to put our suits online e-commerce. Actually, when I say we, it was just me. Like I was kind of interested in like app development and web development. I was really more interested in the idea of like having an app in the app store and making money off of it. That was kind of really, if I want to be completely like

honest, that's kind of how I really wanted to learn coding to do. But in the meantime, we were trying to hire developers to like build us a website to sell suits online. And I was so, so like out of touch with what actually needs to be done for that to happen, because I had no tech background, that we were continually being disappointed because we were hiring people, you know, local developers and trying to pay them just like a few thousand dollars. Turns out for two or $3,000, you can't actually build an entire e-commerce platform even back then. So we failed a few times with that. And I was like, you know what, let me try to build this myself. I took an HTML programming class in community college 10 years prior. So I knew how to write HTML. And I figured that would

be enough to like build out an e-commerce platform. Anyway, after doing some digging, I discovered WordPress. And with WordPress, you can basically build an e-commerce site with plugins and stuff. So that actually worked out. We, over the course of like nine months, like I, I would say, built out this e-commerce site, learned a little bit of PHP and CSS and very, very little JavaScript and HTML, of course, and was able to kind of like get this e-commerce store up and running and also profitable and making money. And at certain points, we were making more money on the website than we were making in the store. So it was a success. And it was like the first real success that I had had in my life, honestly. And it felt really good. And I also knew that this was my thing. I want to get into coding.

Like this is the thing that seems to speak to me that I'm like, okay, yeah. And the rest is kind of history. That was when I decided to look for a job. And I found a job, like I said, in LA and moved out over the course of a weekend so I could have my first day. And I found a job, like I said, in LA and moved out over the course of a weekend so I could have my first day. And I don't want to go into a lot of more details, but I got fired after that, like two months later. My wife had just come out there. And a few days after she got there, I got fired from my contract. So that was a really tough time, but got through that. Getting fired is one of my core competencies. It's really an underrated skill. I mean, it taught me a lot.

I mean, I wouldn't ever want anyone to go through it in a really critical time like that. But, you know, here I am. I'm still around. It seems like a lot of this built to where you are by giving you exposure to a lot of different areas. There's a certain, I guess, hustle required in those moments when you're, oh, it turns out that that money I was counting on is no longer going to be coming in because that job I thought I had doesn't exist. And I have a limited runway here. And you combine that with various roles that exposed you to the wonder known as the general public. And it forces you to be able to have civil conversations with people you would prefer not to. And I really feel like this is

the sort of stuff that, although it sucks at the time when you're going through a lot of it, it has the opportunity to really help shape a future where you can blend technology with people. And that really seems to be where the most interesting work is being done. Yeah. And I really look forward to the future and I kind of see a lot more people coming into tech from non-traditional backgrounds. If I could go back and do it all over, I would have loved to actually gone and gotten my computer science degree and been a very good student and all that stuff. Like if I could go back with the discipline and all the stuff, I guess, maturity that I have now. But at the same time, a lot of people are like me and they go to college and

maybe they don't want to do the thing that they got a degree in or that maybe they just are not going to college at all. And there's so many, so many resources online now that people can kind of use to get there. And people start at all ages these days. I mean, there's people that I see that are online that are starting in their 50s and their 40s and even in their 60s that are just starting. And the awesome thing about technology is that there's a lot of stuff online that you can just pick up and learn for free. And there's different barriers to entry and different levels of privilege and things like that, of course, that you have to take into consideration.

But at the end of the day, I feel like there is more of an opportunity for someone to come into tech and make a name for themselves and become successful than almost any other traditional discipline like engineering or medicine or law, right? Where you have to have these accredited things. With tech, you don't really have to be accredited. You are your accreditation. What you say and the things that you provide online are kind of like how people are going to vet you. It's a hard lesson. If you can learn it, it really acts as something of a superpower. And a sad number of people seem to never quite get around there. We talk about coming from positions

of privilege, and we all do to some extent. But on some level, having to scrape a little bit early in your professional career really feels like it is in some ways a benefit. Now, let's be clear, I don't wish that on anyone, but if you have to go through it, I can't shake the feeling that it does lend itself to interesting things later career. But of course, you've got to get through that first. Right. Exactly. Yeah. I mean, one thing that always is in the back of my mind is when you have gone through a lot of tough times, you almost have like a post-traumatic stress syndrome that you have that you always remember those really, really, really tough times

that are financial tough times. And they always kind of like spur you to kind of continue doing the thing that you're doing. And I don't know if it's that way for people that never had to deal with any of that stuff because I have no idea. But for me, for sure, that's part of it. Like it's almost hard for me to say no to anything

that might advance my career at this point. And it's not a good thing. Honestly, I would like to be able to say no to more things. But because of having those bad times, you always are like, oh, I don't ever want to go back to that point. So I'm going to do everything I can to continue going forward. That's my mental state right now.

And like I said, it's probably not the best place to be at all the, all the times it does stress you out sometimes, but it's one of those things I've never been able to like shake. And I don't know if it's a good thing or a bad thing. It just is. It is what it is. It is. Nader, thank you so much for taking the time to speak with me today. If people want to learn more about what you're up to these days, where can they find you? Thank you for having me, Corey. Yeah, so the number one place would probably be Twitter. So Dabbit3, D-A-B-I-T, and the number three on Twitter.

I've been on Clubhouse a little bit lately at Dabbit, D-A-B-I-T. And I have a YouTube channel. It's YouTube slash Natter Dabbit. So those three places are probably where you'll see me around. And we will, of course, include links to them in the show notes. Thank you so much for taking the time to speak with me. I really appreciate it. And best of luck in your new role. I really enjoyed the conversation. Thanks for having me. Of course. Nader Dabit, currently about to embark on a new journey in developer relations at Edge and Node. 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've hated this podcast, please leave a five-star review on your podcast platform of choice and a gatekeeping comment telling me that no, JavaScript is not a good language written entirely in Perl. 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