Podcasts about packt publishing

How Privacy-Enhancing Technologies (PETs) can safeguard data in an AI-driven world. As organizations increasingly rely on AI, concerns around data privacy, security, and compliance grow. PETs provide a technical safeguard to ensure sensitive information remains protected, even in the most advanced AI applications. With new regulations like the EU AI Act, organizations must adopt privacy-first strategies. PETs are a critical tool to ensure AI transparency, fairness, and trust while maintaining regulatory compliance.Our guest, Jetro Wils, cybersecurity expert and researcher, breaks down how PETs help organizations de-risk AI adoption while ensuring privacy, compliance, and security.Watch now to discover how PETs can help you build digital trust and secure AI-powered innovations!KEY CONVERSION POINT 00:01:33 How would you define digital trust?00:02:32 What is Privacy Enhancing Technology?00:04:21 Why do we need PET when we have laws and principles?00:10:19 Kind of AI risk that can also be mitigated by these PETS00:15:12 How would a PET de-risk that in an AI adoption situation ABOUT GUEST Jetro Wils is a Cloud & Information Security Officer and Cybersecurity Advisor, dedicated to helping organizations operate securely in the cloud era. With a strong focus on information security and compliance, he enables businesses to reduce risk, strengthen cybersecurity frameworks, and achieve peace of mind.With 18 years of experience in Belgium's tech industry, Jetro has held roles spanning software development, business analysis, product management, and cloud specialization. Since 2016, he has witnessed the rapid evolution of cloud technology and the growing challenge organizations face in securely adopting it. Jetro is a 3x Microsoft Certified Azure Expert and a 2x Microsoft Certified Trainer (2022-2024), conducting 10-20 certified training sessions annually on cloud, AI, and security. He has trained over 100 professionals, including enterprise architects, project managers, and engineers. As a technical reviewer for Packt Publishing, he ensures the accuracy of books on cloud and cybersecurity. Additionally, he hosts the BlueDragon Podcast, where he discusses cloud, AI, and security trends with European decision-makers.Jetro holds a professional Bachelor's Degree in Applied Computer Science (2006) and is currently pursuing a Master's in IT Risk and Cybersecurity Management at Antwerp Management School (2023-2025). His research focuses on derisking AI adoption by enhancing AI security through Privacy Enhancing Technologies (PETs). He is also a certified NIS 2 Lead Implementer working toward a DORA certification.  ABOUT HOST Punit Bhatia is one of the leading privacy experts who works independently and has worked with professionals in over 30 countries. Punit works with business and privacy leaders to create an organization culture with high privacy awareness and compliance as a business priority. Selectively, Punit is open to mentor and coach professionals.  Punit is the author of books “Be Ready for GDPR'' which was rated as the best GDPR Book, “AI & Privacy – How to Find Balance”, “Intro To GDPR”, and “Be an Effective DPO”. Punit is a global speaker who has spoken at over 30 global events. Punit is the creator and host of the FIT4PRIVACY Podcast. This podcast has been featured amongst top GDPR and privacy podcasts.As a person, Punit is an avid thinker and believes in thinking, believing, and acting in line with one's value to have joy in life. He has developed the philosophy named ‘ABC for joy of life' which passionately shares. Punit is based out of Belgium, the heart of Europe.  RESOURCES Websites www.fit4privacy.com, www.punitbhatia.com,  https://www.linkedin.com/in/jetrow/  Podcast https://www.fit4privacy.com/podcast Blog https://www.fit4privacy.com/blog YouTube http://youtube.com/fit4privacy   

Want to save 30 minutes a day, and your team too, right now using GenAI? The next 26 minutes is so action-packed with straightforward, real-world practical tips, you'll be questioning why you haven't been using artificial intelligence this way already to improve efficiency and productivity at work. Chartered Accountant, and GenAI expert, Kayur Patel CA returns for Part 2 of this two-part special on artificial intelligence and everyday accounting. He and host Gillian Bowen dive into GenAI use-cases (text, data and bespoke) available to accountants today, particularly those in small and medium-sized practices. Get ready to take notes!  Resources referred to in the episode:  GenAI for SMPs (Part 1) - focused on the big picture of GenAI: What is it, the current state of play, the impact on workplaces and what's around the corner?  CA Library Artificial Intelligence general reading list  CA Library articles/resources involving AI and accountancy:  AI and the transformation of the CFO role (Isaac Heller, Strategic Finance, January 2024)  Generative AI in accounting applications (Kelly Richmond Pope et al, Strategic Finance, November 2023)  Writing advanced Excel macros with GPT-4 (Fidel Dhana, Journal of Accountancy, November 2023)  Six principles for the effective use of artificial intelligence large language models (Daniel Street et al, CPA Journal, Nov/Dec 2023)  Accounting in the age of generative AI (Tala Khalifeh, Strategic Finance, October 2023)  Innovative processes in finance and accounting (AI and automation) (Vineet Jain, Strategic Finance, October 2023)  Generative AI and risks to CPA firms (Sarah Beckett Ference, Journal of Accountancy, October 2023)  The future of accounting: how artificial intelligence is revolutionizing the field (ACCA & Learn Signal, 31 October 2023)  Ethical principles apply to AI (Accounting) (Daniel Butcher, Strategic Finance, August 2023)  Using ChatGPT with Excel (Kelly L. Williams, Journal of Accountancy, April 2023)  The future of finance with ChatGPT and Power BI: transform your trading, investing, and financial reporting with ChatGPT and Power BI (James Bryant & Aloke Mukherjee, Packt Publishing, 2023. eBook)  Small Firm, Big Impact podcast pageSee omnystudio.com/listener for privacy information.

It's time to check-in on the fast-moving world of artificial intelligence (AI) and learn how it's impacting workplaces in 2024. Kayur Patel is a Chartered Accountant, and lecturer at the University of Auckland, who specialises in Generative AI. It's his job to explain the state of play and to help educate accountants and their clients on how GenAI works, what it means for their businesses and why GenAI has a role in the future. This discussion takes place over two episodes. Part 1 sets the scene while part 2 focuses on accounting-specific use cases for small and medium-sized practices. Resources referred to in Part 1: CA Library Artificial Intelligence general reading list CA Library articles/resources involving AI and accountancy: AI and the transformation of the CFO role (Isaac Heller, Strategic Finance, January 2024) Generative AI in accounting applications (Kelly Richmond Pope et al, Strategic Finance, November 2023) Writing advanced Excel macros with GPT-4 (Fidel Dhana, Journal of Accountancy, November 2023) Six principles for the effective use of artificial intelligence large language models (Daniel Street et al, CPA Journal, Nov/Dec 2023) Accounting in the age of generative AI (Tala Khalifeh, Strategic Finance, October 2023) Innovative processes in finance and accounting (AI and automation) (Vineet Jain, Strategic Finance, October 2023) Generative AI and risks to CPA firms (Sarah Beckett Ference, Journal of Accountancy, October 2023) The future of accounting: how artificial intelligence is revolutionizing the field (ACCA & Learn Signal, 31 October 2023) Ethical principles apply to AI (Accounting) (Daniel Butcher, Strategic Finance, August 2023) Using ChatGPT with Excel (Kelly L. Williams, Journal of Accountancy, April 2023) The future of finance with ChatGPT and Power BI: transform your trading, investing, and financial reporting with ChatGPT and Power BI (James Bryant & Aloke Mukherjee, Packt Publishing, 2023. eBook) Small Firm, Big Impact episode from Season 3: Accounting and generative A.I. See omnystudio.com/listener for privacy information.

NService Bus This episode of The Modern .NET Show is supported, in part, by NServiceBus, the ultimate tool to build robust and reliable systems that can handle failures gracefully, maintain high availability, and scale to meet growing demand. Make sure you click the link in the show notes to learn more about NServiceBus. Show Notes Welcome to The Modern .NET Show! Formerly known as The .NET Core Podcast, we are the go-to podcast for all .NET developers worldwide and I am your host Jamie "GaProgMan" Taylor. In this episode, I spoke with Mark J Price, a software developer and educator with over 20 years of experience. We talked about .NET 8, Blazor, server-side rendering, and more. We also explore the compiler changes in .NET 8 and how they can improve performance and efficiency. Mark also discusses his upcoming trilogy of .NET 8 books, which cater to developers of all levels, from beginners to professionals: What I find when I'm learning something new is even if something has some documentation and it might have a kind of introductory tutorial, they are not always kept up to date and they're not always easy to follow because what tends to happen is the experts who build the platform are then told, oh, just write a tutorial for it. Now they're the experts, but they're not experts at education and so they're not always that great at actually explaining how to get started with something. So that's where my books come in, I feel. I'm an expert at education and I'm an expert because I'm actually not a quick learner. I'm not the quickest, I'm not the brightest, but I do notice the things that trip people up. And so when I first learnt GRPC, I had some misconceptions, I struggled with certain areas, but I notice all of that and I can write it down and so I can write a chapter that I think really helps people get started. —Mark J Price With a focus on providing accurate and up-to-date educational resources, Mark's dedication to the community and continuous improvement shines through in this engaging and informative conversation. With a focus on providing accurate and up-to-date educational resources, Mark's dedication to the community and continuous improvement shines through in this engaging and informative conversation. So let's sit back, open up a terminal, type in dotnet new podcast and we'll dive into the core of Modern .NET. Supporting the Show If you find this episode useful in any way, please consider supporting the show by either leaving a review (check our review page for ways to do that), sharing the episode with a friend or colleague, buying the host a coffee, or considering becoming a Patron of the show. Full Show Notes The full show notes, including links to some of the things we discussed and a full transcription of this episode, can be found at: https://dotnetcore.show/season-6/the-net-trilogy-and-learning-net-with-mark-j-price/ Useful Links Mark's previous appearances on the show: Episode 44 - Learning .NET Core with Mark J Price Episode 91 - C# 10 and .NET 6 with Mark J Price Episode 117 - Our Perspectives on the Future of .NET with Mark J Price Mark's .NET Trilogy books: C# 12 and .NET 8 – Modern Cross-Platform Development Fundamentals Apps and Services with .NET 8 Tools and Skills for .NET 8 Pros (there is no link for this, at the time of creating the show notes) Announcing .NET 8 Release Candidate 2 Tools and Skills for .NET 8 Pros GitHub Repo Conversation about PGO Episode 72 - Emulating a Video Game System in .NET with Ryujinx Performance Improvements in .NET 8 target framework moniker (TFM) The LangVersion element Dapper Cosmos DB JetBrains Rider Visual Studio Code Design Patterns: Elements of Reusable Object-Oriented Software Packt Publishing discord server Supporting the show: Leave a rating or review Buy the show a coffee Become a patron Getting in touch: via the contact page joining the Discord Music created by Mono Memory Music, licensed to RJJ Software for use in The Modern .NET Show Remember to rate and review the show on  Apple Podcasts, Podchaser, or wherever you find your podcasts, this will help the show's audience grow. Or you can just share the show with a friend. And don't forget to reach out via our Contact page. We're very interested in your opinion of the show, so please get in touch. You can support the show by making a monthly donation on the show's Patreon page at: https://www.patreon.com/TheDotNetCorePodcast.

In this first LIVE interview, Kevin sits down with Alvin Ashcraft, a published author and an organizer of TechBash. Alvin, who has released multiple tech books with Packt Publishing, gives insightful details about his book writing process, from concept to manuscript, timeline, tech editing, and publishing. He also discusses the benefits of book authorship for career advancement, revealing how his book helped him land a job at Microsoft. This interview is a valuable resource for any aspiring writer in the tech industry.Alvin in Twitter: https://twitter.com/alvinashcraftMorning Dew: https://www.alvinashcraft.com/Learn WinUI 3 by Alvin Ashcraft: https://www.amazon.com/dp/1805120069

Potionomics composer Greg Nicolett discusses his work with Disney, how he learned the game composer's process, and Shia LeBeouf's unexpected influence on his career. Show notes: CodeWritePlay.com This episode was sponsored in part by Packt Publishing. Check out Unity 3D Game Development, available now! Greg's links: Potionomics on Steam Potionomics soundtrack on bandcamp Greg Nicolett on Twitter --- Send in a voice message: https://anchor.fm/gamedevbreakdown/message Support this podcast: https://anchor.fm/gamedevbreakdown/support

Former RuneScape developer, Chris Knowles, discusses his time at Jagex, his design philosophy, and the one thing he refuses to do with his upcoming indie game. This episode was sponsored in part by Packt Publishing. Check out Unity 3D Game Development, available now! Chris Knowles Links: Chris on Twitter: https://twitter.com/tarrenam Hexahedra Demo on Steam: Hexahedra on Steam (steampowered.com) Hexahedra's Kickstarter campaign: Hexahedra by Sidequest Ninja — Kickstarter --- Send in a voice message: https://anchor.fm/gamedevbreakdown/message Support this podcast: https://anchor.fm/gamedevbreakdown/support

Alvin Ashcraft has over 27 years of programming experience in the healthcare, financial, and manufacturing industries. He is a Content Developer for Microsoft, creating docs for Windows developers on Microsoft Docs. He has authored a book for Packt Publishing titled Learn WinUI 3, and has just published his second book, Parallel Programming and Concurrency with C# 10 and .NET 6, out now.   Alvin is one of the founders and organizers of the TechBash developer conference held annually at the Kalahari Resort in Pocono Manor, PA. In his previous life, he worked for consulting firms as a software developer. During those years Alvin developed solutions for clients in the manufacturing, financial, and healthcare industries. Alvin is a blogger, technology geek, family guy, and former Microsoft MVP. He has a wonderful wife and three amazing daughters.   Topics of Discussion: [3:18] How Alvin got started with his blog, and how blogging made RSS a thing. [5:48] What exactly does NewsBlur do for you? [10:10] Are we overstating it when we say that people who work in development need to become expert users of all the frameworks and tools they intend to use? [12:20] Alvin talks about the inspiration behind his new book, and why he chose parallel programming and concurrency as the topics. [16:35] Okay, what is it really like having TechBash at the beautiful Kalahari resort? [22:00] What does the future hold for Windows development? [24:03] How else can we best be prepared for the future?   Mentioned in this Episode: Architect Tips — New video podcast! Azure DevOps Clear Measure (Sponsor) .NET DevOps for Azure: A Developer's Guide to DevOps Architecture the Right Way, by Jeffrey Palermo — Available on Amazon! Jeffrey Palermo's YouTube Jeffrey Palermo's Twitter — Follow to stay informed about future events! Programming with Palermo programming@palermo.network Alvin's main blog Alvin's WinUI blog Twitter TechBash Twitter TechBash site Alvin's GitHub OpenLiveWriter plugin The Documentation landing page on MS Learn: Learn.microsoft.com/docs/ The landing page for Windows developer docs: Learn.microsoft.com/windows/apps/ A list of sample apps and samples repos for Windows developers Learn WinUI 3 book: Parallel Programming  and Concurrency with C# 10 and .NET 6 book Newsblur.com/ Feedly.com/ Openlivewriter.com/ Github.com/MicrosoftDocs/win32 Github.com/MicrosoftDocs/windows-dev-docs Github.com/MicrosoftDocs/sdk-api TPL Data Flow library   Want to Learn More? Visit AzureDevOps.Show for show notes and additional episodes.

Kevin Horek is a Chief Design Officer, UX/UI prototyper, TV/Radio Host, and a published author by Packt Publishing on Zurb's responsive framework, Foundation 5. He studied web development and design at universities across North America, including UCLA and the University of Alberta. His Radio/TV/Podcast, Building The Future, was started to get over a fear of public speaking. Kevin continues to push himself out of my comfort zone by blogging for AlphaGamma, TechZulu, and SOCAP. He also recently emceed SUP-X - The Start-Up Expo and had a live fireside chat on stage with the keynote speaker.For over 26 years, Kevin has been working on web and mobile apps for some of the world's most notable and well-respected organizations. Among them are BMW, Best Buy, Apple, Adobe, Sprint, Eastlink, TD Canada Trust, Qantas Airlines, Emirates Airlines, CB Richard Ellis, Microsoft, The Home Depot, and CalTech

In this episode, we welcome Tushar Gupta, Senior Book Producer from Packt Publishing. Tushar and I aggregated questions from social media about technical book publishing and answered them in this Q&A live stream session on LinkedIn Live and YouTube. We converted this episode to a podcast format and delivered it right to your earbuds for your listening pleasure. I had a lot of fun talking about a subject I am passionate about. I hope by sharing the experience from Tushar and I, you can also share your technical knowledge in a book format some day in the future. If you do, please do drop me a line, I will be excited to hear about it! --- Links ---YouTube Live Link: https://www.youtube.com/watch?v=Gy2UfQSIH2E Packt Publishing: https://www.packtpub.com/  Connect with Tushar on LinkedIn: https://www.linkedin.com/in/tushar-gupta-2a998415/ --- Stay in Touch with Us ---Subscribe on YouTube: https://www.youtube.com/c/EricChouNetworkAutomationNerds Follow Eric on Twitter: https://twitter.com/ericchou

Ted Ipsen is the President and COO of Positroniq, a strategic security and risk consultancy. He is an experienced executive manager with over 20 years of experience specializing in high-tech crime investigation, digital forensics, and the delivery and oversight of consulting and advisory services in the areas of information security, secure development, security assessment, information risk management, IT governance, compliance, business continuity management, and aligning strategic IT and security goals with business objectives. He was recruited out of law enforcement by a global “Big 4” audit and professional services firm, and has since moved progressively to more technical, and focused security consultancies. Mr. Ipsen has worked with organizations across many industries, reviewing security and IT programs against industry leading practices, standards, and regulatory frameworks, integrating security operational processes, and providing security training to infosec practitioners, software developers, and executives. He has served as the interim-CISO for a major airline, and built security programs for organizations of all sizes. He has spoken at many national and international security conferences, and is the co-author of “Law Enforcement Challenges in Digital Forensics,” presented at the National Colloquium for Information Systems Security Education. He has contributed to a number of security publications, including “Securing Linux, Step by Step” and “Disaster Recovery, Step by Step”, issued by the SANS Institute, and “Practical Cybersecurity Architecture”, from Packt Publishing. Resources Mentioned: https://www.provendatarecovery.com/blog/what-is-digital-forensics/ https://www.cisostreet.com/effective-board-communication-for-cisos/

Ria talks with Ravit about his YouTube channel ‘The Ravit Show' and what inspired him to transition from a finance background to the data community. He speaks about the best practices to get involved with the data and how to stand out in such a diverse environment. Ravit elaborates on the importance of networking, and from his own experience how a niche is never permanent. Ravit Jain, host of The Ravit Show and Community Manager at Packt Publishing, is an amazing personality with a love for data and interacting with people! Ravit is passionate about supporting Packt and the data science community by sharing the literary works of experts in the field and hosting “The Ravit Show”, showcasing intimate, live 1:1 interviews with key influencers and practitioners on the same.

Dan Borges - Author @1njection   Buy the book on Amazon: https://www.amazon.com/Adversarial-Tradecraft-Cybersecurity-real-time-computer-ebook-dp-B0957LV496/dp/B0957LV496?_encoding=UTF8&me=&qid=&linkCode=ll1&tag=bdspod-20&linkId=8f2daf0b3563cbbc2cee6a2d2138149d&language=en_US&ref_=as_li_ss_tl   https://news.sophos.com/en-us/2021/07/04/independence-day-revil-uses-supply-chain-exploit-to-attack-hundreds-of-businesses/amp/   Cool near real time updates on the hack: https://www.huntress.com/blog/rapid-response-kaseya-vsa-mass-msp-ransomware-incident https://twitter.com/DAlperovitch/status/1412033278081708034 https://github.com/ahhh/Cybersecurity-Tradecraft/tree/main/   https://www.amazon.com/Network-Attacks-Exploitation-Matthew-Monte/dp/1118987128 https://en.wikipedia.org/wiki/Best_response https://labs.bishopfox.com/tech-blog/sliver https://www.amazon.com/Rootkits-Bootkits-Reversing-Malware-Generation/dp/1593277164   Www.Globalcptc.org   Virtual CCDC:  How easy was the process working with Packt?  Did they approach you or vice versa? 5 D's of Physical Security The five D's of security seek to do one or more of the following: Deter, Detect, Delay, Deny and Defend. https://www.securitymagazine.com/articles/82833-the-5-ds-of-outdoor-perimeter-security Check out our Store on Teepub! https://brakesec.com/store Join us on our #Slack Channel! Send a request to @brakesec on Twitter or email bds.podcast@gmail.com #AmazonMusic: https://brakesec.com/amazonmusic  #Spotify: https://brakesec.com/spotifyBDS #Pandora: https://brakesec.com/pandora  #RSS: https://brakesec.com/BrakesecRSS #Youtube Channel:  http://www.youtube.com/c/BDSPodcast #iTunes Store Link: https://brakesec.com/BDSiTunes #Google Play Store: https://brakesec.com/BDS-GooglePlay Our main site:  https://brakesec.com/bdswebsite #iHeartRadio App:  https://brakesec.com/iHeartBrakesec #SoundCloud: https://brakesec.com/SoundcloudBrakesec Comments, Questions, Feedback: bds.podcast@gmail.com Support Brakeing Down Security Podcast by using our #Paypal: https://brakesec.com/PaypalBDS OR our #Patreon https://brakesec.com/BDSPatreon #Twitter: @brakesec @boettcherpwned @bryanbrake @infosystir #Player.FM : https://brakesec.com/BDS-PlayerFM #Stitcher Network: https://brakesec.com/BrakeSecStitcher #TuneIn Radio App: https://brakesec.com/TuneInBrakesec

Dan Borges - Author @1njection   Buy the book on Amazon: https://www.amazon.com/Adversarial-Tradecraft-Cybersecurity-real-time-computer-ebook-dp-B0957LV496/dp/B0957LV496?_encoding=UTF8&me=&qid=&linkCode=ll1&tag=bdspod-20&linkId=8f2daf0b3563cbbc2cee6a2d2138149d&language=en_US&ref_=as_li_ss_tl   https://news.sophos.com/en-us/2021/07/04/independence-day-revil-uses-supply-chain-exploit-to-attack-hundreds-of-businesses/amp/   Cool near real time updates on the hack: https://www.huntress.com/blog/rapid-response-kaseya-vsa-mass-msp-ransomware-incident https://twitter.com/DAlperovitch/status/1412033278081708034 https://github.com/ahhh/Cybersecurity-Tradecraft/tree/main/   https://www.amazon.com/Network-Attacks-Exploitation-Matthew-Monte/dp/1118987128   https://en.wikipedia.org/wiki/Best_response   https://labs.bishopfox.com/tech-blog/sliver   https://www.amazon.com/Rootkits-Bootkits-Reversing-Malware-Generation/dp/1593277164   Www.Globalcptc.org   Virtual CCDC:  How easy was the process working with Packt?  Did they approach you or vice versa? 5 D's of Physical Security The five D's of security seek to do one or more of the following: Deter, Detect, Delay, Deny and Defend. https://www.securitymagazine.com/articles/82833-the-5-ds-of-outdoor-perimeter-security Check out our Store on Teepub! https://brakesec.com/store Join us on our #Slack Channel! Send a request to @brakesec on Twitter or email bds.podcast@gmail.com #AmazonMusic: https://brakesec.com/amazonmusic  #Spotify: https://brakesec.com/spotifyBDS #Pandora: https://brakesec.com/pandora  #RSS: https://brakesec.com/BrakesecRSS #Youtube Channel:  http://www.youtube.com/c/BDSPodcast #iTunes Store Link: https://brakesec.com/BDSiTunes #Google Play Store: https://brakesec.com/BDS-GooglePlay Our main site:  https://brakesec.com/bdswebsite #iHeartRadio App:  https://brakesec.com/iHeartBrakesec #SoundCloud: https://brakesec.com/SoundcloudBrakesec Comments, Questions, Feedback: bds.podcast@gmail.com Support Brakeing Down Security Podcast by using our #Paypal: https://brakesec.com/PaypalBDS OR our #Patreon https://brakesec.com/BDSPatreon #Twitter: @brakesec @boettcherpwned @bryanbrake @infosystir #Player.FM : https://brakesec.com/BDS-PlayerFM #Stitcher Network: https://brakesec.com/BrakeSecStitcher #TuneIn Radio App: https://brakesec.com/TuneInBrakesec  

I spoke with Erik Hanchett. Erik is a Senior Software Engineer working for Cerity. Beyond that Erik has a YouTube channel with over 70K subscribers. Most of his content focus on front-end development and more specifically on Vue.js. For the ones that are not familiar, Vue.js is a JavaScript Framework that goes head to head against Angular and React. Erik is also a book author with published books by Packt Publishing and Manning. Erik is a big proponent of Vue.js and when asked which JavaScript Framework he would pick,  guess what was his answer? Did I mention that Erik has create a full online course on Vue.js? Stick around to hear from Vue.js fanboy Erik Hanchett. Enjoy! Full show notes and links: https://SoloCoder.com/70

Gamification Nation was created by An Coppens, an award-winning speaker, learning and development expert, business and executive coach and author, with over 15 years experience in creating behavior and organisational change through creative and innovative (tech) gaming solutions.  As a leading expert in gamification for employee engagement, An's company won the Outstanding Gamification Agency Award in 2017 at Gamification Europe and the Excellence in No-Tech Gamification Design in 2018 at GamiCon 18. In this interview with Jane, An discusses her work with global brands in media, leisure, health and finance markets, plus other business owners and managers in a range of different industries,  An was ranked in the top 100 Innovation and gamification experts in 2012 and since 2015 stayed in the top 10 of gamification gurus worldwide. In February 2016, she was given the HR visionary award at the WHRD congress in Mumbai and in 2018 she reached elite standard in the global e-learning community. She has been a speaker at many global conferences and was commissioned to write about “Gamification in business” for Bookboon.com and previously “How to attract IT talent” for Packt Publishing. (Entrepreneur Spotlight) ABOUT THE HOST: Jane Bayler is a serial entrepreneur, investor, speaker, event host and business scale up expert. She had a 20 year history in global media and advertising, before becoming a serial entrepreneur herself, with multiple businesses in real estate, marketing and education. Having grown and sold a £6M brand identity business to US communications group Interpublic, today she is most passionate about and committed to serving other entrepreneurs – helping them grow their businesses and achieve their best lives.  Enquire about working 1:1 with Jane, book a call here: https://bit.ly/2Z07DML Discover Jane's Ideal Client Success Accelerator Programme here: www.idealclientsuccess.com/masterclass

Some of the highlights of the show include The diplomacy that's required between software engineers and management, and why influence is needed to move projects forward to completion. Driving factors behind Ygrene's Kubernetes migration, which included an infrastructure bottleneck, a need to streamline deployment, and a desire to leverage their internal team of cloud experts. Management's request to ship code faster, and why it was important to the organization.  How the company's engineers responded to the request to ship code faster, and overcame disconnects with management. How the team obtained executive buy-in for a Kubernetes migration. Key cultural changes that were required to make the migration to Kubernetes successful. How unexpected challenges forced the team to learn the “depths of Kubernetes,” and how it helped with root cause analysis. Why the transition to Kubernetes was a success, enabling the team to ship code faster, deliver more value, secure more customers, and drive more revenue.  Links: HerdX: https://www.herdx.com/ Ygrene: https://ygrene.com/ Austin Twitter: https://twitter.com/_austbot Austin LinkedIn: https://www.linkedin.com/in/austbot/ Arnold's book on publisher site: https://www.packtpub.com/cloud-networking/the-kubernetes-workshop  Arnold's book on Amazon: https://www.amazon.com/Kubernetes-Workshop-Interactive-Approach-Learning/dp/1838820752/ TranscriptAnnouncer: Welcome to The Business of Cloud Native podcast where we explore how end users talk and think about the transition to Kubernetes and cloud-native architectures.Emily: Welcome to The Business of Cloud Native. My name is Emily Omier, and I am here with Austin Adams and Zack Arnold, and we are here to talk about why companies go cloud-native.Austin: So, I'm currently the CTO of a small Agrotech startup called HerdX. And that means I spend my days designing software, designing architecture for how distributed systems talk, and also leading teams of engineers to build proof-of-concepts and then production systems as they take over the projects that I've designed. Emily: And then, what did you do at Ygrene? Austin: I did the exact same thing, except for without the CTO title. And I also had other higher-level engineers working with me at Ygrene. So, we made a lot of technical decisions together. We all migrated to Kubernetes together, and Zack was a chief proponent of that, especially with the culture change. So, I focused on the designing software that teams of implementation engineers could take over and actually build out for the long run. And I think Zack really focused on—oh, I'll let Zack say what he focused on. [laughs].Emily: Go for it, Zach.Zach: Hello. I'm Zack. I also no longer work for Ygrene, although I have a lot of admiration and respect for the people who do. It was a fantastic company. So, Austin called me up a while back and asked me to think about participating in a DevOps engineering role at Ygrene. And he sort of said at the outset, we don't really know what it looks like, and we're pretty sure that we just created a position out of a culture, but would you be willing to embody it? And up until this point, I'd had cloud experience, and I had had software engineering experience, but I didn't really spend a ton of time focused on the actual movement of software from developer's laptops to production with as few hiccups, and as many tests, and as much safety as possible in between. So, I always told people the role felt like it was three parts. It was part IT automation expert, part software engineer, and then part diplomat. And the diplomacy was mostly in between people who are more operations focused. So, support engineers, project managers, and people who were on-call day in and day out, and being a go-between higher levels of management and software engineers themselves because there's this awkward, coordinated motion that has to really happen at a fine-grained level in order to get DevOps to really work at a company. What I mean by that is, essentially, Dev and Ops seem to on the surface have opposing goals, the operation staff, it's job is to maintain stability, and the development side's job is to introduce change, which invariably introduces instability. So, that dichotomy means that being able to simultaneously satisfy both desires is really a goal of DevOps, but it's difficult to achieve at an organizational level without dealing with some pretty critical cultural components. So, what do I spend my day on? The answer to that question is, yes. It really depends on the day. Sometimes it's cloud engineers. Sometimes it's QA folks, sometimes it's management. Sometimes I'm heads-down writing software for integrations in between tools. And every now and again, I get to contribute to open-source. So, a lot of different actual daily tasks take place in my position.Emily: Tell me a little bit more about this diplomacy between software engineers and management.Zach: [laughs]. Well, I'm not sure who's going to be listening in this amazing audience of ours, but I assume, because people are human, that they have capital O-pinions about how things should work, especially as it pertains to either software development lifecycle, the ITIL process of introducing change into a datacenter, into a cloud environment, compliance, security. There's lots of, I'll call them thought frameworks that have a very narrow focus on how we should be doing something with respect to software. So, diplomacy is the—well, I guess in true statecraft, it's being able to work in between countries. But in this particular case, diplomacy is using relational equity or influence, to be able to have every group achieve a common and shared purpose. At the end of the day, in most companies the goal is actually to be able to produce a product that people would want to pay for, and we can do so as quickly and as efficiently as possible. To do that, though, it again requires a lot of people with differing goals to work together towards that shared purpose. So, the diplomacy looks like, aside from just having way too many meetings, it actually looks like being able to communicate other thought frameworks to different stakeholders and being able to synthesize all of the different narrow-focused frameworks into a common shared, overarching process. So, I'll give you a concrete example because it feels like I just spewed a bunch of buzzwords. A concrete example would be, let's say in the common feature that's being delivered for ABC Company, for this feature it requires X number of hours of software development; X number of hours of testing; X number of hours of preparing, either capacity planning, or fleet size recommendations, or some form of operational pre-work; and then the actual deployment, and running, and monitoring. So, in the company that I currently work for, we just described roughly 20 different teams that would have to work together in order to achieve the delivery of this feature as rapidly as possible. So, the process of DevOps and the diplomacy of DevOps, for me looks like—aside from trying to automate as much as humanly possible and to provide what I call interface guarantees, which are basically shared agreements of functionality between two teams. So, the way that the developers will speak to the QA engineers is through Git. They develop new software, and they push it into shared code repositories, the way that the QA engineers will speak to people who are going to be handling the deployments—or at management in this particular case—is going to be through a well-formatted XML test file. So, providing automation around those particular interfaces and then ensuring that everyone's shared goals are met at the particular period of time where they're going to be invoked over the course of the delivery of that feature, is the “subtle art,”—air quotes, you can't see but—to me of DevOps diplomacy. That kind of help?Emily: Yeah, absolutely. Let's take, actually, just a little bit of a step back. Can you talk about what some of the business goals were behind moving to Kubernetes for Ygrene? Who was the champion of this move? Was it business stakeholders saying, “Hey, we really need this to change,” or engineering going to business stakeholders? Who needed a change. I believe that the desire for Kubernetes came from a bottleneck of infrastructure. Not so much around performance, such as the applications weren't performing due to scale. We had projected scale that we were coming to where it would cause a problem potentially, but it was also in the ease of deployment. It had a very operations mindset as Zack was saying, our infrastructure was almost entirely managed—of the core applications set—by outsourcing. And so, we depended on them to innovate, we depended on them to spin up new environments and services. But we also have this internal competing team that always had this cloud background. And so, what we were trying to do was lessen the time between idea to deployment by utilizing platforms that were more scalable, more flexible, and all the things that Docker gives with the Dev/Prod Parity, the ease of packaging your environment together so that small team can ship an entire application. And so, I think our main goal with that was to take that team that already had a lot of cloud experience, and give them more power to drive the innovation and not be bottlenecked just by what the outsourcing team could do. Which, by the way, just for the record, the outsourcing team was an amazing team, but they didn't have the Kubernetes or cloud experience, either. So, in terms of a hero or champion of it, it just started as an idea between me and the new CTO, or CIO that came in, talking about how can we ship code faster? So, one of the things that happened in my career was the desire for a rapid response team which, that sounds like a buzzword or something, but it was this idea that Ygrene was shipping software fairly slow, and we wanted to get faster. So, really the CIO, and one of the development managers, they were the really big champions of, “Hey, let's deliver value to the business faster.” And they had the experience to ask their engineers how to make that happen, and then trust Zack and I through this process of delivering Kubernetes, and Istio, and container security, and all these different things that eventually got implemented.Emily: Why do you think shipping code faster matters?Austin: I think, for this company, why it mattered was the PACE financing industry is relatively new. And while financing has some old established patterns, I feel like there's still always room for innovation. If you hear the early days of the Bridgewater Financial Hedge Fund, they were a source of innovation and they used technology to deliver new types of assets and things like that. And so, our team at Ygrene was excellent because they wanted to try new things. They wanted to try new patterns of PACE financing, or ways of getting in front of the customer, or connections with different analytics so they could understand their customer better. So, it was important to be able to try things, experiment to see what was going to be successful. To get things out into the real world to know, okay, this is actually going to work, or no, this isn't going to work. And then, also, one of the things within financing is—especially newer financing—is there's a lot of speed bumps along the way. Compliance laws can come into effect, as well as working with cities and governments that have specialized rules and specialized things that they need—because everyone's an expert when it comes to legislation, apparently—they decide that they need X, and they give us a time when we have to get it done. And so, we actually have another customer out there, which is the legislative bodies. So, they have to get the software—their features that are needed within the financing system out by certain dates, or we're no longer eligible to operate in those counties. So, one of it was a core business risk, so we needed to be able to deliver faster. The other was how can we grow the business?Emily: Zach, this might be a question for you. Was there anything that was lost in translation as you were explaining what engineering was going to do in order to meet this goal of shipping code faster, of being more agile, when you were talking to C level management? How did they understand, and did anything get lost in translation?Zach: One of the largest disconnects, both on a technical and from a high level speaking to management issue I had was explaining how we were no longer going to be managing application servers as though they were pets. When you come from an on-premise setup, and you've got your VMware ESXi, and you're managing virtual machines, the most important thing that you have is backups because you want to keep those machines exactly as they are, and you install new software on those machines. When Kubernetes says, I'm going to put your pods wherever they fit on the cluster, assuming it conforms with the scheduling pattern, and if a node dies, it's totally fine, I'm going to spin a new one up for you, and move pods around and ensure that the application is exactly as you had stated—as in, it's in its desired state—that kind of thinking from switching from infrastructure as pets to infrastructure as cattle, is difficult to explain to people who have spent their careers in building and maintaining datacenters. And I think a lot—well, it's not guaranteed that this is across the board, but if you want to talk about a generational divide, people that usually occupy the C level office chairs are familiar with—in their heyday of their career—a datacenter-based setup. In a cloud-based consumption model where it really doesn't matter—I can just spin up anything anywhere—when you talk about moving from reasoning about your application as the servers it comprises and instead talking about your application as the workload it comprises, it becomes a place where you have to really, really concretely explain to people exactly how it's going to work that the entire earth will not come crashing down if you lose a server, or if you lose a pod, or if a container hiccups and gets restarted by Kubernetes on that node. I think that was the real key one. And the reason why that actually became incredibly beneficial for us is because once we actually had that executive buy-off when it came to, while I still may not understand, I trust that you know what you're doing and that this infrastructure really is replaceable, it allowed us to get a little bit more aggressive with how we managed our resources. So, now using Horizontal Pod Autoscaling, using the Kubernetes Cluster Autoscaler, and leveraging Amazon EC2 Spot Fleets, we were only ever paying for the exact amount of infrastructure that was required to run our business. And I think that is usually the thing that translates the best to management and non-technical leadership. Because when it comes down to if I'm aware that using this tool, and using a cloud-native approach to running my application, I am only ever going to be paying for the computational resource that I need in that exact minute to run my business, then the budget discussions become a lot easier, because everyone is aware that this is your exact run-rate when it comes to technology. Does that make sense? Emily: Absolutely. How important was having that executive buy-in? My understanding is that a lot of companies, they think that they're going to get all these savings from Kubernetes, and it doesn't always materialize. So, I'm just curious, it sounds like it really did for Ygrene.Zach: There was two things that really worked well for us when this transformation was taking place. The first was, Ygrene was still growing, so if the budget grew alongside of the growth of the company, nobody noticed. So, that was one really incredible thing that happened that, I think, now having had different positions in the industry, I don't know if I appreciated that enough because if you're attempting to make a cost-neutral migration to the Cloud, or to adopt cloud-native management principles, you're going to probably move too little, too late. And when that happens, you run the risk of really doing a poor job of adopting cloud-native, and then scrapping that project, because it never materialized the benefit, as you just described, that some people didn't experience. And the other benefit that we had, I think was the fact that because there were enough incredibly senior technical people—and again, I learned everything from these people—working with us, and because we were all, for the most part, on the same page when it came to this migration, it was easy to have a unified front with our management because every engineer saw the value of this new way of running our infrastructure and running our application. In one non—and this obviously helps with our engineers—one non-monetary benefit that helped really get the buy-in was the fact that, with Kubernetes, our on-call SEV-1 pages went down, I want to say, by over 40 percent which was insane because Kubernetes was automatically intervening in the case where servers went down. JVMs run out of memory, exceptions cause strange things, but a simple restart usually fixes the vast majority of them. Well, now Kubernetes was doing this and we didn't need to wake somebody up in order to keep the machine running.Emily: From when you started this transition to when you, I should say, when you probably left the company, but what were some of the surprises, either surprises for you, or surprises for other people in the organization?Austin: The initial surprise was the yes that we got. So, initially I pitched it and started talking about it, and then the culture started changing to where we realized we really needed to change, and bringing Zack on and then getting the yes from management was the initial surprise. And—Emily: Why was that a surprise?Austin: It was just surprising because, when you work as an engineer—I mean, none of us were C suite, or Dev managers, or anything. We were just highly respected engineers working in the HQ. So, it was just a surprise that what we felt was a semi-crazy idea at the time—because Kubernetes was a little bit earlier. I mean, EKS wasn't even a thing from Amazon. We ran our Kubernetes clusters from the hip, which is using kops, which is—kops is a great tool, but obviously it wasn't managed. It was managed by us, mainly by Zach and his team, to be honest. So, that was a surprise that they would trust a billion-dollar financing engine to run on the proposal of two engineers. And then, the next ones were just how much the single-server, vertical scaling, and depending on running on the same server was into our applications. So, as we started to look at the core applications and moving them into a containerized environment, but also into an environment that can be spun up and spun down, looking at the assumptions the application was making around being on the same server; having specific IP addresses, or hostnames; and things like that, where we had to take those assumptions out and make things more flexible. So, we had to remove some stateful assumptions in the applications, that was a surprise. We also had to enforce more of the idea of idempotency, especially when introducing Istio, and [00:21:44 retryable] connections and retryable logic around circuit breaking and service-to-service communication. So, some of those were the bigger surprises, is the paradigm shift between, “Okay, we've got this service that's always going to run on the same machine, and it's always going to have local access to its files,” to, “Now we're on a pod that's got a volume mounted, and there's 50 of them.” And it's just different. So, that was a big—[laughs], that was a big surprise for us.Emily: Was there anything that you'd call a pleasant surprise? Things that went well that you anticipated to be really difficult?Zach: Oh, my gosh, yes. When you read through Kubernetes for the first time, you tend to have this—especially if somebody else told you, “Hey, we're going to do this,” this sinking feeling of, “Oh my god, I don't even know nothing,” because it's so immense in its complexity. It requires a retooling of how you think, but there have been lots of open-source community efforts to improve the cluster lifecycle management of Kubernetes, and one such project that really helped us get going—do you remember this Austin?—was kops.Austin: Yep. Yep, kops is great.Zach: I want to say Justin Santa Barbara was the original creator of that project, and it's still open source, and I think he still maintains it. But to have a production-ready, and we really mean production-ready: it was private, everything was isolated, the CNI was provisioned correctly, everything was in the right place, to have a fully production-ready Kubernetes cluster ready to go within a few hours of us being able to learn about this tool in AWS was huge because then we could start to focus on what we didn't even understand inside of the cluster. Because there were lots of—Kubernetes is—there's two sides of it, and both of them are confusing. There's the infrastructure that participates in the cluster, and there's the actual components inside of the cluster which get orchestrated to make your application possible. So, not having to initially focus on the infrastructure that made up the cluster, so we could just figure out the difference between our butt and the hole in the ground, when it came to our application inside of Kubernetes was immensely helpful to us. I mean, there are a lot of tools these days that do that now: GKE, EKS, AKS, but we got into Kubernetes right after it went GA, and this was huge to help with that.Emily: Can you tell me also a little bit about the cultural changes that had to happen? And what were these cultural changes, and then how did it go?Zach: As Austin said, the notion of—I think a lot—and I don't want to offer this as a sweeping statement—but I think the vast majority of the engineers that we had in Seattle, in San Jose, and in Petaluma where the company was headquartered, I think, even if they didn't understand what the word idempotent meant, they understood more or less how that was going to work. The larger challenge for us was actually in helping our contractors, who actually made up the vast majority of our labor force towards the end of my tenure there, how a lot of these principles worked in software. So, take a perfect example: part of the application is written in Ruby on Rails, and in Ruby on Rails, there's a concept of one-off tasks called rake tasks. When you are running a single server, and you're sending lots of emails that have attachments, those attachments have to be on the file system. And this is the phrase I always said to people, as we refactor the code together, I repeated the statement, “You have to pretend this request is going to start on one server and finish on a different one, and you don't know what either of them are, ahead of time.” And I think using just that simple nugget really helped, culturally, start to reshape this skill of people because when you can't use or depend on something like the file system, or you can't depend on that I'm still on the same server, you begin to break your task into components, and you begin to store those components in either a central database or a central file system like Amazon S3. And adopting those parts of, I would call, cloud-native engineering were critical to the cultural adoption of this tool. I think the other thing was, obviously, lots of training had to take place. And I think a lot of operational handoff had to take place. I remember for, basically, a fairly long stretch of time, I was on-call along with whoever was also on-call because I had the vast majority of the operational knowledge of Kubernetes for that particular team. So, I think there was a good bit of rescaling and mindset shift from the technical side of being able to adopt a cloud-native approach to software building. Does that make sense?Emily: Absolutely. What do you think actually were some of the biggest challenges or the biggest pain points? Zach: So, challenges of cultural shift, or challenges of specifically Kubernetes adoption?Emily: I was thinking challenges of Kubernetes adoption, but I'm also curious about the cultural shift if that's one of the biggest pain points.Zach: It really was for us. I think—because now it wouldn't—if you wanted to take out Kubernetes and replace it with Nomad there? All of the engineers would know what you're talking about. It wouldn't take but whatever the amount of time it would to migrate your Kubernetes manifests to Nomad HCL files. So, I do think the rescaling and the mindset shift, culturally speaking, was probably the thing that helped solidify it from an engineering level. But Kubernetes adoption—or at least problems in Kubernetes adoption, there was a lot of migration horror stories that we encountered. A lot of cluster instability in earlier versions of Kubernetes prevented any form of smooth upgrades. I had to leave—it was with my brother's—it was his wedding, what was it—oh, rehearsal dinner, that's what it was. I had to leave his rehearsal dinner because the production cluster for Ygrene went down, and we needed to get it back up. So, lots of funny stories like that. Or Nordstrom did a really fantastic talk on this in KubeCon in Austin in 2017. But the [00:28:57 unintelligible] split-brain problem where suddenly the consensus in between all of the Kubernetes master nodes began to fail for one reason or another. And because they were serving incorrect information to the controller managers, then the controller managers were acting on incorrect information and causing the schedulers to do really crazy things, like delete entire deployments, or move pods, or kill nodes, or lots of interesting things. I think we unnecessarily bit off a little bit too much when it came to trying to do tricky stuff when it came to infrastructure. We introduced a good bit of instability when it came to Amazon EC2 Spot that I think, all things considered, I would have revised the decision on that. Because we faced a lot of node instability, which translated into application instability, which would cause really, really interesting edge cases to show up basically only in production.Austin: One of the more notable ones—and I think this is the symptom of one of the larger challenges was during testing, one of our project managers that also helped out in the testing side—technical project managers—which we nicknamed the Edge Case Factory, because she was just, anointed, or somehow had this superpower to find the most interesting edge cases, and things that never went wrong for anyone else always went wrong for her, and it really helped us build more robust software for sure, but there's some people out there with mutant powers to catch bugs, and she was one of them. We had two clusters, we had lower environment clusters, and then we had production cluster. The production cluster hosted two namespaces: the staging namespace, which is supposed to be an exact copy of production; and then the production namespace, so that you can smoke-test legitimate production resources, and blah blah blah. So, one time, we started to get some calls that, all of a sudden, people were getting the staging environment underneath the production URL. Zach: Yeah.Austin: And we were like, “Uh… excuse me?” It comes down to—we eventually figured it out. It was something within the networking layer. But it was this thing, as we rolled along, the deeper understanding of, okay, how does this—to use a term that Zack Arnold coined—this benevolent botnet, how does this thing even work, at the most fundamental and most detailed levels? And so, as problems and issues would occur, pre-production or even in production, we had to really learn the depths of Kubernetes. And I think the reason we had to learn it at that stage was because of how new Kubernetes was, all things considered. But I think now with a lot more of the managed systems, I would say it's not necessary, but it's definitely helpful to really know how Kubernetes works down in the depths. So, that was one of the big challenges was, to put it succinctly, when an issue comes up, knowing really what's going on under the hood, really, really helped us as we discovered and learned things about Kubernetes.Zach: And what you're saying, Austin, was really illuminated by the fact that the telemetry that we had in production was not sufficient, in our minds, at least until very recently, to be able to adequately capture all the data necessary to accurately do root cause analyses on particular issues. In early days, there was far too much root cause analysis by, “It was probably this,” and then we moved on. Now having actually taken the time to instrument tracing, to instrument metrics, to instrument logs with correlation, we used, eventually, Datadog, but working our way through the various telemetry tools to achieve this, we really struggled being able to give accurate information to stakeholders about what was really going wrong in production. And I think Austin was probably the first person in the headquarters side of the company—I'm not entirely certain about some of our satellite dev offices—but to really champion a data-driven way of actually running software. Which, it seems trivial now because obviously that's how a lot of these tools work out of the box. But for us, it was really like, “Oh, I guess we really do need to think about the HTTP error rate.” [laughs].Emily: So, taking another step back here, do you think that Ygrene got everything that it expected, or that it wanted out of moving to Kubernetes?Austin: I think we're obviously playing up some of the challenges that we had because it was our day-to-day, but I do believe that trust in the dev team grew, we were able to deploy code during the day, which we could have done that in the beginning, even with vertically scaled infrastructure, we would have done it with downtime, but it really was that as we started to show that Kubernetes and these cloud-native tools like Fluentd, Prometheus, Istio, and other things like that when you set them up properly, they do take a lot of the risk out. It added trust in the development team. It gave more responsibility to the developers to manage their own code in production, which is the DevOps culture, the DevOps mindset. And I think in the end, we were able to ship code faster, we were able to deliver more value, we were able to go into new jurisdictions and markets quicker, to get more customers, and to ultimately increase the amount of revenue that Ygrene had. So, it built a bridge between the data science side of things, the development side of things, the project management side of things, and the compliance side of things. So, I definitely think they got a lot out of trusting us with this migration. I think that were we to continue, probably Zack and I even to this day, we would have been able to implement more, and more, and more. Obviously, I left the company, Zach left the company to pursue other opportunities, but I do believe we left them in a good spot to take this ecosystem that was put in place and run with it. To continue to innovate and do experiments to get more business.Zach: Emily, I'd characterize it with an anecdote. After our Chief Information Officer left the company, our Chief Operating Officer actually took over the management of the Technology Group, and aside from basically giving dev management carte blanche authority to do as they needed to, I think there was so much trust there that we didn't have at the beginning of our journey with technology and Ygrene. And it was characterized in, we had monthly calls with all of the regional account managers, which are basically our out-of-office sales staff. And generally, the project managers from our group would have to sit in those meetings and hear just about how terrible our technology was relative to the competition, either lacking in features, lacking in stability, lacking in design quality, lacking in user interface design, or way overdoing the amount of compliance we had to have. And towards the end of my tenure, those complaints dropped to zero, which I think was really a testament to the fact that we were running things stably, the amount of on-call pages went down tremendously, the amount of user-impacting production outages was dramatically reduced, and I think the overall quality of software increased with every release. And to be able to say that, as a finance company, we were able to deploy 10 times during the day if we needed to, and not because it was an emergency, but because it was genuinely a value-added feature for customers. I think that that really demonstrated that we reached a level of success adopting Kubernetes and cloud-native, that really helped our business win. And we positioned them, basically, now to make experiments that they thought would work from a business sense we implement the technology behind it, and then we find out whether or not we were right.Emily: Let's go ahead and wrap up. We're nearing the top of the hour, but just two questions for both of you. One is, where could listeners find you or connect with you? And the second one is, do you have a can't-live-without engineering tool?Austin: Yeah, so I'll go first. Listeners can find me on Twitter @_austbot, or on LinkedIn. Those are really the only tools I use. And I can't really live without Prometheus and Grafana. I really love being able to see everything that's happening in my applications. I love instrumentation. I'm very data-driven on what's happening inside. So, obviously Kubernetes is there, but it's almost become that Kubernetes is the Cloud. I don't even think about it anymore. It's these other tools that help us monitor and create active monitoring paradigms in our application so we can deploy fast, and know if we broke something. Zach: And if you want to stay in contact with me, I would recommend not using Twitter, I lost my password and I'm not entirely certain how to get it back. I don't have a blue checkmark, so I can't talk to Twitter about that. I probably am on LinkedIn… you know what, you can find me in my house. I'm currently working. The engineering tool that I really can't live without, I think my IDE. I use IntelliJ by JetBrains, and—Austin: Yeah, it's good stuff.Zach: —I think I wouldn't be able to program without it. I fear for my next coding interview because I'll be pretending that there's type ahead completion in a Google Doc, and it just won't work. So, yeah, I think that would be the tool I'd keep forever.Austin: And if any of Zach's managers are listening, he's not planning on doing any coding interviews anytime soon.Zach: [laughs]. Yes, obviously.Emily: Well, thank you so much. Zach: Emily Omier, thank you so much for your time.Austin: Right, thanks.Austin: And don't forget Zack is an author. He and his team worked very hard on that book.Emily: Zack, do you want to give a plug to your book?Zach: Oh, yeah. Some really intelligent people that, for some reason, dragged me along, worked on a book. Basically it started as an introduction to Kubernetes, and it turned into a Master's Course on Kubernetes. It's from Packt Publishing and yeah, you can find it there, amazon.com or steal it on the internet. If you're looking to get started with Kubernetes I cannot recommend the team that worked on this book enough. It was a real honor to be able to work with people I consider to be heavyweights in the industry. It was really fun.Emily: Thank you so much.Announcer: Thank you for listening to The Business of Cloud Native podcast. Keep up with the latest on the podcast at thebusinessofcloudnative.com and subscribe on iTunes, Spotify, Google Podcasts, or wherever fine podcasts are distributed. We'll see you next time.This has been HumblePod production. Stay humble.

“AI can reduce dramatically the time to finding solutions for COVID-19. But applications that are not supported by domain experts are usually dangerous. They can be based on mistakes or misinterpretations. So it's vital that we understand the scientific methodologists which are being applied.” This is a conversation with Giuseppe Bonaccorso. Giuseppe is Head of Data Science in a large pharmaceutical corporate. His main interests include machine/deep learning, reinforcement learning, big data, and bio-inspired adaptive systems. He is author of several publications including Machine Learning Algorithms and Hands-On Unsupervised Learning with Python, published by Packt Publishing. In this episode, Giuseppe talks about how AI is being applied in healthcare. We talk about whether biases in data could slow down a cure for Covid-19 and the challenges that remain with health data collection, even when it starts with good intentions.

In this episode of Adventures in Angular the panel interviews Zama Khan Mohammed about his recent book and other open source work he has done in the Angular community. Zama explains what is so different about his book and why it is worth reading. His book takes an approach different than the common practice of walking readers through concepts, instead, his book walks readers through using a project perspective.    The first chapter walks through setting up Angular, installing Angular CLI and Angular console. After the set up is complete he walks readers through a very basic flashbase application. Zama explains how this first chapter is geared toward beginners. In his book, Zama shows users how to use the whole platform. He covers PWA and how to create brand new projects from scratch.     The panel asks him about his unique project perspective strategy for this book. Each chapter of Zama’s book walks the readers through a different project, unlike most technical books that walk readers through one project introducing a different concept each chapter. Zama explains why he wrote the book this way. He wanted to bring different libraries and tools into each project to highlight how deep and rich the Angular community and ecosystem are. The panel shares how the ecosystem and community make Angular so great to use.    Zama’s book is called Angular Projects and was published by Packt Publishing. Zama shares where to find it for those interested. The panel considers how hard writing a book must be. Zama explains the time and stress involved in writing a book. He admits he has been approached to write more books but has resolved to wait a bit before diving back into writing.    The panel discusses Zama’s open source efforts in the Angular community. They consider a few of his projects including, ngx-formly, codelyzer, and ngx-loading. He wrote ngx-formly after using formerly and he decided he wanted to use it with Angular 2.0. The panel was impressed with his contributions to codelyzer, where he helped with the accessibility requirements.    After using react-loadable Zama knew he wanted a similar feature in Angular to provide more control over loading so he built ngx-loadable. The panel defines lazy loading for listeners and explains how having control over what can load and how fast it can load can be useful in applications. Zama shares some of the improvements he has made in version 2.0.    Zama shares his hopes for speaking at ng-conf 2020, this takes the panel down a tangent discussing the exciting workshops that will be at ng-conf next year. Brian Love will be teaching a two-day workshop on Angular fundamentals. Aaron Frost is teaching and observables class and a reactive angular class. They advise everyone to buy an ng-conf ticket and not to be afraid to submit a CFP.    Back on topic, Zama shares the challenges in writing, publishing and maintaining an opensource library. He explains how contributing to open source is a great way to learn and a great way to see what a framework can do. He shares advice for those looking to get into open source and invites everyone to try Hacktoberfest.   Panelists Aaron Frost Brian Love Guest Zama Khan Mohammed Adventures in Angular is produced by DevChat.TV in partnership with Hero Devs Sponsors Sentry use the code “devchat” for 2 months free on Sentry small plan Angular Bootcamp Flatfile Cachefly Links https://angularprojects.com/ https://twitter.com/mgechev https://github.com/mohammedzamakhan https://www.ng-conf.org/ https://hacktoberfest.digitalocean.com/ https://m.hero.dev/ngstory  https://github.com/aaronfrost Audit your Angular app's accessibility with codelyzer https://twitter.com/mohamedzamakhan?lang=en  https://www.facebook.com/adventuresinangular https://twitter.com/angularpodcast Picks Brain Love: ng-conf: CFP Office Hours Aaron Frost: Late Night with Seth Meyers Zama Khan Mohammed: Hacking the Angular Compiler

In this episode of Adventures in Angular the panel interviews Zama Khan Mohammed about his recent book and other open source work he has done in the Angular community. Zama explains what is so different about his book and why it is worth reading. His book takes an approach different than the common practice of walking readers through concepts, instead, his book walks readers through using a project perspective.    The first chapter walks through setting up Angular, installing Angular CLI and Angular console. After the set up is complete he walks readers through a very basic flashbase application. Zama explains how this first chapter is geared toward beginners. In his book, Zama shows users how to use the whole platform. He covers PWA and how to create brand new projects from scratch.     The panel asks him about his unique project perspective strategy for this book. Each chapter of Zama’s book walks the readers through a different project, unlike most technical books that walk readers through one project introducing a different concept each chapter. Zama explains why he wrote the book this way. He wanted to bring different libraries and tools into each project to highlight how deep and rich the Angular community and ecosystem are. The panel shares how the ecosystem and community make Angular so great to use.    Zama’s book is called Angular Projects and was published by Packt Publishing. Zama shares where to find it for those interested. The panel considers how hard writing a book must be. Zama explains the time and stress involved in writing a book. He admits he has been approached to write more books but has resolved to wait a bit before diving back into writing.    The panel discusses Zama’s open source efforts in the Angular community. They consider a few of his projects including, ngx-formly, codelyzer, and ngx-loading. He wrote ngx-formly after using formerly and he decided he wanted to use it with Angular 2.0. The panel was impressed with his contributions to codelyzer, where he helped with the accessibility requirements.    After using react-loadable Zama knew he wanted a similar feature in Angular to provide more control over loading so he built ngx-loadable. The panel defines lazy loading for listeners and explains how having control over what can load and how fast it can load can be useful in applications. Zama shares some of the improvements he has made in version 2.0.    Zama shares his hopes for speaking at ng-conf 2020, this takes the panel down a tangent discussing the exciting workshops that will be at ng-conf next year. Brian Love will be teaching a two-day workshop on Angular fundamentals. Aaron Frost is teaching and observables class and a reactive angular class. They advise everyone to buy an ng-conf ticket and not to be afraid to submit a CFP.    Back on topic, Zama shares the challenges in writing, publishing and maintaining an opensource library. He explains how contributing to open source is a great way to learn and a great way to see what a framework can do. He shares advice for those looking to get into open source and invites everyone to try Hacktoberfest.   Panelists Aaron Frost Brian Love Guest Zama Khan Mohammed Adventures in Angular is produced by DevChat.TV in partnership with Hero Devs Sponsors Sentry use the code “devchat” for 2 months free on Sentry small plan Angular Bootcamp Flatfile Cachefly Links https://angularprojects.com/ https://twitter.com/mgechev https://github.com/mohammedzamakhan https://www.ng-conf.org/ https://hacktoberfest.digitalocean.com/ https://m.hero.dev/ngstory  https://github.com/aaronfrost Audit your Angular app's accessibility with codelyzer https://twitter.com/mohamedzamakhan?lang=en  https://www.facebook.com/adventuresinangular https://twitter.com/angularpodcast Picks Brain Love: ng-conf: CFP Office Hours Aaron Frost: Late Night with Seth Meyers Zama Khan Mohammed: Hacking the Angular Compiler

In this episode of Adventures in Angular the panel interviews Zama Khan Mohammed about his recent book and other open source work he has done in the Angular community. Zama explains what is so different about his book and why it is worth reading. His book takes an approach different than the common practice of walking readers through concepts, instead, his book walks readers through using a project perspective.    The first chapter walks through setting up Angular, installing Angular CLI and Angular console. After the set up is complete he walks readers through a very basic flashbase application. Zama explains how this first chapter is geared toward beginners. In his book, Zama shows users how to use the whole platform. He covers PWA and how to create brand new projects from scratch.     The panel asks him about his unique project perspective strategy for this book. Each chapter of Zama’s book walks the readers through a different project, unlike most technical books that walk readers through one project introducing a different concept each chapter. Zama explains why he wrote the book this way. He wanted to bring different libraries and tools into each project to highlight how deep and rich the Angular community and ecosystem are. The panel shares how the ecosystem and community make Angular so great to use.    Zama’s book is called Angular Projects and was published by Packt Publishing. Zama shares where to find it for those interested. The panel considers how hard writing a book must be. Zama explains the time and stress involved in writing a book. He admits he has been approached to write more books but has resolved to wait a bit before diving back into writing.    The panel discusses Zama’s open source efforts in the Angular community. They consider a few of his projects including, ngx-formly, codelyzer, and ngx-loading. He wrote ngx-formly after using formerly and he decided he wanted to use it with Angular 2.0. The panel was impressed with his contributions to codelyzer, where he helped with the accessibility requirements.    After using react-loadable Zama knew he wanted a similar feature in Angular to provide more control over loading so he built ngx-loadable. The panel defines lazy loading for listeners and explains how having control over what can load and how fast it can load can be useful in applications. Zama shares some of the improvements he has made in version 2.0.    Zama shares his hopes for speaking at ng-conf 2020, this takes the panel down a tangent discussing the exciting workshops that will be at ng-conf next year. Brian Love will be teaching a two-day workshop on Angular fundamentals. Aaron Frost is teaching and observables class and a reactive angular class. They advise everyone to buy an ng-conf ticket and not to be afraid to submit a CFP.    Back on topic, Zama shares the challenges in writing, publishing and maintaining an opensource library. He explains how contributing to open source is a great way to learn and a great way to see what a framework can do. He shares advice for those looking to get into open source and invites everyone to try Hacktoberfest.   Panelists Aaron Frost Brian Love Guest Zama Khan Mohammed Adventures in Angular is produced by DevChat.TV in partnership with Hero Devs Sponsors Sentry use the code “devchat” for 2 months free on Sentry small plan Angular Bootcamp Flatfile Cachefly Links https://angularprojects.com/ https://twitter.com/mgechev https://github.com/mohammedzamakhan https://www.ng-conf.org/ https://hacktoberfest.digitalocean.com/ https://m.hero.dev/ngstory  https://github.com/aaronfrost Audit your Angular app's accessibility with codelyzer https://twitter.com/mohamedzamakhan?lang=en  https://www.facebook.com/adventuresinangular https://twitter.com/angularpodcast Picks Brain Love: ng-conf: CFP Office Hours Aaron Frost: Late Night with Seth Meyers Zama Khan Mohammed: Hacking the Angular Compiler

In this episode Dylan and Erik look at technical book publshing. As a developer how do you get a book deal, what should you expect, should you do self publishing or not? And what to expect if you work with a publisher!

Welcome to this inspiring interview with Kevin Horek, the author of 'Learning Zurb Foundation,' a book to learn HTML, CSS, and JavaScript. This is our very own show 'Bootstrapping Your Dreams' hosted by Manuj Aggarwal.Kevin is best known for his work published on the foundation five, which is a responsive web framework. He's also a Radio-TV and podcast host. In his Podcast 'Building the future,' he interviews Founders, CEOs, investors, advisors, and anybody who is doing something interesting or chasing their passion.So what are you waiting for? Tune in Now!In this episode, we will learn:●    Bringing the luck in your favor. ●    Applying the things that work for you. ●    Using free tools for networking.●    Business opportunities in the coming future.●    The podcast industry business model.●    Playing the cards that life dealt you.●    Finding and taking the opportunities life gives to you. About Kevin Horek:●    Experience: Kevin Horek is a published author and best known for his work published by Packt Publishing on Zurb's responsive framework, Foundation 5. He studied web development and design at universities across North America, including UCLA and the University of Alberta. He started his own Radio/TV/Podcast, 'Building The Future,' to get over his fear of public speaking. He continued to push himself out of his comfort zone by guest blogging for Alpha Gamma, TechZulu, SOCAP. He recently emceed SUP-X, The Start-Up Expo, as well as had a live fireside chat on stage with the keynote speaker.●    Accomplishments: He wrote a tech book, "Learning Zurb Foundation." Built his radio and TV show, "Building the Future" that reaches 10 million listeners a month.●    Fun Facts: He still wishes to be a drummer in a rock and roll band.●    Obstacles Overcame: To get over his fear of public speaking started his show "Building the Future." Links & Mentions From This Episode:●    Kevin's Website: https://www.buildingthefutureshow.com/●    TetraNoodle consulting services: https://bootstraptechstartup.com ●    TetraNoodle professional training: https://courses.tetranoodle.comThanks for Tuning In!Thanks, so much for being with us this week. Have some feedback you'd like to share? Please leave a note in the comments section!Enjoyed the episode? Kindly share it with your friends. Don't forget to subscribe to the show on iTunes to get automatic episode updates for our "Bootstrapping Your Dreams Show!"

Live from DevOpsDays Toronto, I meet up with my fellow DevRel road warrior, Quintessence Anx of Logz.io. Quintessence bring years of experience and compassion to her role. Quintessence is a champion for mindfulness around accessibility and diversity. In her own words... I’ve worked in the IT community for over 10 years, including as a database administrator and a DevOps / Cloud / Infrastructure engineer. I was a core contributor to Stark & Wayne’s SHIELD project, which adds backup functionality to Cloud Foundry, as well as a technical reviewer for Learning Go Programming published by Packt Publishing. Currently I am the US Developer Advocate for Logz.io, driving DevOps community engagement. Outside of work I am a chapter leader of Girl Develop It’s Buffalo chapter to help women in the Buffalo community launch careers in development. https://twitter.com/QuintessenceAnx https://twitter.com/inctechbuffalo

Have you ever thought about building a video course? Have you wanted to share your expertise with other people via a video course on different platforms like Udemy? Have you wondered what are the economics and revenue details of building a course? This podcast episode is for you!  In this episode, I talk about my experience in building my first data science video course, lessons learnt and how you can use these in your own video course.   00:00 to 09:30- I talk about my experience with Packt Publishing in developing the video course. 09:30 onwards- I talk about the 3 lessons learnt and how you can leverage these to fully maximize the potential of your video course.  Links:  1) My First Video course: https://www.packtpub.com/big-data-and-business-intelligence/hands-fundamentals-data-science-go-video  2) Link to my previous podcast on recommendation engines 3) Github link to the starter code of recommendation engines on movie reviews: https://github.com/sanketg10/the-data-life-podcast  4) Link to my new course on "Overview of Query Understanding Techniques": https://sanketgupta.teachable.com/p/query-understanding-techniques  5) Google Ads Keyword Planner: https://ads.google.com/home/tools/keyword-planner/  #video-course #course #teachable #udemy #packt #data-science --- Send in a voice message: https://anchor.fm/the-data-life-podcast/message Support this podcast: https://anchor.fm/the-data-life-podcast/support

Recently my first self published book went live on Amazon. This is my second published book. The book’s title is ‘How To Market Your Game Like A Pro And Make Money’. My first book was published by Packt Publishing and it was focused on developing an Android game. I wrote that book in 2016 and […] The post Why I Wrote A Book On Game Marketing appeared first on nikmlnkr.com.

La editorial Packt Publishing especializada en tecnologías de código abierto, publica desde el 2015 un informe llamado SkillUp, basado en una encuesta realizada a desarrolladores de todo el mundo. El objetivo es conocer las tendencias en tecnologías y herramientas de la industria del software. Con esta encuesta Packt desea obtener respuestas a tres cuestiones: 1. Las herramientas mas populares de uso diario entre los desarrolladores. 2. Que tecnologías o herramientas consideran más utiles los desarrolladores para aprender. 3. Como se sienten los desarrolladores sobre trabajar en la industria y en la comunidad tecnológica. En este episodio hago un recorrido a grandes rasgos por los resultados de este relevante informe, de gran utilidad para cualquier persona vinculada al mundo de la tecnología y la programación. Descargar Informe completo SkillUp 2018 https://www.packtpub.com/skill-up-2018 Como siempre muy agradecido por vuestros comentarios y valoraciones al episodio.

La editorial Packt Publishing especializada en tecnologías de código abierto, publica desde el 2015 un informe llamado SkillUp, basado en una encuesta realizada a desarrolladores de todo el mundo. El objetivo es conocer las tendencias en tecnologías y herramientas de la industria del software. Con esta encuesta Packt desea obtener respuestas a tres cuestiones: 1. Las herramientas mas populares de uso diario entre los desarrolladores. 2. Que tecnologías o herramientas consideran más utiles los desarrolladores para aprender. 3. Como se sienten los desarrolladores sobre trabajar en la industria y en la comunidad tecnológica. En este episodio hago un recorrido a grandes rasgos por los resultados de este relevante informe, de gran utilidad para cualquier persona vinculada al mundo de la tecnología y la programación. Descargar Informe completo SkillUp 2018 https://www.packtpub.com/skill-up-2018 Como siempre muy agradecido por vuestros comentarios y valoraciones al episodio.

Andy Bell, Sander Rensen, Phil Wilkins, and Luis Weir are the authors of Implementing Oracle API Platform Cloud Service, now available from Packt Publishing, and as you'll hear in this podcast, they bring considerable insight and expertise to this discussion of what's happening in API management. The conversation goes beyond the current state of API management to delve into architectural implications, API design, and how working in SOA may have left you with some bad habits. View the complete show notes.

Panel: Chris Fritz Erik Hanchett Divya Sasidharan Brett Nelson Joe Eames Special Guests: Roman Kuba In this episode of Views on Vue, the panelists discuss Vue testing with Roman Kuba. Roman is currently the senior software engineer at Codeship, where he pushes front-end development forward. He talks about his experience switching Cosdehip over to using Vue from Angular, how he completed this task and the pros to using Vue. The panel also touches on the importance of reading the source code and much more! In particular, we dive pretty deep on: Brett intro Roman intro Vue Using Vue in the front-end at Codeship Angular Transition from Angular to Vue How did you do the transition? CoffeeScript Did you find there were differences in how Vue integrated? Why did you choose Vue? Vue is nice to progress into Documentation was really well written Got a lot of great feedback from back-end engineers Did you have any concerns of its long-term viability? Read through a lot of the Vue source code Had template written in Slim Babble and TypeScript Vue is a progressive framework Time reading the source code JavaScript Would you recommend using the source code to other developers? What was your approach to reading the source code? And much, much more! Links: WIPdeveloper.com Codeship Vue Angular CoffeeScript Slim Babble TypeScript JavaScript @Codebryo Roman’s GitHub Picks: Chris We Have Concerns Podcast The Anthropocene Reviewed Podcast The Obelisk Gate by N. K. Jemisin Divya Thorsten’s post on a Vue implementation of React’s context API Vue Test Utils @Akryum Erik Testing Vue.js Applications by Edd Yerburgh Vue.js in Action by Erik Hanchett Joe Seven Languages in Seven Weeks by Bruce Tate Brett Flashforge Find 3D printer Last Shot (Star Wars) by Daniel José Older Roman Technology vs. Humanity by Gerd Leonhard Vue.js course to come on Packt Publishing

Panel: Chris Fritz Erik Hanchett Divya Sasidharan Brett Nelson Joe Eames Special Guests: Roman Kuba In this episode of Views on Vue, the panelists discuss Vue testing with Roman Kuba. Roman is currently the senior software engineer at Codeship, where he pushes front-end development forward. He talks about his experience switching Cosdehip over to using Vue from Angular, how he completed this task and the pros to using Vue. The panel also touches on the importance of reading the source code and much more! In particular, we dive pretty deep on: Brett intro Roman intro Vue Using Vue in the front-end at Codeship Angular Transition from Angular to Vue How did you do the transition? CoffeeScript Did you find there were differences in how Vue integrated? Why did you choose Vue? Vue is nice to progress into Documentation was really well written Got a lot of great feedback from back-end engineers Did you have any concerns of its long-term viability? Read through a lot of the Vue source code Had template written in Slim Babble and TypeScript Vue is a progressive framework Time reading the source code JavaScript Would you recommend using the source code to other developers? What was your approach to reading the source code? And much, much more! Links: WIPdeveloper.com Codeship Vue Angular CoffeeScript Slim Babble TypeScript JavaScript @Codebryo Roman’s GitHub Picks: Chris We Have Concerns Podcast The Anthropocene Reviewed Podcast The Obelisk Gate by N. K. Jemisin Divya Thorsten’s post on a Vue implementation of React’s context API Vue Test Utils @Akryum Erik Testing Vue.js Applications by Edd Yerburgh Vue.js in Action by Erik Hanchett Joe Seven Languages in Seven Weeks by Bruce Tate Brett Flashforge Find 3D printer Last Shot (Star Wars) by Daniel José Older Roman Technology vs. Humanity by Gerd Leonhard Vue.js course to come on Packt Publishing

Align your effors for increased growth. Mentions: Verbling, Uber, Packt Publishing, LinkedIn, Upwork 

Team: Episode 2017-09-04 of Unregrettable Podcast by Johann Lilly in Annapolis, Maryland. Image by LEMUR In Arhus, Denmark on Unsplash [CC0. ]Track Yesterday from Come by @Jahzzar in Gijón, Spain on Betterwithmusic.com [CC]. Audio Engineer, Project Manager, Social Media Manager, Motion Graphics Artist and Video Editor: Juan Celemin in Bogota, Colombia, Graphic Designer and Graphics Consultant: Luke Balbirnie in Dublin, Ireland. Watch:
 Facebook: http://upc.st/facebook
 YouTube: http://upc.st/youtube
 Listen:
 SoundCloud: http://upc.st/soundcloud
 Google Play: http://upc.st/play 
iTunes: http://upc.st/itunes 
Read:
 Medium: http://upc.st/medium
 LinkedIn: http://upc.st/linkedin 
Follow: 
Twitter: http://upc.st/twitter 
Instagram: http://upc.st/instagram
 Subscribe:
 RSS: http://upc.st/rss Tags: work, education, study, mastery, skill, supplement, job, sidehustle, better, effective, foreignlanguage, graduatestudy, gradschool, masters, translation, tutor, teacher, English, content

Bob Fitts guest hosts the show & interviews me about the launch of Stacks, a fully-hosted web platform designed for libraries. SUP-X: The StartUp Expo, North America’s premier startup conference, is March 6-7, 2017, in sunny Fort Lauderdale, Florida. Affordably priced, SUP-X is a two day international conference featuring workshops, panels, speeches, a $50,000 startup competition and over 100 exhibitors. www.sup-x.org www.buildingthefutureshow.com/past-shows…global-llc www.buildingthefutureshow.com/past-shows…/bob-fitts My name is Kevin Horek and I was born and raised in Edmonton, Alberta, Canada. I work as a creative director and partner at a ventures firm. I graduated from NAIT's multimedia program, with honors, the University of Alberta Web Builder program, with honors, and spent a summer studying corporate design at UCLA. For over 20 years, I have worked on web apps, mobile apps and I remember the days when you used to use tables for layout. I wrote a book for Packt Publishing on Zurb's responsive framework Foundation 5. I have worked on projects for BMW, Best Buy, Apple, Adobe, Investors Group, Sprint, Eastlink, ATB, TD, Qantas Airlines, Emirates Airlines, Syngenta, CB Richard Ellis, Grubb&Ellis, Cushman & Wakefield, and Colliers International. My work has won site of the day, best site of the year for Colliers International, and has been published in Hit Parader magazine. https://www.ebsco.com/news-center/press-releases/ebsco-and-stacks-inc.-announce-the-release-of-stacks-a-user-focused-web-pla www.stacksdiscovery.com www.stacksdiscovery.mobi www.hybridventures.io

Gregg Marshall contacted me while he was finalizing his book, Mastering Drupal 8 Views, for Packt Publishing. Flatteringly, he asked me whether I'd be willing to write a foreword for it, after having a look at a late draft. I had a look, I liked it, I wrote the foreword and was pleased to run into Gregg at DrupalCon New Orleans. Listen to the audio or watch the video of our conversation. Below is also a full transcript of our chat. Read the full post and see the conversation video at the Acquia Developer Center: https://dev.acquia.com/podcast/235-mastering-drupal-8-views-meet-gregg-marshall

The authors of "Oracle SOA Suite 12c Administrator's Guide" (2015, Packt Publishing) discuss the role, the technology, and the challenges.

In this episode we talk to Thom Parkin about his new video course on mastering Git, and other things interesting for those who want to improve their Git skills. If you cannot see the audio controls, your browser does not support the audio element. Use the link below to download the mp3 manually. Link to mp3 Listen to the episode on YouTubeLinksThom on Github, Twitter, SitepointGit Fundamentals book Learnable: Introduction to Nitrous.ionitrous.io (for hosted development sandbox)ScreenHero (for remote pairing)Beegit (authoring platform)Mastering Git* on Packt PublishingGet Thom's "Mastering Git" Video Tutorial for 50% off, on the Packt Publishing website if you use the Discount Code GITMASTER2015.  This offer will only last a limited time.Repository for resources, addendum, etc.The Gititudes Kohsuke Kawaguchi’s thoughts on what should be in your commit message* Note that there is a different video course published in 2011 with the same title: McCullough and Berglund on Mastering Git.How to find lost stashesDuring a discussion of git-lost-found (now deprecated in favor of git fsck --lost-found), we asked how to find dropped stashes. git fsck --lost-found will indeed show these as well, although you have to inspect them yourself to identify which came from stash.Episode outline00:00:00 Intro 00:02:25 Bio/welcome 00:02:56 Tell us about your background 00:04:14 What is your experience with VCS? 00:05:47 You have a video course out about Git. Tell us about it! 00:06:28 What is SitePoint? 00:12:32 A video course on/by Packt? 00:13:09 Tell us more about the structure of your video course. 00:15:39 You had your son do the graphical artistry? 00:16:16 Always interesting to see how Git is visualized 00:18:11 Let's talk about nitrous.io 00:30:09 Tangent: Installing GIt on different OSes 00:32:10 Any other things from your video course you would like to discuss? 00:33:20 How do I find lost commits? 00:35:45 Don't stashes appear in the reflog? 00:40:11 What are the other "Gititudes"? 00:45:37 Crafting history, commit messages, squashing vs merging? 01:00:29 How much Git teaching is still left to do in the world? 01:04:13 Where can people find you online? 01:04:58 What is your favorite Git pro tip? 01:05:43 Thank you for coming onto the show! 01:05:50 Outro 01:06:36 Bonus: Head in the closet?

Scott chats with Jason Dentler about NHibernate and their new 3.0 release. Jason is the author of the upcoming "NHibernate 3 Cookbook" from Packt Publishing. Is NHibernate hard and scary? Jason gets Scott up to speed and talks open source community.

Ruby on Rails podcast A new book, just released by Packt Publishing, can help make elearning solutions more efficient by using the Ruby on Rails web development framework. The book, which is intended for users who have a basic familiarity with the framework, and who wish to develop their own applications or enterprise solutions, contains valuable guidance and insight. It is not intended for users who want to develop exotic uses, nor does it require users to be familiar with more complex web-based applications. It is most valuable for the ways in which it instructs users in the planning, development, and deployment processes. The book is entitled Ruby on Rails Enterprise Application Development: Plan, Program, Extend.  For the entire text, please read the entry at ELearning Queen.  

Ruby on Rails podcast A new book, just released by Packt Publishing, can help make elearning solutions more efficient by using the Ruby on Rails web development framework. The book, which is intended for users who have a basic familiarity with the framework, and who wish to develop their own applications or enterprise solutions, contains valuable guidance and insight. It is not intended for users who want to develop exotic uses, nor does it require users to be familiar with more complex web-based applications. It is most valuable for the ways in which it instructs users in the planning, development, and deployment processes. The book is entitled Ruby on Rails Enterprise Application Development: Plan, Program, Extend.  For the entire text, please read the entry at ELearning Queen.  

https://mcdn.podbean.com/mf/web/y4bqi2/drupaleasy-podcast-s16e2-luca-lusso.mp3 We talk with Luca Lusso, author of Modernizing Drupal 10 Theme Development, published in August, 2023 by Packt Publishing. URLs mentionedModernizing Drupal 10 Theme Development bookWebProfiler moduleStorybook Single Directory Components (SDC)Google LighthouseDrupalEasy NewsProfessional Module Development - 15 weeks, 90 hours, live, online course.  Drupal Career Online - 12 weeks, 77 hours, live online, beginner-focused course.Audio transcriptWe're using the machine-driven Amazon Transcribe service to provide an audio transcript of this episode.SubscribeSubscribe to our podcast on iTunes, Google Play, iHeart, Amazon, YouTube, or Spotify. If you'd like to leave us a voicemail, call 321-396-2340. Please keep in mind that we might play your voicemail during one of our future podcasts. Feel free to call in with suggestions, rants, questions, or corrections. If you'd rather just send us an email, please use our contact page.CreditsPodcast edited by Amelia Anello.