Podcasts about software development engineer

South East Technological University (SETU) proudly hosted the fifth annual Women in Technology event at the SETU Arena in Waterford recently. Designed to empower young women, the event aimed to break down barriers in the tech industry, showcase career opportunities, and highlight relevant courses at SETU. Over 1,100 female students from Cork, Tipperary, Kilkenny, Wexford, and Waterford attended, gaining inspiration from keynote speakers and industry professionals through engaging discussions and one-on-one conversations. Kim McKenzie-Doyle of The Big Idea delivered an insightful keynote address, empowering the young women to think creatively and solve real-world problems by connecting with industry to forge their futures, while RTÉ broadcaster and advocate Zoe Ryan, acted as MC for the event. Guest speakers Rebecca Troy, Associate Engineer at Sun Life, and Zara Grunner, Software Development Engineer at Security Risk Advisors, spoke about their career journeys, emphasising the wealth of opportunities available for women in technology. Leading tech companies from the region also participated, offering students valuable insights into career pathways within the sector. Unum's Business Architect Sarah Adderley facilitated a successful Stemming Ahead workshop with attendees. Amanda Freeman-Gater, Assistant Head of the Computing and Mathematics Department at SETU, highlighted the increasing need for more women in technology. "The tech industry needs more female graduates, and studying the wide range of technological courses available at SETU opens pathways to dynamic careers. Graduates of these courses can take up technical roles that offer flexibility, teamwork, and the chance to develop innovative ideas, services, and products," she said. "Now is the time to nurture the next generation of female tech talent to ensure a more balanced pipeline of professionals. Achieving gender equality in technology is essential - not just for the industry, but for society as a whole," added Ms Freeman-Gater. The event not only challenged perceptions about careers in technology but also showcased the diverse opportunities available in computing, physics, and engineering. Attendees explored exhibitions, interactive technology demonstrations, and insightful discussions led by female industry leaders. They also received information about the wide range of third-level programmes at SETU.

Welcome to Open Tech Talks. In this episode, we're speaking with Mayank Jindal, a Software Development Engineer, about AI's evolving landscape and its impact on software engineering. From AI use cases to challenges in model development, we cover strategies for aligning AI solutions with business needs, tips for staying updated in this fast-paced field, and career advice for aspiring developers. Whether new to AI or looking to refine your skills, this episode delivers insights you can apply immediately. Large language models (LLMs) are transforming software engineering by automating code generation, debugging, and testing. They enable developers to accelerate workflows but require engineers to upskill and adapt. While AI reduces repetitive tasks, developers need to focus on designing architectures, validating outputs, and ensuring AI-generated code meets quality standards. This episode has covered AI's evolving role, its impact on software engineering, and strategies for addressing challenges in AI development. Episode # 153 Today's Guest: Mayank Jindal, Software Development Engineer, Amazon He is a Software Engineer passionate about leveraging Artificial Intelligence to enhance the digital world. Linkedin: Mayank What Listeners Will Learn: Understand how large language models (LLMs) influence software engineers' role and reshape development workflows. Explore common challenges faced in AI development, including data quality, scalability, and performance optimization. Discover strategies for keeping up with the rapid advancements in AI and machine learning technologies. Gain practical tips for newcomers looking to start or grow their AI and software development careers. Learn methods for translating business requirements into effective AI and machine learning models and tips for overcoming common obstacles. Learn about real-world AI applications that are transforming industries and solving complex problems with AI Resources:      

Join us as we uncover DevOps's secrets, exploring his journey from full-stack developer to leading innovations, the power of AI tools, and cutting-edge strategies for seamless integration and productivity. Give TestHub a try to manage, automate, and deliver: testguild.me/testhub Today, we're diving deep into the world of DevOps with our special guest, Michael Martinez. Michael is an experienced DevOps manager and lead for Stoplight and SmartBear's platform products, with a rich background as a full-stack developer and Software Development Engineer in Test (SDAT). In this episode, we'll explore Michael's journey from full-stack development to spearheading DevOps, the crucial role of collaboration and empathy in the field, and how he tackled the challenges of integrating startup energy into SmartBear's larger organizational structure after Stoplight's acquisition. We'll also explore innovative uses of AI tools for cost efficiency and productivity, the importance of repeatable processes, and implementing infrastructure as code. Michael shares insights on maintaining environments close to production for smooth releases, using Helm charts, automated testing, and ensuring shared responsibility for uptime—all while emphasizing the importance of continuous improvement and customer-centric actions. We'll also touch upon modern CI/CD tools, security in the DevOps pipeline, and how empowering developers with AI tools like GitHub Copilot is shaping the future of DevOps. So, prepare for an enlightening discussion filled with practical advice and forward-thinking strategies to help you navigate the ever-evolving world of DevOps. Listen up!

Welcome back to the podcast! In today's must-listen episode, Chantel got to speak with Jordan Moradian   Jordan Moradian is an experienced professional who currently holds the position of Head of Growth at SiPhox Health. Prior to this role, Jordan was the Co-Founder and CEO of Crawl Technologies Inc. Jordan has also worked as a Software Development Engineer at Amazon Web Services (AWS), specifically in the AWS AI | Rekognition department. With a background in data science and robotics, Jordan has interned at companies like Linden Lab, Tufts Human Robot Interaction Lab, Walleye Trading Advisors, and MD Biosciences. Jordan graduated from Tufts University in 2019.   Enjoy!   Heart and Soil: Website: http://chantelrayway.com/liver  Use Coupon Code: chantelray   Today's Episode Is Sponsored By BiOptimizers Masszymes: http://masszymes.com/waistawayfree    Use code waistaway10 for a special discount!   Today's Episode Is Sponsored By BiOptimizers Magnesium Breakthrough: Visit https://magbreakthrough.com/waistaway and enter code waistaway for 10% off any order. https://magbreakthrough.com/rf_special?rfsn=7678975.73fd57&utm_source=refersion&utm_medium=affiliate&utm_campaign=7678975.73fd57     Masszymes - https://bioptimizers.com/shop/products/masszymes?rfsn=7678975.73fd57&utm_source=refersion&utm_medium=affiliate&utm_campaign=7678975.73fd57   HCL (Hydrochloric Acid) - https://bioptimizers.com/shop/products/hcl-breakthrough?rfsn=7678975.73fd57&utm_source=refersion&utm_medium=affiliate&utm_campaign=7678975.73fd57     Sleep Breakthrough - https://bioptimizers.com/shop/products/sleep-breakthrough?rfsn=7678975.73fd57&utm_source=refersion&utm_medium=affiliate&utm_campaign=7678975.73fd57    Join Our Non-Toxic Family MasterClass: Website: https://nontoxicfamily.com/masterclass/ Join Our Facebook Group: https://www.facebook.com/groups/TheChantelRayWay/   Order One Meal And A Tasting: https://chantelrayway.com/onemeal/    Order All The Books: Waist Away: The Chantel Ray Way - 2nd Edition:  https://www.amazon.com/gp/product/0999823116/ref=dbs_a_def_rwt_hsch_vapi_tpbk_p1_i0    Fasting to Freedom: The Gift of Fasting: https://www.amazon.com/Fasting-Freedom-Gift-Chantel-Ray/dp/0999823132/ref=tmm_pap_swatch_0?_encoding=UTF8&qid=&sr=    Freedom From Food: A Six Week Bible Study Course: https://www.amazon.com/Freedom-Food-Bible-Study-Course/dp/0999823159/ref=pd_bxgy_img_3/135-7722513-4171815?_encoding=UTF8&pd_rd_i=0999823159&pd_rd_r=91d59435-2126-4f9d-867e-00646964e3e4&pd_rd_w=mg3U0&pd_rd_wg=FcVwL&pf_rd_p=fd3ebcd0-c1a2-44cf-aba2-bbf4810b3732&pf_rd_r=NWM3687GJSRKKQ4BYQP4&psc=1&refRID=NWM3687GJSRKKQ4BYQP4    Connect With Us:   Leave us a review: https://chantelrayway.com/review/    Share YOUR Story: https://chantelrayway.com/contact/   Contact directly through email at questions@chantelrayway.com    Enjoy refreshing, all-natural wine: https://chantelrayway.com/wine/   Listen to the new audiobook as a podcast HERE: https://chantelrayway.com/purchase-audio-book/   Free Video Preview: https://chantelrayway.com/top-12-thin-eater-tips-free-video/   Check out the VIDEO COURSE here: https://chantelrayway.com/video-course/   Purchase on Amazon Here: https://www.amazon.com/shop/intermittentfastingthechantelrayway   Strengthen your immune system with Vitamin C: https://chantelrayway.com/vitaminc/    Enjoy a FREE smoothie recipe book: https://chantelrayway.com/freerecipe/   Re-energize with nutritious algae Energybits: https://chantelrayway.com/energybits    Castor Oil: https://chantelrayway.com/castoroil   Connect with us on Social Media:   YouTube Channel Link: https://www.youtube.com/channel/UCteFjiVaY6n0SOAixcyZbWA   Like us on Facebook at https://www.facebook.com/TheChantelRayWay       Things we love: https://chantelrayway.com/things-i-love-2/   Facebook group: https://www.facebook.com/groups/TheChantelRayWay   ***As always, this podcast is not designed to diagnose, treat, prevent or cure any condition and is for information purposes only. Please consult with your healthcare professional before making any changes to your current lifestyle.***

Meet Hiwot “Hiwi” Woldeyohannes, a passionate and dedicated Software Development Engineer at Amazon. After finishing her BA degree in Software Engineering at AAU, Hiwot worked in various local companies until she went to the States to continue her education. She joined Maharishi University for her Master's degree in computer science. She then worked in various roles, including a Full Stack Developer for Ford Motor Company and a contractor for Creospan, Inc., a consultancy firm based in Illinois. She has also worked for Blue Cross Blue Shield and Northern Trust Bank clients. Hiwi's dream has always been to land a role at a FAANG company, not just for herself, but to inspire tech workers in her community back in Ethiopia. Her journey from Ethiopia to the tech industry in the U.S. is a story of perseverance, passion, and the power of education. Gugut is an entertainment/educational podcast which is focused on discussing different perspectives on technology, philosophy and day-to-day lives of everyday people. For any inquiries

On this episode of the “I Am a Mainframer” podcast, host Steven Dickens is joined by Zareen Rydhan, Software Development Engineer in Test II and Lead Test Automation Engineer with Rocket Software. During their conversation, Steven and Zareen talk about the mainframe being the foundation of many of the world's most critical applications and how, as the world becomes increasingly digital, the need for mainframes is only going to grow. Zareen emphasizes that what this means for developers if that if you want to be successful in the tech industry, you need to know how to develop for the mainframe. Zareen also shares a few reasons developers should consider mainframe development: a high demand for mainframe developers with very competitive salaries, challenging and rewarding work, and long-term career security, with skills that will be in demand for years to come. When asked for advice and tips for mainframe developers, Zareen shared: * Learn the basics. The first step to becoming a mainframe developer is to learn the basics of the platform. This includes COBOL, JCL, and the mainframe operating system. * Get involved in the community. There are a number of online and in-person communities for mainframe developers. These can be great resources for learning, networking, and getting help. * Stay up-to-date. The mainframe is constantly evolving, so it's important to stay current on the latest trends. You can do this by attending conferences, reading relevant blogs, and taking courses. The "I Am A Mainframer" podcast explores the careers of those in the mainframe ecosystem. Hosted by Steven Dickens, Senior Analyst at Futurum Research, each episode is a conversation that highlights the modern mainframe, insight into the mainframe industry, and advice for those looking to learn more about the technology. The podcast is sponsored by the Open Mainframe Project, a Linux Foundation project that aims to build community and adoption of Open Source on the mainframe by eliminating barriers to Open Source adoption on the mainframe, demonstrating the value of the mainframe. #mainframe #opensource #opensourceadoption #IamaMainframer #podcast #OpenMainframeProject #LinuxFoundation #ZareenRydhan #RocketSoftware #StevenDickens #TheFuturumGroup

Manorama Jha, Software Development Engineer, AI, and Computer Vision, 3DAI at GridRaster Inc., shares her talk entitled “Introduction to Extended Reality.” In it, she discusses the challenges of developing immersive extended-reality experiences while explaining the fundamentals of building the Metaverse.

Nikita Koselev, the Lead Software Development Engineer at Mastercard, joins us to share how he got his start in software engineering and highlight the peaks and troughs of the industry. He goes on to speak about how he has been helping people learn open source coding and other technical skills that are highly required in the industry.

En este episodio hablamos con Juanjo Montiel, técnico desarrollador de aplicaciones informáticas y Senior Software Development Engineer (programador, simplificando), formador para LinkedIn y presentador y redactor en AccessiBites, con más de 15 años de experiencia como programador en varias empresas y proyectos propios como Litersoft y Daisy Converter.

Larry is a Software Development Engineer and an undergraduate of Computer Science and Engineering from UC San Diego. In this episode Larry and I speak towards working as engineers, being an engineering student, the pervasiveness of technology in industries, balancing innovation and industry, the legacy of tech giants, integrated hardware products, our favorite books, and leadership.Support the show

Interested in startups or working for yourself? That's what this episode is all about. Toby Cannon graduated from York in 2019 with a degree in Computer Science. He now runs Myles, a startup that began as an app allowing people to complete virtual challenges by tracking their fitness activity. He explains what his day looks like, what it takes to work in a startup and what students can do to follow in his footsteps. There's a full transcript and useful links on our blog. Toby's bio: After graduating in 2019 Toby joined Capital One as a Software Development Engineer, working on a range of products which are used by millions of people. At the start of the pandemic, he launched Myles initially as a tool to keep himself and his family motivated with their fitness goals. The company has grown since then and he's now full time on the business and is part of a team of four, with clients including Dell, Brewin Dolphin and Capital One.

About SeanSean is a senior software engineer at TheZebra, working to build developer experience tooling with a focus on application stability and scalability. Over the past seven years, they have helped create software and proprietary platforms that help teams understand and better their own work.Links: TheZebra: https://www.thezebra.com/ Twitter: https://twitter.com/sc_codeUM LinkedIn: https://www.linkedin.com/in/sean-corbett-574a5321/ Email: scorbett@thezebra.com TranscriptSean: 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.Corey: Today's episode is brought to you in part by our friends at MinIO the high-performance Kubernetes native object store that's built for the multi-cloud, creating a consistent data storage layer for your public cloud instances, your private cloud instances, and even your edge instances, depending upon what the heck you're defining those as, which depends probably on where you work. It's getting that unified is one of the greatest challenges facing developers and architects today. It requires S3 compatibility, enterprise-grade security and resiliency, the speed to run any workload, and the footprint to run anywhere, and that's exactly what MinIO offers. With superb read speeds in excess of 360 gigs and 100 megabyte binary that doesn't eat all the data you've gotten on the system, it's exactly what you've been looking for. Check it out today at min.io/download, and see for yourself. That's min.io/download, and be sure to tell them that I sent you.Corey: This episode is sponsored in part by our friends at Sysdig. Sysdig is the solution for securing DevOps. They have a blog post that went up recently about how an insecure AWS Lambda function could be used as a pivot point to get access into your environment. They've also gone deep in-depth with a bunch of other approaches to how DevOps and security are inextricably linked. To learn more, visit sysdig.com and tell them I sent you. That's S-Y-S-D-I-G dot com. My thanks to them for their continued support of this ridiculous nonsense.Corey: Welcome to Screaming in the Cloud, I'm Corey Quinn. An awful lot of companies out they're calling themselves unicorns, which is odd because if you look at the root ‘uni,' it means one, but they're sure a lot of them out there. Conversely, my guest today works at a company called TheZebra with the singular definite article being the key differentiator here, and frankly, I'm a big fan of being that specific. My guest is Senior Software Development Engineer in Test, Sean Corbett. Sean, thank you for taking the time to join me today, and more or less suffer the slings and arrows, I will no doubt be hurling your direction.Sean: Thank you very much for having me here.Corey: So, you've been a great Twitter follow for a while: You're clearly deeply technically skilled; you also have a soul, you're strong on the empathy point, and that is an embarrassing lack in large swaths of our industry. I'm going to talk about that right now because I'm sure it comes through the way it does when you talk about virtually anything else. Instead, you are a Software Development Engineer in Test or SDET. I believe you are the only person I'm aware of in my orbit who uses that title, so I have to ask—and please don't view this as me in any way criticizing you; it's mostly my own ignorance speaking—what is that?Sean: So, what is a Software Development Engineer in Test? If you look back—I believe it was Microsoft originally came up with the title, and what it stems from was they needed software development engineers who particularly specialized in creating automation frameworks for testing stuff at scale. And that was over a decade ago, I believe. Microsoft has since stopped using the term, but it persists in areas in the industry.And what is an SDET today? Well, I think we're going to find out it's a strange mixture of things. SDET today is not just someone that creates automated frameworks or writes tests, or any of those things. An SDET is the strange amalgamation of everything from full-stack to DevOps to even some product management to even a little bit machine-learning engineer; it's a truly strange field that, at least for me, has allowed me to basically embrace almost every other discipline and area of the current modern engineering around, to some degree. So, it's fun, is what it is. [laugh].Corey: This sounds similar in some respects to oh, I think back to a role that I had in 2008, 2009, where there was an entire department that was termed QA or Quality Assurance, and they were sort of the next step. You know, development would build something and start, and then deploy it to a test environment or staging environment, and then QA would climb all over this, sometimes with automation—which was still in the early days, back in that era—and sometimes by clicking the button, and going through scripts, and making sure that the website looked okay. Is that aligned with what you're doing, or is that a bit of a different branch?Sean: That is a little bit of a different branch from me. The way I would put it is QA and QA departments are an interesting artifact that I think, in particular, newer orgs still feel like they might need one, and what you quickly realize today, particularly with modern development and this, kind of, DevOps focus is that having that centralized QA department doesn't really work. So, SDETs absolutely can do all those things: They can climb over a test environment with automation, they can click the buttons, they can tell you everything's good, they can check the boxes for you if you want, but if that is what you're using your SDETs for you are, frankly, missing out because I guarantee you, the people that you've hired as SDETs have a lot more skills than that, and not utilizing those to your advantage is missing out on a lot of potential benefit, both in terms of not just quality—which is this fantastic concept that dates all the way back to—gives people a lot of weird feelings [laugh] to be frank, and product.Corey: So, one of the challenges I've always had is people talk about test-driven development, which sounds like a beautiful idea in theory, and in practice is something people—you know, just like using the AWS console, and then lying about it forms this heart and soul of ClickOps—we claim to be using test-driven development but we don't seem to be the reality of software development. And again, no judgment on these; things are hard. I built out a, more or less, piecing together a whole bunch of toothpicks and string to come up with my newsletter production pipeline. And that's about 29 Lambdas Function, behind about 5 APIs Gateway, and that was all kinds of ridiculous nonsense.And I can deploy each of the six or so microservices that do this, independently. And I sometimes even do continuous build or slash continuous deploy to it because integration would imply I have tests, which is why I bring the topic up. And more often than not—because I'm very bad at computers—I will even have syntax errors, make it into this thing, and I push the button and suddenly it doesn't work. It's the iterative guess-and-check model that goes on here. So, I introduced regressions, a fair bit at the time, and the reason that I'm being so blase about this is that I am the only customer of this system, which means that I'm not out there making people's lives harder, no one is paying me money to use this thing, no one else is being put out by it. It's just me smacking into a wall and feeling dumb all the time.And when I talk to people about the idea of building tests. And it's like, “Oh, you should have unit tests and integration tests and all the rest.” And I did some research into the topics, and a lot of it sounds like what people were talking about 10 to 15 years ago in the world of tests. And again, to be clear, I've implemented none of these things because I am irresponsible and bad at computers. But what has changed over the last five or ten years? Because it feels like the overall high level as I understood it from intro to testing 101 in the world of Python, the first 18 chapters are about dependency manager—because of course they are; it's Python—then the rest of it just seems to be the concepts that we've never really gotten away from. What's new, what's exciting, what's emerging in your space?Sean: There's definitely some emerging and exciting stuff in the space. There's everything from, like, what Applitools does with using machine learning to do visual regressions—that's a huge advantage, a huge time saver, so you don't have to look pixel by pixel, and waste your time doing it—to things like our team at TheZebra is working on, which is, for example, a framework that utilizes Directed Acrylic Graph workflows that's written GoLang—the prototype is—and it allows you to work with these tests, rather than just as kind of these blasé scripts that you either keep in a monorepo, or maybe possibly in each individual services' repo, and just run them all together clumsily in this, kind of, packaged product, into this distributed resource that lets you think about tests as these, kind of, user flows and experiences and to dip between things like API layer, where you might, for example, say introduce regression [unintelligible 00:07:48] calling to a third-party resource, and something goes wrong, you can orchestrate that workflow as a whole. Rather than just having to write a script after script after script after script to cover all these test cases, you can focus on well, I'm going to create this block that represents this general action, can accept a general payload that conforms to this spec, and I'm going to orchestrate these general actions, maybe modify the payload of it, but I can recall those actions with a slightly different payload and not have to write script after script after script after script.But the problem is that, like you've noticed, a lot of test tooling doesn't embrace those, kind of, modern practices and ideas. It's still very much the, your tests, you—particularly integration tests do this—will exist in one place, a monorepo, they will have all the resources there, they'll be packaged together, you will run them after the fact, after a deploy, on an environment. And it makes it so that all these testing tools are very reactive, they don't encourage a lot of experimentation, and they make it at times very difficult to experiment, in particular because the more tests you add, the more chaotic that code and that framework gets, and the harder it gets to run in a CI/CD environment, the longer it takes. Whereas if you have something like this graph tool that we're building, these things just become data. You can store them in a database, for the love of God. You can apply modern DevOps practices, you can implement things like Jaeger.Corey: I don't think it's ever used or anything in the database. Great, then you can use anything itself as a database, which is my entire schtick, so great.Sean: Exactly.Corey: That's right, that means the entire world can indeed be reduced to TXT records in DNS, which I maintain is the… the holiest of all databases. I'm sorry, please, continue.Sean: No, nonono, that's true. The thing that has always driven me is this idea that why are we still just, kind of, spitting out code to test things in a way that is very prescriptive and very reactive? And so, the exciting things in test come from places like Applitools and places like the—oh, I forget. It was at a Test Days conference, where they talked about—they developed this test framework that was able to auto generate the models, and then it was so good at auto generating those models for test, they'd actually ended up auto generating the models for the actual product. [laugh]. I think it used a degree of machine learning to do so. It was for a flashcard site. A friend of mine, Jacob Evans on Twitter always likes to talk about it.These are where the exciting things lay is where people are starting to break out of that very reactive, prescriptive, kind of, test philosophy of, like I like to say, checking the boxes to, “Let's stop checking boxes and let's create, like insight tooling. Let's get ahead of the curve. What is the system actively doing? Let's check in. What data do we have? What is the system doing right at this moment? How ahead of the curve can we get with what we're actually using to test?”Corey: One question I have is the cultural changes because back in those early days where things were handed off from the developers to the QA team, and then ideally to where I was sitting over in operations—lots of handoffs; not a lot of integrations there—QA was not popular on the development side of the world, specifically because their entire perception was that of, “Oh, they're just the critics. They're going to wind up doing the thing I just worked hard on and telling me what's wrong with it.” And it becomes a ‘Department of No,' on some level. One of the, I think, benefits of test automation is that suddenly you're blaming a computer for things, which is, “Yep. You are a developer. Good work.” But the idea of putting people almost in the line of fire of being either actually or perceived as the person who's the blocker, how has that evolved? And I'm really hoping the answer is that it has.Sean: In some places, yes, in some places, no. I think it's always, there's a little bit more nuance than just yes, it's all changed, it's all better, or just no, we're still back in QA are quote-unquote, “The bad guys,” and all that stuff. The perception that QA are the critics and are there to block a great idea from seeing fruition and to block you from that promotion definitely still persists. And it also persists a lot in terms of a number of other attitudes that get directed towards QA folks, in terms of the fact that our skill sets are limited to writing stuff like automation tooling for test frameworks and stuff like that, or that we only know how to use things like—okay, well, they know how to use Selenium and all this other stuff, but they don't know how to work a database, they don't know how an app [unintelligible 00:12:07] up, they don't all the work that I put in. That's really not the case. More and more so, folks I'm seeing in test have actually a lot of other engineers experience to back that up.And so the places where I do see it moving forward is actually like TheZebra, it's much more of a collaborative environment where the engineers are working together with the teams that they're embedded in or with the SDETs to build things and help things that help engineers get ahead of the curve. So, the way I propose it to folks is, “We're going to make sure you know and see exactly what you wrote in terms of the code, and that you can take full [confidence 00:12:44] on that so when you walk up to your manager for your one-on-one, you can go like, ‘I did this. And it's great. And here's what I know what it does, and this is where it goes, and this is how it affects everything else, and my test person helped me see all this, and that's awesome.'” It's this transition of QA and product as these adversarial relationships to recognizing that there's no real differentiator at all there when you stop with that reactive mindset in test. Instead of trying to just catch things you're trying to get ahead of the curve and focus on insight and that sort of thing.Corey: This episode is sponsored in part by our friends at Vultr. Spelled V-U-L-T-R because they're all about helping save money, including on things like, you know, vowels. So, what they do is they are a cloud provider that provides surprisingly high performance cloud compute at a price that—while sure they claim its better than AWS pricing—and when they say that they mean it is less money. Sure, I don't dispute that but what I find interesting is that it's predictable. They tell you in advance on a monthly basis what it's going to going to cost. They have a bunch of advanced networking features. They have nineteen global locations and scale things elastically. Not to be confused with openly, because apparently elastic and open can mean the same thing sometimes. They have had over a million users. Deployments take less that sixty seconds across twelve pre-selected operating systems. Or, if you're one of those nutters like me, you can bring your own ISO and install basically any operating system you want. Starting with pricing as low as $2.50 a month for Vultr cloud compute they have plans for developers and businesses of all sizes, except maybe Amazon, who stubbornly insists on having something to scale all on their own. Try Vultr today for free by visiting: vultr.com/screaming, and you'll receive a $100 in credit. Thats V-U-L-T-R.com slash screaming.Corey: One of my questions is, I guess, the terminology around a lot of this. If you tell me you're an SDE, I know that oh, you're a Software Development Engineer. If you tell me you're a DBA, I know oh, great, you're a Database Administrator. If you told me you're an SRE, I know oh, okay, great. You worked at Google.But what I'm trying to figure out is I don't see SDET, at least in the waters that I tend to swim in, as a title, really, other than you. Is that a relatively new emerging title? Is it one that has historically been very industry or segment-specific, or you're doing what I did, which is, “I don't know what to call myself, so I described myself as a Cloud Economist,” two words no one can define. Cloud being a bunch of other people's computers, and economist meaning claiming to know everything about money, but dresses like a flood victim. So, no one knows what I am when I make it up, and then people start giving actual job titles to people that are Cloud Economists now, and I'm starting to wonder, oh dear Lord, have I started the thing? What is, I guess, the history and positioning of SDET as a job title slash acronym?Sean: So SDET, like I was saying, it came from Microsoft, I believe, back in the double-ohs.Corey: Mmm.Sean: And other companies caught on. I think Google actually [unintelligible 00:14:33] as well. And it's hung on certain places, particularly places that feel like they need a concentrated quality department. That's where you usually will see places that have that title of SDET. It is increasingly less common because the idea of having centralized quality—like I said before, particularly with the modern, kind of, DevOps-focused development, Agile, and all that sort of thing, it becomes much, much more difficult.If you have a waterfall type of development cycle, it's a lot easier to have a central singular quality department, and then you can have SDET stuff [unintelligible 00:15:08], that gets a lot easier when you have Agile and you have that, kind of, regular integration and you have, particularly, DevOps [unintelligible 00:15:14] cycle, it becomes increasingly difficult, so a lot of places that have been moving away from that. It is definitely a strange title, but it is not entirely rare. If you want to peek, put a SDET on your LinkedIn for about two weeks and see how many offers come in, or how many folks in your inbox you get. It is absolutely in demand. People want engineers to write these test frameworks, but that's an entirely different point; that gets down to the point of the fact that people want people in these roles because a lot of test tooling, frankly, sucks.Corey: It's interesting you talk about that as a validation of it. I get remarkably few outreaches on LinkedIn, either for recruiting, which almost never happens or for trying to sell me something which happens once every week or so. My business partner has a CEO title, and he winds up getting people trying to sell him things four times a day by lunchtime, and occasionally people reaching out of, “Hey, I don't know much about your company, but if it's not going well, do you want to come work on something completely unrelated?” Great. And it's odd because both he and I have similar settings where neither of us have the ‘looking for work' box checked on LinkedIn because it turns out that does send a message to your staff who are depending on their job still being here next month, and that isn't overly positive because we're not on the market.But changing just titles and how we describe what we do and how we do it absolutely has a bearing as to how that is perceived by others. And increasingly, I'm spending more of my time focusing less on the technical substance of things and more about how what they do is being communicated. Because increasingly, what I'm finding about the world of enterprise technology and enterprise cloud and all of this murky industry in which we swim, is that the technology is great—anything can be made to work; mostly—but so few companies are doing an effective job of telling the story. And we see it with not just an engineering-land; in most in all parts of the business. People are not storytelling about what they do, about the outcomes they drive, and we're falling back to labels and buzzwords and acronyms and the rest.Where do you stand on this? I know we've spoken briefly before about how this is one of those things that you're paying attention to as well, so I know that we're not—I'm not completely off base here. What's your take on it?Sean: I definitely look at the labels and things of that sort. It's one of those things where humans like to group and aggregate things. Our brains like that degree of organization, and I'm going to say something that is very stereotypical here: This is helped a lot by social media which depends on things like hashtags and ability to group massive amounts of information is largely facilitated. And I don't know if it's caused by it, but it certainly aggravates the situation.We like being able to group things with few words. But as you said before, that doesn't help us. So, in a particular case, with something like a SDET title, yeah, that does absolutely send a signal, and it doesn't necessarily send the right one in terms of the person that you're talking to, you might have vastly different capabilities from the next SDET that you talk to. And it's were putting up a story of impact-driven, kind of, that classic way of focusing on not just the labels, but what was actually done and who had helped and who had enabled and the impact of it, that is key. The trick is trying to balance that with this increasing focus on the cut-down presentation.You and I've talked about this before, too, where you can only say so much on something like a LinkedIn profile before people just turn off their brains and they walk away to the next person. Or you can only put so much on your resume before people go, “Okay, ten pages, I'm done.” And it's just one of those things where… the trick I find that test people increasingly have is there was a very certain label applied to us that was rooted in one particular company's needs, and we have spent the better part of over a decade trying to escape and redefine that, and it's incredibly challenging. And a lot of it comes down to folks like, for example, Angie Jones, who simply, just through pure action and being very open about exactly what they're doing, change that narrative just by showing. That form of storytelling is show it, don't say it, you know? Rather than saying, “Oh, well, I bring into all this,” they just show it, and they bring it forward that way.Corey: I think you hit on something there with the idea of social media, where there is validity to the idea of being able to describe something concisely. “What's your elevator pitch?” Is a common question in business. “What is the problem you solve? What would someone use you for?”And if your answer to that requires you sabotage the elevator for 45 minutes in order to deliver your message, it's not going to work. With some products, especially very early-stage products where the only people who are working on them are the technical people building them, they have a lot of passion for the space, but they aren't—haven't quite gotten the messaging down to be able to articulate it. People's attention spans aren't great, by and large, so there's a, if it doesn't fit in a tweet, it's boring and crappy is sort of the takeaway here. And yeah, you're never going to encapsulate volume and nuance and shading into a tweet, but the baseline description of, “So, what do you do?” If it doesn't fit in a tweet, keep workshopping it, to some extent.And it's odd because I do think you're right, it leads to very yes or no, binary decisions about almost anything, someone is good or trash. There's no, people are complicated, depending upon what aspect we're talking about. And same story with companies. Companies are incredibly complex, but that tends to distill down in the Twitter ecosystem to, “Engineers are smart and executives are buffoons.” And anytime a company does something, clearly, it's a giant mistake.Well, contrary to popular opinion, Global Fortune 2000 companies do not tend to hire people who are not highly capable at the thing they're doing. They have context and nuance and constraints that are not visible from the outside. So, that is one of the frustrating parts to me. So, labels are helpful as far as explaining what someone is and where they fit in the ecosystem. For example, yeah, if you describe yourself as an SDET, I know that we're talking about testing to some extent; you're not about to show up and start talking to me extensively about, oh, I don't know, how you market observability products.It at least gives a direction and bounding to the context. The challenge I always had, why I picked a title that no one else had, was that what I do is complicated, and if once people have a label that they think encompasses where you start and where you stop, they stop listening, in some cases. What's been your experience, given that you do have a title that is not as widely traveled as a number of the more commonly used ones?Sean: Definitely that experience. I think that I've absolutely worked at places where—the thing is, though, and I do want to cite this, that when folks do end up just turning off once they have that nice little snippet that they think encompasses who you are—because increasingly nowadays, we like to attach what you do to who you are—and it makes a certain degree of sense, absolutely, but it's very hard to encompass those sorts of things, and let alone, kind of, closely nestle them together when you have, you know, 280 characters.Yes, folks like to do that to folks like SDETs. There's a definite mindset of, ‘stay in your lane,' in certain shops. I will say that it's not to the benefit of those shops, and it creates and often aggravates an adversarial relationship that is to the detriment of both, particularly today where the ability to spin up a rival product of reasonable quality and scale has never been easier, slowing yourself down with arbitrary delineations that are meant to relegate and overly-define folks, not necessarily for the actual convenience of your business, but for the convenience of your person, that is a very dangerous move. A previous company that I worked at almost lost a significant amount of their market share because they actively antagonized the SDET team to the point where several key members left. And it left them completely unable to cover areas of product with scalable automation tooling and other things. And it's a very complex product.And it almost cost them their position in the industry, potentially, the entire company as a whole got very close to that point. And that's one of the things we have to be careful of when it comes to applying these labels, is that when you apply a label to encompass someone, yes, you affect them, but it also we'll come back and affect you because when you apply that label to someone, you are immediately confining your relationship with that person. And that relationship is a two-way street. If you apply a label that closes off other roads of communication or potential collaboration or work or creativity or those sorts of things, that is your decision and you will have to accept those consequences.Corey: I've gotten the sense that a lot of folks, as they describe what they do and how they do it, they are often thinking longer-term; their careers often trend toward the thing that happens to them rather than a thing that winds up being actively managed. And… like, one of my favorite interview questions whenever I'm looking to bring someone in, it's always, “Yeah, ignore this job we're talking about. Magically you get it or you don't; whatever. That's not relevant right now. What's your next job? What's the one after that? What is the trajectory here?”And it's always fun to me to see people's responses to it. Often it's, “I have no idea,” versus the, “Oh, I want to do this, and this is the thing I'm interested in working with you for because I think it'll shore up this, this, and this.” And like, those are two extreme ends of the spectrum. There's no wrong answer, but it's helpful, I find, just to ask the question in the final round interview that I'm a part of, just to, I guess sort of like, boost them a bit into a longer-term picture view, as opposed to next week, next month, next year. Because if what you're doing doesn't bring you closer to what you want to be doing in the job after the next one, then I think you're looking at it wrong, in some cases.And I guess I'll turn the question on to you. If you look at what you're doing now, ignore whatever you do next, what's your role after that? Like, where are you aiming at?Sean: Ignoring the next position… which is interesting because I always—part of how I learned to operate, kind of in my earlier years was focus on the next two weeks because the longer you go out from that window, the more things you can't control, [laugh] and the harder it is to actually make an effective plan. But for me, the real goal is I want to be in any position that enables the hard work we do in building these things to make people's lives easier, better, give them access to additional information, maybe it's joy in terms of, like, a content platform, maybe it's something that helps other developers do what they do, something like Honeycomb, for example, just that little bit of extra insight to help them work a little bit better. And that's, for me, where I want to be, is building things that make the hard work we do to create these tools, these products easier. So, for me, that would look a lot like an internal tooling team of some sort, something that helps with developer efficiency, with workflow.One of the reasons—and it's funny because I got to asked this recently: “Why are you still even in test? You know what reputation this field has”—wrongly deserved, maybe so—“Why are you still in test?” My response was, “Because”—and maybe with a degree of hubris, stubbornly so—“I want to make things better for test.” There are a lot of issues we're facing, not just in terms of tooling, but in terms of processes, and how we think about solving problems, and like I said before, that kind of reactive nature, it sort of ends up kind of being an ouroboros, eating its own tail. Reactive tools generate reactive engineers, that then create more reactive tools, and it becomes this ouroboros eating itself.Where I want to be in terms of this is creating things that change that, push us forward in that direction. So, I think that internal tooling team is a fantastic place to do that, but frankly, any place where I could do that at any level would be fantastic.Corey: It's nice to see the things that you care about involve a lot more about around things like impact, as opposed to raw technologies and the rest. And again, I'm not passing judgment on anyone who chooses to focus on technology or different areas of these things. It's just, it's nice to see folks who are deeply technical themselves, raising their head a little bit above it and saying, “All right, here's the impact I want to have.” It's great, and lots of folks do, but I'm always frustrated when I find myself talking to folks who think that the code ultimately speaks; code is the arbiter. Like, you see this with some of the smart contract stuff, too.It's the, “All right, if you believe that's going to solve all the problems, I have a simple challenge to you, and then I will never criticize you again: Go to small claims court for a morning, four hours and watch all the disputes that wind up going through there, and ask yourselves how many of those a smart contract would have solved?”Every time I bring that point up to someone, they never come back and say, “This is still a good idea.” Maybe I'm a little too anti-computer, a little bit too human these days. But again, most of cloud economics, in my experience, is psychology more than it is math.Sean: I think it's really the truth. And I think that [unintelligible 00:29:06] that I really want to seize on for a second because code and technology as this ultimate arbiter, we've become fascinated with it, not necessarily to our benefit. One of the things you will often see me—to take a line from Game of Thrones—whinging about [laugh] is we are overly focused on utilizing technology, whether code or anything else, to solve what are fundamentally human problems. These are problems that are rooted in human tendencies, habits, characters, psychology—as you were saying—that require human interaction and influence, as uncomfortable as that may be to quote-unquote, “Solve.”And the reality of it is, is that the more that we insist upon, trying to use technology to solve those problems—things like cases of equity in terms of generational wealth and things of that sort, things like helping people communicate issues with one another within a software development engineering team—the more we will create complexity and additional problems, and the more we will fracture people's focus and ability to stay focused on what the underlying cause of the problem is, which is something human. And just as a side note, the fundamental idea that code is this ultimate arbiter of truth is terrible because if code was the ultimate arbiter of truth, I wouldn't have a job, Corey. [laugh]. I would be out of business so fast.Corey: Oh, yeah, it's great. It's—ugh, I—it feels like that's a naive perspective that people tend to have early in their career, and Lord knows I did. Everything was so straightforward and simple, back when I was in that era, whereas the older I get, the more the world is shades of nuance.Sean: There are cases where technology can help, but I tend to find those a very specific class of solutions, and even then they can only assist a human with maybe providing some additional context. This is an idea from a Seeking SRE book that I love to reference—I think it's, like, the first chapter—the Chief of Netflix SRE, I think it is, he talks about this is this, solving problems is this thing of relaying context, establishing context—and he focused a lot less on the technology side, a lot more of the human side, and brings in, like, “The technology can help this because it can give you a little bit better insight of how to communicate context, but context is valuable, but you're still going to have to do some talking at the end of the day and establish these human relationships.” And I think that technology can help with a very specific class of insight or context issues, but I would like to reemphasize that is a very specific class, and very specific sort, and most of the human problems we're trying to solve the technology don't fall in there.Corey: I think that's probably a great place for us to call it an episode. I really appreciate the way you view these things. I think that you are one of the most empathetic people that I find myself talking to on an ongoing basis. If people want to learn more, where's the best place to find you?Sean: You can find me on Twitter at S-C—underscore—code, capital U, capital M. That's probably the best place to find me. I'm most frequently on there.Corey: We will, of course, include links to that in the [show notes 00:32:37].Sean: And then, of course, my LinkedIn is not a bad place to reach out. So, you can probably find me there, Sean Corbett, working at TheZebra. And as always, you can reach me at scorbett@thezebra.com. That is my work email; feel free to email me there if you have any questions.Corey: And we will, of course, put links to all of that in the [show notes 00:33:00]. Sean, thank you so much for taking the time to speak with me today. I really appreciate it.Sean: Thank you.Corey: Sean Corbett, Senior Software Development Engineer in Test at TheZebra—because there's only one. 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 along with an angry ranting comment about how absolutely code speaks, and it is the ultimate arbiter of truth, and oh wait, what's that the FBI is at the door make some inquiries about your recent online behavior.Corey: If your AWS bill keeps rising and your blood pressure is doing the same, then you need The Duckbill Group. We help companies fix their AWS bill by making it smaller and less horrifying. The Duckbill Group works for you, not AWS. We tailor recommendations to your business and we get to the point. Visit duckbillgroup.com to get started.Announcer: This has been a HumblePod production. Stay humble.

During the economic downturn in 2008, Sean Gu's parents realized that their son's education was the best investment they could ever make. At that point, they decided to enroll him at Cranbrook and he received more than just an education. Sean reflects on Wilderness and other formative experiences with band, cross-country, and eventually weight lifting. In this episode, Sean talks about his experimentation with hobbies and building discipline. Join him and Robert as they discuss trying different things and finding direction in personal life.About the Guest:Sean Gu (‘15) is a talented guitarist, history buff, ballroom dancer, and weightlifter. When he's not training for his next competition he's working as a Software Development Engineer at Amazon.Reach Him At:Sean Gu on LinkedInSean Gu on InstagramSelected Quotes:Cranbrook's Role on His Weightlifting Journey[00:09:28] I started going into the Cranbrook weight room. I think a lot of other guys can probably relate to that. You know, The ones who were also at Cranbrook. I remember seeing Jon Tenuta up there. And, he actually showed me the basics. I just started there and then I figured everything else out on my own. That's more or less how it started.On Finding a Mentor[00:16:17] What attracted me to weightlifting the most, in the beginning, was everything is under your control. Yes, there are other factors involved that could affect your performance —your coach, your teammates, or your training environment. But at the end of the day, if you put in the work, it's up to you. To do what you need to do on the competition platform like no one else can do for you. It's completely up to you… I think that is what attracted me to weightlifting because it was somewhat black and white in the sense. That, yes, it's hard, but all of it is within your control. You dictate the outcome, essentially.Keeping True to Yourself[00:20:56] If I could go back, pull my freshman year self aside and, sit him down and give him some advice, I would say, ‘Don't be pressured into doing things just because everyone else is doing it'. Because when we began our college journey after high school, there's that image or perception of what college kids are supposed to do. What their experience is supposed to be like. I feel during my freshman year — being lost the way that I was — I went along and did many things that I didn't genuinely enjoy. Just because everyone else did it. I think looking back, I would say, ‘Obviously, you need to step outside your comfort zone and try new things'. But at the end of the day, if you genuinely don't enjoy doing something and you think that it's not like a good use of your time, don't be afraid to like, not do it . Even if, even if it goes against the image that's sort of portrayed of what your college experience should be. I think at the end of the day, you need to sort of muster up the confidence to decide what it is exactly that you want to do, as opposed to just following along and doing what the majority does.

In this episode, Dave chats with Danielle Kucera, Sr. Product Marketing Manager, AWS Marketing, and Adam Ruka, Software Development Engineer for AWS SDKs and Tools. They cover the launch of Construct Hub, a simplified way of finding and using open-source Cloud Development Kit (CDK) libraries, as well as all things CDK V2, including new changes to the core libraries, payload size, as well as the new CDK Watch command. Danielle on LinkedIn: https://www.linkedin.com/in/danielleraekucera/ Adam on Twitter: https://twitter.com/adam_ruka Adam on LinkedIn: https://www.linkedin.com/in/adamruka/ Adam's Blog: https://www.endoflineblog.com -- AWS Cloud Development Kit (CDK) - https://aws.amazon.com/cdk/ Construct Hub - https://constructs.dev/ CDK Git Repo - https://github.com/aws/aws-cdk Increasing Development Speed with CDK Watch - https://go.aws/3EN8Vgi Best Practices for Discoverability of a Construct Library on Construct Hub - https://go.aws/33koFd3 CDK V1 Maintenance Policy: https://go.aws/3pKrvj8 ----------- Connect with Us on Twitter: Emily on Twitter: https://twitter.com/editingemily Dave on Twitter: https://twitter.com/thedavedev Subscribe: Amazon Music: https://music.amazon.com/podcasts/f8bf7630-2521-4b40-be90-c46a9222c159/aws-developers-podcast Apple Podcasts: https://podcasts.apple.com/us/podcast/aws-developers-podcast/id1574162669 Google Podcasts: https://podcasts.google.com/feed/aHR0cHM6Ly9mZWVkcy5zb3VuZGNsb3VkLmNvbS91c2Vycy9zb3VuZGNsb3VkOnVzZXJzOjk5NDM2MzU0OS9zb3VuZHMucnNz Spotify: https://open.spotify.com/show/7rQjgnBvuyr18K03tnEHBI TuneIn: https://tunein.com/podcasts/Technology-Podcasts/AWS-Developers-Podcast-p1461814/ RSS Feed: https://feeds.soundcloud.com/users/soundcloud:users:994363549/sounds.rss

Horane Haughton is a Managing Partner at Virtus Investment Group, a Real Estate Investment company based in North Carolina. I connected with Horane while he moderated one of Clubhouse's chatrooms and discovered he was a wealth of REI knowledge. An ex-Marine, he followed his time in the military as a Software Development Engineer, working for large corporations including Monitech Inc and Deutsche Bank. Horane currently creates systems and processes for Virtus to understand the real estate market better and ensure his company's growth in the face of fluctuating economic conditions. In today's episode, Horane joins me to discuss his early success in wholesale investment and why such early success can weaken business planning foundations. He discusses the lessons learned when he and his business partner 'scaled too fast,' leaving them with a lot of bills and not a lot of deals. Horane reveals how they had to reset their mindset in the property game and learn how to construct a solid plan of action and formulate strategic planning to understand if and when they were spending too much money. He also explains how a mentor in the business can help you cancel out the noise of the YouTubers' advice and save your business a lot of money in the long run. "One of the biggest challenges is to try to reset your mindset. Reset. And learn the things that you didn't learn in the beginning" Horane Houghton "One of the things that we learned is that our backyard is not always the best yard to play" – Horane Houghton "Not scaling properly - for us - was a failure to actually put a proper plan of action in place" – Horane Houghton "You can't just throw money at the wall and say, 'Hey you know I've $10,000 I want to make $100,000. That's just not how it works. You still have to have a proper plan" – Horane Houghton "For me, scaling is understanding your market -understanding how you're approaching your market every single day" – Horane Houghton "Now listen. Pay that extra dollar to get that mentorship. Trust me. It will save you a lot of money" – Horane Houghton This week on Flip Talk: Resources Mentioned: Connect with Horane Haughton: Rate, Review, Learn and Share Thanks for tuning into the FlipTalk podcast! If you enjoyed this episode and want to learn even more about what it takes to build a 7-figure real estate business, head over to iTunes and subscribe to the show. Don't forget to tune into our other show: FlipTalk's Rookie PlayBook and share your favorite episodes on social media to help other new investors learn what it takes to grow a successful business in the real estate investing industry. Join the community of FlipTalk fans on Facebook, YouTube,  and visit our website for even more content, information, and resources about real estate investing.

Horane Haughton is a Managing Partner at Virtus Investment Group, a Real Estate Investment company based in North Carolina. I connected with Horane while he moderated one of Clubhouse's chatrooms and discovered he was a wealth of REI knowledge. An ex-Marine, he followed his time in the military as a Software Development Engineer, working for large corporations including Monitech Inc and Deutsche Bank. Horane currently creates systems and processes for Virtus to understand the real estate market better and ensure his company's growth in the face of fluctuating economic conditions. In today's episode, Horane joins me to discuss his early success in wholesale investment and why such early success can weaken business planning foundations. He discusses the lessons learned when he and his business partner 'scaled too fast,' leaving them with a lot of bills and not a lot of deals. Horane reveals how they had to reset their mindset in the property game and learn how to construct a solid plan of action and formulate strategic planning to understand if and when they were spending too much money. He also explains how a mentor in the business can help you cancel out the noise of the YouTubers' advice and save your business a lot of money in the long run. "One of the biggest challenges is to try to reset your mindset. Reset. And learn the things that you didn't learn in the beginning" Horane Houghton "One of the things that we learned is that our backyard is not always the best yard to play" – Horane Houghton "Not scaling properly - for us - was a failure to actually put a proper plan of action in place" – Horane Houghton "You can't just throw money at the wall and say, 'Hey you know I've $10,000 I want to make $100,000. That's just not how it works. You still have to have a proper plan" – Horane Houghton "For me, scaling is understanding your market -understanding how you're approaching your market every single day" – Horane Houghton "Now listen. Pay that extra dollar to get that mentorship. Trust me. It will save you a lot of money" – Horane Houghton This week on Flip Talk: Why early success can teach you the wrong lessons in Wholesale Investing What happens when you scale too fast What it means to 'scale' properly What your Plan of Action for scaling should entail How seeking out a Mentor will save you a lot of money Why cold calling is Horane's marketing tool of choice Resources Mentioned: Clubhouse Connect with Horane Haughton: Virtus Investment Group Website Horane Haughton on Instagram Horane Haughton on LinkedIn Horane Haughton on Facebook Rate, Review, Learn and Share  Thanks for tuning into the FlipTalk podcast! If you enjoyed this episode and want to learn even more about what it takes to build a 7-figure real estate business, head over to iTunes and subscribe to the show. Don't forget to tune into our other show: FlipTalk's Rookie PlayBook and share your favorite episodes on social media to help other new investors learn what it takes to grow a successful business in the real estate investing industry.  Join the community of FlipTalk fans on Facebook, YouTube,  and visit our website for even more content, information, and resources about real estate investing. 

Horane Haughton is a Managing Partner at Virtus Investment Group, a Real Estate Investment company based in North Carolina. I connected with Horane while he moderated one of Clubhouse's chatrooms and discovered he was a wealth of REI knowledge. An ex-Marine, he followed his time in the military as a Software Development Engineer, working for large corporations including Monitech Inc and Deutsche Bank. Horane currently creates systems and processes for Virtus to understand the real estate market better and ensure his company's growth in the face of fluctuating economic conditions. In today's episode, Horane joins me to discuss his early success in wholesale investment and why such early success can weaken business planning foundations. He discusses the lessons learned when he and his business partner 'scaled too fast,' leaving them with a lot of bills and not a lot of deals. Horane reveals how they had to reset their mindset in the property game and learn how to construct a solid plan of action and formulate strategic planning to understand if and when they were spending too much money. He also explains how a mentor in the business can help you cancel out the noise of the YouTubers' advice and save your business a lot of money in the long run. "One of the biggest challenges is to try to reset your mindset. Reset. And learn the things that you didn't learn in the beginning" Horane Houghton "One of the things that we learned is that our backyard is not always the best yard to play" – Horane Houghton "Not scaling properly - for us - was a failure to actually put a proper plan of action in place" – Horane Houghton "You can't just throw money at the wall and say, 'Hey you know I've $10,000 I want to make $100,000. That's just not how it works. You still have to have a proper plan" – Horane Houghton "For me, scaling is understanding your market -understanding how you're approaching your market every single day" – Horane Houghton "Now listen. Pay that extra dollar to get that mentorship. Trust me. It will save you a lot of money" – Horane Houghton This week on Flip Talk: Why early success can teach you the wrong lessons in Wholesale Investing What happens when you scale too fast What it means to 'scale' properly What your Plan of Action for scaling should entail How seeking out a Mentor will save you a lot of money Why cold calling is Horane's marketing tool of choice Resources Mentioned: Clubhouse Connect with Horane Haughton: Virtus Investment Group Website Horane Haughton on Instagram Horane Haughton on LinkedIn Horane Haughton on Facebook Rate, Review, Learn and Share  Thanks for tuning into the FlipTalk podcast! If you enjoyed this episode and want to learn even more about what it takes to build a 7-figure real estate business, head over to iTunes and subscribe to the show. Don't forget to tune into our other show: FlipTalk's Rookie PlayBook and share your favorite episodes on social media to help other new investors learn what it takes to grow a successful business in the real estate investing industry.  Join the community of FlipTalk fans on Facebook, YouTube,  and visit our website for even more content, information, and resources about real estate investing. 

Madhavan Malolan is the Founder & CEO of Questbook, an app that makes it easy for busy professionals to up-skill other professionals with bite-sized courses. He has also worked as a Software Development Engineer at Microsoft.On this episode of The Shape of Work, we picked his brain to have a litany of tactical insights on Web3, blockchain & more. We discuss with Madhavan:The most common recruiting challenges and how they overcame thatThe no-code potential in the Web3 worldDAO & its future/potentialHow to assess candidates for job-fitEpisode Highlights:Building a crypto community on Discord Madhavan Malolan shares his snippets about his journey of building a crypto company and nurturing an active community on Discord, a platform with a large population of cryptocurrency enthusiasts. Issues in the Web3 and Crypto space The Questbook founder talks about the potential of cryptocurrencies in a world where even highly educated professionals are not fully aware of crypto and Web3 and what can be built using these digital currencies.Incentivizing community members in the context of Web3Madhavan strongly feels that without incentivizing the community members, it is impossible to sustain a business that is so heavily dependent on its community. He talks about how individuals are now upskilling in the field of Web3 and cryptocurrencies, and they use Questbook as a marketplace to find opportunities. Recruitment challenges faced by companies dealing with these technologies While it's a great time for product managers and user experience designers to establish themselves in the tech market, there aren't sufficient Web3 developers in the ecosystem. It is why Madhavan has built Questbook - to enable developers to learn Web3 technology. As a company, Questbook is focusing on helping developers upskill and reach their potential to survive in today's thriving digital economy. Future and existing potential of DAOs DAO at its fundamental level facilitates decentralization of decision-making. Madhavan shares his thoughts on how Facebook, a highly centralized platform where Mark Zuckerburg takes all the decisions, is likely to move faster compared to DAO. He sheds light on how the need of the hour is to design economic incentives such that companies achieve both decentralization and speed. Choosing blockchain to build products Every blockchain has its advantages and disadvantages. Therefore, you need to choose them based on the use cases depending upon whether you prioritize security, faster transactions, or other things. For example, to achieve high security, bitcoin is a suitable blockchain. Comparison between ETH and ENS Madhavan says that ENS solves the issue of sharing addresses that one encounters while sharing an address on ETH. ENS is gaining prominence over other projects because of its emphasis on community, people, and the non-greedy approach of founders across tech companies. Future of NFT and Web3Though people buy NFTs only for further sale, Madhavan feels that it has got huge potential ahead. He also believes that NFTs will not reach millions of users but instead will be used as an identity or as credentials by professionals.Follow Madhavan on LinkedIn.

Horane Haughton is a Managing Partner at Virtus Investment Group, a Real Estate Investment company based in North Carolina. I connected with Horane while he moderated one of Clubhouse's chatrooms and discovered he was a wealth of REI knowledge. An ex-Marine, he followed his time in the military as a Software Development Engineer, working for large corporations including Monitech Inc and Deutsche Bank. Horane currently creates systems and processes for Virtus to understand the real estate market better and ensure his company's growth in the face of fluctuating economic conditions. In today's episode, Horane joins me to discuss his early success in wholesale investment and why such early success can weaken business planning foundations. He discusses the lessons learned when he and his business partner 'scaled too fast,' leaving them with a lot of bills and not a lot of deals. Horane reveals how they had to reset their mindset in the property game and learn how to construct a solid plan of action and formulate strategic planning to understand if and when they were spending too much money. He also explains how a mentor in the business can help you cancel out the noise of the YouTubers' advice and save your business a lot of money in the long run. "One of the biggest challenges is to try to reset your mindset. Reset. And learn the things that you didn't learn in the beginning" Horane Houghton "One of the things that we learned is that our backyard is not always the best yard to play" – Horane Houghton "Not scaling properly - for us - was a failure to actually put a proper plan of action in place" – Horane Houghton "You can't just throw money at the wall and say, 'Hey you know I've $10,000 I want to make $100,000. That's just not how it works. You still have to have a proper plan" – Horane Houghton "For me, scaling is understanding your market -understanding how you're approaching your market every single day" – Horane Houghton "Now listen. Pay that extra dollar to get that mentorship. Trust me. It will save you a lot of money" – Horane Houghton This week on Flip Talk: Resources Mentioned: Connect with Horane Haughton: Rate, Review, Learn and Share Thanks for tuning into the FlipTalk podcast! If you enjoyed this episode and want to learn even more about what it takes to build a 7-figure real estate business, head over to iTunes and subscribe to the show. Don't forget to tune into our other show: FlipTalk's Rookie PlayBook and share your favorite episodes on social media to help other new investors learn what it takes to grow a successful business in the real estate investing industry. Join the community of FlipTalk fans on Facebook, YouTube,  and visit our website for even more content, information, and resources about real estate investing.

Horane Haughton is a Managing Partner at Virtus Investment Group, a Real Estate Investment company based in North Carolina. I connected with Horane while he moderated one of Clubhouse's chatrooms and discovered he was a wealth of REI knowledge. An ex-Marine, he followed his time in the military as a Software Development Engineer, working for large corporations including Monitech Inc and Deutsche Bank. Horane currently creates systems and processes for Virtus to understand the real estate market better and ensure his company's growth in the face of fluctuating economic conditions. In today's episode, Horane joins me to discuss his early success in wholesale investment and why such early success can weaken business planning foundations. He discusses the lessons learned when he and his business partner 'scaled too fast,' leaving them with a lot of bills and not a lot of deals. Horane reveals how they had to reset their mindset in the property game and learn how to construct a solid plan of action and formulate strategic planning to understand if and when they were spending too much money. He also explains how a mentor in the business can help you cancel out the noise of the YouTubers' advice and save your business a lot of money in the long run. "One of the biggest challenges is to try to reset your mindset. Reset. And learn the things that you didn't learn in the beginning" Horane Houghton "One of the things that we learned is that our backyard is not always the best yard to play" – Horane Houghton "Not scaling properly - for us - was a failure to actually put a proper plan of action in place" – Horane Houghton "You can't just throw money at the wall and say, 'Hey you know I've $10,000 I want to make $100,000. That's just not how it works. You still have to have a proper plan" – Horane Houghton "For me, scaling is understanding your market -understanding how you're approaching your market every single day" – Horane Houghton "Now listen. Pay that extra dollar to get that mentorship. Trust me. It will save you a lot of money" – Horane Houghton This week on Flip Talk: Why early success can teach you the wrong lessons in Wholesale Investing What happens when you scale too fast What it means to 'scale' properly What your Plan of Action for scaling should entail How seeking out a Mentor will save you a lot of money Why cold calling is Horane's marketing tool of choice Resources Mentioned: Clubhouse Connect with Horane Haughton: Virtus Investment Group Website Horane Haughton on Instagram Horane Haughton on LinkedIn Horane Haughton on Facebook Rate, Review, Learn and Share  Thanks for tuning into the FlipTalk podcast! If you enjoyed this episode and want to learn even more about what it takes to build a 7-figure real estate business, head over to iTunes and subscribe to the show. Don't forget to tune into our other show: FlipTalk's Rookie PlayBook and share your favorite episodes on social media to help other new investors learn what it takes to grow a successful business in the real estate investing industry.  Join the community of FlipTalk fans on Facebook, YouTube,  and visit our website for even more content, information, and resources about real estate investing. 

Horane Haughton is a Managing Partner at Virtus Investment Group, a Real Estate Investment company based in North Carolina. I connected with Horane while he moderated one of Clubhouse's chatrooms and discovered he was a wealth of REI knowledge. An ex-Marine, he followed his time in the military as a Software Development Engineer, working for large corporations including Monitech Inc and Deutsche Bank. Horane currently creates systems and processes for Virtus to understand the real estate market better and ensure his company's growth in the face of fluctuating economic conditions. In today's episode, Horane joins me to discuss his early success in wholesale investment and why such early success can weaken business planning foundations. He discusses the lessons learned when he and his business partner 'scaled too fast,' leaving them with a lot of bills and not a lot of deals. Horane reveals how they had to reset their mindset in the property game and learn how to construct a solid plan of action and formulate strategic planning to understand if and when they were spending too much money. He also explains how a mentor in the business can help you cancel out the noise of the YouTubers' advice and save your business a lot of money in the long run. "One of the biggest challenges is to try to reset your mindset. Reset. And learn the things that you didn't learn in the beginning" Horane Houghton "One of the things that we learned is that our backyard is not always the best yard to play" – Horane Houghton "Not scaling properly - for us - was a failure to actually put a proper plan of action in place" – Horane Houghton "You can't just throw money at the wall and say, 'Hey you know I've $10,000 I want to make $100,000. That's just not how it works. You still have to have a proper plan" – Horane Houghton "For me, scaling is understanding your market -understanding how you're approaching your market every single day" – Horane Houghton "Now listen. Pay that extra dollar to get that mentorship. Trust me. It will save you a lot of money" – Horane Houghton This week on Flip Talk: Why early success can teach you the wrong lessons in Wholesale Investing What happens when you scale too fast What it means to 'scale' properly What your Plan of Action for scaling should entail How seeking out a Mentor will save you a lot of money Why cold calling is Horane's marketing tool of choice Resources Mentioned: Clubhouse Connect with Horane Haughton: Virtus Investment Group Website Horane Haughton on Instagram Horane Haughton on LinkedIn Horane Haughton on Facebook Rate, Review, Learn and Share  Thanks for tuning into the FlipTalk podcast! If you enjoyed this episode and want to learn even more about what it takes to build a 7-figure real estate business, head over to iTunes and subscribe to the show. Don't forget to tune into our other show: FlipTalk's Rookie PlayBook and share your favorite episodes on social media to help other new investors learn what it takes to grow a successful business in the real estate investing industry.  Join the community of FlipTalk fans on Facebook, YouTube,  and visit our website for even more content, information, and resources about real estate investing. 

ConfirmTkt is an online train ticket discovery and booking engine that delivers a seamless search and booking experience to travelers. They are now acquired by an online travel aggregator ixigo for an undisclosed amount. Dinesh Kumar Kotha is the Co-founder & CEO of ConfirmTkt. Before starting ConfirmTkt he was a Software Development Engineer in a company known as o9. He also worked as an Application Developer(Java) in IBM. Here's what you can learn from this episode: What was his role in o9 Solutions and IBM? How was the idea behind his first startup Meterup conceptualized? When did he realize Meterup was not going to scale? How was Confirmtkt born? What was the trigger that told him to leave his well-established job and work on Confirmtkt full-time? How did he meet his first investor- Pravin? What were his expectations when he came to pitch at Nasscom? How much money did he raise in the timeframe of Confirmtkt? How did Dinesh cut the burn rate in the initial stage and make a new path for the company? How did he build his first 100 users? How did he go from a 1k a day company to a 3crore a day company? How did the ixigo conversation take place? How did he work out the modalities with the acquisition during the pandemic? What are the 3 things he is proud of during his tenure with Confirmtkt? If he had a chance to do it all over again what would he do differently? --- Send in a voice message: https://anchor.fm/damanitalks/message Support this podcast: https://anchor.fm/damanitalks/support

Monica and Taylor chat with badass engineer and fellow bootcamp grad Ellie Demis, currently a Software Development Engineer 2 at Amazon. Ellie shares her philosophy on tackling salary negotiation and challenges the advice to "always negotiate". Join us as we work through the anxiety brought up by uncomfortable conversations and discuss how to find the confidence to ask for what you're worth.

What does the perfect resume look like? What works and what doesn’t? Here’s a tip, there is no one size fits all approach. Resumes are supposed to tell your accomplishments: what you did, how you did it and what was the result. But everyone has different skills, different job history, and different problems they solved. As a former VP of Amazon (Newly Retired), watch Ethan Evans talk about what makes a great resume. Learn simple changes that you can implement now that could get you more interviews and job offers. Over the years Ethan has reviewed over 2,500 resumes and can tell you what recruiters are looking for and more importantly, what hiring managers want.

What does an Amazon software development engineer do? What is the interview process like? This week I had the chance to speak to Kamini Saldanha about her journey as a new grad software development engineer! --- This episode is sponsored by · Anchor: The easiest way to make a podcast. https://anchor.fm/app Support this podcast: https://anchor.fm/tech-gal-diaries/support

Joe Thomas is a Software Development Engineer, former President of the UBC Blockchain Club, and Bitcoin enthusiast who has spent the last 5 years studying the technical nature of Bitcoin. We talk about what BTC is, and how the market works. I've also partnered up with Reza Varzidehkar from https://ovou.com/ to allow my listeners to get a discount off the card. Discount code: joe10 I've also partnered up with Gordon Patrick Newell from http://bondbourne.com/ for discounts on his leadership coaching and training. Discount code: earnit Intro and Outro: IG: YouJayBeats, Soundcloud: soundcloud.com/user-586386126

Kodluyoruz Alchemist'in yeni bölümünde, Stanford Üniversitesi'nde misafir araştırmacı olarak araştırmalarını sürdüren ve Amazon.com'da Software Development Engineer II olarak çalışan Emrah Budur ile birlikte yazılım kariyeri süresince zor tercihlerin üstesinden gelmeyi, kariyer tercihlerini yaparken nelere dikkat etmek gerektiğini ve de Emrah Budur'un kendi kariyer ve eğitim geçmişini konuştuk. KodluyoruzTürkiye'de yapay zeka ekosistemini yeşertmek, bu alanda çalışacak gençleri yetiştirmek için dünyanın önde gelen 13 uzman/girişimci/akademisyenini Kodluyoruz Yapay Zeka Danışma Kurulu'nda bir araya getiriyor. Sunucular: Aykut İbrişim :Kodluyoruz & Podfresh Kurucu Ortağı Gizem Aşıcı: Kodluyoruz Community Engagement Specialist Konuklar: Emrah Budur: Amazon Yayın Sponsoru: Garanti BBVA Podcast Prodüksiyon: Podfresh

When talking about data, we usually think about big data and scale, and what do we do next. Such limits are sometimes a good problem to have. In this talk, we'll discuss our approach to this situation using the Ingress Controller. Laurent is a Software Development Engineer at Adobe. He started in Dev, went to Ops (sometimes referred to as "SRE" these days), then became a manager and now he's back to being an individual contributor. This is all on purpose: he likes to do new things! He grew up in Marseille, France (go Olympique de Marseille!), but moved to the US right after college and actually he's never had a real job in Europe... When he isn't coding, he likes playing soccer (although he's been doing a lot of "watching" since March 2020).

In this episode we talk to Ana, a Software Development Engineer at Gousto.What we cover:What is software development and software engineeringHow it works in GoustoWhat is the typical route into software engineeringWhat other roles are there in a tech companyWho is the right person for a software engineering jobIn this episode, we learn that you don't just have to be good at Maths to become a software engineer, but you need a logical thinking brain.Ana breaks down the different roles within a tech company, and explains her role very clearly. It's a fun and progressively industry, and if you dig a bit deep into this world, you'll learn there are sub-sectors within every other industry.Gousto website - https://www.gousto.co.uk/Handy links:Getting into software engineering - https://nationalcareers.service.gov.uk/job-profiles/software-developerOther handy links - https://www.theguardian.com/careers/ten-signs-career-coding-software-development-right-for-youQuestions and comments – sam@beginanddiscover.com Hosted on Acast. See acast.com/privacy for more information.

Сайн уу манайхаан, Германд IT-ын чиглэлээр сурахаар сонирхож байгаа бүх хүмүүстээ зориулаад энэхүү дугаараа бэлдлээ. Энэ удаагийн маань зочиноор "Дэлхийн 50 гаруй улсад 270.000 гаруй ажилчинтай Consulting, Digital transformation, Technology болон Engineer-ийн чиглэлээр үйл ажиллагаагаа явуулдаг Capgemini компаний Software Development Engineer Г.Наранжаргал"-ыг уриж: - Германд компьютерын шинжлэх ухааны чиглэлээр бакалавр болон мастераар сурсан туршлага - Олон улсад үйл ажиллагаагаа явуулдаг Siemens болон Capgemini компанид ажиллаж, хуримтуулсан туршлага - Герман улсын соёлоос юуг өөртөө шингээж авч болох тухай - IT-ын салбарт ажиллахад эрэгтэй, эмэгтэй хүмүүсийн ялгаа юу байдаг вэ зэрэг маш олон гоё сэдвүүдийн хүрээнд ярилцсан байгаа шүү. Та бүхэн маань хэрэгтэй мэдээллээ авна гэдэгт найдаж байна.

Why being a Tech-God is not enough. Thoughts from Shraddha Patel, CMU Grad, and a Business Analytics Consultant at Servian, Australia.Our aim of these webinars is to connect you with the brightest minds in the field of Machine Learning/Data Science so that you can learn how to break into the field and build an incredible career!About the Speaker:Shraddha is a recent graduate of CMU with a focus on Business Intelligence and Data Analytics. She has work experience as a Software Development Engineer and Machine Learning Engineer and shared with us some of the insights as she paved her way to being a consultant.Hosted by:Jay Shah: https://www.linkedin.com/in/shahjay22/You can reach out to https://www.public.asu.edu/~jgshah1/ for any queries.Stay tuned for upcoming webinars!***Disclaimer: The information contained in this video represents the views and opinions of the speaker and does not necessarily represent the views or opinions of any institution. It does not constitute an endorsement by any Institution or its affiliates of such video content.***

This Episode My guest for this Twitch stream was Ryan Barker, Former EverQuest Game Designer & Lead Designer and EQ Next Content Lead. Ryan has also worked at Intrepid Studios as a Programmer on Ashes of Creation, and (at the time of this posting) is at Amazon Game Studios as a Software Development Engineer. About This Format I'm a former EQ designer, turned Producer and games executive, who currently streams at: https://www.twitch.tv/alovingrobot I'm using this stream as a means of reconnecting with my old colleagues, tapping into the nostalgia of a great era in our lives (and MMO gaming), and ensuring that some of the fun stories of the past aren't forgotten. Video available on Twitch & YouTube.

Ever wondered what it's like working for one of the most influential companies in the world? Interested in life as a FAANG software engineer? Listen now to find out! --- Support this podcast: https://podcasters.spotify.com/pod/show/careerbites.ohmaneats/support

CRUXPay is a decentralized protocol for blockchain naming and payment system. It enables users to create CRUX ID, which can be linked to the user's blockchain addresses. Using CRUX ID, users will be able to send, receive, and request payment. Additionally, users will be able to securely connect to any service/dApps on any device anywhere in the world. The company insists that CRUX ID is completely secure and tamper-proof. It is generated by your wallet using your local public/private keys and is secured by hash power of Bitcoin by registering your CRUX ID on the bitcoin network. But I felt compelled to find out more about what makes this solution different than all the others out there. Ashish Singal, the Co-Founder, and CEO of CRUXPay is also a hacker to the core and has won almost every major Hackathon in India, including those hosted by Sequoia, Google, Amazon, and LinkedIn. While working at Amazon as a Software Development Engineer in 2014, he led the internal team in building Amazon Prime's 1-hour delivery model. Ashish Singal joins me on the Tech Talks Daily podcast in a conversation about the trends and technology that are shaping the broader adoption of cryptocurrency payments. We also discuss the potential pitfalls or otherwise of Libra's digital currency adoption. I learn how crypto payments are outpacing modern payments technology and how crypto payments are a potential disruptor to modern banking systems.

Machine learning isn't just for the Googles and Facebooks of the world. But how can startups (or even, growth equity investment firms

This session will be all about exciting Foundations/Platform-related content that we'll announce at .conf19. We can't tell you about it now, but trust us — it's awesome. Speaker(s) Geoffrey hendrey, Sr Principal Engineer, splunk Aditi Nath, Software Development Engineer, Splunk Slides PDF link - https://conf.splunk.com/files/2019/slides/FN1735.pdf?podcast=1577146226 Product: Splunk Enterprise, Splunk Developer Cloud Track: Foundations/Platform Level: Intermediate

This session will be all about exciting Foundations/Platform-related content that we'll announce at .conf19. We can't tell you about it now, but trust us — it's awesome. Speaker(s) Geoffrey hendrey, Sr Principal Engineer, splunk Aditi Nath, Software Development Engineer, Splunk Slides PDF link - https://conf.splunk.com/files/2019/slides/FN1735.pdf?podcast=1577146254 Product: Splunk Enterprise, Splunk Developer Cloud Track: Foundations/Platform Level: Intermediate

This session will be all about exciting Foundations/Platform-related content that we'll announce at .conf19. We can't tell you about it now, but trust us — it's awesome. Speaker(s) Geoffrey hendrey, Sr Principal Engineer, splunk Aditi Nath, Software Development Engineer, Splunk Slides PDF link - https://conf.splunk.com/files/2019/slides/FN1735.pdf?podcast=1577146203 Product: Splunk Enterprise, Splunk Developer Cloud Track: Foundations/Platform Level: Intermediate

This session will be all about exciting Foundations/Platform-related content that we'll announce at .conf19. We can't tell you about it now, but trust us — it's awesome. Speaker(s) Geoffrey hendrey, Sr Principal Engineer, splunk Aditi Nath, Software Development Engineer, Splunk Slides PDF link - https://conf.splunk.com/files/2019/slides/FN1735.pdf?podcast=1577146230 Product: Splunk Enterprise, Splunk Developer Cloud Track: Foundations/Platform Level: Intermediate

Ushashi Chakraborty is a Director of Engineering for Backend Engineering at Mode Analytics in San Francisco. She moved to California in October 2018 from Chicago where she worked in Groupon for 5 years as an Engineering Manager for Consumer Applications and before that as a Software Development Engineer in Test. She has also worked in Microsoft and Thomson Reuters. She holds a Masters degree in Computer Science from North Dakota State University.   Ushashi has been involved with theater since high school and, especially, with improv since 2015. She is a Second City Training Center, Chicago alumni and has performed improv, sketch and stand up across several small theaters in Chicago.   Ushashi has spoken at major conferences including Grace Hopper Conference (SOL, 2014), expo:QA, Madrid, multiple chapters of CTO Summit in Nasdaq NYC, Austin, Chicago, and SF as well as in Leadership Summits by Code Climate, VerveCon, and General Assembly Breakfast Talk in 2018-19. She has recorded podcasts for the startupcto and frontier by gun.io. She, most recently, spoke at the Grace Hopper Conference, Orlando, 2019.  

Climate change has become a major risk factor for corporations. With groups like the Carbon Disclosure Project grading companies on their carbon footprint, employees, consumers and investors are taking note -- and woe to those CEOs who are slow to pick up the ball. “We’re gonna start to see some efforts where silence is complacency and it’s no longer acceptable,” says Joel Makower of Greenbiz. “You’re gonna have to get off the sidelines, to use the football metaphor, and get into the game one way or the other. And companies that aren’t, I think, are gonna find themselves facing some new pressures.” Visit climateone.org/watch-and-listen/podcasts for more information on today's episode. Guests: Sarah Read, User Experience Researcher for Prime Video, Amazon; Amazon Employees for Climate Justice Member Jacob Adamson, Software Development Engineer, Amazon; Amazon Employees for Climate Justice Member Joel Makower, Chairman and Executive Editor, GreenBiz Group Andrew Winston, Author, Green to Gold: How Smart Companies Use Environmental Strategy to Innovate, Create Value, and Build a Competitive Advantage (Yale University Press, 2006) Sara Law, Head of Global Initiatives, Carbon Disclosure Project Swami Venkataraman, Senior VP and Manager, ESG Analytics and Integration at Moody's Investors Service Portions of this program were recorded at The Commonwealth Club of California in San Francisco.

Lauren Granger began their career working with adults experiencing homelessness in Seattle.Lauren’s path to social work began on the night of Barack Obama’s inauguration when during his speech, he encouraged every person to get involved and volunteer. And that they did; Lauren dedicated the next decade of their life to giving back to their community. They managed low-income houses and did incredible work for individuals facing homelessness in Seattle's community. Pivoting from work in social service work, Lauren then attended Ada Developers Academy to learn to code and is a Software Development Engineer today at Amazon. They work on the Freetime team, which works to offer peace of mind for parents of young children. Lauren and I dive deep into the power of volunteerism and giving back to our communities. We discuss the importance of finding your people, active allyship, and how to use the professional skills we bring with us to the table from prior life/work experiences to succeed in our careers in tech. Resources: - Downtown Emergency Service Center - Ada Developers Academy - Find Lauren Granger on Twitter & LinkedIn

Nora is nonprofit fundraising professional turned coder. Today, she & I chat about her journey to tech after dedicating her career and education to mission-driven companies and how she used to perceive corporate Americas as the “dark-side.” She shares that it was in fact her therapist, who told her about Ada Developers Academy and encouraged her to pursue software development. She’s so thankful for that advice, as she has now discovered a way to blend her passion for tech with her love for helping people and does so today as a Software Development Engineer on a Kindle team at Amazon. We chat about the parallels between the fundraising and technical marketing industries and how many of the skills are transferrable from one to the other. This episode is not one to miss and Nora wants you to know that you have the right AND the ability to learn anything! Resources:Ada Developers AcademyYou are a Badass @NTPetesNora's LinkedIn

In this episode, Jeffrey speaks with Lori Lamkin, Microsoft’s Director of Program Management. She has been leading the Visual Studio Team Services program management since the conception of Team Foundation Server in 2002 — that’s 16 years in the space of better shipping software using Microsoft technologies! She led the transition of the team to Agile methodologies, to open source reuse, to Cloud services, and Azure.   Lori and Jeffrey discuss what’s next for Lori in and of her role as Director of PM, her strategy behind leading the big shift from VSTS to Azure DevOps, the current roles and duties within Microsoft Azure DevOps, what she sees as the biggest shift in progressing from Agile and adopting DevOps, and how DevOps has become more and more efficient.   Topics of Discussion: [:51] About today’s guest, Lori Lamkin! [1:18] Jeffrey welcomes Lori to the podcast. [3:22] Lori speaks about the strategy behind leading the big shift from VSTS to Azure DevOps. [5:42] What’s next for Lori in and out of her role as Director of PM? What has she been up to? [8:18] Lori gives some background on Azure DevOps history. [15:37] Lori talks about the current roles and duties within Microsoft Azure DevOps. [18:08] A word from Azure DevOps sponsor: Clear Measure. [18:34] How the organization for Azure DevOps is structured much differently than many other organizations. [20:38] What Lori thinks is the biggest shift in progressing from Agile and adopting DevOps. [23:34] Why everyone in Lori’s team is a Software Development Engineer. [25:08] Did Lori’s team used to have Systems Engineers (otherwise known as IT Pros)? [27:18] The broad set of skills that is required of the developers to operate the components of Azure DevOps that the Azure Data Center is running on. [28:55] The change in business with DevOps and how it has become more efficient. [31:21] Lori’s take on the culture change CEO Satya Nadella is driving as well as his 1ES (one engineering system) plan. [35:26] Is there no software Git can’t handle? [36:18] Where Lori suggests you further your learning after listening to this episode.   Mentioned in this Episode: Azure DevOpsAzure DevOps ServicesAzure Cloud Clear Measure (Sponsor) Microsoft Secrets: How the World's Most Powerful Software Company Creates Technology, Shapes Markets, and Manages People, by Michael A. Cusumano Satya Nadella on transforming Microsoft’s culture More about Satya’s One Engineering System initiativeTFVS AKA.MS/DevOps GitHub   Want to Learn More? Visit AzureDevOps.Show for show notes and additional episodes.   Follow Up with Our Guest: Lori Lamkin’s LinkedIn

Working technology for a political campaign involves the shortest timelines, tightest deadlines, and highest stakes you will likely ever encounter in a technology career. Come hear a tale of two political campaigns - a state measure campaign and a presidential campaign - and the application of both DevOps technologies and culture to move fast, pivot quickly, and hopefully win. One of the key challenges of politics - as well as DevOps in general - is harnessing automation without losing the critical human touch which moves hearts and changes minds. Learn how to find the line where too much automation (yes, there is such a thing) is counterproductive and you need to pull back to maintain a personal connection with voters, customers, employees, and more. You will also walk away knowing how to take the lessons and experience learned to future campaigns and projects - especially when your candidate, product, etc. does not end up winning. There is value - sometimes more value - in a loss as well as a win. Learn how to take what you can, iterate, and refine it for a future application.   Nell Shamrell-Harrington is a Software Development Engineer at Chef, focusing on the Habitat open source product. She is also CTO of Operation Code - a non-profit dedicated to teaching software engineer skills to Veterans that heavily creates and uses open source. Additionally, she is a technology volunteer for multiple political campaigns. She specializes in Chef, Ruby, Rails, Rust, DevOps, and Regular Expressions and has traveled the world speaking on these topics. Prior to entering the world of software development, she studied and worked in the field of Theatre.

Série Carreira Dev, episódio 04 - www.codenation.com.br Hey, Dev! A conversa desta semana é com a super Letícia Santos que hoje trabalha na Amazon como Software Development Engineer in Relational Database Services Team. Natural de Manaus e hoje vivendo em Seattle, EUA, ela tirou um tempinho para conversar com a gente sobre como foi sua jornada de universidade - startup - Amazon. Falamos sobre as experiências que a levaram ao cargo que se encontra hoje, o papel que o LinkedIn teve nisto e como mantém-se atualizada e constantemente em modo aprendizado. A conversa está demais - esperamos que curta tanto quanto nós! Se tiver alguma dúvida ou sugestão, aproveita para deixar nos comentários aqui embaixo, beleza? :)

“I joined Microsoft about 7 months ago. I am currently in the graphics drivers team, and previously was on the Direct3D (DirectX) team. Before Microsoft, I received a Master's in Game Science at University of Washington. Ask me about work as a graphics industry developer, Microsoft, or academic careers in games. My personal game projects ... Read more

It’s true. John spent thousands of hours reading books, writing code, and watching computer science lectures, all to prepare for his dream job interview at Google. When things didn't go his way, he shifted gears. Here's his story. Written by John Washam: https://twitter.com/startupnextdoor Read by Quincy Larson: https://twitter.com/ossia Original article: https://fcc.im/2ERJpuC Learn to code for free at: https://www.freecodecamp.org Intro music by Vangough: https://fcc.im/2APOG02 Transcript:  It’s true. I’ve spent thousands of hours reading books, writing code, and watching computer science lectures, all to prepare for the Google software engineer interview. How I Got Here I started programming in middle school, but when it came time for college I pursued a degree in Economics. My rationale was that there would be too many programmers looking for jobs by the time I graduated. Boy, I was wrong. Later, I joined the Army to become a programmer, but the recruiter talked me into a military intelligence position, and I spent the next two years studying the Korean language. I served in South Korea for 2 years afterward. Before I left the Army, I attempted to get back into programming and was surprised at the difficulty. I had learned BASIC in middle school and kept programming it through high school. But I restarted my programming studies with C++, and the leap was too large. I just couldn’t grasp it. I did enjoy making websites, however, but I used software with a Word-like interface that I used to publish my websites. I didn’t know how to make websites from scratch. After the Army, I decided to stay in Korea for a year and teach English. I used my nights and weekends to study web programming, using Perl, HTML, CSS (which was new at the time), JavaScript, and SQL. After a year of intense study, I landed a job in the Seattle area, and I’ve been here ever since. I’ve been a web developer now for 15 years. I’ve started 3 companies, 2 of which are still running and generating revenue. I’ve worked at large and small companies, helped startups launch and grow, and recruited and managed teams. I’ve been a product manager, a CEO, a designer, and a marketer. I’ve had a successful career and learned a lot along the way. But I’m not done yet. Seeking a Career Change Remember the part where I didn’t get a computer science degree? It has made a difference. A few years ago, I thought I could get hired anywhere. I thought I was hot stuff: the elusive full-stack web developer. But during my job search in 2013, I realized my skills were lacking. I had spent so much time chasing dollars by running startups in my spare time, that I had let my skills atrophy. I hadn’t kept up with technology. For years, I had learned just enough to get by. I had a wide skill set but wasn’t an expert in anything. Don’t get me wrong, I could still get hired, but not in the technologies or areas I wanted to work in. I could get hired for areas where the tech stack was somewhat outdated, like me. There’s big money in there, but I didn’t see exciting prospects. The realization reached its peak last year at a career fair. I was interested in perhaps working for one of the local companies that were startup labs run by venture capital firms. However, the fact that I lacked a computer science degree, and the skills and knowledge that accompany such a degree, meant I didn’t have a chance. I was working full-time on my businesses at the time, and still am today. At the beginning of 2016, I decided it was time to make a career change from web developer to software engineer. I would need to study hard and practice in order to compress a computer science degree into a few months, but once I did, I could start a new career. You may not see web development and software engineering as different positions. Both involve programming and craftsmanship, but software engineering adds to it knowledge of data structures and algorithms, compiled languages, memory considerations, and understanding the impact of coding and architecture decisions on the machines where they reside. Large companies that hire for software engineering positions expect candidates to have this knowledge. I reached out to an acquaintance who works at Google and asked him questions about his experience at the company. I had been reading How Google Works and was pretty familiar with Google already. Through another contact, I received a copy of Google’s coaching notes that are provided to interview candidates. This became the basis of my study plan. Google is a pretty awesome place to work, but before I even knew that, Google was my goal. Why Google? Google sets a very high bar for hiring. They want to hire only the best. So if I set my sights high (getting hired at Google), I’ll still be quite hireable elsewhere even if I’m not selected. The more I learn about Google, the more I want to work there. In brief, Google is a company that hires smart, creative people, and treats them well. Google rewards merit, encourages big ideas, and gives employees the freedom to make good decisions for the user. The hiring process is calibrated to bring in smart, passionate people. Google has honed the recruitment and interview process over the years. The brain teaser questions are long gone. Nowadays candidates are chosen based on coding ability, technical knowledge, and Googleyness. There’s a lot going on in that one word. Management is different. Managers don’t micro-manage. They trust engineers to make the right decisions. Trusting employees changes the role of managers at Google from what most folks envision when they think of management. In addition, managers can’t unilaterally, hire, fire, or promote. Many of the important management decisions that could be perceived as office politics are handled by a committee to remove that danger. Google’s people operations (HR) has learned what works over time, and they use data and employee feedback to improve evaluation systems, the hiring process, promotions, compensation, benefits, and more. Read Work Rules! by Laszlo Bock (SVP, People Operations) for more. Yes, the benefits are amazing. I went on a tour of the Google office in Kirkland, WA, and it surpassed my expectations. And my expectations were already high. Google Interview University Remember the coaching notes I received telling me what to study? The list of topics seemed manageable, even though I didn’t know anything on the list. I turned the topics on the notes into an outline and started filling in the topics with YouTube videos of lectures from MIT and UC Berkeley. A video on linked lists in one place, a video about queues in another. The list started to grow. I published the list on Github because my Github account was pretty empty. Since all the code I wrote for my businesses and work was private, my Github account made it look like I didn’t code at all. I needed to build up a portfolio. I originally called the project “Project 9894”. Google launched on Sept 4, 1998. Hence the name. I later renamed it to “Google Interview University”. Over time I added some optional topics that I discovered along the way. I was pretty amazed I had gotten so far in my career without even knowing how a CPU processed a program, how memory worked, or any of it. I had known “just enough” to be a success. My little Github project started getting a few stars, and I published a blog post celebrating 20 stars. One morning, I awoke to find it had grown to 120 stars. Someone famous had tweeted about it during the night, and that led to it ending up on the Github daily trending report. I was #1 trending on Github for a few days. Many kind people reached out to thank and encourage me. It turns out there are thousands of people who want to not only work at Google but want to work as a software engineer, and this list was just the to-do list they needed. It’s now at over 21,000 stars. I still can’t believe it. What If I Don’t Get the Job? It won’t be the end of the world. I’ve put the time and dedication into my studies for the goal of getting hired as a Google software engineer, but even if I fail, I’ll still be armed with the skills and knowledge required to work as a software engineer at any company. Wherever I end up, I’m going in as an entry-level software engineer. I’m not going in with 15 years of software engineering experience because I simply don’t have it. When it comes to this stuff, I’m the equivalent of a fresh CS grad. But I have the enthusiasm of a new grad, too. This is a new world for me. I’m just getting started. I’m not afraid to make mistakes. I know I will. I also want to learn everything I can and be an excellent addition to any team. Don’t Study As Much As I Did Yes, I took 8 months. But I could have abbreviated the process. Like any startup with a big goal, you make mistakes and do things that waste time. There are many things I wish I go back and do differently. I studied topics I didn’t need to, some because I thought I would need them for the interview, and some because I wanted to have the knowledge on hand for when I started working. I didn’t want to be a burden on the team I’m assigned to. It turns out I simply over-prepared. I spent 3 weeks reading a 1,000-page book on C++. I don’t remember 1,000 pages worth, but I know a good bit about C++ now. As it turns out, I’m using Python for the interview, not C++. I had assumed I needed C++, C, or Java, but I was wrong. It’s good to ask, not assume. I read way more books than I needed to. There are only 3 or 4 books I should have read. I have a code catalog of dozens of algorithms that I review, most of which I wouldn’t expect in an interview. You don’t need to do that. I watched many hours of YouTube videos but could have watched far less, and spread out topics over time. I should have stopped reading books and watching videos earlier and started on coding problems sooner. I would have been able to spend more time applying the topics I learned. Spaced repetition is the key to memorization. Once you learn something, review it again later, and again even later. At each repetition, you reinforce your learning. Spending hours and hours at one time on priority queues won’t make you an expert. You become an expert by revisiting and reviewing over time. If you do so, you’ll get to the point where can’t forget details. To help review, I made 1,792 flashcards (digital flashcards). This is way too many. I review them on my phone or tablet whenever I get a spare moment (such as during Christmas shopping). Flash cards and spaced repetition go hand-in-hand. Once I get an answer on a flashcard right, I don’t mark it as known. I keep it in the deck and once I’ve seen it and answered it correctly many times, then I mark it as known. My sense of fear (“What if they ask me a question about red-black trees?”) led me to study far more topics than I needed to. But I didn’t want to just prepare for the interview, I wanted to prepare for a career at Google, solving large-scale problems. That means knowing algorithms that will save computing resources of time, space, and I/O. I may never need to know a maximum flow algorithm (Ford-Fulkerson), but it’s nice to know I have that tool available if the situation arises (without memorizing the implementation), and can recognize its application to a problem space. Conclusion Early on, I wished I could skip all this learning, and just hurry up and get hired so I could instead spend my time learning the languages and tools for the team I join. But along the way, I realized how important this knowledge is, and even though most of it may not be applicable on a daily basis, I’m glad I put in the effort. I have a new appreciation of the history of computing, the greats in the field, data structures and algorithms (and how they complement each other), and how computer systems work at low-level. I’ll be putting in my application soon. It’s been a long journey getting to this point — almost an entire year. It began back in January, but I wasn’t able to commit to full-time study until April. I’m about as prepared as I can be. I can’t keep studying and putting off the application forever. At some point, I have to take the leap. I see a bright future ahead. First of all, thank you to everyone who cheered me on and supported me with your kind words over the last few months. I appreciate all of you so much. Your encouragement helped me get back to the whiteboard every day and practice. Why didn’t I get hired? I don’t know why. Last week I received a rejection email from the recruiter, and at first, I thought it was a mistake, and laughed it off. I checked in with my referral and he inquired into it and lobbied on my behalf, but in the end, it didn’t change the situation. The thing that bothers me is that I didn’t even get a phone screen. I didn’t even talk to a recruiter over the phone. After all this work and enthusiasm, I didn’t even get a chance to prove myself. I’ve done a lot of speculation about the reason why, but I won’t do that here. It’s all just guessing, which accomplishes nothing. But I still like Google. However, I don’t know if I’ll apply again in the future. I want to get hired and stay at a company for a long time. I don’t want to hop around. The company that ends up hiring me will get a loyal, hardworking, enthusiastic employee. There are a lot of places where I can strive for greatness and have that effort rewarded. Respect your Recruiter Recruiters look at hundreds of resumes every day, and they are highly tuned to detecting quality candidates and rejecting those who don’t match up with their model. For some reason, I just didn’t fit the profile. They probably are doing me a favor. It’s possible that I would have been in over my head and continually dragged my team down. Google is known for having false negatives in their selection process, but if you’re good enough for Google, you’ll eventually get in. Recruiters know what works, and what doesn’t. So respect their decision and be polite. I’ll bet they deal with irate rejected candidates on a daily basis, so don’t be like that. Just get more experience and knowledge and try again later. As you may know, the last 11 months have been very difficult for me. As a self-taught web developer of 15 years, my computer science study plan took me months to get through, and the main motivator was to start a new career as a software engineer, tackling large problems at a large tech company. Google was the company I had audaciously set my sights on, but in the end that turned into disappointment. If you haven’t read about my story, you’re missing out. Go ahead and read it first. Well, I reached out to my network, and made a lot of new friends. I got connected with every tech giant in the Pacific northwest. Of all of them, Amazon had always stood out — even more than Google — as the most innovative company over the last 10 years. I applied via a referral, whom I had met at a startup event in 2013, and got the process rolling. After so many months of non-stop effort, sacrifice, and worry, I’m pleased to announce that I finally made it! Today I accepted an offer to be a Software Development Engineer at Amazon.com.

Job Titles, especially for software developers, is something I usually call BULLSHIT! I’ve been a software developer for over 15 years and I still don’t know what to call myself. Beyond trying to agree on a generalized name for developers, software developers, programmers, software engineers, coders, computer programmers, and the like, we’ve got to contend with job titles. What the heck is the difference between a Senior Software Engineer and a Junior Software Engineer? And how do they compare to Software Developer II and Software Development Engineer in Test? This is some pretty confusing stuff. And of course, if it confuses me, I strongly believe it confuses you too... So, how should software developers call themselves? Does it even matter? Watch this video and find out! Your Job Title Is Wrong, Here Is What It Should Be: https://simpleprogrammer.com/2013/05/26/job-titles/ Coding Is Not The Same As Programming: https://www.youtube.com/watch?v=1Y9bwyEFFGY Made To Stick Book: https://simpleprogrammer.com/madetostickbook The Complete Software Developer's Career Guide: https://simpleprogrammer.com/career-guide-yt

On today’s episode, Charles Max Wood and Jerome Hardaway discuss Packaging Ruby with Nell Shamrell-Harrington. Nell is an expert Software Development Engineer at Chef Software. Tune in to learn how you can provide viable packaging solutions!

On today’s episode, Charles Max Wood and Jerome Hardaway discuss Packaging Ruby with Nell Shamrell-Harrington. Nell is an expert Software Development Engineer at Chef Software. Tune in to learn how you can provide viable packaging solutions!

On today’s episode, Charles Max Wood and Jerome Hardaway discuss Packaging Ruby with Nell Shamrell-Harrington. Nell is an expert Software Development Engineer at Chef Software. Tune in to learn how you can provide viable packaging solutions!

The BDPA iRadio Show creates a vibrant communications platform that speaks to all BDPA stakeholders.  We have an exciting line-up for our show on March 8, 2016. - Candice Peters, Founder & CEO, Hello Parent - Vanessa Anderson, Software Development Engineer, Time - Morgan Collingwood, College Student, Bloomfield College The BDPA iRadio Show. Linking Business, Education and Technology. The BDPA iRadio Show creates a vibrant communications platform that speaks to all BDPA stakeholders. Sponsored by the BDPA Education and Technology Foundation, and BETF Executive Director Wayne Hicks. Produced by Franne McNeal. Studio Engineering by Everaldo Gallimore. Co-Hosting by Franne McNeal, Timothy Butts, Jala Cruz and Ronald Story. The BDPA iRadio Show broadcasts the 2nd and 4th Tuesday of every month. Join us on blogtalkradio.com/BDPA.

Shawn welcomes our new Adventures in .NET hosts namely Adam Furmanek, Christian Wenz, and Mark Miller. Adam Furmanek is a Software Development Engineer, Public Speaker, Writer, Blogger, and Scientist. Christian Wenz is the owner of Arrabiata Solutions GmbH. Mark Miller is the Chief Scientist at DevExpress on the IDE Tools Team. They talk about their experiences as a developer and much more. SponsorsChuck's Resume TemplateRaygun - Application Monitoring For Web & Mobile AppsBecome a Top 1% Dev with a Top End Devs MembershipSocialsTwitter: @MillerMarkPicksChristian - Indiana Jones movie listMark - Hamilton - The Official London SiteShawn - The Night Agent (TV Series 2023Support this podcast at — https://redcircle.com/adventures-in-net/donationsAdvertising Inquiries: https://redcircle.com/brandsPrivacy & Opt-Out: https://redcircle.com/privacy