Podcast appearances and mentions of angie jones

The political future of Victorian Liberal Party leader John Pesutto is up in the air after a judge ruled he defamed independent MP Moira Deeming. Find out more about The Front podcast here. You can read about this story and more on The Australian's website or on The Australian’s app. This episode of The Front is presented and produced by Kristen Amiet, and edited by Josh Burton. Our regular host is Claire Harvey and original music is composed by Jasper Leak. See omnystudio.com/listener for privacy information.

Superstar barristers Sue Chrysanthou and Matt Collins lock horns over the women's rights MP booted from the Liberal Party.  Find out more about The Front podcast here. You can read about this story and more on The Australian's website or on The Australian's app. This episode of The Front is presented by Claire Harvey, produced by Kristen Amiet, and edited by Tiffany Dimmack. The multimedia editor is Lia Tsamoglou, and original music is composed by Jasper Leak.See omnystudio.com/listener for privacy information.

Min, Angie Jones

Exiled Liberal MP Moira Deeming sues Victorian Opposition leader John Pesutto for expelling her after a rally attended by neo-Nazis.  Find out more about The Front podcast here. You can read about this story and more on The Australian's website or on The Australian's app. This episode of The Front is presented by Claire Harvey, produced by Kristen Amiet and edited by Tiffany Dimmack. The multimedia editor is Lia Tsamoglou, and original music is composed by Jasper Leak.See omnystudio.com/listener for privacy information.

On this episode, 'Laolu, Furo, and Nosa have a guest! They are joined by Angie Jones, the Global Vice President of Developer Relations for tbd. This is Block's new business unit focused on decentralized technologies to move money in a fast and compliant way.They discuss tbd's flagship protocol tbDEX, and the upcoming hackathon happening at the Africa Bitcoin Conference in December._We love hearing your thoughts! Find us on Twitter and Instagram (@openafricapod) and tag us in your conversations. Hosted on Acast. See acast.com/privacy for more information.

In this episode, we dive into the career journey of Angie Jones, the Global Vice President of Developer Relations at Block. Angie shares her experiences transitioning from a Senior Software Engineer at Twitter to leading developer relations initiatives at Applitools and now at Block. Angie also provides insights on the future of developer relations and the evolving landscape of tech communities. Whether you're an aspiring developer advocate or a seasoned professional, this episode is packed with wisdom and practical tips. Guests: Angie Jones - @techgirl1908 Panelists: Ryan Burgess - @burgessdryan Episode transcript: https://www.frontendhappyhour.com/episodes/sips-of-wisdom-interview-with-angie-jones

Scott's in Berlin this week and talks to Angie Jones, Global Vice President of Developer Relations, TBD @ Block, about the job of Developer Relations. What does a DevRel person even do? Are they just hanging out in the Delta Lounge or are the Developers? What does it mean to Advocate versus Evangelize? 

Meet Angie Jones

Angie Jones Interview...An Evening with Beth Macy 02/12/24

Min. Angie Jones, SUNDAY PM, 1 28 24

Technology meets economic empowerment in this episode featuring Angie Jones, Global Vice President of Developer Relations at TBD, a Block division. Angie sheds light on the role of decentralized technologies in shaping the future of digital identity and cross-border payments. Her journey from software engineering to a leadership role in tech innovation illustrates her profound impact on the industry. This episode offers valuable insights into how technological advancements are driving economic growth and changing the financial landscape. Angie's expertise and unique perspective make this a must-listen for anyone interested in the cutting-edge intersection of technology, finance, and innovation.About AngieAngie Jones is the Global Vice President of Developer Relations for TBD, Block's new business unit focused on decentralized technologies. She is an award-winning teacher and international keynote speaker who shares her wealth of knowledge at software companies and conferences all over the world.As a Master Inventor, Angie is known for her innovative and out-of-the-box thinking style which has resulted in 27 patented inventions in the areas of metaverses, collaboration software, social networking, smarter planet, and software development processes.Show notes:(00:25) Introduction to Angie Jones and Her Role at TBD(01:25) Angie's Recognition in a USA Today Crossword(02:50) Career Journey and Transition into Developer Relations(06:04) Block's Mission and Services in Economic Empowerment(10:09) Convenience vs. Decentralization in Technology(16:49) Innovations in Cross-Border Payments(25:01) Decentralized Tech Stories and Reflections on Tech Innovation(30:22) Challenging Tech Industry Norms and Global PerspectivesLinks Referenced:TBD: https://www.tbd.website/Twitter: https://twitter.com/techgirl1908LinkedIn: https://www.linkedin.com/in/angiejones/

Angie Jones is the Global Vice President of Developer Relations for TBD, Block's new business unit focused on decentralized technologies. She is an award-winning teacher and international keynote speaker who shares her wealth of knowledge at software companies and conferences all over the world. As a Master Inventor, Angie is known for her innovative and out-of-the-box thinking style which has resulted in more than 25 patented inventions in the areas of metaverses, collaboration software, social networking, smarter planet, and software development processes. You can find Angie Jones on the following sites: Website Twitter GitHub YouTube LinkedIn PLEASE SUBSCRIBE TO THE PODCAST Spotify Apple Podcasts Google Podcasts Amazon Music RSS Feed You can check out more episodes of Coffee and Open Source on https://www.coffeeandopensource.com Coffee and Open Source is hosted by Isaac Levin --- Support this podcast: https://podcasters.spotify.com/pod/show/coffeandopensource/support

I am joined by Angie Jones VP of Global Developer Relations at Block. We are diving into a TON of topics around decentralization, interviewing tips, devrel, and personal branding! Come hang with us! Like what you hear? Connect with me - Website: gun.io/taylor Email: taylordesseyn@gun.io LinkedIn: Taylor Desseyn Tweet me: @tdesseyn Pics of the life, wife, daughter & dog: @tdesseyn

Angie Jones Interview: Piff the Magic Dragon 11/16/23

Min. Angie Jones, Sunday PM, 10 22 23

For this week here's a throwback episode from Season 2 with Angie Jones!   Angie Jones is a Java Champion and Senior Developer Advocate who specializes in test automation strategies and techniques. She shares her wealth of knowledge by speaking and teaching at software conferences all over the world, writing tutorials and technical articles on angiejones.tech, and leading the online learning platform, Test Automation University.   As a Master Inventor, Angie is known for her innovative and out-of-the-box thinking style which has resulted in more than 25 patented inventions in the US and China. In her spare time, Angie volunteers with Black Girls Code to teach coding workshops to young girls in an effort to attract more women and minorities to tech.   In this episode, I chat with Angie Jones who is a Senior Developer Advocate specialized in test automation strategies & techniques about how she discovered her niche in tech. Angie shares how she got her patents, teaches us her secret to fighting imposters syndrome, and shows us how having a personal brand can help you level up in your career.   Key takeaways from this episode: What is test automation? The skillsets needed to become an effective test automation engineer One simple exercise you can do to combat imposter syndrome The # 1 type of testing everyone should know about Misconceptions about being a test automation engineer The importance of speaking up and sharing your ideas How developing your personal brand can level up your career 3 major keys for getting into tech as a developer Connect with Angie : YouTube: https://www.youtube.com/user/angieluvboo?sub_confirmation=1 LinkedIn: https://www.linkedin.com/in/angiejones Website: https://angiejones.tech/ Twitter: https://twitter.com/techgirl1908 Free Courses: https://testautomationu.applitools.com/instructors/angie_jones.html Connect with Grace: Twitter: https://twitter.com/GraceMacjones LinkedIn: https://www.linkedin.com/in/gracemacjones/   Follow the podcast: Twitter: https://twitter.com/techunlockedpod Instagram: https://www.instagram.com/techunlockedpod/ LinkedIn: Tech Unlocked   Thank you so much for listening to this podcast! If you enjoyed listening to this episode, please leave a rating and review on iTunes. Use the hashtag #Techunlocked to ask questions and share your thoughts. Have a tech-related question? Shoot us an email techunlockedpod@gmail.com

In this week's episode of the New Flesh Podcast, Ricky and Jon interview return Angie Jones. Angie is a Melbourne based gender critical woman, who runs the YouTube channel TERF Talk Down Under. Angie is a fierce advocate for women, and is outspoken about self ID, biological men in women's spaces, and the right for females and girls to have sex-separated sports categories. She recently gave a speech in the Federal parliament on the subject “Why can't women talk about sex?” Topics covered include; the controversy surrounding the Let Women Speak Tour Down-Under and it's immediate aftermath, the censorship  behind closed doors in newsrooms around the country in relation to trans ideology, Daniel Andrews Parliament hosted drag queen story hour AND more.  ---ARTICLES AND LINKS DISCUSSEDFollow Angie on X:@angijones---Follow Terf Talk Down Under:https://www.youtube.com/@TERFTalkDownUnder---Let Women Speak: The Vilification of Angie Jones - Women's Forumhttps://www.womensforumaustralia.org/the_vilification_of_angie_jones---SUPPORT THE NEW FLESHBuy Me A Coffee:https://www.buymeacoffee.com/thenewflesh---Instagram: @thenewfleshpodcast---Twitter: @TheNewFleshpod---Follow Ricky: @ricky_allpike on InstagramFollow Ricky: @NewfleshRicky on TwitterFollow Jon: @thejonastro on Instagram---Theme Song: Dreamdrive "Vermilion Lips" 

Soufflées ou gratinées, farcies, en paille ou en galette, en tortilla, au four en robe de chambre, sautées, frites, en patatas bravas et petit piment : La pomme de terre, quel bonheur ! Quel cadeau de la terre ! Une patate et mille recettes viennent en tête, qu'elle soit patate douce (comble du chic au Pérou, région d'origine de la pomme de terre puisque la mère des patates a été découverte au XVème siècle dans les Andes : la déesse Papà rapportée par les conquistadors dans leurs malles. Comment la cuire, la choisir, la préparer, lui donner son bain de friture préféré, avec qui la marier ? Patates douces ou pommes de terre du Nord, elle sait combler les ventres, on l'aime parce qu'elle est magique, seule cuite vapeur ou chic en duchesse, elle est accessible à tous, facile à cuisiner, et se mange à toute heure, en solo, avec la famille, les voisins, les copains !Avec Jean-François Mallet, photographe, globe-trotteur, cuisinier, auteur de plusieurs livres dont une encyclopédie des produits et des métiers de bouche, et du génialissime : Simplissime qui permet à quiconque de bien cuisiner !Cette émission sur les pommes de terre est la première d'une série autour d'un trio fantastique et savoureux de la cuisine : des patates, de la viande et la sauce dont le steak frites n'est qu'une émanation parmi tant.Dans cette émission aussi, il sera aussi question du premier championnat du monde de la frite ! La première édition se tiendra le 7 octobre 2023 à Arras. Populaire comme la frite, ce championnat inédit s'adresse à tous : aux familles, aux passionnés, comme aux cuisiniers professionnels. Plusieurs sélections permettront de distinguer le meilleur « friteur », la meilleure sauce, la frite la plus originale. Les détails avec Marie-Laure Fréchet, présidente de la toute nouvelle « Confrérie de la frite fraîche » et membre du jury du championnat organisé par l'Office du Tourisme d'Arras Pays d'Artois. Marie-Laure Fréchet est aussi l'auteure de « Le grand livre des patates » qui paraît ce 13 septembre 2023, aux éditions Flammarion.- Un extrait de Tortilla de patata, le film de Mélody da Fonseca avec sa grand-mère Juana, issue de la web série Grandmas project- Raphaël, friteur à Lille sur la folie du dimanche soir- Un clin d'œil à Emmanuelle Jary, dont la série C meilleur quand c'est bon nous a fait découvrir les frites à la crème, le 2ème numéro de la revue vient de sortir : un steak en couverture ! pour la découvrir :Harouna Sow, cuisinier complice du Goût du monde, chef des cuisines du Refugee Food et de son restaurant Waalo à Paris.Programmation musicale- Diabate Diaware- Afonhe de Kimi Djabaté- Somaw de Fatoumata Diawara feat. Angie Jones. 

Soufflées ou gratinées, farcies, en paille ou en galette, en tortilla, au four en robe de chambre, sautées, frites, en patatas bravas et petit piment : La pomme de terre, quel bonheur ! Quel cadeau de la terre ! Une patate et mille recettes viennent en tête, qu'elle soit patate douce (comble du chic au Pérou, région d'origine de la pomme de terre puisque la mère des patates a été découverte au XVème siècle dans les Andes : la déesse Papà rapportée par les conquistadors dans leurs malles. Comment la cuire, la choisir, la préparer, lui donner son bain de friture préféré, avec qui la marier ? Patates douces ou pommes de terre du Nord, elle sait combler les ventres, on l'aime parce qu'elle est magique, seule cuite vapeur ou chic en duchesse, elle est accessible à tous, facile à cuisiner, et se mange à toute heure, en solo, avec la famille, les voisins, les copains !Avec Jean-François Mallet, photographe, globe-trotteur, cuisinier, auteur de plusieurs livres dont une encyclopédie des produits et des métiers de bouche, et du génialissime : Simplissime qui permet à quiconque de bien cuisiner !Cette émission sur les pommes de terre est la première d'une série autour d'un trio fantastique et savoureux de la cuisine : des patates, de la viande et la sauce dont le steak frites n'est qu'une émanation parmi tant.Dans cette émission aussi, il sera aussi question du premier championnat du monde de la frite ! La première édition se tiendra le 7 octobre 2023 à Arras. Populaire comme la frite, ce championnat inédit s'adresse à tous : aux familles, aux passionnés, comme aux cuisiniers professionnels. Plusieurs sélections permettront de distinguer le meilleur « friteur », la meilleure sauce, la frite la plus originale. Les détails avec Marie-Laure Fréchet, présidente de la toute nouvelle « Confrérie de la frite fraîche » et membre du jury du championnat organisé par l'Office du Tourisme d'Arras Pays d'Artois. Marie-Laure Fréchet est aussi l'auteure de « Le grand livre des patates » qui paraît ce 13 septembre 2023, aux éditions Flammarion.- Un extrait de Tortilla de patata, le film de Mélody da Fonseca avec sa grand-mère Juana, issue de la web série Grandmas project- Raphaël, friteur à Lille sur la folie du dimanche soir- Un clin d'œil à Emmanuelle Jary, dont la série C meilleur quand c'est bon nous a fait découvrir les frites à la crème, le 2ème numéro de la revue vient de sortir : un steak en couverture ! pour la découvrir :Harouna Sow, cuisinier complice du Goût du monde, chef des cuisines du Refugee Food et de son restaurant Waalo à Paris.Programmation musicale- Diabate Diaware- Afonhe de Kimi Djabaté- Somaw de Fatoumata Diawara feat. Angie Jones. 

As we learned in Episode 79, “How We Broke DevRel as an Industry (https://www.communitypulse.io/79-how-we-broke-devrel-as-an-industry)”, sometimes the people in charge may not know how to set you up for success. The tasks you're expected to do can take you away from your core focus. In today's episode, we'll talk through how to define your role and defend your team against that very real possibility of being tasked with items that don't belong within your purview. Checkouts Evan Hamilton * Factfulness: Ten Reasons We're Wrong about the World by Hans Rosling (https://www.amazon.com/Factfulness-Reasons-World-Things-Better/dp/1250123828/ref=sr_1_1?hvadid=580750427006&hvdev=c&hvlocphy=9010222&hvnetw=g&hvqmt=e&hvrand=5641429314803382062&hvtargid=kwd-429505407993&hydadcr=22567_13493270&keywords=factfulness+by+hans+rosling&qid=1690810799&s=books&sr=1-1) * People I Mostly Admire speaks to Chicago's innovative sheriff (https://freakonomics.com/podcast/chicagos-renegade-sheriff-wants-to-fix-law-enforcement/) * Chris Detzel (https://chrisdetzel.com/) * Community Manager Breakfast (https://www.evanhamilton.com/community-manager-breakfast/) Angie Jones * ChatGPT (https://openai.com/) * Hackathons! Wesley Faulkner * Positioning with April Dunford (http://positioning.show) * Setting up For Success in Your Next Role: Where to start? (https://www.devrelx.com/post/setting-up-for-success-in-your-next-role-where-to-start) Jason Hand * DASH conference (https://www.dashcon.io/) * Beginners Guide to Sketchnoting: Focus Better, Learn Faster and Remember Longer by Drawing Your Notes (https://a.co/d/eSaombF) by Ashton Rodenhiser Mary Thengvall * American Dirt (https://www.goodreads.com/book/show/45721673-american-dirt) by Jeanine Cummins * Puppy Training: Sexier than a Squirrel (https://absolute-dogs.com/product/squirrel/) Enjoy the podcast? Please take a few moments to leave us a review on iTunes (https://itunes.apple.com/us/podcast/community-pulse/id1218368182?mt=2) and follow us on Spotify (https://open.spotify.com/show/3I7g5WfMSgpWu38zZMjet?si=565TMb81SaWwrJYbAIeOxQ), or leave a review on one of the other many podcasting sites that we're on! Your support means a lot to us and helps us continue to produce episodes every month. Like all things Community, this too takes a village. All headings are in bold. Callouts are using full host names. Artwork photo by Paul Skorupskas (https://unsplash.com/@pawelskor?utm_source=unsplash&utm_medium=referral&utm_content=creditCopyText) on Unsplash (https://unsplash.com/@pawelskor?utm_source=unsplash&utm_medium=referral&utm_content=creditCopyText) Special Guests: Angie Jones and Evan Hamilton.

You probably have a habit of putting things off and then feeling bad about putting it off - but then you put it off some more - and then you feel even worse! On this episode we slow it way down and discover that there is a light side to procrastinating too! So if you're ready to get clear on the pros and cons of procrastination, give this episode a listen and let us know what you think!Click HERE for our monthly somatic Stress Release Class. Click HERE to schedule a free consultation with Elizabeth or CaseyEnjoy the inspirational interview with intrepid travelers Jeremy and Angie Jones of the most helpful Pittsburgh resource: Discover the Burgh. Links to their other awesome blogs:https://www.livingthedreamrtw.comhttps://hipsterhomesteaders.comhttps://thegrapepursuit.com

Interview w/Angie Jones Re: MAS Rocket Man at the Keith Albee

Mountain Stage w/Host Kathy Mattea - Interview w/Angie Jones

In this interview episode I speak with Angie Jones from the Youtube channel 'Terf Talk Down Under' about the recent protest staged by feminists in Australia against men being granted access to women only spaces, the perils of 'self ID' and much more. We talk about Angies political background within the Australian feminist and left movements, the growth of gender ideology in Australian public institutions and why she and other feminists saw the need to take a stand against it. We also cover the chaos that followed the recent protest in Melbourne, the appearance of a group of Nazis and the lies told by Victorian PM Dan Andrews and opposition leader John Pesutto about Angie herself and protest. Be sure to follow Angie on twitter @angijones

Interview w/Angie Jones from Marshall Artist Series - Tedeschi Trucks Band

In this week's episode, Ricky and Jon interview Angie Jones, Angie is a Melbourne based pod-caster who runs the YouTube channel "TERF Talk Down Under" with Stassja Frei. Angie is a fierce advocate for women, and is outspoken about self ID, biological men in women's spaces, and the right for females and girls to have sex separated sports categories.---ARTICLES AND LINKS DISCUSSEDFollow Angie on Twitter:@angijonesTERF Talk Downunder: https://www.youtube.com/channel/UCj5aZKhh-U6AzT1NFpSSy0g---FOLLOW THE CONVERSATION ON reddit:https://www.reddit.com/r/thenewfleshpodcast/---SUPPORT THE NEW FLESHBuy Me A Coffee:https://www.buymeacoffee.com/thenewflesh---Instagram: @thenewfleshpodcast---Twitter: @TheNewFleshpod---Follow Ricky: @ricky_allpike on InstagramFollow Jon: @thejonastro on Instagram---Logo Design by Made To Move: @made.tomove on InstagramTheme Song: Dreamdrive "Chase Dreams"

Hubbard Street Dance Chicago / Interview with Angie Jones

Interview w/Angie Jones from MAS on Dave Koz and Friends

Are your applications ready for Black Friday? Have you seen Angie Jones's new Java course and what's a year in the life like for a Site Reliability engineer? Find out in this episode of the Automation and DevSecOps news show for the week of November 13th. So grab a cup of coffee or tea, and let's do this. Time News Title Rocket Link 0:18 Create a FREE Applitools Account https://rcl.ink/xroZw 0:42 Serenity 3.4.1 Is Out! https://testguild.me/jsqrq1 1:49 Black Friday Ensuring a Reliable Digital Experience  https://links.testguild.com/nzyK7 2:47 Playwright typescript template. https://testguild.me/r6ts97 3:38 Hands-On Introduction to Java https://testguild.me/0j5zsg 4:26 Lambdatest  OTT testing https://testguild.me/vs91qd 5:32 A year of a SRE https://testguild.me/cmklvg 6:11 CloudTruth raises $2.4M https://testguild.me/18ol7e 7:14 Hacking the cloud https://testguild.me/qfaxvq 7:53 Wallarm Q3 API ThreatStats https://testguild.me/nxvchl  

Interview with Angie Jones About the International Film Festival 11/03/2022

Interview with Angie Jones about RESPECT 10/21/2022

Angie Jones with the Marshall Artist Series 10/06/2022

Have you ever thought about becoming a foster parent? If so, this is the podcast for you! We talk with Arnie Eby, the Executive Director of the National Foster Parent Association and a foster parent for 22 years; and Angie Jones, a licensed clinical social worker and the Intensive Service Foster Care Recruiter and Trainer at Vista Del Mar, an agency placing foster children.In this episode, we cover:What is the goal of the foster care system?How to become a foster parent?What are the typical requirements for becoming a foster parent? What disqualifies you to become a foster parent?What type of pre-service training is involved?How long does it usually take to become a licensed foster parent?Who licenses foster parents?What types of questions should parents ask when deciding on which agency to work with?What are the different levels of licensing for foster homes? Do foster parents get paid?Can you foster if you rent your home or apartment?Does one parent have to be at home if they want to have infants or young pre-school aged children placed with them?How much control do foster parents have on which child is placed with them?What is expected of foster parents when a child is placed with them?Can you travel with a foster child? Out of state? Out of the country?What is shared parenting or co-parenting?What type of support should foster parents expect from the agency they are licensed through?Is it possible to adopt your foster child? How do you foster and adopt?How much control do foster parents have on visitation, medical treatment, mental health care, and reunification?How to cope with the grief when a foster child leaves?Where can foster parents turn for support?This podcast is produced  by www.CreatingaFamily.org. We are a national non-profit with the mission to strengthen and inspire adoptive, foster & kinship parents and the professionals who support them. Creating a Family brings you the following trauma-informed, expert-based content:Weekly podcastsWeekly articles/blog postsResource pages on all aspects of family buildingPlease leave us a rating or review RateThisPodcast.com/creatingafamilySupport the show

Min. Angie Jones, Sunday PM, 9 11 22

Joshua 4:1-13 | Psalm 104 | Matthew 5:33-48

If you've ever taken a course on the internet you may have come across an exercise or some kind example that just left you thinkingokay but why?This lack of real-world context is a problem that a lot of courses suffer from.Creating examples that are engaging learners, isolates the skill being used, while also showing off the context in which the skill is used takes time and expertise but the payoff is well worth it. It's not just examples/exercises though. Creating an engaging environment to learn in is important. Angie Jones has a ton of advice in this episode and talks about what she did at Test Automation University to build that environment.The true goal of all this work is to improve the outcomes of your learners. Making sure that you are giving them the means to succeed and stay committed to their learning goals on your platform. If you stay true to this goal, you'll both improve the lives of your learners and the success of your business.

Our guest today is Frances Kirkwood, Angie Jones, Wellness Supervisor at the Knoxville Recreation, and Jane McConeghey, Frances’ niece. We talk about Frances turning 100 years old Friday, August 19.

In this Coffee Talk Aleksandra Desmurs-Linczewska (https://www.callstack.com/team/aleksandra-desmurs-linczewska) and Łukasz Chludziński (https://www.callstack.com/team/lukasz-chludzinski) provide a lot of ideas for staying up to date with the community news. They discuss the most valuable resources such as newsletters, top Twitter accounts, blogs, podcasts, conferences, GitHub and release notes: Newsletters: The React Native Newsletter, Tyler's (ui.dev) newsletter, JavaScript Weekly, Cassidy Williams's newsletter Twitter accounts: official React and React Native accounts Callstack, Remix, Next, Vercel accounts of people who are well-known in the community: Angie Jones (@techgirl1908), Sara Vieira (@NikkitaFTW), Kadi Kraman (@kadikraman), Evan Bacon (@Baconbrix), Dan Abramov (@dan_abramov), Lorenzo Sciandra (@Kelset), Rick Hanloni (@rickhanlonii), Ryan Cavanaugh (@SeaRyanC), Cassidy Williams (@cassidoo), Michal Pierzchala (@thymikee), Wes Bos (@wesbos), Jamon Holmgren (@jamonholmgren), Kent C Dodds (@kentcdodds), Michael Jackson (@mjackson), Ryan Florence (@ryanflorence), Sebastien Lorber (@sebastienlorber) Conferences: React Native EU https://hubs.li/Q01bt5WQ0 React Summit https://reactsummit.com/ Chain React https://cr.infinite.red/ Podcasts: The React Native Show https://hubs.li/Q01bt7gK0 React Native Radio https://reactnativeradio.com/ DevSpresso JS News https://bit.ly/3LnLYmC YouTube channels: Ben Awad https://www.youtube.com/c/BenAwad97 William Candilion https://www.youtube.com/c/wcandillon Fireship.io https://www.youtube.com/c/Fireship The overview of resources will come in handy for every React Native developer regardless of whether you have much experience or you are new to the React Native world.

Angie Jones Talking About Charlie & the Chocolate Factory 04/27/2022

Min. Angie Jones, Sunday Evening 3 13 22

Angie Jones from Marshall Artists Series 03/02/2022

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.

Angie Jones Interview: Russell Bruce Film Festival 02/16/2022

How far would you go to "find your purpose" in life?  So far Angie Jones has explored "car camping" and walked the Great Wall of China in search of inner peace. She's still searching but has taken time out to share some insights about her journey thus far.

Hey, did you hear that Angie Jones is leaving the testing space? Want to know why AWS went down last week and do you use log4j. If so, your software might be at risk? Find out the answers to these and all other end and full pipeline DevOps automation, performance and security testing in this episode of the Test Guild new show for the week of December 12th. So grab your favorite cup of coffee or tea, and let's do this. Time News Title News Link 0:25 Applitools https://rcl.ink/xroZw 0:57 Angie Jones leaving Applitools https://links.testguild.com/EheA4 1:47 Karate Labs https://links.testguild.com/6qZKq 2:30 Software Testing Book https://links.testguild.com/t9yTp 3:14 Ansible Azure Cloud https://links.testguild.com/3TxVX 3:53 MockLab https://links.testguild.com/GAZ2Z 4:48 Automation Guild 2022 Reg https://links.testguild.com/2GiHM 5:41 Tips performance testing https://links.testguild.com/TR0W7 6:15 AWS outage https://links.testguild.com/Rj44K 7:35 Log4j exploploit https://links.testguild.com/NC9CE 8:35  GitGuardian https://links.testguild.com/owGIF

In this podcast episode, we talked to Applitools' Angie Jones about all things related to test automation: tools, best practices, how to reach a higher level of DevTestOps, what role AI will play in software testing, and a lot more. About Angie Angie Jones works as Head of Developer Relations at Applitools and is the founder and Executive Director of Test Automation University. She's previously worked as a Senior Software Developer at Twitter and regularly gives talks about Javascript, software development, and testing best practices. To learn more about her work and upcoming projects, you can follow Angie on her Twitter profile or check out her courses at Test Automation University. In this episode We discussed the must-have practices engineering teams should implement into their processes, along with the different challenges that can arise in software testing and the tips & tricks to solve them. We also looked at Angie's maturity framework that helps teams measure how advanced they are and enables them to reach a high level of maturity in DevTestOps. Some of the most interesting questions we covered in this episode: What role will AI play in software testing and how will it impact the day-to-day work of developers? Which should definitely be automated and which ones are still better done manually? What is your opinion about the future of codeless testing tools and their effects on the test engineers' role? How to scale and look after an ever-growing test suite? How to choose between native and cross-platform mobile test automation frameworks? Show notes & resources Angie's website: https://angiejones.tech/ Test Automation University: https://testautomationu.applitools.com/ The Future Tester, by Jason Arbon: https://www.linkedin.com/pulse/future-tester-jason-arbon/

MAS Fall Intl Film Festival with Angie Jones 10/20/2021

Marshall Artists Series 'Waitress' / Angie Jones Interview 10/05/2021

About Angie Angie Jones is a Java Champion and Senior Director who specializes in test automation strategies and techniques. She shares her wealth of knowledge by speaking and teaching at software conferences all over the world, writing tutorials and technical articles on angiejones.tech, and leading the online learning platform, Test Automation University.As a Master Inventor, Angie is known for her innovative and out-of-the-box thinking style  which has resulted in more than 25 patented inventions in the US and China. In her spare time, Angie volunteers with Black Girls Code to teach coding workshops to young girls in an effort to attract more women and minorities to tech.Links: Applitools: https://applitools.com Black Girls Code: https://www.blackgirlscode.com Test Automation University: https://testautomationu.applitools.com Personal website: https://angiejones.tech Twitter: https://twitter.com/techgirl1908 TranscriptAnnouncer: 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: This episode is sponsored in part by CircleCI. CircleCI is the leading platform for software innovation at scale. With intelligent automation and delivery tools, more than 25,000 engineering organizations worldwide—including most of the ones that you've heard of—are using CircleCI to radically reduce the time from idea to execution to—if you were Google—deprecating the entire product. Check out CircleCI and stop trying to build these things yourself from scratch, when people are solving this problem better than you are internally. I promise. To learn more, visit circleci.com.Corey: This episode is sponsored in part by Thinkst. This is going to take a minute to explain, so bear with me. I linked against an early version of their tool, canarytokens.org in the very early days of my newsletter, and what it does is relatively simple and straightforward. It winds up embedding credentials, files, that sort of thing in various parts of your environment, wherever you want to; it gives you fake AWS API credentials, for example. And the only thing that these things do is alert you whenever someone attempts to use those things. It's an awesome approach. I've used something similar for years. Check them out. But wait, there's more. They also have an enterprise option that you should be very much aware of canary.tools. You can take a look at this, but what it does is it provides an enterprise approach to drive these things throughout your entire environment. You can get a physical device that hangs out on your network and impersonates whatever you want to. When it gets Nmap scanned, or someone attempts to log into it, or access files on it, you get instant alerts. It's awesome. If you don't do something like this, you're likely to find out that you've gotten breached, the hard way. Take a look at this. It's one of those few things that I look at and say, “Wow, that is an amazing idea. I love it.” That's canarytokens.org and canary.tools. The first one is free. The second one is enterprise-y. Take a look. I'm a big fan of this. More from them in the coming weeks.Corey: Welcome to Screaming in the Cloud. I'm Corey Quinn. If there's one thing that I have never gotten the hang of, its testing. Normally, I just whack the deploy button, throw it out into the general ecosystem, and my monitoring system is usually called ‘customers.' And if I don't want to hear from them, I just stopped answering calls from the support desk. Apparently, that is no longer state of the art because it's been about 15 years. Here to talk about testing from a more responsible direction is Angie Jones, a senior director and developer at Applitools. Thanks for joining me.Angie: Hey, Corey. [laugh]. I am cracking up at your confession there and I appreciate it because you're not unique in that story. I find that a lot of engineers [laugh] follow that same trend.Corey: There are things we talk about and there are the things that we really do instead. We see it all over the place. We talk about infrastructure as code, but everyone clicks around for a few things in the Cloud Console, for example. And so on, and so forth. We all know we should in theory be doing things, but expediency tends to win the day.And for better or worse, talking about testing, in many cases, makes some of us feel better about not actually doing testing. And one of these days, it's one of those, “I really should learn how TDD would work in an approach like this.” But my primary language has always been, well, always been a crappy version of whatever I'm using, but for the last few years, it's been Python. There are whole testing frameworks around all of these things, but I feel like it requires me to actually have good programming practices to begin with which, let's be very clear here, I most assuredly doubt.Angie: [laugh]. That's a fair assessment, but I would also argue, in cases like those, you need testing even more, right? You need something to cover your butt. So, what are you doing? You're just, kind of, living on the edge here?Corey: Sort of. In my case, it's always been that I'll bring in an actual developer who knows what they're doing to—Angie: Ah.Corey: —turn some of my early scripts into actual tools. And the first question is, “Okay, can you explain what this is doing for me?” “Great. So, we're going to throw it away and completely replace it with—so what are the inputs, what are the outputs, and do you want me to preserve the bugs or not?” At which point, it's great.It's more or less like I'm inviting someone to come in and just savage my code, which is apparently also a best practice. But for better or worse, I've never really thought of myself as an engineer, so it's one of those areas where it's it doesn't cut to the core of my identity in any particular way. I do know it would be nice that, oh yeah, when I wind up doing an iterative deployment of a Lambda function or something, if it takes five minutes to get updated, and then I forgot to put a comma in or something ridiculous like that. Yeah. Would have been nice to have something—you know, a pre-commit hook—that caught something like that.Angie: Yeah, yeah. It's interesting. You said, “Well, maybe one of these days, I'll learn.” And that's the issue I find. No matter what route you took to learn how to become—whatever you are, software engineer, whatever—testing likely wasn't part of that curriculum.So, we focus—when teaching—very heavily on teaching you how to code and how to build something, but very little, if any, on how to ensure you built the right thing and that it stands the test of time.Corey: My approach has always been well, time to write some code, and it started off as just, as a grumpy systems administrator, it was always shell scripts, which, okay, great. Instead of doing this thing on 15 machines, run upon a for loop and just iterate through them. And in time, you start inheriting other people's crappy tooling, and well, I could rewrite the entire thing and a week-and-a-half, or I could figure out just enough Perl to change that one line in there, and that's how they get you. You sort of stumbled your way into it in that direction. Naive questions I always like to ask around testing that never really get answers for because I don't think to ask these when other people are in the room and it's not two o'clock in the morning and the power is gone out.You have a basic linter test of, do you have basic syntax errors in the code? Will it run? Seems to be a sort of baseline, easy acceptance test. But then you get into higher-level testing of unit tests, integration tests, and a bunch of others I'm sure I'm glossing over because—to be direct—I tend to conflate all these in my head. What is the hierarchy of testing if there is such a thing?Angie: Yeah, so Mike Cohn actually created a model that is very heavily used within the industry, and it's called the ‘Test Automation Pyramid.' And what this model suggests is that you have your unit tests; you have some kind of, like, integration-type tests in the middle, and then you have these end-to-end tests on top. So, think of a pyramid divided into three sections. But that's not divided equally; the largest part of that pyramid, which is the base, is the unit test. So, this suggests that the bulk of your test suite should comprise of unit tests.The idea here is that these are very small, they're very targeted, meaning they're easier to write, they take less time to run, and if you have an error, it kind of pinpoints exactly what's wrong in the system. So, these are great. The next level would be your integration. So, now how do two units integrate together? So, you can test this layer multiple different ways: it might be with APIs, it might be the business logic itself, you know, calling into functions or something like that.And this one is smaller than the unit test but not as large as the final part, which is the end-to-end test. And that one is your smallest piece, and it doesn't even have to be end-to-end. It could be UI, actually. That's how it's labeled by Mike Cohn in his book: UI tests. So, the UI tests, these are going to be your most fragile tests, these are going to take the most time to write as well as the most time to execute.If something goes wrong, you have to dig down to figure out what exactly broke to make this happen. So, this should be the smallest chunk of your overall testing strategy.Corey: People far smarter than I have said that in many cases—along with access—testing, and monitoring—or observability, which is apparently a term for hipster monitoring—are lying on the same axis. Where in the olden days of systems administration, you can ping the machine and it responds just fine, but the only thing that's left on that crashed machine is just enough of the network stack to return a ping, so everything except the thing that tells you it's fine is in fact broken. So, as you wind up building more and more sophisticated applications, the idea being that the testing and the ‘is everything all right' monitoring ping tends to, more or less, coalesce into the same thing. Is that accurate from your view of the world? Is that something that is an oversimplification of something much more nuanced? Or did I completely misunderstand what they were saying, which is perfectly possible?Angie: You kind of lost me somewhere in the middle. So, I'm just going to nod and say yes. [laugh].Corey: [laugh]. No, no, it—the hard part that I've always found is… I lie to myself, when I'm writing code: “Oh, I don't need to write a unit test for this,” because I'd gotten it working, I tested it with something that I know is good, it returns what I expect; I tested with something bad and well, some undefined behavior happens—because that's a normal thing to happen with code—and great, I don't need to have a test for that because I've already got it working. Problem solved.Angie: Right. Right.Corey: It's a great lie.Angie: Yeah.Corey: And then I make a change later on that, in fact, does break it. It's the, “But I'm writing this code once and why would I ever go back to this code and write it again? It's just a quick-and-dirty patch that only needs to exist for a couple of weeks.” Yeah, the todo: remove this later, and that code segment winds up being load-bearing decades into the future. I'm like, “Yeah, one of these days, someone's going to go back and clean up all of my code for me.” Like, the code fairies are going to come in the middle of the night with the elves, and tidy everything up. I would love to hire those mythical creatures, but can't find them.Angie: This mythical sprint, where it's, “Oh, let's only clean up this entire sprint.” You know, everybody's kind of holding out and waiting for that. But no, you hit the nail on the head with the reason why you need to automate your tests, essentially. So, I find a lot of newer folks to the space, they really don't understand, why on earth would I spend time writing code to represent this test? Just like you said, “I implemented the feature. I tried it out, it worked.” [laugh]. “And hey, I even tried a non-happy path. And when it broke, I had a nice little error message to tell the user what to do.”And they feel really good about that, so they can't understand, “Why would I invest the time—which I don't have—to write some tests?” The reason for that it's just as you said: this is for regression. Unless that's the end of this application and you're not going to touch it ever again for any reason, then you need to write some tests [laugh] because you're going to constantly change the application, whether that be refactoring, whether that be adding new features to it, it's going to change in some way and you cannot be sure that the tests of yesterday still work today because whenever you make the change, you're just going to poke around manually at that little area not realizing there could be some integration things that you totally screwed up here and you miss that until it goes out into prod.Corey: The worst developer I've ever met—hands down—was me, six months before I'm looking at whatever it is that I've written. And given that I do a lot of my stuff in a vacuum and I'm the only person to ever touch these repositories, I could run Git blame, but I already know exactly what it's going to tell me—Angie: “It's me.” [laugh].Corey: —so we're just going to skip that part. Like it's a test. And, “Yeah, we're just going to try and fix that and never speak about it again.” But I can't count the number of times I have looked at code that I've written—and I do mean written; not blindly copy-and-pasted out of Stack Overflow, but actually wrote, and at the time, I understood exactly what it did—and then I look at it, and it is, “What on earth was I thinking? What—what—it technically doesn't even return anything; it can't be doing anything. I can just remove that piece entirely.” And the whole thing breaks.I've out-clevered myself in many respects. And I love the idea, the vision, that testing would catch these things as I'm making those changes, but then I never do it. It's getting started down that path and developing a more nuanced, and dare I say it, formal understanding of the art and science of software development. Always feels like the sort of thing I'll get to one of these days, but never actually got around to. Nowadays, my testing strategy is to just actually deploy things into someone else's account and hope for the best.And, “Oh, good. Well, everyone has a test account; ideally, it's not their own production account.” And then we start to expand on beyond that. You have come to this from a very different direction in a number of different ways. You are—among other things—a Java Champion, which makes it sound like you fought the final boss at the end of the developer internet. And they sound really hard. What is a Java Champion?Angie: Yeah. So, a Java Champion is essentially an influencer in the Java ecosystem. You can't just call yourself this; like you say, you got to fight the guy at the end, you know? But seriously, in order to become one, a current Java Champion has to nominate you, and all of the other Java Champions has to review your package, basically looking at your work. What have you contributed to the developer community, in terms of Java?So, I've done a number of courses that I've taught; I've taught at the university level, as well; I am always talking about testing and using Java to show how to do that, as well as talks and all of this stuff. So apparently, I had enough [laugh] for folks to vote me in. So, it is an organization that's kind of ordained by Oracle, the Gods of Java. So, it's a great accomplishment for me. I'm extremely happy about it. And just so happens to be the first black woman to become a Java Champion. So, the news made a big deal about that. [laugh].Corey: Congratulations. Anytime you wind up getting that level of recognition in any given ecosystem, it's something to stop and take note of. But that's compounded by just the sheer scale and scope of the Java community as a whole. Every big tech company I know has inordinate amounts of Java scattered throughout their infrastructure, a lot of their core services are written in Java, which makes me feel increasingly strange for not really knowing anything about it, other than that, it's big and that there are—this entire ecosystem of IDs, and frameworks, and ways to approach these things that it feels like those of us playing around in crappy bash-scripting-land have the exact opposite experience of, “Oh, I'm just going to fire up an empty page and fill it with a bunch of weird commands and run it, and it fails, and run it again, and it fails. And it finally succeeds when I fixed all the syntax errors, and that's great.” It feels like there is a much more structured approach to writing Java compared to other languages, be they scripts or full-on languages.Angie: Yeah. That's been a gift and a curse of the language. So, as newer frameworks have come out, or even as JavaScript has made its way to the front of the line, people start looking at Java, it's kind of bloated, and all of these rules and structures were in place, but that feels like boilerplate stuff and cumbersome in today's development space. So, fortunately, the powers that be have been doing a lot of changes in Java. We went for quite a while where releases were about, mmm, every three years or so.And now they've committed to releases every six months. So, [laugh] most people are on Java 8 still, but we're actually at, like, Java 16, now. So, now it's kind of hard to keep up but that makes it fun as well. There's all of these newer features and new capabilities, and now you can even do functional programming in Java, so it's pretty nice.Corey: Question I have is, does testing lend itself more easily to Java versus other language? And I promise I'm not trying to start a language war here. I just know that, “Well, how do I effectively test my Python code?” Leads to a whole bunch of? “Well, it depends.”It's like asking an attorney any question on the planet; same story. Like, “Well, it really depends on a whole bunch of things.” Is it a clearer, more structured path in Java, or is it still the same murky there are 15 different ways to do it and whichever one you pick, there's a whole cacophony of folks telling you you've done it wrong?Angie: Yeah, that's a very interesting question. I haven't dug into that deep, but Java is by far the most popular programming language for UI test automation. And I wonder why that is because you don't use Java for building front end. You use Java scripts. I don't know how this ca—I—well, I do know how it came to be.Like, back in the day, when we first started doing test automation, JavaScript was a joke, right? People would laugh at you if you said that you were going to use JavaScript. It's, you know, “I'm going to learn JavaScript and try to enter the workforce.” So, you know, that was a big no-no, and kind of a joke back then. So, Java was what a lot of your developers were using even if they were only using it for the backend, maybe.You didn't really have a [unintelligible 00:16:32] language on the client-side, back then. You had your PHP on the back end, you just did some HTML and some CSS on the front end. So, there wasn't a whole lot of scripting going on back then. So, Java was the language that people chose to use. And so there's a whole community out there for Java and testing.Like, the libraries are very mature, there's open-source products and things like this. So, this is by far the most popular language that people use, no matter what their application is built in.This episode is sponsored by our friends at Oracle Cloud. Counting the pennies, but still dreaming of deploying apps instead of "Hello, World" demos? Allow me to introduce you to Oracle's Always Free tier. It provides over 20 free services and infrastructure, networking databases, observability, management, and security.And - let me be clear here - it's actually free. There's no surprise billing until you intentionally and proactively upgrade your account. This means you can provision a virtual machine instance or spin up an autonomous database that manages itself all while gaining the networking load, balancing and storage resources that somehow never quite make it into most free tiers needed to support the application that you want to build.With Always Free you can do things like run small scale applications, or do proof of concept testing without spending a dime. You know that I always like to put asterisks next to the word free. This is actually free. No asterisk. Start now. Visit https://snark.cloud/oci-free that's https://snark.cloud/oci-free.Corey: If I were looking to get a job in enterprise these days, it feels like Java is the direction to go in, with the counterpoint that, let's say that I go the path that I went through: I don't have a college degree; I don't have a high school diploma. If I were to start out trying to be a software engineering today, or advising someone to do the same, it feels like the lingua franca of everything today seems to be JavaScript in many different respects. It does front end; it does back end; people love to complain about it, so you know it's valid. To be clear, I find myself befuddled every time I pick it up. I'm not coming at this from a JavaScript fanboy perspective in any respect.The asynchronous execution flow always messes with my head and leaves me with more questions than answers. Is that assessment though—of starting languages—accurate? Are there cases where Java is absolutely the right answer, as far as what to learn first?Angie: Yeah. So, I first started with C++, and then I learned Java. Well, what I find is, Java because it's so strict—it's a statically typed language, and there's lots of rules, and you really need to understand paradigms and stuff like that with this language—it's harder to learn, but once you learn it, it's much easier to pick up other languages, even if they're dynamically typed, you know? So, that's been my experience with this. As far as jobs, so the last time I looked at this, someone did some research and wrote it up—this was 2019—and they looked at the job openings available at the time, and they divided it by language. And Java was at, like, 65,000 jobs open, Python was a close second was 62,000, and JavaScript was third place with 39,000.So, quite a big difference. But if you looked at tech Twitter, you'd think, like, JavaScript is all there is. Most of my followers and folks that I follow are JavaScript folks, front-end folks. So, it is a language I think you definitely need to learn; it's becoming more and more prevalent. If you're going to do any sort of web app, [laugh] you definitely want to know it.So, I'm definitely not saying, “Oh, just learn Java and that's it.” I think there's definitely a need for adding JavaScript to your repertoire. But Java, there does seem to be more jobs, especially the big enterprise-type jobs, in Java.Corey: The reason I ask so much about some of the early-stage stuff is that in your spare time—which it sounds like you have so much of these days—you volunteer with Black Girls Code to help teach coding workshops to young girls in an effort to attract more women and minorities to tech. Which is phenomenal. Few years ago, I was a volunteer instructor for Year Up before people really realized, “Oh, maybe having an instructor who teaches by counterexample isn't necessarily the best approach of teaching folks who are new to the space.”But the curriculum I was given for teaching people how Linux worked and how to build a web servers and the rest, started off with a three-day module on how to use VI, an arcane text editor that no one understands, and the only reason we use it is because we don't know how to quit it.Angie: [laugh].Corey: And that's great and all, but I'm looking at this and my immediate impression was, “We're scrapping that, replacing it with nano,” which is basically what you see is what you get, and something that everyone can understand and appreciate without three days of training. And it felt an awful lot like we're teaching people VI almost as a form of gatekeeping. I'm curious; when you presumably go down the path of teaching people who are brand-new to the space? How do you wind up presenting testing as something that they should start with? Because it feels like a thing you have to know first before you can start building anything at scale, but it resonates, on some level, with feeling like it's, ah, you must be able to learn this religion first; then you'll be able to go and proceed further. How do you square that circle?Angie: Yeah. So, I had the privilege of being an adjunct professor at a college, and I taught Java programming to freshmen. This was really interesting because there's so much to teach, and this is true of all the courses. So, when I say that they don't include it in the curriculum, that's not really that much of a slight on them. Like, it's just so much you have to cover.So I, me, the testing guru, I still couldn't find space to devote an entire sitting, a chapter, or whatever on testing. So, I kind of wove it into my teaching style. So, I would just teach the concept, let's say I'm teaching loops today, and I'll have a little exercise that you do in class. So, we do things together, and then I say, okay, now you try it by yourself. Here's a problem; call me over when you're done.And as they would call me over when they're done, I would break it; I would break their code, right? I'd do some input that they weren't expecting and all of a sudden is broken. And they started expecting me to do this, you know? “She's going to come and she's going to break my stuff.” So, they start thinking themselves, “Let me test it before I give it to my user,” who is Professor Angie, or whatever.So, that's how I taught them that. Same with homework assignments. So, they would submit it, I would treat it like a code review, go through line by line, I didn't have any automated systems to test their homework assignments. I did it like a code review, gave them feedback on how to improve their style, but also I would try to break it and give them, “Here's all the areas that you didn't think of.” So, that was my way of teaching them that quality matters in how to think about beyond the requirement.The requirement is going to say, “Someone needs to be able to log in.” It's not going to give you all of the things that should happen, you know if there's a wrong password, so these are things, as an engineer, you need to think beyond that one line requirement that you've got and realize that this is part of it as well.Corey: So, it's almost a matter of giving people context beyond just the writing of the code, which frankly, seems to be something that's been missing for many aspects of engineering culture for a while, the understanding the people involved, understanding that it is not just you, or your department, or even your company in some cases.Angie: Exactly. And I tried to stress that very heavily in each lecture: who is your end-user? And your end-user cannot see your code, they cannot see your comments in the code that's telling them, “Make sure you input it this way,” or whatever. None of that is seen so you have to be very explicit in your messages, and your intent, and behavior with the end-user.Corey: One last area I wanted to cover with you, when I was doing some research on you before the show, is that you are an IBM Master Inventor, which I had no idea what that was. Is that a term of art? Let me Google it. And it turns out that you have, according to LinkedIn at least, 27 patents in your name. And it's, “Oh.”Yeah, it's one of those areas where you look at something like, what gives someone the hubris to call themselves—or the grounds to call themselves that? And, “Oh, yeah. Oh, they're super accomplished, and they have a demonstrated track record of inventing things that are substantial and meaningful. I guess that would do it.” I'd never heard the term until now. What is that? And how are you that prolific, for lack of a better term?Angie: Yeah, so I used to work at IBM and they're really big on innovation. And I haven't kept track in a while, but for many, many years, they were the number one producer of patents [laugh] of this year or whatever. So, it was kind of in the culture to innovate. Now, I will say, like, a very small percentage of people—employees—there would take it as far as I did to actually go and patent something—[laugh]—Corey: Oh, it's the ‘don't offer if you're not serious,' model.Angie: Yeah. [laugh]. But I mean, it was there; it was a program there where, hey, you got an idea for a software patent? Write it up, we'll have our lawyers, our IP lawyers review it, and then they'll take your little one-page doc and turn it into a twenty-five-page legal document that we submit to the USPTO—United States Patent Trademark Office—who then reviews it and decides if this is novel enough and grants it, or dismisses it. And, “Hey, we'll pay you for these patents. We'll pay for the whole process.” And so I thought, “Heck, why not?”And I kind of got hooked. [laugh]. So, it just so happens that I got a lot of good ideas. And I would collaborate with people from other areas of the business, and it was an excellent way for me to learn about new technologies. If something new was coming out, I would jump on that to explore, play with it, and think about, are there any problems that this technology is not aimed to solve, but if I tweak it in some way, or if I integrate it with some other concept or some other technology, do I get something unique and novel here?And it got to the point where I just started walking through life and as I'm hit with problems—like, I'll give you an example. I'm in the grocery store, right, and this inevitably happens to everyone, what, you choose the wrong line in the grocery store. “This one looks like it's moving, I'm going to go here.” And then the whole time, you're looking to your right, and that line is moving. And you're, like, stuck.Corey: Every single time.Angie: Every time. So, it got—[laugh]—Corey: Toll booths are the same way.Angie: —it got to the point where I started recognizing when I'm frustrated, and say, “This is a problem. How can I use tech to solve this?” And so I, in that problem, I came up with this solution of how I could be able to tell which one of these is the right line to get into. And that consisted of lots of things like scanning the things in everyone's cart. On your cart, you have these smart carts that know what's inside of them, polling the customers' spending or their behavior; so are they going to come up here and send the clerk back to go get cigarettes, or alcohol, or are they going to pull out 50 coupons? Are they going to write a check, which takes longer?So, kind of factoring in all of these habitual behaviors and what's in your cart right now, and determining an overall processing time. And that way, if you display that over each queue, which one would be the fastest to get into. So, things like that is what I started doing and patenting.Corey: Well, my favorite part of that story is that it is clearly a deeply technical insight into this, but you've told the story in a way that someone who is not themselves deeply technical can wrap their heads around. And I just—making sure you're aware of exactly how rare and valuable that particular skill set is. So, often there are people who are so in love with a technology that they cannot explain to another living soul who is not equally in love with that technology. That alone is one of the biggest reasons I wanted to have you on this show was your repeated, demonstrated ability to explain complex things simply in a way that—I know this is anathema for the tech industry—that is not condescending. I come away feeling I understand what you were talking about, now.Angie: Thank you so much. That is one of the skills I pride myself on. When I give talks, I want everyone in that room to understand it, even if they're not technical. And lots of times I've had comments from anyone from, like, the janitor to the folks who are working A/V who, they don't work with computers or anything at all and they've come to me after these talks like, “Okay, I heard a lot of talks in here. Everybody is over my head. I understood everything you said. Thank you.” And yet it's still beneficial to those who are deeply technical as well. Thank you so much for that.Corey: No, it's a very valuable thing and it's what I look for the most. In fact, my last question for you is tying around that exact thing. You have convinced me. I want to learn more about test automation, and learn how this works and with an eye toward possibly one day applying it to some of my crappy nonsense that I'm writing. Other than going on Google and typing in a variety of search terms that will lead me to, probably, a Stack Overflow thread that has been closed as off-topic, but still left up to pollute Google search results, where should I go?Angie: Yeah. So, I've actually started an entire university devoted to testing, and it's called Test Automation Universityand I got my employer, Applitools, to sponsor this, so all of the courses are free.And they are taught by myself as well as other leading experts in the test automation space. So, you know that it's trusted; I vet all of the instructors, I'm very [laugh] involved in going through their material and making sure that it's correct and accurate so the courses are of top quality. We have about a little over 85,000 students at Test Automation University, so you definitely need to become one if you want to learn more about testing. And we cover all of the languages, so Java, JavaScript, Python, Ruby, we have all of the frameworks, we have things around mobile testing, UI testing, unit testing, API testing. So, whatever it is that you need, we got you covered.Corey: You also go further than that; you don't just break it down by language, you break it down by use case. If I—Angie: Yeah.Corey: —look at Python, for example, you've got a Web UI path, you've got an—Angie: Exactly.Corey: API path, you've got a mobile path. It aligns not just with the language but with the use case, in many respects.Angie: Mm-hm.Corey: I'm really glad I asked that question, and we will, of course, include a link to that in the [show notes 00:31:10]. Thank you so much for taking the time to speak with me. If people want to learn more, other than going to Test Automation University, where can they find you?Angie: Mm-hm. So, my website is angiejones.tech—T-E-C-H—and I blog about test automation strategies and techniques there, so lots of good info there. I also keep my calendar of events there, so if you wanted to hear me speak or one of my talks, you can find that information there. And I live on Twitter, so definitely give me a follow. It's @techgirl1908.Corey: And we will, of course, include links to all of that. Thank you so much for being so generous with your time and insight. I really appreciate it.Angie: Yeah, thank you so much for having me. This was fun.Corey: Angie Jones, Java Champion and senior director at Applitools. I'm Cloud Economist Corey Quinn and this is Screaming in the Cloud. If you've enjoyed this podcast, please leave a five-star review on your podcast platform of choice, whereas if you hated this podcast, please leave a five-star review on your podcast platform of choice along with a long, ranting, incoherent comment that fails to save because someone on that platform failed to write a test.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.

This week we chat with Angie Jones about all things testing. We'll cover unit testing, visual testing, end-to-end testing, and more!

This week we chat with Angie Jones about all things testing. We'll cover unit testing, visual testing, end-to-end testing, and more!

In this episode, we talk about about test automation with Angie Jones, senior director of developer relations at Applitools, and creator of Test Automation University. Show Notes DevNews (sponsor) CodeNewbie (sponsor) RudderStack (sponsor) Cockroach Labs (sponsor) Cloudways (sponsor) Applitools Test Automation University Selenium Webdriver Test automation

Mercedes unveils its EQS, an all electric S-class luxury sedan, Reddit launches its Clubhouse competitor, and Nica Montford from SnobOS introduces us to Angie Jones, First-Ever Black Female Java Champion.Starring Tom Merritt, Sarah Lane, Tim Stevens, Roger Chang, Joe.Link to the Show Notes.  See acast.com/privacy for privacy and opt-out information.

Mercedes unveils its EQS, an all electric S-class luxury sedan, Reddit launches its Clubhouse competitor, and Nica Montford from SnobOS introduces us to Angie Jones, First-Ever Black Female Java Champion. Starring Tom Merritt, Sarah Lane, Tim Stevens, Roger Chang, Joe. MP3 Download Using a Screen Reader? Click here Multiple versions (ogg, video etc.) from Archive.org Follow us on Twitter Instgram YouTube and Twitch Please SUBSCRIBE HERE. Subscribe through Apple Podcasts. A special thanks to all our supporters–without you, none of this would be possible. If you are willing to support the show or to give as little as 10 cents a day on Patreon, Thank you! Become a Patron! Big thanks to Dan Lueders for the headlines music and Martin Bell for the opening theme! Big thanks to Mustafa A. from thepolarcat.com for the logo! Thanks to our mods Jack_Shid and KAPT_Kipper on the subreddit Send to email to feedback@dailytechnewsshow.com Show Notes To read the show notes in a separate page click here!

H1, S2 - MAS Angie Jones & Mountain Stage 04/09/2021

Hi, Spring fans! Welcome to another wild and wonderful installment of _A Bootiful Podcast_! In this episode, [Josh Long (@starbuxman)](http://twitter.com/starbuxman) talks to inspiration, legend and fellow Java champion and legend [Angie Jones (@techgirl1908)](http://twitter.com/techgirl1908). Also: Java 16, the R2DBC driver for Oracle database, Spring Native (GraalVM!), and Bootiful Cassandra!

Angie Jones, Java Champion, and Principal Developer Advocate at Applitools, walk Adi Polak through the concept of Visual testing, How Data & AI assists with test automation, and how Applitools partners with Microsoft.Follow @CH9 http://www.twitter.com/ch9 Follow @TechExceptions https://twitter.com/TechExceptions Follow @AdiPolak https://twitter.com/AdiPolak

Visual Testing has come a long way from the early days of x,y mouse clicks and pixel comparisons. Angie Jones joins the show to discuss how modern visual testing tools work and how to incorporate visual testing into a complete testing strategy. Some of the discussion: Classes of visual testing: problems with pixel to pixel testing DOM comparisons, css, html, etc. AI driven picture level testing, where failures look into the DOM to help describe the problem. Where visual testing fits into a test strategy. Combining "does this look right" visual testing with other test workflows. "A picture is worth a thousand assertions" - functional assertions built into visual testing. Baselining pictures in the test workflow. Also discussed: - automation engineer - Test Automation University Special Guest: Angie Jones.

In this week's episode of the Between Two Divs podcast I chatted with Angie Jones and we talked about her tech journey up until this point. We also discussed what the current election means for us and what is a dish that has to be at every Thanksgiving table. Follow Angie @techgirl1908 on Twitter and if you want to be a testing superstar check out Test Automation University https://testautomationu.applitools.com/

  Angie is a Principal Automation Architect, Director of Test Automation University, she is an International Keynote Speaker and Java Champion, and is the creator of more than 25 patented inventions.   Links https://angiejones.tech https://twitter.com/techgirl1908 https://github.com/angiejones https://www.youtube.com/user/angieluvboo https://www.linkedin.com/in/angiejones/   Resources https://testautomationu.applitools.com/ https://www.youtube.com/watch?v=pKKZ2QM_36k "Tempting Time" by Animals As Leaders used with permissions - All Rights Reserved   × Subscribe now! Never miss a post, subscribe to The 6 Figure Developer Podcast! Are you interested in being a guest on The 6 Figure Developer Podcast? Click here to check availability!  

“My difference are my superpowers” -Angie Jones   Angie Jones is a Java Champion and Senior Developer Advocate who specializes in test automation strategies and techniques. She shares her wealth of knowledge by speaking and teaching at software conferences all over the world, writing tutorials and technical articles on angiejones.tech, and leading the online learning platform, Test Automation University.   As a Master Inventor, Angie is known for her innovative and out-of-the-box thinking style which has resulted in more than 25 patented inventions in the US and China. In her spare time, Angie volunteers with Black Girls Code to teach coding workshops to young girls in an effort to attract more women and minorities to tech.   In this episode, I chat with Angie Jones who is a Senior Developer Advocate specialized in test automation strategies & techniques about how she discovered her niche in tech. Angie shares how she got her patents, teaches us her secret to fighting imposters syndrome, and shows us how having a personal brand can help you level up in your career.   Key takeaways from this episode: What is test automation? The skillsets needed to become an effective test automation engineer One simple exercise you can do to combat imposter syndrome The # 1 type of testing everyone should know about Misconceptions about being a test automation engineer The importance of speaking up and sharing your ideas How developing your personal brand can level up your career 3 major keys for getting into tech as a developer Connect with Angie : YouTube: https://www.youtube.com/user/angieluvboo?sub_confirmation=1 LinkedIn: https://www.linkedin.com/in/angiejones Website: https://angiejones.tech/ Twitter: https://twitter.com/techgirl1908 Free Courses: https://testautomationu.applitools.com/instructors/angie_jones.html Connect with Grace: Twitter: https://twitter.com/GraceMacjones LinkedIn: https://www.linkedin.com/in/gracemacjones/   Follow the podcast: Twitter: https://twitter.com/techunlockedpod Instagram: https://www.instagram.com/techunlockedpod/ LinkedIn: Tech Unlocked   Thank you so much for listening to this podcast! If you enjoyed listening to this episode, please leave a rating and review on iTunes. Use the hashtag #Techunlocked to ask questions and share your thoughts. Have a tech-related question? Shoot us an email techunlockedpod@gmail.com 

For this episode, I interviewed Oren Rubin, the CEO and founder of Testim (https://www.testim.io/, a leading innovative product in the Web test automation domain. He has over 20 years of experience in the Software Industry building products for developers. Highlights of this first part of the interview: - We shared the funny story of how we met (thanks Angie Jones!) - We discuss the pesky challenge of test automation: dealing with flaky tests - Oren also talked about many test automation tools, highlighting the main differences between them including Selenium, Cypress, Puppeteer, and so on. Hope you enjoy the talk! If you want to read a transcript as you listen, check it out here: https://bit.ly/2NEGGaI

In this episode, we’re talking about testing code with Angie Jones, Senior Developer Advocate at Applitools, and former Senior Software Engineer in Test at Twitter. Angie talks about how she got into testing, some of the testing and problems she had to solve while working at Twitter, and why all developers should understand the basics of testing. Show Links Digital Ocean (sponsor) MongoDB (sponsor) Heroku (sponsor) TwilioQuest (sponsor) Applitools C++ Test automation Java Software widget Library Heuristic Pair programming Faker Application programming interface (API) Boolean expression Test Automation Frameworks Codebase Unit testing UI (User interface) Code review Test Automation University JavaScript Debugging React Ministry of Testing Conditional For loop Data structure Language-agnostic

Homework: Go through Angie's Visual Testing Course: Automated Visual Testing: A Fast Path To Test Automation SuccessVisual testing is like snapshot testing with images. So when your application is in the state that you want it to be in, you verify this as a human being, and then utilize tools to take a picture of your application in that state. Visual testing isn't a new concept, but the technology was previously flaky. But now, Applitools is using AI and machine learning to be able only to detect the things that we care about as human beings.Visual testing catches issues that your scripts won't detect, and Applitools is especially powerful at it. The processing gets offloaded onto the Applitools servers, and snapshots of your app are tested on multiple platforms so you can be confident that no visual bugs get created anywhere!Transcript"Angie Jones Chats With Kent About Automated Visual Testing" TranscriptResourcesTest Automation UniversityAutomated Visual Testing: A Fast Path To Test Automation SuccessAngie JonesTwitterGithubWebsiteLinkedInKent C. DoddsWebsiteTwitterGithubYoutubeTesting JavaScript

Brandi Olson on Agile Uprising, Judy Rees on Engineering Culture by InfoQ, J. J. Sutherland on Agile FM, Angie Jones on Developing Up, and Eric Ries on Unlearn. I’d love for you to email me with any comments about the show or any suggestions for podcasts I might want to feature. Email podcast@thekguy.com. And, if you haven’t done it already, don’t forget to hit the subscribe button, and if you like the show, please tell a friend or co-worker who might be interested. This episode covers the five podcast episodes I found most interesting and wanted to share links to during the two week period starting November 11, 2019. These podcast episodes may have been released much earlier, but this was the fortnight when I started sharing links to them to my social network followers. BRANDI OLSON ON AGILE UPRISING The Agile Uprising podcast featured Brandi Olson with host Andy Cleff. Andy asked Brandi about what she means by multitasking. At the individual level, she says we use the word multitasking to describe what is happening when we are trying to do more than one thing at the same time. It is a misnomer though because our brains do not actually do more than one thing at the same time. Her bigger interest is in what happens when you have groups of people trying to multitask all day long. She calls this “organizational multitasking.” Say you have a team and they have a backlog. Organizational multitasking happens when somebody tells that team, “You need to get all ten of these things done this week and you need to start them all and I want to see the progress you are making each day.”  The opposite of that, organizational focus, happens when you say, “Work on this thing first before you work on the next thing.” At the team level, she says, there are a number of illusions about how to be more productive and effective. One illusion is that getting started on everything is the way to get it done and if everything is important we have to do it all at the same time. This breaks down because of the reality of how our brains work. Research shows that when a person has to juggle two projects throughout a day, they will spend 40% of their brain capacity and energy on context-switching. For three projects, energy devoted to context-switching jumps to 60%. Not only does this take time away from more productive work, but we don’t even notice the time we lost. A further cost of having entire teams of people running around at 40% brain capacity is that they are less likely to identify the real problems to work on and it feels like they cannot slow down to figure out what the real problems are. Andy asked whether the solution should come up at the individual level where someone starts to say, “No,” or is it something that starts at a leadership layer. Brandi says it is not a problem that can be solved individually. It needs to start with our leaders. Some of the problems that start to show up in these contexts are a failure to solve the right problems, a reduction in quality, an increase in employee turnover, a reduction in equity and diversity, and burnout. These problems typically get addressed by solving the symptoms. Andy asked what she does to help organizations separate the symptoms from the cause. Brandi says she does this by making the costs of multitasking visible. She told the story of a company that surveyed 600 companies and their HR leaders about the biggest threats to their workforce. Over 80% of those leaders said that employee turnover was the biggest threat. The company then surveyed the employees at those same companies and the employees overwhelming named having too much overtime and unrealistic work expectations. Going back to the same HR leaders, a fifth of them wouldn’t be doing anything about their turnover problem in the next year because the leaders had too many competing priorities. The overwhelming illusion that too many leaders buy into is that, while turnover and burnout are problems, we cannot do anything about it because there is too much important work to do. A further illusion is that we can capacity plan by cutting everybody’s time up; we can break up your time among projects and it will all add back up to 100%. Apple Podcasts link: https://podcasts.apple.com/ca/podcast/the-cost-of-organizational-multi-tasking-with-brandi-olson/id1163230424?i=1000453339079 Website link: http://agileuprising.libsyn.com/the-cost-of-organizational-multi-tasking-with-brandi-olson JUDY REES ON ENGINEERING CULTURE BY INFOQ The Engineering Culture by InfoQ podcast featured Judy Rees with host Shane Hastie. Shane asked Judy if it is possible to have an effective remote meeting. She says absolutely and backed it up with an example of one of her own students telling her recently that participants in her remote meeting said that her remote meeting was better than an in-person meeting. Shane asked about the secret sauce of a good remote meeting. Judy says it is probably planning. She also said that when remote, each person brings part of the meeting room with them. She says people don’t realize how important the environment is to conversations. When you put people in a small space, they pay attention to small details and administrative kinds of things. For “blue sky thinking,” take people outside or to a room with a big view. In real world spaces, we already know where to find small rooms and rooms with big views, but online, we need to create equivalent spaces. You need not only to ensure that all participants turn up with a decent headset, cameras turned on, and light on their faces, but also to figure out the activities so that you have enough social time at the beginning, during, or end of the meeting. The beginning and end of the meeting are critical parts of a meeting. Online, we often miss out on these beginnings and endings and it affects the quality of the conversations. She also says that most people find it easier to engage and participate when the meeting is small. This connects with what Courtland Allen said on Software Engineering Daily about communities in the previous fortnight’s review. She says that if you can’t limit the space, you can limit presentation time to 5 to 7 minutes and get then people doing something. She also says to use breakout rooms and use liberating structures like 1-2-4-All (http://www.liberatingstructures.com/1-1-2-4-all/). Knowing Judy’s expertise in Clean Language, Shane asked how might Clean Language be used to enhance remote meetings. Judy says that teaching people on remote teams to ask more non-judgmental questions about what somebody means by what they say can have a profound effect. Because of the missing socialization in remote meetings mentioned earlier and the fact that remote teams often have more cultural differences than co-located teams, misunderstandings are more likely. Therefore, learning to ask questions to clarify in a way that doesn’t sound like an interrogation but helps both parties to get clearer more quickly becomes particularly valuable. Apple Podcasts link: https://podcasts.apple.com/ca/podcast/judy-rees-on-effective-remote-meetings/id1161431874?i=1000450875620 Website link: https://soundcloud.com/infoq-engineering-culture/judy-rees-on-effective-remote-meetings J. J. SUTHERLAND ON AGILE FM The Agile FM podcast featured J. J. Sutherland with host Joe Krebs. J. J. Sutherland is the CEO of Scrum Inc. and the son of Jeff Sutherland, the co-creator of Scrum. J. J.’s new book is called “The Scrum Fieldbook.” Joe asked what made him pick such a title. J. J. said he wanted to write a book about all the places Scrum Inc. has been all over the world and the many different domains far beyond software. He also wanted to show how Scrum Inc. thinks about Scrum and what are the patterns and anti-patterns. He says that Scrum is a universal framework for accelerating human effort with applications in aerospace, banking, and even beer-making. No one does Scrum just to do Scrum. Scrum is designed to produce value, which requires knowing more than just the Scrum guide. It involves understanding why Scrum works the way it does, understanding complex adaptive systems theory, knowing that you need to empower your teams and ensuring your teams are the right size. Scrum is about running experiments and getting feedback from the customer and adapting to that feedback. He sees people spending six months to a year planning how to do Scrum before they even start. Instead, he says to just do something. That is where you’ll get the information to iterate towards the right thing. Joe expressed his appreciation as a Scrum coach for the chapter in the book on the difference between busy and done. When J. J. worked in radio, producers used to talk about how much effort they put into the radio programs and he would have to point out to them that no listener cares how hard you worked on it; they care about what comes out of the box. Apple Podcasts link: https://podcasts.apple.com/ca/podcast/jj-sutherland-agile-fm/id1263932838?i=1000453430262 Website link: https://agile.fm/agilefm/jjsutherland ANGIE JONES ON DEVELOPING UP The Developing Up podcast featured Angie Jones with host Mike Miles. Mike asked Angie what she considers the ultimate goal of code review. Angie says the goal is to ensure everyone is aware of and content with what is being contributed to the code base; it is not a nitpicking session or an opportunity to bash your least favorite developer. Code review is also a good way to catch missed requirements. Angie encourages code reviewers to review the unit tests just as closely as the implementation.  Angie says the best code reviews are those you block out time for and make part of your routine. They aren’t something you skim while you drink a cup of coffee. When she reviews code, she always pulls up the requirement in the spec, doc, or ticket to see that the code under review fulfilled it. She looks for whether the implementation is efficient and at the right level of abstraction. She says that code reviewers have the opportunity to think at a broader level and see opportunities for code reuse. Angie sees code review as a form of mentoring without having an official mentorship relationship. Official forms of mentoring can feel like an obligation for the mentor because they have to set up meetings, learn the mentee’s career goals. Angie says that code review is a more subtle form of mentorship that is just as powerful. Apple Podcasts link: https://podcasts.apple.com/ca/podcast/code-reviews/id1156687172?i=1000452808997 Website link: https://www.developingup.com/episodes/46-dflXzZ1V ERIC RIES ON UNLEARN The Unlearn podcast featured Eric Ries with host Barry O’Reilly. Eric described how he started his company IMVU and how, when wanted to do practices like split testing, he got pushback. People thought of it as a direct marketing technique, not a product development technique. He would argue, “Shouldn’t we use the scientific method to test our hypotheses?” He wanted customers involved from day one, he wanted to ship more frequently than was considered normal at the time. Looking back, he sees how extreme his ideas were at the time and is glad his cofounders didn’t fire him. As the company got more successful, his techniques got more controversial because the company now had more to lose. He said, “When you do things in an unconventional way, every problem the company has gets blamed on the unconventional method.” Barry pointed out that having to constantly explain the value of these unconventional methods likely made his thinking more resilient and could have been the seed for his next step. At one board meeting, he felt like he was going to be fired. He was tempted to apologize and compromise, but made the conscious choice to advocate for what he actually believed despite the potential negative consequences. He rationalized it like this: this is a small business and a small business is like a small town. In a small town, everybody knows everybody and he wanted people to know what he stood for. If people don’t like it this time and they fire him, okay. A day will come, he reasoned, when they are going to be in a situation where they need to get something done fast and will remember him because they know what he stands for. He radically misjudged the situation: the more he stood for those values and explained them, the more they resonated with people. If he hadn’t had the courage to put his career and reputation at risk, he never would have found out who the ideas resonated with. Eric says it wasn’t until later that he understood the importance of iteration happening within the context of a long term vision. Today, people understand Lean Startup as scientific hypotheses, a testing philosophy, small batches, and pivoting or changing strategy without changing vision. They know it is logically incoherent to have a pivot if you have no vision. Companies who were early disciples of Lean Startup, unfortunately, did not understand this and thought they could A/B test their way to success without any kind of vision. Apple Podcasts link: https://podcasts.apple.com/ca/podcast/the-lean-startup-pivot-with-eric-ries/id1460270044?i=1000451993479 LINKS Ask questions, make comments, and let your voice be heard by emailing podcast@thekguy.com. Twitter: https://twitter.com/thekguy LinkedIn: https://www.linkedin.com/in/keithmmcdonald/ Facebook: https://www.facebook.com/thekguypage Instagram: https://www.instagram.com/the_k_guy/ YouTube: https://www.youtube.com/c/TheKGuy Website:

The core of having a career in development is focused on writing code. To grow and improve in your career, means improving on the code that you write. To do so, requires insights and feedback from those you work with. In this episode we talk with Angie Jones (@techgirl1908), a developer advocate, about the benefits of code reviews. Angie provides her insights into what developers and teams can do to have meaningful code reviews that look beyond just syntax issues. Our conversation focuses on helpful mindsets to take when participating in a code reviews, roles developers of all levels can take on and how ultimately reviews help developers improve. Growth in your development career requires improving your technical capabilities and code reviews are one tool to do so.Links from this EpisodeAngie Jonesangiejones.tech10 Commandments of Code ReviewsPrevious Episodes MentionedThe Art of the Code ReviewHave an idea for a future episode?Tweet Us: @devuppodcastEmail Us: hello@developingup.com

As DevOps matures, and the “shift-everything-left” philosophy gains ascendancy, there’s a movement to automate all—or most—phases of testing. However, there are some critical functions that may resist automation. In fact, contrary to the “automate-everything” impetus, human testers won’t ever go away. Indeed, human testers need to be more involved, and earlier in the development process. In this podcast, Mike Kavis and guest, Angie Jones, discuss the human aspect of testing and how humans add significant value by assessing the system as a whole, helping developers design better code, and determining the level of testing automation that should occur. Angie also shares the testing automation matrix she has developed. Finally, they cover testing of machine learning algorithms—ways to help prevent or reduce bias and make algorithms more effective, and the emerging field of visual testing, which uses humans to ensure that graphics-heavy apps function and appear as designed.

Have you ever wondered what it takes to be an effective teacher in the tech industry? Well wonder no more!We had the pleasure of chatting with Angie Jones, Senior Developer Advocate at Applitools and Director at Test Automation University about her experience as a teacher. Angie talks to us about her teaching and learning styles and shares some advice for those looking to get into the world of teaching.In this episode, we discussed how to teach to multiple skill levels, common misconceptions about being a teacher, and much more!For the full show notes and links to the speakers, check out our website!

In the summer of 1982 , professor Edsger Dijkstra wrote a paper exhorting computer scientists to start numbering at 0. Quite Odd! What is not great about starting numbering a set of items at 1? What’s different between for-loops that starts counting at 0 or 1 ? Well, let’s read professor Djikstra’s paper to understand his reasoning behind such fixation with 0 being the first index, which is still a big deal in Tech. - Research Paper - ( #Reading_Dijkstra ) “Why numbering should start at 0. ” by Edsger W. Dijkstra [ https://www.cs.utexas.edu/users/EWD/transcriptions/EWD08xx/EWD831.html ] - Acknowledgements - Thanks to Angie Jones and “Adam In SF” for your tweets, you inspired this podcast! - Twitter accounts, You might want to follow - Angie Jones : @techgirl1908 “Adam In SF” : @asolove Podcast : @ReadingSPaper Host : @NVidaYotcho - Related Blogs - https://medium.com/@nvidayotcho/conventions-and-gatekeeping-in-tech-c79bde3567ce

While scrolling my twitter feed, I got reminded how thrilling scientific papers can be to the point of starting the routine of reading them daily. After reflection, I thought “the merrier, the better” and decided to take you on this journey with me. Let’s push the limits of the unknown together! Are you ready? Good! By the way, I am N’Vida! - Acknowledgements - Thanks to Angie Jones for being such an inspiration for women like me in Tech, and inspiring this new journey of mine! - Twitter accounts, You might want to follow - Angie Jones : @techgirl1908 Podcast : @ReadingSPaper Host : @NVidaYotcho - @NajyJj [ anime only ] - Related Blogs - https://medium.com/@nvidayotcho www.readingsientificpaper.com

Welcome a community favorite back to the podcast to chat with us about her intriguing keynote at the upcoming STPCON conference which is entitled: “A Tale of Testing the Un-Testable." Angie Jones is an accomplished inventor, programmer, thought-leading automation guru and all-around one of the most passionate techies we know. Visit https://www.stpcon.com to register today!

Welcome a community favorite back to the podcast to chat with us about her intriguing keynote at the upcoming STPCON conference which is entitled: “A Tale of Testing the Un-Testable." Angie Jones is an accomplished inventor, programmer, thought-leading automation guru and all-around one of the most passionate techies we know. Visit https://www.stpcon.com to register today!

Barb Emmett is joined by Angie Jones to talk about dock dogs, and Susan Higginson to talk about the versatile Portuguese water dog.

Are you trying to find a way to learn test automation? Or maybe you want to refresh or enhance what you already know. Today we’ll be TestTalking with Angie Jones all about ways to learn more about automation. So listen up and discover a must know resource for the automation testing community.

Arlene Andrews talks about good online learning resources. This episode is not sponsored! Want to be a sponsor? You can contact me or check out my sponsorship gig on Fiverr Show Notes: Arlene Andrews Our Learning Map Free Code Camps Coding Blocks "Clean Code" episodes CodingBlocks Slack The Ministry of Testing QIT is a search engine for podcasts. As of April 21st, this very podcast will now start showing up in QIT searches! QIT source code QIT feed loader source code Test Automation University Angie Jones Amber Race CS 50 via EdX @SWYX: Learn in Public Arlene is on Twitter Want to be on the next episode? You can! All you need is the willingness to talk about something technical.

GUEST BIO: Anne-Marie is a software tester, trainer and coach with a reputation of excellence and passion for the craft of software testing.  An electronic engineer by trade, software testing chose her when she started testing protocols against European standards. Anne-Marie has developed software testing courses and lectured at the University of Technology, Sydney. EPISODE DESCRIPTION: Phil’s guest on today’s show is Anne-Marie Charrett. She is currently running her own software testing, training and coaching business. By trade, she is an electronic engineer, who, early in her career became interested in testing protocols, which she has been doing for the past 20 years. Anne-Marie is also a coach, trainer and Software Test Consultant. She is also a well-known conference speaker. KEY TAKEAWAYS: (1.01) – So Anne-Marie, can I ask you to expand on that brief intro and tell us a little bit more about yourself? Anne-Marie explains that when she left university, it was not her intention to become involved in software testing. However, at the time, there was growing interest in protocols and making sure that they conformed to European standards, something that Anne-Marie was drawn to. Anne-Marie got used to testing each layer to make sure that it conformed to the standard. But, she soon realised that this was not an indication of quality. She recognised the fact that things had to work together properly for the system or software to be deemed as truly fit for purpose. The realisation that testers had to dive deeper and go beyond whether the software meets a standard and check that it does its job drove her to become a software tester. From there, becoming a software engineer was a natural progression. (3.17) – Can you please share a unique career tip with the I.T. career audience? Over the course of her career, Anne-Marie has learned to follow the advice – “don’t be nice, but do be kind.” She goes on to explain what she means by that. She says that you need to work smart. To do what is right for your career and the project that you are working on. So, sometimes you have to push to get things done and stand up for what you know has to be done. But, you can still do that in a kind way. She went on to add that you need to think strategically about your career and how you get things done in the workplace. This is something Anne-Marie thinks Angie Jones does particularly well. (3.17) – Can you tell us about your worst career moment? And what you learned from that experience. Years ago, Anne-Marie moved from managing a team of 30 testers to leading 250 engineers. For her, it was a big change. She was working in a very different environment with people who thought and worked in a different way. Her new team needed to be motivated differently. Unfortunately, Anne-Marie did not fully realize this until it was too late. Anne-Marie had taken a very similar approach as she did when she was running her testing team. Making sure that everyone understood the big picture. What the end customer wanted, how the developers worked as well as what the system needed to do. Her band of 30 loyal testers had happily followed her and thrived when she had managed them in this way. The engineers were not as comfortable with this approach. They were far more empirical. For them, it was facts and figures that motivated them. So, things did not go well. However, she learned a lot from this experience, including the fact that there is a difference between leadership and management. She also realized that you need to communicate your value, even when you have not been asked to do so directly. If you produce software you have something solid to show for your efforts. With testing, it is not as easy to demonstrate how you contribute. It also taught her to think and talk about quality engineering in terms of business outcomes. This helps the person you are speaking with to understand the contribution you are making to the company’s bottom line. Anne-Marie explains that you have to adapt your message to fit in with that person’s role. For example, the finance guys will be more interested in how much the new software saves the company than they would be in the fact it will make someone’s job easier. (10.10) – Phil asks Anne-Marie to share her best career moment. Anne-Marie’s most rewarding experience has been running her own company. She has really enjoyed creating a space in which talented people can work, thrive and discover skills that they never knew they had. Anne-Marie is also really proud of SpeakEasy, which she set up with Fiona Charles. This initiative pairs up those who want to speak at conferences with mentors. The majority of IT conference speakers are still men, something Anne-Marie and Fiona wanted to play a part in changing. As a result, most of the people they help are women or those from minority groups. It has been a huge success. Plenty of experienced speakers have come forward to be mentors and they have helped lots of people. Plus, many conference organizers have agreed to leave a few slots free specifically for SpeakEasy participants, which has been a great help.  (15.03) – Can you tell us what excites you about the future of the IT industry and careers? The fact that the industry has woken up to the importance of diversity is something that Anne-Marie sees as a big positive. Diversity will lead to more ideas and different solutions. (16.39) – What drew you to a career in IT, Anne-Marie? Like many people of her generation Anne-Marie had a Commodore 64, which sparked her interest in IT. But, not necessarily in the same way it did for many others. Like most kids, she found learning to program interesting. But, what really fascinated her was how the computer itself worked. She wanted to find out enough to dismantle her Commodore 64 and find out. (17.37) – What is the best career advice you have ever received? Anne-Marie said that it was a something her Dad told her – Don’t be afraid to ask for advice. People love giving advice. When you ask someone for advice you are laying the foundation for a strong relationship, as well as benefiting from their experience.  (18.52) – If you were to begin your IT career again, right now, what would you do? Anne-Marie says that she would get involved in Site Reliability Engineering, from the start. Learning how to design and set up systems in the most optimal way is fascinating. For someone who loves looking at the big picture and working to push quality levels up, as much as Anne-Marie does, the SRE sector is a perfect fit. (19.30) – What are you currently focusing on in your career? Right now, Anne-Marie wants to scale her business. Fortunately, she has a good partner who is helping her to learn the skills she needs to be able to do this. (20.18) – What is the number one non-technical skill that has helped you the most in your IT career? Being able to ask the right questions has proved to be an invaluable skill for Anne-Marie. She says that most of the time, smart people already have the answers to their problems. Usually, all they need is to be asked the right questions, something that Anne-Marie is very good at doing. (21.13) – Phil asks Anne-Marie to share a final piece of career advice with the audience. Anne-Marie’s advice is to “never let people put you in a box.” Instead, set your own boundaries and work out ways to gradually push beyond them. BEST MOMENTS: (7.44) Anne-Marie – “I learned the importance of communication. You need to communicate your value, even if nobody's asked for that.” (9.06) Anne-Marie – “Now, I talk about quality engineering in terms of business outcomes, “ (14.31) Anne-Marie – “People are interested in personal experiences. People are interested in how you approached a problem and solved it.” (17.41) Anne-Marie – “Don’t be afraid to ask for advice. People love giving advice.” (20.50) Anne-Marie – “By probing and asking thoughtful questions, often, the answers evolve out of that conversation." CONTACT Anne-Marie: Twitter: https://twitter.com/charrett @charrett LinkedIn: https://www.linkedin.com/in/testingtimes Website: https://annemariecharrett.com

In this episode, Angie Jones takes us through the ins and outs of automating software quality processes and how it's a craft of its' own, crucial in large-scale software building. With 15 years of first-hand experience automating software quality at companies such as IBM and Twitter, Angie shows us how building a product and testing it have a lot more in common than people think, and also some fundamental differences in mindset. We also discuss how she came to be a prolific inventor with more than 25 patents granted in the US and China. See acast.com/privacy for privacy and opt-out information.

Angie Jones is a Senior Developer Advocate who specializes in test automation strategies and techniques. She shares her wealth of knowledge by speaking and teaching at software conferences all over the world, as well as writing tutorials and blogs on angiejones.tech.

Angie Jones is a Senior Developer Advocate who specializes in test automation strategies and techniques. She shares her wealth of knowledge by speaking and teaching at software conferences all over the world, as well as writing tutorials and blogs on angiejones.tech.

The Women in Tech with Ariana podcast is a weekly podcast that talks about the latest news in tech, showcasing guest, and sharing tangible resources to help women navigate the tech industry and entrepreneurship. Whether we are talking about funding opportunities for your startup, a conference you should attend, coding bootcamps or a VC fund you should apply for, we want to provide you access to these tools and opportunities. Connect with Chaymeriyia Moncrief: http://bit.ly/WITWarianaEp5C Connect with Angie Jones: http://bit.ly/witwarianaep5AJ Connect with Ariana: https://www.wallwaytech.com/ariana-waller Connect with Podcast: https://www.wallwaytech.com/podcast

Angie speaks all over the world on Test Automation strategies, and she got Scott excited about Selenium again! She keynoted Selenium Conf 2018 and currently works at Applitools making automated visual testing tools. She's most recently launched on a new "Test Automation University" that's free and community driven. http://testautomationu.com http://angiejones.tech

Today Angie Jones, a master inventor and automated testing engineer, speaks with us about what a master inventor is and what it took to receive that title, what testing automation is, having parallel between testers and developers, what developers can be doing to build more testable apps, and finally how modern web development has complicated automated testing.Angie talks about some common problems when it comes to testing. The test team is often separate from the developer team, and it leads to communication problems. Testers should be working in parallel with the dev team to ensure that from the get-go they are writing a testable app!Another common problem is that 100% test coverage gets pushed. However, that's the wrong idea. Automated testing is expensive to implement, so Angie talks about how she figures out what'll give the most "bang for your buck" when deciding what tests get automated.Apps aren't as simple as they used to be, and thicker client-side UIs have made it much harder to implement automated tests. Automated Engineer is a fully fledged development position requiring skill across platforms, which is why Angie says that developers shouldn't be leading automated testing. There is a lot that automated testers have to do and separate skills that they need to develop. There's only so much a person can keep up on at once.Transcript"Incorporating Testers with Every Development Phase with Angie Jones" TranscriptResources:Level up: playing the automation gameBartle taxonomy of player typesWhy Developers Should Not Lead Your Automation EffortsWhich Tests Should We AutomateAngie Jones:TwitterGithubWebsiteYouTubeJoel HooksTwitterWebsite

On this episode, Alison Wade and Jessie Shternshus chat with Angie Jones, a formidable automation engineer who is literally changing the face of technology. This year she recorded and commercial for John Frieda talking about changing the narrative about women of color in tech. Angie holds some 25 patented inventions and has carved a remarkable path for herself working at IBM, Lexis Nexis, Twitter and most recently as Senior Developer Advocate at Applitools. In this episode, you will hear about the decisions that Angie made that lead to her showing up in a way that is b.old and fearless for herself and for others. Listen in and find out what makes Angie Jones tick!

This month on the Cucumber Podcast, we speak about The Screenplay Pattern. As John Ferguson describes it on his [site](http://serenity-bdd.info/docs/articles/screenplay-tutorial.html), "the Screenplay Pattern is a powerful and elegant approach to designing and implementing automated tests, providing a number of improvements over more traditional approaches such as the Page Objects model." The conversation covers why you should consider following the Screenplay Pattern and its potential drawbacks. The conversation closes with our guests providing a single tip for folks looking to try out the Screenplay Pattern on their own. Joining your host Aslak Hellesøy are John Smart, Jan Molak, Angie Jones, Nat Pryce, Matt Wynne and Steve Tooke. ### Shownotes: CukenFest London, April 19th-20th - Join us for our annual conference focused on helping you build stronger ties between business and IT. Keynotes from Dan North and Ulrika Malmgren. More details on our [event page](http://cukenfest.cucumber.io/) [Page Objects Refactored](https://ideas.riverglide.com/page-objects-refactored-12ec3541990) [Screenplay tutorial](http://serenity-bdd.info/docs/articles/screenplay-tutorial.html)

Really enjoyed this panel session talking about all things test automation with Angie Jones, Bas Dijkstra, Paul Grizzaffi, and Ashley Hunsberger. Check us out discussing managing business expectations, what to look for in test automation engineers, planning for maintenance and playing a couple rounds of "Rate that Vendor Claim". Enjoy!

Really enjoyed this panel session talking about all things test automation with Angie Jones, Bas Dijkstra, Paul Grizzaffi, and Ashley Hunsberger. Check us out discussing managing business expectations, what to look for in test automation engineers, planning for maintenance and playing a couple rounds of "Rate that Vendor Claim". Enjoy!

On the podcast this month, Matt Wynne speaks to Angie Jones. We first heard about Angie through her posts about BDD, Test Automation and Cucumber on her website. Her blog is a treat, filled with lots of practical advice for modern software teams. Angie now works for Twitter as an Automation Engineer and is a frequent conference speaker. Here's what they discuss on the podcast: Angie's background and her current role at Twitter. Why developers shouldn't lead your automation efforts. How testers can win over the team with BDD and Cucumber. The future of testers in a world of automation. Shownotes: Angie's blog: https://angiejones.tech/

In this episode, Karen and Kathleen chat with Angie Jones, of Healthy Angie about how using the Facebook Live Stream feature has completely changed her business. Angie discusses her overall strategy, how she prepares for, and the side benefits her business has noticed after using the Live Stream feature. Overall Strategy Just do it! Don't be afraid of going live. Your streams don't have to be perfect, it's all about being yourself. Worst case scenario, delete it afterwards! Be consistent when it comes to your live streams. Try and find a day or time each week and stick with it. Promote it ahead of time. This is when I'll be live streaming, and this is what I'll talk about. Promoting it ahead of time lets your followers know when to tune in AND holds you accountable to follow through. Don't worry about how many people join in on the live portion of your video. Repurpose the content! That one video can turn into a weekly email, a weekly blog post, and be shared across various social media pages, keeping your business in your customer's minds. How to Prepare: Know your opening line. You only have a few seconds to capture the attention of a potential customer. Know your opening hook and have it prepared. Have an outline nearby to guide you. Place any products or props you want to show in the area ahead of time. Don't rehearse too much, it's not about being perfect, but about being you! Know your closer and your call to action, the ending is just as important as the beginning., Remember your video will have two audiences, the live audience and the replay audience. Make yourself accessible to both. Side Benefits: Gaining self confidence in who you are and what you stand for. Client's reaching out more often via message or email, they have a better feeling for who Angie is now and are more comfortable reaching out to her. Angie's email list has more than doubled! Take a look at Angie's Facebook page, and see her past live streams.   Download the Free Facebook Live Stream Checklist Here.  Weekly Action Items: Download Free Facebook Live Stream Checklist. Take Angie's lead and create a live stream for your business this week.

This week, we're honoured to be joined by Angie Jones and Ash Coleman to discuss one of the most important films of recent times, Hidden Figures. It's a heartwarming tale of three women overcoming terrible systemic prejudices, though it's bittersweet as we talk through how many of its stories are still prevalent today. Our guests take us on a deep-dive through some important cultural talking-points, including how we educate children about race issues, how feminist movements tend to favour white women, how we can shift a community's mentality, and the labeling of so-called "Social Justice Warriors". Within the workplace, we look at why companies struggle with diversity and inclusion (D&I), how D&I problems can become business problems, the hallmarks of effective leaders, and how bold young women are leading the way. We also finally get our toes wet in the "manual vs automation" debate, and we welcome our first ever feline guest to the show! Note: News about Google's alleged "anti-diversity" paper was breaking at the time of recording; the leaking of the paper (and subsequent fallout) came some days later. References: Credit Karma Twitter Cineworld Unlimited Alpha Kappa Alpha Sorority, Inc Black Girls Code Black Girls Code on Twitter YouTube: Katherine Johnson receives the Presidential Medal of Freedom from Barack Obama Snopes.com: Pentagon Built with Extra Bathrooms Due to Racial Segregation? (TRUE) BBC News: What happened at Grenfell Tower? (London fire) YouTube: Procter & Gamble commercial: "The Talk" Max Landis: Maybe HBO's Confederate Isn't A Good Idea Guide to Allyship Geek Feminism Wiki: Intersectionality GOV.UK: Equality Act 2010 The Verge: A Google employee wrote an anti-diversity 'manifesto' that's going viral inside the company Gizmodo: Here's the Full 10-Page Anti-Diversity Screed Circulating Internally at Google CrossBrowserTesting: Don't Limit Diversity to Just Your Browsers (Angie article) Techpoint: Google's Photo App Accidentally Tagged Blacks As Gorillas Denver Post: Uber's search for a female CEO has been narrowed down to 3 men BBC News: Report on the BBC's "gender pay gap" CNN: Trump to reinstate US military ban on transgender people collectSPACE: When did John Glenn ask for 'the girl' to check the numbers? Wikipedia: Space Shuttle Challenger disaster Amazon.co.uk: Chris Hadfield - "An Astronaut's Guide To Life On Earth" Amazon.co.uk: Chris Hadifled - "You Are Here: Around the World in 92 Minutes" Amazon.co.uk: Tim Peake - "Hello, is this Planet Earth?" Amazon.co.uk: Stephen Hawking - "A Brief History of Time" Amazon.co.uk: Gary Fildes - "An Astronomer's Tale: A Bricklayer's Guide to the Galaxy" The Guardian: Why the lack of Indian and African faces in Dunkirk matters Angie's upcoming events WeTest New Zealand Let's Test South Africa TestBash Philadelphia YouTube trailers for films referenced in this episode: The Emoji Movie The Transporter Refueled Commando The Shawshank Redemption Detroit Star Wars: The Last Jedi Straight Outta Compton The Zookeeper's Wife A United Kingdom Their Finest Dunkirk Next time, we'll be taking our first dive into the world of 80s action movies, as we pick apart the brilliant madness of Arnold Schwarzenegger's 1985 movie COMMANDO! Twitters:@techgirl1908 @AshColeman30 @neilstudd @TheTestDoctor @ScreenTesting Emails: screentestingpod@gmail.com Intro music: Hans Zimmer - Katherine Outro music: Kim Burrell and Pharrell Williams - I See A Victory

In an episode best summarised as "it seemed like a good idea at the time", Neil and Dan attempt to get their teeth into Netflix's recent high-profile tech offering, The Circle, starring Emma Watson and Tom Hanks, only to find there's very little meat on those plot bones. It's light on spoilers (as there's not a lot to spoil), but we envision a story which might have been, had they decided to actually include character arcs, plot developments and meaningful conclusions. We keep ourselves amused along the way, coming up with the rules of proper Slack and social media etiquette, deciding whether the film's irony was intentional, paying tribute to the wonder of Bill Paxton, and wondering why John Boyega got involved at all. References: Neil's review of The Circle for NewOnNetflixUK YouTube: Bill Paxton being killed by an Alien, a Predator and a Terminator YouTube: Black Mirror - "The Entire History of You" trailer YouTube: Black Mirror - "Nosedive" trailer YouTube: Invasion of the Body Snatchers (1956) trailer YouTube: Invasion of the Body Snatchers (1978) trailer YouTube: My Scientology Movie (Louis Theroux) trailer Slack - Ministry of Testing Slack - Testers.io Neil's Slack @channel meme YouTube: Electrocution from Thunderball YouTube: Eye-gouging from Spectre YouTube: Beck - Dreams YouTube: Detroit trailer YouTube: Attack the Block trailer BBC News: How the world's first webcam made a coffee pot famous YouTube: The Incredibles trailer YouTube: Terminator Genisys trailer Twitter account for Karl The Fog (the famous San Francisco fog) YouTube: Apocalypse Now introduction (featuring The Doors - The End) For our next episode, we'll be talking about HIDDEN FIGURES with two special guests - Angie Jones and Ash Coleman, all the way from San Francisco! Twitters: @ScreenTesting @TheTestDoctor @neilstudd Emails: screentestingpod@gmail.com Intro music: Ocean Colour Scene - The Circle (because why not) Outro music: Jónsi - Simple Gifts

Test Automation is an essential component of the Software Development process. Angie Jones, Consulting Automation Engineer at Lexis Nexis, explains what Test Automation is and the process of collaboration across teams.

Guest: Angie Jones @techgirl1908 Full show notes are at https://developeronfire.com/podcast/episode-214-angie-jones-extreme-involvement

Yet another great STP Radio episode with Mike Lyles! Mike talks with Angie Jones - Consulting Automation Engineer at LexisNexis and Paul Merrill - Principle Software Engineer in Test and Founder of Beaufort Fairmont about "The Dominoes of Automation," Angie and Paul's workshop at STPCon. Also learn more about the other session that both Angie and Paul are presenting at STPCon this Spring in Phoenix, AZ.Learn More about Angie:http://www.stpcon.com/speakers/angie-jones/Learn More about Paul:http://www.stpcon.com/speakers/paul-merrill/

Yet another great STP Radio episode with Mike Lyles! Mike talks with Angie Jones - Consulting Automation Engineer at LexisNexis and Paul Merrill - Principle Software Engineer in Test and Founder of Beaufort Fairmont about "The Dominoes of Automation," Angie and Paul's workshop at STPCon. Also learn more about the other session that both Angie and Paul are presenting at STPCon this Spring in Phoenix, AZ.Learn More about Angie:http://www.stpcon.com/speakers/angie-jones/Learn More about Paul:http://www.stpcon.com/speakers/paul-merrill/

We continue our conversation with Angie Jones about ways that automation can be put first in stories (yes, really) and ways that she has been able to get team buy in and cooperation to make that process effective. Also, we have a mailbag question that we answer in depth, or as much as we can… is it possible to be paid as much as a developer or an SDET if you are just a manual tester? The answer is “it depends”, but we go into a lot more about why that is the case. Resource by QualiTest Group

Have you wondered how your team could better utilize its automation resources? Does your definition of “Done” include new automation efforts for stories that are in flight? How about when changes to functionality (or new additions) cause your old tests to stop working? Do we play continuous catch up, or is there a better way to applying automation efforts?   Angie Jones of Lexus Nexus joins us to talk about better ways to have those automation discussions, who should be responsible for what, and how everyone on the team can contribute to automation efforts (hint, you don’t need to be a coder to help make great automation, but it certainly helps).   Also, this week we delve into Spotify taking over hard drives with continuous writes that could shave years off of their operation life, and are Uber’s autonomous vehicles even close to ready for prime time?   This is part one of a two part series. Come back in two weeks when we continue our conversation with Angie. Resource by QualiTest Group

Angie Jones is a Consulting Automation Engineer who advises several agile teams on automation strategies and has developed automation frameworks for countless software products. She challenges us to consider including Automation earlier in the product development cycle. Is Automation included in your company's "Definition of Done?"

On this episode of the Wez Wanders Podcast we are joined by Michael Tieso from Art of Backpacking, and Jeremy and Angie Jones from Living the Dream RTW, and we talk about the TBU travel bloggers book, a tourist briefly going missing in South America, and some weird foods we’ve eaten around the world.