Podcasts about app dev

Podcasting 2.0 February 21st 2025 Episode 211: "Podcast Plumbing" Adam & Dave discuss the metrics of measuring success ShowNotes We are LIT Is PC2.0 a failure podcast episode - In and around podcasting Define Success "Industry" - Tipping - Listeners are stupid (just want to hit play) - "movement" History of 2.0 Index Value tag 2.0 is the name of this podcast 2.0 is a namespace project From Year one: NEW Podcast apps Rachel Maddow app Fountain LNBeats Truefans Hosting companies are very active - Podhome and RSSBlue PWR - Adam Must do keynotes - See PC Movement backroom The world is decentralizing See YT and Spotify New groups of users Specific features Hyper Local has caught on Location tag for local podcasts NMS YouTube vs Podcasting 160 million yt channels Vs 250k weekly podcasts We can create new uses for podcasts Godcaster Need an APP Dev! NMS PCI finances Rogan dethroned LOL ------------------------------------- MKUltra chat Transcript Search What is Value4Value? - Read all about it at Value4Value.info V4V Stats Last Modified 02/21/2025 14:18:43 by Freedom Controller

Podcasting 2.0 February 21st 2025 Episode 211: "Podcast Plumbing" Adam & Dave discuss the metrics of measuring success ShowNotes We are LIT Is PC2.0 a failure podcast episode - In and around podcasting Define Success "Industry" - Tipping - Listeners are stupid (just want to hit play) - "movement" History of 2.0 Index Value tag 2.0 is the name of this podcast 2.0 is a namespace project From Year one: NEW Podcast apps Rachel Maddow app Fountain LNBeats Truefans Hosting companies are very active - Podhome and RSSBlue PWR - Adam Must do keynotes - See PC Movement backroom The world is decentralizing See YT and Spotify New groups of users Specific features Hyper Local has caught on Location tag for local podcasts NMS YouTube vs Podcasting 160 million yt channels Vs 250k weekly podcasts We can create new uses for podcasts Godcaster Need an APP Dev! NMS PCI finances Rogan dethroned LOL ------------------------------------- MKUltra chat Transcript Search What is Value4Value? - Read all about it at Value4Value.info V4V Stats Last Modified 02/21/2025 14:18:43 by Freedom Controller

(06:49) Brought to you by Lemon.io⁠Lemon.io⁠ is your go-to platform for hiring top-tier, pre-vetted software engineers from Europe and Latin America. You'll get matched with your developer in just 48 hours.Tech Lead Journal listeners get 15% off your first 4 weeks of work at ⁠lemon.io⁠.Want to learn the key principles and future of DevOps that can help you ship code faster and more reliably?In this episode, I sit down with Yevgeniy Brikman, co-founder of Gruntwork and author of “Terraform: Up & Running,” to discuss his upcoming book, “The Fundamentals of DevOps and Software Delivery.”We explore:- Common pitfalls and anti-patterns in DevOps implementations- The concept of “minimum effective dose” and "incrementalism" in adopting technologies- Why application developers should understand infrastructure and software delivery- The future of DevOps, including “infrastructureless” and the impact of GenAI- The importance of “secure-by-default” practices in modern software development- Recent changes in open source licensing and their impact on the tech industry- The power of continuous learning and sharing knowledge in tech careersListen out for:(00:02:15) Career Turning Points(00:08:32) Deliberate Time for Learning(00:16:27) Transitioning from App Dev to Infra (00:24:19) Understanding How to Deliver Software(00:32:05) Minimum Effective Dose(00:40:34) DevOps Antipatterns(00:44:02) Incrementalism(00:49:37) The Future of DevOps and Software Delivery(01:10:39) Recent Trend in Open Source License Changes(01:20:32) 3 Tech Lead Wisdom_____Yevgeniy Brikman's BioYevgeniy (Jim) Brikman loves programming, writing, speaking, traveling, and lifting heavy things. He does not love talking about himself in the 3rd person. He is the co-founder of Gruntwork, a company that offers products & services for setting up world-class DevOps Foundations. He's also the author of three books published by O'Reilly Media: Fundamentals of DevOps and Software Delivery, Terraform: Up & Running, and Hello, Startup. Previously, he spent more than a decade building infrastructure and products that served hundreds of millions of users while working as a software engineer at LinkedIn, TripAdvisor, Cisco Systems, and Thomson Financial.Follow Yevgeniy: LinkedIn – linkedin.com/in/jbrikman X / Twitter – @brikis98 Website – ybrikman.com

In this special breaking analysis, we're pleased to introduce a new predictions episode featuring some of the top analysts at theCUBE Research. With us today are six of our industry analysts:Bob Laliberte, who covers networking, Scott Hebner on the AI front, Savannah Peterson who will be talking about the impact of consumer tech, Jackie McGuire our newest cybersecurity analyst, Christophe Bertrand who will be discussing his predictions on cyber resiliency, and Paul Nashawaty who leads our App/Dev practice. Thank you all for being here. We really appreciate the collaboration and we are very excited for our inaugural team predictions.

One of the most important skills in life is the ability to zoom out and take a holistic view on a problem. This approach is really instrumental in marketing as well. If you are an app marketer and your job is to drive growth, you should always take a broader look at where your potential or existing app users spend their time online. On today's web, there are many online communities where app users go to dig for information, seek an advice or to share one. But there is only one of a kind that we'll be talking about today - Reddit and to do so we have Sherwin. Today's Topics Include: Sherwin's background What is Reddit How app users use Reddit communities How brands can leverage communities on Reddit Advice for brands for how to work promote their apps on community-centric platforms like Reddit. Android or iOS? Leaving his smartphone at home, what features would Sherwin miss most? What features he would like to see added to his smartphone? Links and Resources: Sherwin Su on LinkedIn Reddit for Business LnkedIn Samsung X Switchers Anonymous Campaign Business Of Apps - connecting the app industry Quotes from Sherwin Su: "So when you think about mobile app users, Reddit is a place where we as an organization, as a company, as a platform, are sitting on 18 plus years of conversations across different types of mobile apps. And it's at different stages of the journey where app users either try to discover, learn how to use and maximize the different apps and then eventually make recommendations on how other folks in their communities can also enjoy the benefits of like the apps that they're using. So for app users, they trust Reddit because they know that these communities have genuine discussions about the apps that they care about." "First, being in advertising, I want to talk about it from a media perspective, that a lot of brands can really leverage the power of community to build their brand and build very authentic and genuine relationships with the customers that they want to serve. There are lot of different ways here at Reddit, having community at the core, that enables brands to engage meaningfully in the space and the internet that no other platform is able to provide. The second one is acquiring customers. And I think this is a journey on its own, because acquiring customers really pushes brands to focus on the core value propositions that they want to share." Host Business Of Apps - connecting the app industry since 2012

Modern applications require modern platforms and team collaboration to deliver velocity, stability and security. So how do we overcome the hurdles to making platform adoption work? SHOW: 840SHOW TRANSCRIPT: The Cloudcast #840 TranscriptSHOW VIDEO: https://youtube.com/@TheCloudcastNET CLOUD NEWS OF THE WEEK: http://bit.ly/cloudcast-cnotwCHECK OUT OUR NEW PODCAST: "CLOUDCAST BASICS"SHOW SPONSOR:Panoptica, Cisco's Cloud Application Security solutionSHOW NOTES:WHY DO PLATFORMS MAKE SENSE FOR MODERN APPLICATIONS?Reduce the cognitive load on application teamsDeliver self-service capabilities where it makes senseDeliver consistent services across teams, with efficient operationsReduce costs, reduce snowflakes, etc.WHAT ARE THE PLATFORM HURDLES, AND HOW TO OVERCOME THEM?The jump from initial projects to scalable delivery across apps and teamsApplication teams wanting snowflake environmentsBuying and budgeting centers not aligning to platform deliveryGetting application team buy-in to platform servicesGetting cross-functional team alignment and coordinationBalancing stability and pace of innovationFEEDBACK?Email: show at the cloudcast dot netTwitter: @cloudcastpodInstagram: @cloudcastpodTikTok: @cloudcastpod

On this episode of DevOps Dialogues: Insights & Innovations, I am joined by VP and Practice Lead, Bob Sutor, for discussion of the impacts of quantum computing on AI, DevOps and AppDev. Our conversation covered: What quantum software development is, what people use as their SDK, the platform, rise of Rust with a Python wrapper and WASM Quantum, AI and AppDev overlap and market space, including qualification TEV, ROI and the economic models Why this is important, and why prospects should care  How this relates to the topics of quantum, DevOps, AI, AppDev, etc These topics reflect ongoing discussions, challenges, and innovations within the DevOps community.  

AI is accelerating application development and modernization in many ways, but developers are just ramping up their use of the technology. This episode of Utilizing Tech includes Paul Nashawaty, who focuses on application development at The Futurum Group, discussing this topic with Allyson Klein and Stephen Foskett. Use cases for AI include documentation, chatbots, data integration, programming co-pilots, and more. Regardless of how AI is used, organizations must accept that they are ultimately responsible for the products and outputs produced. Accelerating testing and thus the entire DevOps release cycle is one area where AI is making incredible growth. Another popular concept is retrieval-augmented generation (RAG) which brings existing datasets to generative AI to improve results. There is currently a lack of confidence in AI-based solutions and concern about the complexity and level of effort required to bring them to market, so vendors must help make deployment easier and better integrated. Product vendors are addressing this by delivering solutions with partners and popular platforms and frameworks. Open source tools and open data are also helping to move AI technologies forward. Developers want invisible infrastructure and platforms that just work, and the emerging AI PC segment promises more processing power on the desktop. 2024 is shaping up to be the year of AI in application development. Hosts: Stephen Foskett, Organizer of Tech Field Day: ⁠https://www.linkedin.com/in/sfoskett/⁠ Allyson Klein: ⁠https://www.linkedin.com/in/allysonklein/ Paul Nashawaty, Practice Lead, Application Development Modernization at The Futurum Group: https://www.linkedin.com/in/paulnashawaty/ Follow Utilizing Tech Website: ⁠https://www.UtilizingTech.com/⁠ X/Twitter: ⁠https://www.twitter.com/UtilizingTech ⁠ Tech Field Day Website: ⁠https://www.TechFieldDay.com⁠ LinkedIn: ⁠https://www.LinkedIn.com/company/Tech-Field-Day ⁠ X/Twitter: https://www.Twitter.com/TechFieldDay Tags: #UtilizingAI, #AppDev, #AI, @TheFuturumGroup, @GestaltIT, @TechFieldDay, @SFoskett, @TechAllyson, @PNashawaty,

If you're planning to deploy AI for your business, here's 5 important capabilities your business needs from the cloud era in order to be successful. SHOW: 806CLOUD NEWS OF THE WEEK - http://bit.ly/cloudcast-cnotwCHECK OUT OUR NEW PODCAST - "CLOUDCAST BASICS"SHOW SPONSORS:Want to win a Tesla Cybertruck or $100,000? Enter the WS02 Choreo Code Challenge (before April 30th)WSO2 Choreo - Why build a platform? Just add developers insteadSHOW NOTES:The Year Ahead in Cloud and Expectations for AI in 2024 (Altitude podcast)IF YOU WANT TO DO AI WELL, YOU NEED TO HAVE DONE CLOUD WELLWhen we first started doing cloud, the smart people would say, “If you don't do IT well today, you won't do cloud well in the future”.The same pattern will repeat itself with AI5 IMPORTANT CLOUD CAPABILITIES NEEDED TO SUCCEED WITH AIAutomate everything - Make automation mission-criticalBuild the right abstractions and flexibilities (e.g. sharing GPUs, Devtools, etc.)Leverage platforms to bring together Data Science, MLOps and AppDevKnow how much things cost (e.g. FinOps)Socialize success, and socialize learnings across teamsFEEDBACK?Email: show at the cloudcast dot netTwitter: @cloudcastpodInstagram: @cloudcastpodTikTok: @cloudcastpod

Low-code dev platforms have gained momentum in recent years, in large part because they promise to shorten what's otherwise typically a lengthy app development cycle. Learn more about your ad choices. Visit megaphone.fm/adchoices

Today we're talking to David Seidenfrau. He has been a leader of about every Tech focus you can imagine from AppDev, TechOps, DataEng, Program/Product Management, Implementation services - you name it, he has led it. Dave has had this opportunity as he's been part of 3 Successful startups 2 with Exits (1 IPO, 1 Acquisition). Most recently Dave has led an Eng. Org from seed to Series C. Dave sat on the board of https://primaryportal.com/ guiding the company from seed funding to a successful series A. Including finding them a CTO. Dave also actively participates as a VC investor primarily through https://www.ideafundpartners.com/portfolio. We're talking about the influence of the right champions in propelling your career forward and how to become a master networker without going to awkward networking events. Dave's sharing how you can spot the right champions, how they can help you identify superpowers you possess and might not even be aware of and use this knowledge to land your next opportunity. Along his career, Dave has become a master networker and relationship builder and he's sharing how it has served him and can serve you! Take a listen and I hope you walk away with at least one actionable insight you can apply to take your job and career in the direction of your dreams! Dave ended the conversation with challenging you to add 100 new connections on you LinkedIn to grow your network, plus one of those you can use to connect with him at https://www.linkedin.com/in/dseidenfrau/ Connect with me on IG at https://www.instagram.com/yourcareerintechnicolor where I share style ideas and fashion finds for career and life you can fall in love with!

You all have no idea how exciting it is to upload this episode! Moosie and I invited Bambosh and Gio on to talk about the creation of The Unofficial Homestuck Collection -- a desktop application that not only lets you read Homestuck as it was intended, but adds in some awesome functionality as well!Download The Unofficial Homestuck CollectionOceanfallsGio's WebsiteHS Music WikiSupport the showEdited and music by DomiWebsiteKo-fiDiscordTwitterYoutubeTumblrDomi's SoundcloudDomi's Ko-FiStart your own podcast!

Let's look at the NEW announcements from AWS re:Invent. Not as many as usual, but some interesting new focus areas for AppDev, AppNet, and Security.SHOW: 675CLOUD NEWS OF THE WEEK - http://bit.ly/cloudcast-cnotwCHECK OUT OUR NEW PODCAST - "CLOUDCAST BASICS"SHOW SPONSORS:AWS Insiders is an edgy, entertaining podcast about the services and future of cloud computing at AWS. Listen to AWS Insiders in your favorite podcast player. Cloudfix HomepageEaton HomepageEaton and Tripp Lite have joined forces to bring more sanity to IT pros days, every day. Visit www.eaton.com/audio to learn more!FujiFilm. Your archival and backup data strategy, built on tape. Fujifilm tape is helping businesses get a handle on their vast amounts of data in the most secure, scalable and efficient way. Find out more at builtontape.fujifilmusa.comSHOW NOTES:2022 AWS re:Invent announcements (AWS Website)2022 AWS re:Invent announcements (Cloudcast notes)~130 new announcements (features, services, partner-related capabilities)< 10 brand new services FEEDBACK?Email: show at the cloudcast dot netTwitter: @thecloudcastnet

Devtoberfest roundup Week 1 Devtoberfest 2022 Week 1: https://blogs.sap.com/2022/09/29/devtoberfest-2022-week-1/?campaigncode=CRM-XB22-MKT-DGEPDCST Devtoberfest 2022 Week 2: https://blogs.sap.com/2022/10/06/devtoberfest-2022-week-2/?campaigncode=CRM-XB22-MKT-DGEPDCST All the Devtoberfest 2022 events: https://groups.community.sap.com/t5/devtoberfest/eb-p/devtoberfest-events/?campaigncode=CRM-XB22-MKT-DGEPDCST SAP Data Warehouse Cloud: Q3 updates, Devtoberfest sessions 2022 Q3 Updates: https://blogs.sap.com/2022/10/05/sap-data-warehouse-cloud-in-q3-news/?campaigncode=CRM-XB22-MKT-DGEPDCST 2022 Q3 Updates webinar: https://event.on24.com/wcc/r/3899854/A025472140C03A7C14B318468B520012 SAP Data Warehouse Cloud at Devtoberfest: https://blogs.sap.com/2022/09/29/data-analytics-sessions-during-devtoberfest-2022/?campaigncode=CRM-XB22-MKT-DGEPDCST SAP TechEd 2022 App Dev and Automation SAP TechEd Application Development and Automation Track: https://go3.events.sap.com/sapteched/hybrid/2022/reg/flow/sap/saptech2022/virtualdashboard/page/showcase/application?url_id=ctabutton-sap-overview-rf SAP TechEd Registration: https://go3.events.sap.com/sapteched/hybrid/2022/reg/flow/sap/saptech2022/registration/page/welcome?url_id=ctabutton-sap-overview-rf Upcoming US CodeJam Events ASUG SAP BTP Summit: https://www.asug.com/events/asug-sap-business-technology-platform-btp-summit SAP CodeJam ABAP: SAP BTP, ABAP Environment & RAP (Atlanta, GA USA): https://groups.community.sap.com/t5/sap-codejam/sap-codejam-abap-sap-btp-abap-environment-amp-rap-atlanta-ga-usa/ec-p/9651#M16%2F%3Fcampaigncode=CRM-XB22-MKT-DGEPDCST SAP CodeJam SAP Cloud Application Programming Model with SAP HANA Cloud (Dallas, TX, USA): https://groups.community.sap.com/t5/sap-codejam/sap-codejam-sap-cloud-application-programming-model-with-sap/ev-p/9652/?campaigncode=CRM-XB22-MKT-DGEPDCST Open Documentation Initiative updates Introducing the Open Documentation Initiative: https://blogs.sap.com/2021/05/20/introducing-the-open-documentation-initiative/?campaigncode=CRM-XB22-MKT-DGEPDCST Join forces with us and collaborate on the SAP Custom Domain Service guides!: https://blogs.sap.com/2022/09/25/join-forces-with-us-and-collaborate-on-the-sap-custom-domain-service-guides/?campaigncode=CRM-XB22-MKT-DGEPDCST Spotlight: SAP HANA Cloud supports the SAP Open Documentation Initiative: https://blogs.sap.com/2022/09/30/spotlight-sap-hana-cloud-supports-the-sap-open-documentation-initiative/?campaigncode=CRM-XB22-MKT-DGEPDCST Collaborate with us on SAP BTP, Neo Environment Documentation: https://blogs.sap.com/2022/10/03/collaborate-with-us-on-sap-btp-neo-environment-documentation/?campaigncode=CRM-XB22-MKT-DGEPDCST SAPUI5 Roadmap Update Roadmap Explorer SAPUI5 Topic: https://roadmaps.sap.com/board?PRODUCT=73554900100800001361&range=CURRENT-LAST#Q4%202022&campaigncode=CRM-XB22-MKT-DGEPDCST

Breaches continue to balloon for healthcare applications as the industry continues to drive innovations in virtual care, personalized medicine, and digital healthcare. Organizations that deploy robust application development security programs create the opportunity to identify and correct security weaknesses before products hit the market.  Software Development Lifecycle (SDLC) security programs provide the tools, processes, and training required to design products with security in mind to reduce the likelihood of breaches of sensitive information.  Join us for this episode of the CyberPHIx podcast where we hear from Ed Adams, CEO for Security Innovation. Security Innovation provides application security services, training, testing, and consulting to healthcare and other industries.  Topics covered in this session include:   Application development security trends  The latest threats and vulnerabilities impacting healthcare application development  Best practices for securing AppDev, DevOps, and DevSecOps teams and processes  Common development misconceptions and missteps that lead to security exposures Security training approaches for healthcare app developers  Frameworks and external resources for SDLC security including OWASP and others  Healthcare-specific vulnerabilities and risk exposures identified during application development  Third-party and fourth-party risks including open-sourced code and IoT devices Budget priorities for SDLC security investments 

Hi! I'm Dr. Myrdalis Diaz-Ramirez. And, this is Episode #24!Today, we have a very special guest, a total rockstar, and one of our beloved mastermind alumni, Dr. Richard Harris, from Great Health and Wellness and Nimbus. We have a great conversation with Dr. Richard Harris about building up your startup, business planning, raising capital, and getting your business to the next level. Enjoy this episode!You can contact and follow Dr. Harris at these links:Physician Website: TheGHWellness.comBusiness Website: NimbusMensCare.comPodcast: Strive for Great Health PodcastCourses: Featured CoursesYou can also see Dr, Harris on social media:YouTube: Richard Harris MDLinkedIn: drharrismdTwitter: drharrismdThank you for joining us this week!----------------------------------------------------------------------------------------------------Follow Dr. Myrdalis Diaz at these links: Website: drmyrdalisdiaz.comPodcast: Design Your Physician LifeLinkedin: Myrdalis Diaz-Ramirez Facebook: Dr. Myrdalis Diaz-Ramirez

Ken Ahrens (@kahrens_atl, Co-Founder @Speedscaleai) talks about the challenges of testing applications in Kubernetes environments.  SHOW: 635CLOUD NEWS OF THE WEEK - http://bit.ly/cloudcast-cnotwCHECK OUT OUR NEW PODCAST - "CLOUDCAST BASICS"SHOW SPONSORS:Streamline on-call, collaboration, incident management, and automation with a free 30-day trial of Lightstep Incident Response, built on ServiceNow. Listeners of The Cloudcast will also receive a free Lightstep Incident Response T-shirt after firing an alert or incident.Pay for the services you use, not the number of people on your team with Lightstep Incident Response. Try free for 30 days. Fire an alert or incident today and receive a free LightstepIncident Response t-shirt.Datadog Kubernetes Solution: Maximum Visibility into Container EnvironmentsStart monitoring the health and performance of your container environment with a free 14 day Datadog trial. Listeners of The Cloudcast will also receive a free Datadog T-shirt.SHOW NOTES:Speedscale (homepage)Kubernetes Load Test (tutorial)Speedscale Traffic Replay Topic 1 - Welcome to the show. Let's talk about your background and what led to start Speedscale. Topic 2 - Kubernetes has definitely gone mainstream at this point, but mainstream doesn't mean that it's easy to use or operate. How do you see the market today in terms of companies being comfortable with operating Kubernetes - what works well, and where are their struggles?Topic 3 - In the past we had things that would test Kubernetes conformance (from CNCF, or Sonobuoy from Heptio). Where does Speedscale come into play in terms of Kubernetes testing?Topic 4 - Where do you see opportunities to bring value to testing of Kubernetes environments? Does this testing tend to help DevOps teams or AppDev teams more?Topic 5 - What are some of the common areas where you see companies getting benefits from Kubernetes testing? Topic 6 - What are some of the best ways to get started in testing for Kubernetes?FEEDBACK?Email: show at the cloudcast dot netTwitter: @thecloudcastnetFuture Fit FounderBrave founders jump in my coaching time machine to revisit their toughest momentListen on: Apple Podcasts Spotify

DevRel has evolved over the past few years and in this podcast we are talking to the groundbreaking thought leaders who are paving the way for people and organizations who want to follow DevRel best practices. To many people, Developer Relations is the community management for technical audiences, but for others it's a lot more. It's building relationships and fostering trust, it's collecting and relaying feedback to other teams or it's inspiring people to build tools to empower.This week's guest is Rain Leander, AppDev Technical Evangelist @ Cockroach Labs.LinkedIn: linkedin.com/in/rainleanderTwitter:  https://twitter.com/rainleander 

About MichaelMichael is the creator of IT automation platforms Cobbler and Ansible, the latter allegedly used by ~60% of the Fortune 500, and at one time one of the top 10 contributed to projects on GitHub.Links Referenced: Speaking Tech: https://michaeldehaan.substack.com/ michaeldehaan.net: https://michaeldehaan.net Twitter: https://twitter.com/laserllama TranscriptAnnouncer: Hello, and welcome to Screaming in the Cloud with your host, Chief Cloud Economist at The Duckbill Group, Corey Quinn. This weekly show features conversations with people doing interesting work in the world of cloud, thoughtful commentary on the state of the technical world, and ridiculous titles for which Corey refuses to apologize. This is Screaming in the Cloud.Corey: This episode is sponsored by our friends at Revelo. Revelo is the Spanish word of the day, and its spelled R-E-V-E-L-O. It means “I reveal.” Now, have you tried to hire an engineer lately? I assure you it is significantly harder than it sounds. One of the things that Revelo has recognized is something I've been talking about for a while, specifically that while talent is evenly distributed, opportunity is absolutely not. They're exposing a new talent pool to, basically, those of us without a presence in Latin America via their platform. It's the largest tech talent marketplace in Latin America with over a million engineers in their network, which includes—but isn't limited to—talent in Mexico, Costa Rica, Brazil, and Argentina. Now, not only do they wind up spreading all of their talent on English ability, as well as you know, their engineering skills, but they go significantly beyond that. Some of the folks on their platform are hands down the most talented engineers that I've ever spoken to. Let's also not forget that Latin America has high time zone overlap with what we have here in the United States, so you can hire full-time remote engineers who share most of the workday as your team. It's an end-to-end talent service, so you can find and hire engineers in Central and South America without having to worry about, frankly, the colossal pain of cross-border payroll and benefits and compliance because Revelo handles all of it. If you're hiring engineers, check out revelo.io/screaming to get 20% off your first three months. That's R-E-V-E-L-O dot I-O slash screaming.Corey: This episode is sponsored in part by LaunchDarkly. Take a look at what it takes to get your code into production. I'm going to just guess that it's awful because it's always awful. No one loves their deployment process. What if launching new features didn't require you to do a full-on code and possibly infrastructure deploy? What if you could test on a small subset of users and then roll it back immediately if results aren't what you expect? LaunchDarkly does exactly this. To learn more, visit launchdarkly.com and tell them Corey sent you, and watch for the wince.Corey: Once upon a time, Docker came out and change an entire industry forever. But believe it or not, for many of you, this predates your involvement in the space. There was a time where we had to manage computer systems ourselves with our hands—kind of—like in the prehistoric days, chiseling bits onto disk and whatnot. It was an area crying out for automation, as we started using more and more computers to run various websites. “Oh, that's a big website. It needs three servers now.” Et cetera.The times have changed rather significantly. One of the formative voices in that era was Michael DeHaan, who's joining me today, originally one of the—or if not the creator of Cobbler, and later—for which you became better known—Ansible. First, thanks for joining me.Michael: Thank you for having me. You're also making me feel very, very old there. So, uh, yes.Corey: I hear you. I keep telling people, I'm in my mid-30s, and my wife gets incensed because I'm turning 40 in July. But still. I go for the idea of yeah, the middle is expanding all the time, but it's always disturbing talking to people who are in our sector, who are younger than some of the code that we're using, which is just bizarre to me. We're all standing on the backs of giants. Like it or not, one of them's you.Michael: Oh, well, thank you. Thank you very much. Yeah, I was, like, talking to some undergrads, I was doing a little bit of stuff helping out my alma mater for a little bit, and teaching somebody the REST lecture. I was like, “In another year, REST is going to be older than everybody in the room.” And then I was just kind of… scared.Corey: Yeah. It's been a wild ride for basically everyone who's been around long enough if you don't fall off the teeter-totter and wind up breaking a limb somewhere. So, back in the bad old days, before cloud, when everything was no longer things back then were constrained by how much room you had on your credit card like they are today with cloud, but instead by things like how much space you had in the data center, what kind of purchase order you could ram through your various accounting departments. And one of the big problems you have is, great. So, finally—never on time—Dell has shipped out a whole bunch of servers—or HP or Supermicro or whoever—and the remote hands—which is always distinct from smart hands, which says something very insulting, but they seem to be good about it—would put them into racks for you.And great, so you'd walk in and see all of these brand new servers with nothing on them. How do we go ahead and configure these things? And by hand was how most of us started, and that means, oh, great, we're going to screw things up and not do them all quite the same, and it's just a treasure and a joy. Cobbler was something that you came up with that revolutionized how provisioning of bare-metal systems worked. Tell me about it.Michael: Yeah, um, so it's basically just glue. So, the story of how I came up with that is I was working for the Emerging Technologies Group at Red Hat, and I just joined. And they were like, “We have to have a solution to install Xen and KVM virtual machines.” So obviously, everybody's familiar with, like, EC2 and things now, but this was about people running non-VMware virtualization themselves. So, that was part of the problem, but in order to make that interesting, we really needed to have some automation around bare-metal installs.And that's PXE boot. So, it's TFTP and DHCP protocol and all that kind of boring stuff. And there was glue that existed, but it was usually humans would have to click on buttons to—like Red Hat had system-config-netboot, but what really happened was sysadmins all wrote their own automation at, like, every single company. And the idea that I had, and it was sort of cemented by the fact that, like, my boss, a really good guy left for another company and I didn't have a boss for, like, a couple years, was like, I'm just going to make IRC my boss, and let's get all these admins together and build a tool we can share, right?So, that was a really good experience, and it's just basically gluing all that stuff together to fully automate an install over a network so that when a system comes on, you can either pick it out from a menu; or maybe you've already got the MAC address and you can just say, “When you see this MAC address, go install this operating system.” And there's a kickstart file, or a preseed in the case of Debian, that says, “When you're booting up through the installer, basically, here's just the answers and go do these things.” And that install processes a lot slower than what we're used to, but for a bare-metal machine, that's a pretty good way to do it.Corey: Yeah, it got to a point where you could walk through and just turn on all the servers in a rack and go out to lunch, come back, they would all be configured and ready to go. And it sounds relatively basic the way we're talking about it now, but there were some gnarly cases. Like, “When I've rebooted the database server, why did it wipe itself and reprovision?” And it's, “Oh, dear.” And you have to make sure that things are—that there's a safety built into these things.And you also don't want to have to wind up plugging in a keyboard and monitor to all of these individual machines one-by-one to hit yes and acknowledge the thing. And it was a colossal pain in the ass. That's one of the things that cloud has freed us from.Michael: Yeah, definitely. And one of the nice things about the whole cloud environment is like, if you want to experiment with those ideas, like, I want to set up some DHCP or DNS, I don't have to have this massive lab and all the electricity and costs. But like, if I want to play with a load balancer, I can just get one. That kind of gives the experience of playing with all these data center technologies to everybody, which is pretty cool.Corey: On some level, you can almost view the history of all these things as speeding things up. With a well-tuned Cobbler install, it still took multiple minutes, in some cases, tens of minutes to go from machine you're powering on to getting it provisioned and ready to go. Virtual machines dropped that down to minutes. And cloud, of course, accelerated that a bit. But then you wind up with things like Docker and it gets down to less than a second. It's the meantime to dopamine.But in between the world of containers and bare-metal, there was another project—again, the one you're best known for—Ansible. Tell me about that because I have opinions on this whole space.Michael: [laugh]. Yeah. So, how Ansible got started—well, I guess configuration management is pretty old, so the people writing their own scripts, CFEngine came out, Puppet was a much better CFEngine. I was working at a company and I kind of wanted another open-source project because I enjoyed the Cobbler experience. So, I started Ansible on the side, kind of based on some frustrations around Puppet but also the desire to unify Capistrano kind of logic, which was like, “How do I push out my apps onto these servers that are already running,” with Puppet-style logic was like, “Is this computer's firewall configured directly? And is the time set correctly?”And you can obviously use that to install apps, but there's some places where that blurred together where a lot of people are using two different tools. And there's some prior art that I worked on called Funk, which I wrote with Seth Vidal and Adrian Likins at Red Hat, which was, like, 50% of the Ansible idea, and we just never built the config management layer on top. So, the idea was make something really, really simple that just uses SSH, which was controversial at the time because people thought it, like, wouldn't scale, because I was having trouble with setting up Puppet security because, like, it had DNS or timing issues or whatever.Corey: Yeah. Let's dive in a bit to what config management is first because it turns out that not everyone was living in the trenches in quite the same way that we were. I was a traveling trainer for Puppet for a summer once, and the best descriptor I found to explain it to people who are not in this space was, “All right, let's say that you go and you buy a new computer. What do you do? Well, you're going to install the applications you'd like to use, you're going to set up your own user account, you're going to set your password correctly, you're going to set up preferences, copy some files over so you have the stuff you care about. Great. Now, imagine you need to do that to a thousand computers and they all need to be the same. How do you do that?” Well, that is the world of configuration management.And there was sort of a bifurcation there, where there was the idea of, first, we're going to have configuration management that just describes what the system should look like, and that's going to run on a schedule or whatnot, and then you're going to have the other side of it, which is the idea of remote execution, of I want to run an arbitrary command on this server, or this set of servers, or all the servers, depending upon what it is. And depending on where you started on the side of that world, you wound up wanting things from the other side of that space. With Puppet, for example, is very oriented configuration management and the question became, well, can you use this for remote execution with arbitrary commands? And they wound up doing some work with Mcollective, which was a very complicated and expensive way to say, “No, not really.” There was a need for things that needed to hang out in that space.The two that really stuck out from that era were Ansible, which had its wild runaway success, and the one that I was smacking around for a bit, SaltStack, which never saw anywhere approaching that level of popularity.Michael: Yeah, sure. I mean, I think that you hit it pretty much exactly right. And it's hard to say what makes certain things take off, but I think, like, the just SSH approach was interesting because, well for one, everybody's running it. But there was this belief that this would not scale. And I tried to optimize the heck out of that because I liked performance, but it turns out that wasn't really a business problem because if you can imagine you just wrote this little bit of automation, and you're going to run it against your entire infrastructure and you've got 30,000 machines, do you want that to—if you were to, like, run an update command on 30,000 machines at once, you're going to DDoS something. Definitely, right?Corey: Yeah. Suddenly you have 30,000 machines all talk to the same things at the same times. And you want to do them in batches or smear it across.Michael: Right, so because that was there, like, you just add batch support in Ansible and things are fine, right? People want to target little small groups of things. So, like, that whole story wasn't true, and I think it was just a matter of testing this belief that everybody thought that we needed to have this whole network of things. And honestly, Salt's idea of using a message bus is great, but we took a little bit different approach with YAML because we have YAML variables in it, but they had something that compiled down to YAML. And I think those are some differences in the dialect and some things other people preferred, but—Corey: And they use Jinja, at one point to wind up making it effectively Turing complete; you could wind up having this ridicu—like, loop flow control and loops and the rest. And it was an interesting exposure to things, but yikes, at some l—at the same time.Michael: If you use all the language features in anything you can make something complicated, and too complicated. And I was like, I wanted automation to look like grocery lists. And when I started out, I said, “Hey, if anybody is doing this all day, for a day job, I will have failed.” And it clearly shows you that I have because there are people that are doing that all day. And the goal was, let me concentrate on dev and ops and my other things and keep this really, really simple.And some people just, like, get really, really into that automation technology, which is—in my opinion—why some of the earlier stuff was really popular because sysadmin were bored, so they see something new and it's kind of like a Java developer finding Perl for the first time. They're like, “I'm going to use all these things.” And they have all their little widgets, and it gets, like, really complicated.Corey: The thing that I always found interesting and terrifying at the same time about Ansible was the fact that you did ride on top of SSH, which is great because every company already had a way of controlling access by SSH to IT systems; everyone uses it, so it has an awful lot of eyes on the security protocol on the rest. The thing that I found terrifying in the early days was that more or less every ops person would wind up checking this out onto their laptop or whatnot, so whenever they wanted to run something, they would just run it from their laptop over a VPN or whatnot from wherever they happen to be, and you wind up with a dueling banjos type of circumstance where people were often not doing it from a centralized place. And in time, best practices emerged where, okay, that is going to be the command and control server where that runs at, and you log into it. And then you start guarding that with CI/CD flows and the rest. And like anything else, it wound up building some operational approaches to it.Michael: Yeah. Like, I kind of think that created a problem that allowed us to sell a product, right, which was good. If you knew what you were doing, you could use Jenkins completely and you'd be fine, right, if you had some level of discipline and access control, and you wanted to wire that up. And if you think about cloud, this whole, like, shadow IT idea of, “I just want to do this thing, therefore I'm going to get an Amazon account,” it's kind of the same thing. It's like, “I want to use this config management, but it's not approved. Who can stop me?” Right?And that kind of probably got us in the door in few accounts that way. But yeah, it did definitely create the problem where multiple people could be running things at the same time. So yeah, I mean, that's true.Corey: And the idea of, “Hey, maybe I should be controlling these things in Git,” or some other form of version control was sort of one of those evolutionary ideas that, oh, we could treat this like code. And the early days of DevOps, that was a controversial thing. These days, you say you're not doing it and people look at you very strangely. And things were going reasonably well in that direction for a while. Then this whole Docker thing showed up, where, well, what if instead of having these long-lived servers where you have to install updates and run patches and maintain a whole user list on them, instead you had this immutable infrastructure that every time there was a change, you would just go ahead and deploy a brand new set of servers?And you could do this in the olden days with virtual machines and whatnot; it just took a long time to push things out, so do I really want to roll the entire fleet for a two-line config change? Probably not, so we're going to batch it up, or maybe do this hybrid model. With Docker, it takes less than a second to wind up provisioning the—switching over to the new container series and you're done; you can keep going with that. That really solved a lot of these problems.But there were companies that, like, the entire configuration management space, who suddenly found themselves in a really weird position. Some of them tried to fight the tide forever and say, “Oh, this is terrible because it means we don't have a business model anymore.” But you can only fight the future for so long. And I think today, we'd be hard-pressed to say that Docker hasn't won, on some level.Michael: I mean, I think it has, like, the technology has won. But I guess the interesting thing is, config management now seems to be trying to pivot towards networking where I think the tool hasn't ever been designed for networking, so it's kind of a round peg, square hole. But it's all people have that unless they're buying something. Or, like, deploying the undercloud because, like, people are still running essentially clouds on top of clouds to get their Kubernetes deployments going and those are monstrous. Or maybe to deploy a data layer; like, I know Kafka has gotten off of ZooKeeper, but the Kafka-ZooKeeper thing—and I don't remember ZooKeeper [unintelligible 00:14:37] require [unintelligible 00:14:38] or not, but managing those sort of long, persistent implications, it still has a little bit of a place where it exists.But I mean, I think the whole immutable systems idea is theoretically completely great. I never was really happy with the whole Docker development workflow, and I think it does create a problem where people don't know what they're deploying and you kind of encourage that to where they could be deploying different versions of libraries, or—and that's kind of just a problem of the whole microservices thing in general where, “Did somebody change this?” And then I was working very briefly at one company where we essentially built a whole dashboard to detect service versions and what version of the base image everybody was on, and all these other things, and it can get out of hand, too. So, it's kind of like trading some problems for other problems, I think to me. But in general, containerization is good. I just wished the management glue around it was easy, right?Corey: I wound up giving a talk at a conference a while back, 2015 or so, called, “Heresy in the Church of Docker,” and it was a throwaway five-minute lightning talk, and someone approached me afterwards with, “Hey, can you give the full version of that at ContainerCon?” “There's a full version? Yes. Yes, I can.” And it talked about a number of problems with the management layer and the rest.Now, Kubernetes absolutely solves virtually every problem that I identified with it, but when you look at the other side of it, getting Kubernetes rolled out is effectively you get to cosplay being a cloud provider yourself. It is incredibly complicated, and of course, we're right back to managing it all with YAML.Michael: Right. And I think that's an interesting point, too, is I don't know who's exactly responsible for, like, the YAML explosion. And I like it as a data format; it's really good for humans. Cobbler originally used it more of an internal storage, which I think was a mistake because, like, even—I was trying to avoid setting up a database at the time, so—because I knew if I had to require setting up a database in 2007 or 2008, I'd get way less users, so it used flat files.A lot of the YAML dialects people are developing now are very, very nested and they requires, like, loading a webpage, for the Docks, like, all the time and reading what's valid here, what's valid there. I think people learn the wrong lesson from Ansible's YAML usage, right? It was supposed to be, like, YAML's good for things that are grocery lists. And there's a lot of places where I didn't do a good job. But when you see methods taking 15 parameters and you have to constantly have the reference up, maybe that's a sign that you should do something else.Corey: At least you saved us, on some level, from having to do this all in XML. But still, there are wrong ways and more wrong ways to do it. I don't think anyone could ever agree on the right way to approach these things.Michael: Yeah. I mean, and YAML, at the time was a good answer because I knew I didn't want to write and maintain a parser as, like, a guy that was running a project. We had a lot of awesome contributors, but if I had to also maintain a DSL, not only does that mean that I have to write the code for this thing—which I, you know, observed slowing down some other projects—but also that I'd have to explain it to people. Looking kind of like Bash was not a bad thing. Not having to know and learn something, so you can kind of feel really effective in about 15 minutes or something like that.Corey: One of the things that I find really interesting about you personally is that you were starting off in a bare-metal world; Ansible was sort of wherever you wanted to run it. Great, as long as there are systems that can receive these things, we're great. And now the world has changed, and for better or worse, configuration management slash remote execution is not the problem it once was and it is not a best practice way of solving a lot of those problems either. But you aren't spending your time basically remembering the glory years. You're actively moving forward doing some fairly interesting stuff. How would you describe what you're into these days?Michael: I tried to create a few projects to, like, kind of build other systems management things for the same audience for a while. I was building a build server and a new—trying to do some next-gen config stuff. And I saw people weren't interested. But I like having conversations with people, right, and I think one of the lessons from Ansible was how to explain highly technical things to technical audiences and cut out a lot of the marketing goo and all that; how to get people excited about an idea and make a community be really authentic. So, I've been writing about that for really, it's—rebooted blog is only a couple of weeks old. But also kind of trying to do some—helping out companies with some, like, basic marketing kind of stuff, right?There's just this pattern that everybody has where every website starts with this little basic slogan and two buttons and then there's a bunch of adjectives, but it doesn't say anything. So, how can you have really good documentation, and how can you explain an idea? Because, like, really, the reason you're in it is not just to sell stuff, but it's to help people and to see them get excited about your ideas. And there's just, like, we're not doing a good job in this, like, world where there's thousands upon thousands of applications, all competing at once to, like—how do you rise above that?Corey: And that's always the hard part is at some point, this does become your identity and you become known for a thing. And when you start branching out from that thing, you bring the expertise from that area that you were in, but you start applying it to new things. I feel like so many companies get focused—and people get focused—on assuming that their audience is just like them, where they're coming in with the exact same biases, the exact same experiences. And given that basically no one was as deep in the weeds as you were when it came to configuration management, that meant that you were spending time in that side of the world, not in other pursuits which aligned in some ways more directly with people developing other things. So, I suspect this might be one of the weird things we have in common when we show up and see something new.And a company is really excited. It's like, it's basically a few people talking [unintelligible 00:20:12] that both founders are technical. And they're super excited about something they can't quite articulate. And it's this, “Slow down. Tell me exactly what it is your product does.” And that's a hard thing to do because my default response was always the if I don't understand that is clearly the way in which I am deficient somehow. But marketing is really about clear communication and there's not that much of it in our space, at least not for early-stage companies.Michael: Yeah, I don't know why that is. I mean, I think there's this belief in that there's, like, this buyer audience where there's some vice president that's going to buy your stuff if you drop the right buzzwords. And 15 years ago, like, you had to say ‘synergy,' and now you say ‘time to value' or ‘total cost of ownership' or something. And I don't think that's true. I mean, I think people use products that they like and that they need to be shown them to try them out.So like, why can't your webpage have a diagram and a screenshot instead of this, like, picture of a couple of people drinking coffee around a computer, right? It's basic stuff. But I agree with you, I kind of feel dumb when I'm looking at all these tech products that I should be excited about, and, like, the way that we get there, as we ask questions. And the way that I've actually figured out what some of these things do is usually having to ask questions from someone who uses them that I randomly find on my diminishing circle of friends, right? And that's kind of busted.So, Ansible definitely had a lot of privilege in the way that it was launched in the sense that I launched it off Cobbler list and Cobbler list started off of [ET Management Tools 00:21:34] which was a company list. But people can do things like meetup groups really easily, they can give talks, they can get their blogs reblogged, and, you know, hope for some Hacker News or Reddit juice or whatever. But in order to get that to happen, you have to be able to talk to engineers that really want to know what you're doing, and they should be excited about it. So, learn to talk to them.Corey: You have to speak their language but without going so deep in the weeds that the only people that understand it are the folks who are never going to use your product because they want to build it themselves. It's a delicate balance to strike.Michael: And it's a difficult thing to do, too, when you know about it. So, when I was, like, developing all the Ansible docs, I've told people many times—and I hope it's true—that I, like, spent, like, 40% of my time just on the website and the docs, and whenever I heard somebody complain, I tried to fix it. But the idea was like, you can lose somebody really fast, but you kind of have to forget what you know about the product. So, the worst person to sometimes look at that as the person that built it. So, you have to forget what you know, and try to see, like, what questions they're asking, what do they need to find out? How do they want to learn something?And for me, I want to see a lot of pictures. A lot of people write a bunch of giant walls of text, or worse for me is when there's just these little pithy expressions and I don't know what they mean, right? And everybody's, like, kind of doing that these days.Corey: This episode is sponsored in part by our friends at ChaosSearch. You could run Elasticsearch or Elastic Cloud—or OpenSearch as they're calling it now—or a self-hosted ELK stack. But why? ChaosSearch gives you the same API you've come to know and tolerate, along with unlimited data retention and no data movement. Just throw your data into S3 and proceed from there as you would expect. This is great for IT operations folks, for app performance monitoring, cybersecurity. If you're using Elasticsearch, consider not running Elasticsearch. They're also available now in the AWS marketplace if you'd prefer not to go direct and have half of whatever you pay them count towards your EDB commitment. Discover what companies like Equifax, Armor Security, and Blackboard already have. To learn more, visit chaossearch.io and tell them I sent you just so you can see them facepalm, yet again.48]Corey: One thing that I've really found myself enjoying recently has been your substack-based newsletter, Speaking Techis what you call it. And I didn't quite know what to expect when I signed up for it, but it's been a few weeks now, and you are more or less hitting across the board on a bunch of different things, ranging from engineering design patterns, to a teardown of random company's entire website from a marketing and messaging perspective—which I just adore personally; like that is very aligned with how I see the world—Michael: There's more of that coming.Corey: Yeah, [unintelligible 00:23:17] a bunch of other stuff. Let's talk about, for example, the idea of those teardowns. I always found that I have to be somewhat careful in how I talk about it when I'm doing a tweet thread or something like that because you are talking about people's work, let's be clear here, and I tend to be a lot kinder to small, early-stage companies than I am to, you know, $1.6 trillion companies who really should have solved for this by now, on some level. But so much of it misses the mark of great, here's the way that I think about these things. Here's the way that I don't understand what the hell you're telling me.An easy example of this for me, at least I'm curious to get your thoughts on it, I tend to almost always just skim what they're saying, great. Let's look at the pricing page because I find that speaks to people in a way that very often companies forget that they're speaking to customers.Michael: Yeah, for sure. I always tried to find the product page lately, and then, like, the product page now is, like, a regurgitation of the homepage. But it's what you said earlier. I think I try to stay nice to everybody, but it's good to show people how to understand things by counterexample, to some extent, right? Like, oh, I've got some stuff coming out—I don't know when this is actually going to get published—but next week, where I was like just taking random snippets of home pages, and like, “What's everybody doing with the header these days?”And there's just, like, ridiculous amounts of copying going on. But it's not just for, like, people's companies because everybody listening here isn't going to have a company. If you have a project and you wanted to get it noticed, right, I think, like, in the early days, the projects that I paid attention to and got excited about were often the ones that spend time on their website and their messaging and their experience. So, everybody kind of understands you have to write a good readme now but some of, like, the early Ruby crowd, for instance, did awesome, awesome web pages. They know how to pick out fonts, and I still don't know how to pick out fonts. But—Corey: I ask someone good at those things. That's how I pick ‘em.Michael: Yeah, yeah. That's not my job; get somebody that's good at that. But all that matters, right? So, if you do invest a little bit in not promoting yourself, not promoting your company, but trying to help people and communicate to them, you can build that audience around your thing and it makes it a lot more interesting.Corey: There's so many great tools out there that I find on GitHub that other people have to either point me to or I find it when I'm looking at it from a code-first perspective, just trying to find a particular example of the library being used, where they do such a terrible job of describing the problem that they solve, and it doesn't take much; it takes a paragraph or two at most. Or the idea that, “Oh, yeah, here's a way to do this thing. Just go ahead and get your credential file somewhere else.” Great. Could you maybe link to an example of how to do that?It's the basic stuff; assume that someone who isn't you might possibly want to use this. And I'm not even slightly suggesting that you wind up talking your way through how to do all of that. Just link to somewhere that has a good write-up of it and call it good. Just don't get in the way of people's first-time user experiences.Michael: Yeah, for sure. And—Corey: For some reason, that's a radical thought.Michael: Yeah, I think one of the things the industry has—well, not the industry; it's not their problem to solve, but, like, we don't really have a way for people to find what's cool and interesting anymore. So, various people have their own little lists on GitHub or whatever, but there's just so many people posting on the one or two forums people read and it goes by in a day. So, it's really, really hard to get attention. Even your own circle of followers isn't really logging into Twitter or anything, or LinkedIn. Or there's all the congratulations for your five years of Acme Corp kind of posts, and it's really, really hard to get attention.And I feel for everybody, so like, if somebody like GitHub or Microsoft is listening, and you wanted to build, like, a dashboard of here's the cool 15 projects for the week, kind of thing where everybody would see it, and start spotlight some of these really cool new things, that would be awesome, right?Corey: Whenever you see those roundups, that was things like Kubernetes and Docker. And great, I don't think those projects need the help in the same way.Michael: No, no, they don't. It's like maybe somebody's cool data thing, or a cool visualization, or the other thing that's—it's completely random, but I used to write fun graphics programs for fun or games and libraries. And I don't see that anymore, right? Maybe if you find it, you can look for it, but the things that get people excited about programming. Maybe they have no commercial value at all, but the way that people discover stuff is getting so consolidated is about Docker and Kubernetes. And everyone's talking about these three things, and if you're not Google or you're not Facebook, it's really—or Amazon, obviously—it's hard to get attention.Corey: Open-source on some level has changed from a community perspective. And part of it is because once upon a time, you could start with the very low-level stuff and build something, get it up and working. And that's where things like [Cobbler 00:27:44] and Ansible came out of. Now it's, “Click the button and use the thing everyone else is using. And if you're not doing that, what are you doing over there?”So, the idea of getting started tinkering with computers are built on top of so many frameworks and other things. And that's always been the case, but now it's much more apparent in some ways. “Okay, I'm going to go ahead and build out my first HTML file and serve it out using something in Node.” “Great, what is those NPM stuff that's scrolling past?” It's like, “The devil. That is the devil's own language you are seeing scroll past. And you don't need to worry about that; just pretend it's not there.”But back when I was learning all this stuff, we're paying attention to things scrolling past, like, you know, compilation messages and the Linux boot story as it wound up scrolling past. Terrible story; the protagonist was unreliable, but all right. And you start learning how these things work when you start scratching at the things that you're just sort of hand-waving and glossing over. These days, it feels like every time I use a modern project, that's everything.Michael: I mean, it is. And like what, React has, like, 2000 dependencies, right? So, how do you ever feel like you understand it? Or when recruiters are asking for ten years at Amazon. And then—or we find a library that it can only explain itself by being like this other library and requiring these other five.And you read one of those, and it becomes, like, this… tree of knowledge that you have no way of possibly understanding. So, we've just built these stacks upon stacks upon stacks of things. And I tend to think I kind of believe in minimalism. And like, wouldn't it be cool if we just burned this all and start—you know, we burn the forest and let something new regrow. But we tend to not do that. We just—now running a cloud on top of a cloud, and our JavaScript is thousands of miles high.Corey: I really wish that there were better paths for getting started. Like, I used to think that the right way to wind up learning how all this stuff work is to do what I did: Start off as, you know, the grumpy sysadmin type, and then—or help desk—and then work your way up and the rest. Those jobs aren't there anymore, and it doesn't leave people in a productive environment. “Oh, you want to build a computer game. Great. For an iPhone? Terrific.” Where do you go to get started on that? It's a hard thing to do.And people don't care at that scale, nor should they necessarily, on how to run your own servers. Back in the day when you wanted to have a blog on the internet, you were either reduced to using LiveJournal or MySpace, or you were running your own web server and had to learn how to make sure that it didn't become an attack platform. There was a learning curve that was fairly steep. Now, there are so many different paths to go down, you don't really need to know how any of these things even work.Michael: Yeah, I think, like, one of the—I don't know whether DevOps means anything as a topic or not, but one of the original pieces around that movement was systems administrators learning to code things and really starting to enjoy it, whether that was Python or Ruby, and so on. And now it feels like we're gluing all the things together, but that's happening in App Dev as well, right? The number of people that can build a really, really good library from the ground up, like, something that has C bindings, that's a really, really small crowd. And most of it, what we're doing is gluing together other people's libraries and compensating for the flaws and bugs in them, and duct tape and error handling or whatever. And it feels like programming has changed a lot because of this—and it's good if you want to get an idea up quickly, no doubt. But it's a different experience.Corey: The problem I always ran into was the similar problems I had with doing Debian packaging. It was always the, oh, great, there's going to be four or five different guides on how to do it—same story with RPM—and they're all going to be assuming different things, and you can crossover between them without realizing it. And then you just do something monstrous that kind of works until an actual Debian developer shoves you aside like you were a hazard to everyone around you. Let me do it for you. And there we go.It's basically, get people to do work for you by being really bad at it. And I don't love that pattern, but I'm still reminded of that because there are so many different ways to achieve any outcome that, okay, I want to run a ridiculous Hotdog or Not Hotdog style website out there. Great. I can upload things. Well, Docker or serverless? What provider do I want to put it on? And oh, by the way, a lot of those decisions very early on are one-way doors that you don't realize you're crossing through, as well as not knowing what the nuances of all of those things are. And that's dangerous.Michael: I think people are also learning the vendor as well, right? Some people get really engrossed in whether it's Amazon, or Google, or HashiCorp, or somebody's API, and you spend so much of your brain cells just learning how these people's systems work versus, like, general programming practices or whatever.Corey: I make it a point to build something on other cloud providers that aren't Amazon every now and then, just because I don't want to wind up effectively embracing a monoculture.Michael: Yeah, for sure. I mean, I think that's kind of the trend I see with people looking just at the Kubernetes stuff, or whatever, it's that I don't think it necessarily existed in web dev; there seems to be a lot of—still a lot of creativity and different frameworks there, but people are kind of… what's popular? What gets me my next job, and that kind of thing. Whereas before it was… I wasn't necessarily a sysadmin; I kind of stumbled into building admin tools. I kind of made hammers not houses or whatever, but basically, everybody was kind of building their own tools and deciding what they wanted. Now, like, people that are wanting to make money or deciding what people want for them. And it's kind of not always the simplest, easiest thing.Corey: So, many open-source projects now are—for example, one that I was dealing with recently was the AWS CLI. Great, like, I'm thrilled to throw in issues and challenges here, but I'm not going to spend significant time writing code against it because, one, it's basically impossible to get these things accepted when all the maintainers work at Amazon, and two, is it really an open-source project in the way that you and I think about community and the rest, but it's basically sole purpose is to funnel money to Amazon faster. Like, that isn't really a community ethos I feel comfortable getting behind to be perfectly honest. They're a big company; they can afford to pay people to build these things out, full time.Michael: Yeah. And GitHub, I mean, we all mostly, I think, appreciate the fact that we can host the Git repo and it's performant and everything, and we don't have blazing unicorns quite as often or whatever they used to have, but it kind of changed the whole open-source culture because we used to talk about things on mailing lists, like, what should this be, and there was like an upfront conversation, or it might happen on IRC. And now people are used to just saying, “I've got a problem. Fix it for me.” Or they're throwing code over the wall and it might not be the code or feature that you wanted because they're not really part of your thing.So before, people would get really engrossed with, like, just a couple of projects, and if they were working on them as kind of like a collective of people working against different organizations, we'd talk about things, and they kind of know what was going on. And now it's very easy to get a patch that you don't want and you're, like, “Oh, can you change all of these things?” And then somebody's, like, now they're offended because now they have to do all this extra work, whereas that conversation didn't happen. And GitHub could absolutely remodel themselves to encourage those kinds of conversations and communities, but part of the death of open-source and the fact that now it's, “Give me free code,” is because of that kind of absence of the—because we're looking at that is, like, the front of a community versus, like, a conversation.Corey: I really want to appreciate your taking so much time out of your day to basically reminisce about some of these things. But on a forward-looking basis, if people want to learn more about how you see things, where's the best place to find you?Michael: Yeah. So, if you're interested in my blog, it's pretty random, but it's michaeldehaan.substack.com. I run a small emerging consultancy thing off of michaeldehaan.net. And that's basically it. My Twitter is laserllama if you want to follow that. Yeah, thank you very much for having me. Great conversation. Definitely making all this technology feel old and busted, but maybe there's still some merit in going back—Corey: Old and busted because it wasn't built this year? Great—Michael: Yes.Corey: —yes, its legacy, which is a condescending engineering term for ‘it makes money.' Yeah, there's an entire universe of stuff out there. There are companies that are still toying with virtualization: “Is this something we get on board with?” There's nothing inherently wrong with that. I find that judging what a bunch of startups are doing or ‘company started today' is a poor frame of reference to look at what you should do with your 200-year-old insurance company.Michael: Yeah, like, [unintelligible 00:35:53] software engineering is just ridiculously new. Like, if you compare it to, like, bridge-building, or even electrical engineering, right? The industry doesn't know what it's doing and it's kind of stumbling around trying to escape local maxima and things like that.Corey: I will, of course, put links to where to find you into the [show notes 00:36:09]. Thanks again for being so generous with your time. It's appreciated.Michael: Yeah, thank you very much.Corey: Michael DeHaan, founder of Cobbler, Ansible, and oh, so much more than that. I'm Cloud Economist Corey Quinn, and this is Screaming in the Cloud. If you've enjoyed this podcast, please leave a five-star review on your podcast platform of choice—and/or smash the like and subscribe buttons on the YouTubes—whereas if you've hated this podcast, please leave a five-star review on your podcast platform of choice, smash the buttons as mentioned, and leave a loud, angry comment explaining what you hated about it that I will then summarily reject because it wasn't properly formatted YAML.Corey: If your AWS bill keeps rising and your blood pressure is doing the same, then you need The Duckbill Group. We help companies fix their AWS bill by making it smaller and less horrifying. The Duckbill Group works for you, not AWS. We tailor recommendations to your business and we get to the point. Visit duckbillgroup.com to get started.Announcer: This has been a HumblePod production. Stay humble.

DevOps, CloudOps, DevSecOps, etc…what's in a name? All of these operational titles play a critical role in managing and securing your cloud. In this episode, Jim and Jeff Bozic, Principal Architect at Insight, untangle this alphabet soup and help us understand who the key operational roles, what they do, and why operating the cloud is a true team effort.

Co-founder and CTO at CAST AI. Formerly Vice President of Security Products OCI at Oracle, Leon's professional experience spans across tech companies such as IBM, Truition, and HostedPCI. He founded and served as the CTO of Zenedge, an enterprise security company protecting large enterprises with a cloud WAF. Leon has 20+ years of experience in product management, software design, and development, all the way through to production deployment. He is an authority on cloud computing, web application security and Payment Card Industry Data Security Standard (PCI DSS), e-commerce, and web application architecture.Michael and Leon cover so many topics quickly. The current security landscape and what companies can do to protect themselves. They address cloud and security of that technology.  Leon and Michael talk about Cast AI and how it can cut your cloud hosting bill. How you can easily see the savings in 5 minutes!https://www.cast.aiThe book Leon mentions is here: https://www.amazon.com/Sandworm-Cyberwar-Kremlins-Dangerous-Hackers/dp/0385544405The social hacking video Leon references is here: https://www.youtube.com/watch?v=lc7scxvKQOo

Strategic alignment within an organization is known as lining up a business' strategy with culture, but have you ever thought about how it applies to you? Christina Heath, PMP is in the business of helping project managers find that alignment within their professional and personal lives because why can't these be aligned, too? After earning her stripes as a project manager, spearheading projects in everything from AppDev to digital marketing and communications, Christina made the difficult decision to move out of corporate America and into her own business, doing what she loves - helping people find their purpose. If you're ready to find your balance, Christina offers consultation on how to approach work and life holistically, building authority and being a happier, healthier, and more strategic leader through a 12-week program. After completion of the program, you can expect to gain clarity around your unique PM style and how to use it to further your company and personal goals. Here's a preview of what we cover in this week's episode of The Everyday PM Podcast: - What does it mean to be a strategic alignment coach? - What's behind the name Mango Flow Consulting? - If people want to level up with you, how do they get started? Enjoyed this new-themed episode with Christina? Want to learn more about how she is helping project managers approach work and life holistically? Leave your thoughts and feedback in the comments section below! Make sure to follow Christina and me on LinkedIn for more. Subscribe: youtube.com/anncampea Listen: https://anchor.fm/theeverydaypm Learn more about MangoFlow Consulting: www.mangoflowconsulting.com *** Follow Our Hosts on LinkedIn: Ann Campea, MSPM, MPH, PMP - https://www.linkedin.com/in/anncampea/ Christina Heath, PMP - https://www.linkedin.com/in/christina-heath/ --- Support this podcast: https://anchor.fm/theeverydaypm/support

This is the 3rd episode of Season 2 which was recorded as part of a livestream on Twitch!Topics for today:- Log4Shell- Dell Concept Luna- Microsoft collaborates with iFixit- Simula One- Another comment on App DevelopmentThe full show notes can be found here: https://bnonet.com/podcast/bnotechcast-episode-8-intriguing-times/

Developers need love too! Advocating for developers isn't new, but in a world where they're constantly under pressure to keep pace with the demands of digital transformation, expecting developers to care about security can create friction in many DevSecOps environments.Studies suggest that security teams believe developers don't take the security of applications seriously and will sacrifice security in favor of innovation. Shifting this perception requires strong collaboration combined with automating and integrating well-established security practices into developers' existing workflows.Join us to discuss:Being a developer advocate.Building a culture that reduces friction in DevSecOps.Approaches for integrating security into developers daily activities.

Welche Voraussetzungen erfüllt sein müssen, um eine App in den App Stores von Apple und Google veröffentlichen zu können, haben wir euch in den Folgen 56 und 82 erzählt. Deshalb sprechen wir nun über geschmeidige Automatisierungen für diesen Prozess. Außerdem freuen wir uns schon jetzt auf eure Issues auf GitHub, denn wir haben eine Open Source Software entwickelt, über die wir am Ende der Folge sprechen!Für eine CI/CD Pipeline gibt es viele Definitionen und wir wollen euch einen Einblick geben, was unser aktueller Stand ist. Im Teil der Continuous Integration geht es eher darum, Entwickler:innen Aufwände abzunehmen. Beispielsweise werden geschriebene Tests automatisch ausgeführt, bevor ein Pull Request akzeptiert werden kann. CD kann für Continuous Delivery oder Continuous Deployment stehen und sorgt unter Anderem dafür, dass eine lauffähige Version der App bei allen Tester:innen ankommt und viele Schritte des Veröffentlichungsprozesses automatisiert sind. Wir reden über die von uns getesteten und eingesetzten Tools, wie zum Beispiel buddybuild, BitRise, GitHub Actions, CodeMagic und CircleCI.Um für unsere Flutter App den letzten Part der Veröffentlichung möglichst angenehm zu gestalten, haben wir Fasttrack entwickelt und Open Source für euch zur Verfügung gestellt. Mit dem Tool braucht ihr euch nicht mehr in den Oberflächen der Stores anmelden und könnt die (gestaffelte) Veröffentlichung eurer Apps einfach über euer CLI erledigen. Wir freuen uns sehr auf euer Feedback zu dem Tool – also, ab zu GitHub und Issues erstellen!Schreibt uns! Schickt uns eure Themenwünsche und euer Feedback. podcast@programmier.bar Folgt uns!Bleibt auf dem Laufenden über zukünftige Folgen und virtuelle Meetups und beteiligt euch an Community-Diskussionen. Twitter Instagram Facebook Meetup YouTube Musik: Hanimo 

Kevin McNulty, Director of Professional Services West at SKUID and Deena Tearney, CEO at Pacific Point talk on the key components of building apps. 

In der sechsten Folge unseres CTO-Specials erfahren wir von der Geschichte von Thomas Holl und hören, wie es zur Gründung der Sprachlern-App Babbel kam. In Thomas' Leben spielte Technik schon früh eine entscheidende Rolle. Bereits mit 14 entdeckte er seine Leidenschaft für Programmierung und elektronische Musik. Deshalb entwarf er erste Software-Synthesizer und ein MP3-DJ-Tool, dessen Grundgerüst heute noch unter dem Namen “Traktor” von Native Instruments bekannt ist. Im Jahr 2007 gründete er gemeinsam mit drei Geschäftspartnern Babbel, das aus dem Bedürfnis entstand, mit einem digitalen Vokabeltrainer eine neue Sprache zu lernen. Professionelle Sprachdidaktik war dabei von Beginn an genauso wichtig wie die Internationalisierung des Produkts. Heute ist Babbel eine der bekanntesten Apps zum Lernen von Fremdsprachen. Thomas hat also vom Software-Verkauf über Disketten, die per Briefumschlag verschickt und bezahlt werden, bis zum App-basierten Tech-Unternehmen viele Entwicklungen erlebt, die er in dieser Folge mit uns teilt. Das Babbel Tech Radar, über das wir sprechen, ist eine Auflistung der Technologien, die bei Babbel bereits zum Einsatz kamen und dient als Grundlage für Entwicklungsteams im Unternehmen.  Auf Twitter könnt ihr mit Thomas unter dem Handle @tholl in Kontakt treten. Schreibt uns! Schickt uns eure Themenwünsche und euer Feedback. podcast@programmier.bar Folgt uns! Bleibt auf dem Laufenden über zukünftige Folgen und virtuelle Meetups und beteiligt euch an Community-Diskussionen. Twitter Instagram Facebook Meetup YouTube Musik: Hanimo

Alex Hidalgo (@ahidalgosre, Director of SRE at @nobl9inc) talks about the evolution of SRE teams, implementing SLOs, and enabling AppDev and Ops teams to better manage reliability.SHOW: 502SHOW SPONSOR LINKS:Get started with the JumpCloud Directory Platform today  Visit the JumpCloud Homepage.  Email press@jumpcloud.com for a FREE JumpCloud T-Shirt.CBT Nuggets: Expert IT Training for individuals and teamsSign up for a CBT Nuggets Free Learner account and enter to win a 6-month Premium subscription.Qumulo Homepage: Manage File Data at Scale, AnywhereTest Drive Qumulo: Try Qumulo for free, no downloads or setup requiredCLOUD NEWS OF THE WEEK - http://bit.ly/cloudcast-cnotwCHECK OUT OUR NEW PODCAST - "CLOUDCAST BASICS"SHOW NOTES:Nobl9 HomepageThe SLO Book - Implementing Service Level ObjectivesTopic 1 - Welcome to the show. Congratulations on the launch of Nobl9. Before we get into that, let’s talk about your background and what got you focused on SREs and SLOs.Topic 2 - We’ve spoken about the role of SRE quite a bit the last few years, but not as much about SLOs - and how to achieve them. Paint us some broad brush strokes about the world of SLOs today, and how they are different from SLAs or other commonly used measurements and metrics. Topic 3 - So how do we start taking the SLO concepts and start making them actionable?Topic 4 - How does a move to a SLO-centric model change the AppDev or the Ops teams?   Topic 5 - Is there a “low-hanging fruit” in an adoption of SLO-centric capabilities, or does it take quite a bit of top-down and bottom-up change? Topic 6 - What’s a good way to get started with the Nobl9 platform?FEEDBACK?Email: show at thecloudcast dot netTwitter: @thecloudcastnet

Welcome to the How to Build an App podcast. This show is produced by Strides Development, a full-service app development agency. We specialize in taking your ideas and turning them into a finished app in only a few months. If you have an app you’re building, we would love to talk to you. You can schedule your free strategy call by clicking here.Make sure you’re following Strides on Instagram and Linkedin. Today, we’re talking with Brian Clay. Brian is an expert in design, User Interface (UI), and User Experience (UX).In this episode, we talk about what makes an app experience great, what kills an app experience, and the “table stakes” (as he calls them)… Think of table stakes as the non-negotiables you need in your app build. Brian also shares some great tips for building something “magic” even if you’re on a tight budget, and we talk about the value of over-investing in design so you can save yourself a ton of money in development. 

Wie gelingt ein erfolgreicher Store-Auftritt in Apples App Store? In dieser Folge erzählen wir euch von dem Prozess, den ihr als App-EntwicklerInnen durchlaufen müsst, um im Store für iOS präsent zu sein. Wir beantworten, welche Tools ihr neben Xcode noch benötigt und welche Voraussetzungen ihr außer einer Mitgliedschaft im Apple Developer Program erfüllen müsst. Wie gelingt es beispielsweise, eine App zu signieren? Der Dienst “App Store Connect” wird euer neuer bester Freund, mit dem ihr nach der Veröffentlichung im Analytics-Bereich wertvolle Einblicke erhaltet, neue Versionen einreichen und in den Review-Prozess gehen könnt. Eins ist sicher: Am Ende dieser Folge kennt ihr jeden Schritt der Veröffentlichung und seid bestens darauf vorbereitet, eine frisch gebackene Hello-World-App in die Welt zu schicken. Wenn ihr danach total gehyped seid und eure App auch auf weitere Plattformen bringen wollt, ist Folge 56 spannend für euch, in der wir erklären, wie ihr im Google Play Store diesen Prozess durchlauft. Picks of the Day Jojo: Nutzungsbedingungen von Webseiten und Apps vor der Zustimmung wieder nicht gelesen? ToS;DR hilft euch und schätzt mit praktischen Zusammenfassungen eure meistgenutzten Services ein. Sebi: Diese AsyncLocalStorage Node.js-Klasse hat Sebi die Augen geöffnet!Dennis: Ein Google Suchoperator, um die Zeit jeder Stadt schnell zu finden: “Zeit/Time Stadt”, bspw. “Zeit Bad Nauheim”. Schreibt uns!  Schickt uns eure Themenwünsche und euer Feedback.  podcast@programmier.bar  Folgt uns!  Bleibt auf dem Laufenden über zukünftige Folgen und virtuelle Meetups und beteiligt euch an Community-Diskussionen.  Twitter  Instagram  Facebook  Meetup  YouTube  Musik: Hanimo

In this episode of AWS TechChat we continue with part two of our four part re:Invent 2020 series with this episode covering all Application Development, Containers, and Database announcements. For our developer community, we talked about: * Using CodeGuru’s new Security detectors to help you find and remediate security issues in your code * Python support for CodeGuru’s in preview * We shared another new service, DevOps Guru in preview, for measuring and improving an application’s operational performance * Lambda now supports up to 10 GB of memory and 6 vCPU cores and a billing granularity reduction down to 1ms * Amazon API Gateway now supports integration with Step Functions StartSyncExecution for HTTP APIs * Appflow simplifies cloud app integrations for connect customers with Customer Profiles * Similarly, Appflow can provide similar app integrations with those 3rd party apps to HoneyCode. * For those Amplify users, deploy Fargate containers through the Amplify CLI and you get a new AdminUI to boot that deploys all the underlying bits for you. * AWS Proton to bridge the gap between platform and development teams In containers we kicked it off with EKS. * First, cluster add-ons managed through the EKS console, CLI, or API. * Run EKS on premises with EKS Distribution * EKS on Fargate now has built in logging with Fluent Bit under the hood * You can now see all your Kubernetes resources in the EKS console without needing extra tools * Public registries for your container images with ECR public and the ECR public gallery * Use your existing containers as a lambda package format * ECS Deployment Circuit Breaker is in preview to stop deployments from getting worse and auto-rollback In database land we covered * Bablefish, not the mythological creature, but a translation layer between Aurora PostgresSQL and Microsoft SQL. * v2 of Aurora Serverless has arrived, considerably faster and scales in a fraction of second, with scaling so fast it is perfect for those event driven applications. * Data Exchange adds revision access rules for governing access * RDS Service Delivery Partners for when you want someone to build, deploy, and manage your RDS deployments * RDS Cross-Region backups comes to RDS for Oracle * Share data across Redshift clusters with data sharing in preview and pull data from partners directly via the RedShift Console. * RedShift Federated query comes to RDS for MySQL and Aurora MySQL * Redshift Automatic Table Optimization to keep your data warehouse running in tip top shape automatically. * Move RedShift clusters easily across Availability Zones. * JSON supports in preview for RedShift * Finally, AQUA comes to RedShift in Preview as a caching layer to speed up queries. Stay tuned as we cover all aspects of re:invent 2020 in our coming multi-part re:Invent update

Swift News comes out every Monday - Subscribe or follow me on twitter to be notified of new episodes. In this episode we discuss the new Diversity in Swift initiative, Apple releasing more tutorials and videos, the MacStories App Awards and the story of Uber adopting Swift back in 2016 and how it was nearly a tragedy. We also talk about indie app development, ARKit and more. YouTube Video version: https://youtu.be/ObALdJyiPgU Swift News GitHub Repo with Links to Stories: https://github.com/SAllen0400/swift-news More information about my iOS Development courses: https://seanallen.teachable.com/ Link to my book - How I Became an iOS Developer: https://gumroad.com/l/sean-allen-origin Twitter: https://www.twitter.com/seanallen_dev YouTube Channel: https://www.youtube.com/seanallen Portfolio: https://seanallen.co Book and learning recommendations (Affiliate Links): Ray Wenderlich Books: https://store.raywenderlich.com/a/20866/link/1 Ray Wenderlich Video Tutorials: https://store.raywenderlich.com/a/20866/link/24 Paul Hudson's Hacking With Swift: https://gumroad.com/a/762098803 Learn Advanced Swift Here: https://gumroad.com/a/656585843 My Developer & YouTube Setup: https://www.amazon.com/shop/seanallen --- Support this podcast: https://anchor.fm/seanallen/support

Nigel Poulton (@nigelpoulton, Docker & Kubernetes training) talks about the current and future state of Kubernetes, who is using it and why, implementation and operational challenges, and how get started and what tools he recommendsSHOW: 478SHOW SPONSOR LINKS:Okta - You should not be building your own AuthLearn how Okta helped Cengage improve student success rates during COVID.Datadog Security Monitoring Homepage - Modern Monitoring and AnalyticsTry Datadog yourself by starting a free, 14-day trial today. Listeners of this podcast will also receive a free Datadog T-shirt.CloudAcademy - Build hands-on technical skills. Get measurable results. Get 50% of the monthly price of CloudAcademy by using code CLOUDCASTCLOUD NEWS OF THE WEEK - http://bit.ly/cloudcast-cnotwPodCTL Podcast is Back (Enterprise Kubernetes) - http://podctl.comSHOW NOTES:Nigel Poulton HomepageNigel’s YouTube Channel Kubernetes Deep Drive (ACloudGuru)Nigel’s training courses on PluralSightEps. 320 (Nov 2017) - "Docker adds Kubernetes, now what?"Eps.269 (Sept 2016) - "Putting Docker in your brain"Topic 1 - Welcome back to the show. Tell us about some of your most recent projects, and all the places where people can find your training? Topic 2 - Let’s talk about the State of Kubernetes, level of maturity of users/usage. Where do you think we are at the end of 2020? Topic 3 - Who do you find are trying to learn and use Kubernetes, more Infra/Ops, or AppDev, or somewhere in between (DevOps, DevSecOps, SRE, etc.)?Topic 3a - Where do you see people succeeding, and where are they still struggling to adjust to the requirements of Kubernetes? Topic 4 - The ecosystem of projects around Kubernetes (immutable Linux, Operators, Service Mesh, Prometheus, OPA, Serverless/Knative, etc.) has gotten very broad. How do you find people are dealing with all these moving pieces? Topic 5 - There are a lot of ways to engage with Kubernetes these days - DIY (OSS), vendor distributions, Kubernetes on your laptop, web IDEs, Hosted Services (simple & complex). What do you recommend to people, or do you see trends about how people best engage with Kubernetes? Topic 6 - Do you think it’s OK that Kubernetes doesn’t have a “developer model”, but rather many different options? Do you think this evolves in 2021? FEEDBACK?Email: show at thecloudcast dot netTwitter: @thecloudcastnet

Leo is joined by Jordan Morgan of Spend Stack and Buffer. In this episode, they discuss the new changes to the App Store Revenue cut, their 2020 purchases, how to setup Leo's new M1 Mac Book Air, as well as working remotely with little ones at home in 2020.

Kay Malcolm and Tom McGinn provide an Oracle LiveLabs update, which gives you free access to Oracle's Cloud, enabling you to run a wide variety of labs and workshops. Kay explains LiveLabs, which enables you to learn cutting-edge skills in our Cloud, for both your Cloud and On-premise Training Needs. From the original 18 workshops to now 80 plus and growing, with content experiences across from complete Oracle Portfolio: Cloud, On-Premise, Database, AppDev through to Applications like eBusiness Suite.

In der ersten Folge unseres CTO-Specials haben wir Jesper Richter-Reichhelm zu Gast. Er ist CTO der Heritas GmbH und spricht mit uns über die Erfahrungen aus seiner Zeit als Softwareentwickler bei Jamba, Head of Engineering bei Wooga und CTO bei Outfittery. Jesper erzählt uns davon, wie er – begonnen als Entwickler – bei der Skalierung des Teams von Wooga von 10 auf 300 Personen geholfen hat. Als späterer Head of Engineering organisierte er die Arbeit von rund 90 EntwicklerInnen und lernte viel darüber, was es beim Firmenwachstum zu beachten gibt. Welche Strategien sind bei Einstellungsprozessen erfolgversprechend und wie etabliert man eine Firmenkultur, die auf Feedback und Eigenständigkeit fußt? Haben alle EntwicklerInnen das Zeug zum CTO? Diese und weitere Fragen rund um die Rolle eines Chief Technology Officers klären wir in dieser Folge. Bleibt bis zum Schluss dran, um wertvolle Tipps von Jesper zu erhalten, die er nicht nur (angehenden) CTOs, sondern allen MitarbeiterInnen eines Technologie-Unternehmens mitgeben möchte. Zum Einstieg in das Thema Management im Softwarebereich empfiehlt er das Buch “Accelerate: The Science of Lean Software and Devops”. Im CTO-Special holt sich Dennis Unterstützung durch Dominik, einem der Gründer der Lotum GmbH. Gemeinsam sprechen sie mit CTOs über Erwartungen, Anforderungen und Erfahrungen, welche die Rolle mit sich bringt.Schreibt uns! Was haltet ihr von dem neuen Format? Habt ihr Feedback, das ihr gern mit uns teilen wollt? Schickt uns eure Themenwünsche und euer Feedback. podcast@programmier.bar Folgt uns! Bleibt auf dem Laufenden über zukünftige Folgen und virtuelle Meetups und beteiligt euch an Community-Diskussionen. Twitter Instagram Facebook Meetup YouTube Musik: Hanimo

Mike sits down with Paul Kafasis of Rogue Amoeba to discuss the state of independant macOS development in 2020, a little Objective-C and more. Rogue Amoeba (https://rogueamoeba.com/) Rogue Amoeba on Twitter (https://twitter.com/RogueAmoeba) Piezo Outside the AppStore (https://weblog.rogueamoeba.com/2017/02/10/piezos-life-outside-the-app-store/) SoundSource 5 Release (https://weblog.rogueamoeba.com/2020/08/05/soundsource-5-is-sound-control-reimagined/) Charlie Monroe's Story (http://blog.charliemonroe.net/a-day-without-business/) Mike on Twitter (https://twitter.com/dominucco) The Mad Botter (https://themadbotter.com) Coder Radio's Back (https://coder.show)

From wanting to be a video game programmer to now running his own application development team at Cigna Healthcare, David Janson has a pretty interesting story. Hear about how his father plays a huge role in his life and what really set Dave off on the journey that his career has taken. He graduated from the University of Hartford with his BS in Computer Science and hasn't looked back! Dave started out as IT consultant over a decade ago and now runs an international team of people helping improve internal production workflows and experiences! For a guy in his early 30's, Dave has more tenure and experience in his particular field than most of us will ever get with one company! Check it out now!

Have a business idea or an app idea? Ever wonder what it's like to make a mobile app? Wonder what are the steps and what does the process look like? Jared Stresen-Reuter CEO of Divine Digital sits down with us at Doors Open Connect and walks us through his process after developing and being involved with over 50 apps among many other projects. He talks creativity, how to bring your ideas to life, how to manage expectations and also new tech and AI that is coming on the scene.

Exclusive “App Talk” Listening party for @doeboy| @escomoecity Mixtape.Hosted by @jamalmakesapps.Follow us on IG and download on all platforms.JamalMakesApps.com | Download “Jamal Makes Apps” .

App Talk Podcast Hosted By Jamal Makes Apps.Season 1 : Intro features Jamirrr - Good Vibez (Official Podcast Intro).Follow : @JamalMakesApps on IG.Follow : @JamirrrOfficial on IG.Web : www.JamalMakesApps.comDownload : Jamal Makes Apps , Available on all platforms worldwide.

From $0 to $20,145.92 in 2 months with a side project (https://twitter.com/zenorocha/status/1249348452095373312) Dracula Pro (https://draculatheme.com/pro) Le Cheese (https://lecheese.app) Zeno on Twitter (https://twitter.com/zenorocha) Hyper Terminal (https://hyper.is) Superhuman (https://superhuman.com) Roam Research (https://roamresearch.com) Mike on Twitter (https://twitter.com/dominucco) The Show on Twitter (https://twitter.com/mdominickshow?) The Mad Botter INC (https://themadbotter.com)

The podcast content returns with the first episode of the new "What I'm Working On" (WIMO from here on out). In this episode I discuss what I've been up to in my content creation business, how my indie app (CreatorView) is going, what type of work I'm doing for my consultancy as well as rebuilding my website with Publish and my accidental rebrand. Hope you enjoy! More information about my iOS Development courses: https://seanallen.teachable.com/ Link to my book - How I Became an iOS Developer: https://gumroad.com/l/sean-allen-origin Twitter: https://www.twitter.com/seanallen_dev Instagram: @seanallen_dev YouTube Channel: https://www.youtube.com/seanallen Portfolio: https://seanallen.co Are you a gamer? I'm now streaming video games on Twitch as well: https://twitch.tv/seanallen Book and learning recommendations (Affiliate Links): Ray Wenderlich Books: https://store.raywenderlich.com/a/20866/link/1 Ray Wenderlich Video Tutorials: https://store.raywenderlich.com/a/20866/link/24 Paul Hudson's Hacking With Swift: https://gumroad.com/a/762098803 Learn Advanced Swift Here: https://gumroad.com/a/656585843 My Developer & YouTube Setup: https://www.amazon.com/shop/seanallen --- Support this podcast: https://anchor.fm/seanallen/support

 Trick question of the week: How are developer relations different from developer advocates? The role of the liaison between the company and the developer is not something new. Several titles have appeared since companies decided that engaging with developers can offer a competitive advantage. Early roles, that are still active today, were given titled "evangelist" or "advocate". Is DevRel a natural evolution of the role with a different title or advocates and DevRel work together for a more complete approach? We're not going to spoil it for you. We'll let our guest Chris Riley walk us through this, what makes a good developer advocate and more. Chris has been long in the field and takes us through the evolution of the industry and what makes someone good at such a technical role. Bonus: where can someone new to their Advocacy/DevRel role find resources on how to be more effective? Tons of answers in one all-inclusive episode. DevRelx: Our new portal comes with a bi-weekly digest of the latest industry news. You will still be notified of new podcast episodes and also news, articles and jobs. Interested? Sign-up at www.devrelx.com Chris Riley is a Tech Advocate at Splunk, he is obsessed with bringing modern technologies to those who need to solve real-world problems, going from unicorn to reality. Chris speaks and engages with end-users regularly in the areas of DevOps, SRE, and App Dev. He is a regular contributor to industry blogs such as ContainerJournal.com, DevOps.com and Sweetcode.io and host of the podcast Developers Eating the World. As a bad coder turned technology advocate, Chris understands the challenges and needs of modern engineers, as well as how technology fits into the broader business goals of companies in a demanding high-tech world. Developer personas webinar (https://youtu.be/liTCvhUCiIM)

Ian Crosby (@IanDCrosby, Managing Director @ContainerSoluti) talks about how Cloud-native applications are as much about new technology patterns as they are about new organization patterns, collaboration patterns and risk-management patterns. SHOW: 445SHOW SPONSOR LINKS:Datadog Homepage - Modern Monitoring and AnalyticsTry Datadog yourself by starting a free, 14-day trial today. Listeners of this podcast will also receive a free Datadog T-shirtDivvyCloud - Achieve continuous security & compliance. Request a free trial today!DivvyCloud’s 2020 Cloud Misconfigurations Report - Cloud misconfigurations cost enterprises $5 trillion in 2018 and 2019.MongoDB Homepage - The most popular database for modern applicationsMongoDB Atlas - MongoDB-as-a-Service on AWS, Azure and GCPCLOUD NEWS OF THE WEEK - http://bit.ly/cloudcast-cnotwSHOW NOTES:Container Solutions (homepage)Ian’s Blog (Container Solutions)Cloud Native Transformation Patterns (Strategy, Culture, Tech, Orgs, etc.)Cloud Native Transformation (O’Reilly)Topic 1 - Welcome to the show. Tell us a little bit about your background, as you’ve been around software development and this move to cloud-native for a little while now. Topic 2 - Lets begin by talking about patterns. What are some common application patterns, and how do they begin to change when we’re talking about cloud-native patterns?Topic 3 - What are some of the more commonly used cloud-native patterns? Are they more focused on the underlying technology (e.g. containers, Kubernetes, etc.) or more focused on the actual application (e.g. 12-factor, etc)?Topic 4 - Have you found that some patterns are easier for groups (or companies) to adopt than others? Topic 4a - “Why are patterns useful in Cloud Native?” or “How do you get started using patterns?” are two topics/questions which may be interesting.Topic 5 - Have you found that some patterns are easier or more difficult to maintain over time?Topic 6 - What are some common tips that you share with communities or your clients to help them find early success to build confidence?FEEDBACK?Email: show at thecloudcast dot netTwitter: @thecloudcastnet

Wie ist es, an einem Hackathon von zuhause aus teilzunehmen? In unserer ersten live gestreamten Podcastfolge sprachen wir über diese Erfahrung mit Malte Reimann und Maurice Hofmann, die beim ersten Teil des #WirVsVirus-Hackathon der Bundesregierung mitwirkten. Über 28.000 Teilnehmende fanden sich im März zusammen, um Ideen und Konzepte zur Bewältigung der Corona-Krise zu erarbeiten. In Folge 58 richteten wir eure und unsere Fragen an unsere Gäste. Maurice, UX-Designer in einer Digitalagentur, und Malte, Informatik-Student am KIT, entwickelten gemeinsam mit ihrem Team eine App namens GoBonsai. Diese setzt sich zum Ziel, Sport und gemeinnützige Spenden zu vereinen und soll trotz sozialer Distanz ein Gemeinschaftsgefühl schaffen. Wie die Diversität des Teams in der Konzeptionierung und Umsetzung von besonderem Nutzen sein konnte, erzählen uns Maurice und Malte in dieser Folge. Am Ende des Hackathon-Wochenendes standen ein detailliert ausgearbeitetes Konzept sowie ein Prototyp der App, vor allem aber wertvolle Erfahrungen und ein Projekt, das weiterlebt. Timecodes: (00:51) Was ist #WirVsVirus? (03:05) Malte und Maurice über sich und ihre Hackathon-Erfahrungen (04:18) Wie startete #WirVsVirus und wie konnte man teilnehmen? (10:59) Wie fand das Team zusammen? (16:03) Die Idee hinter GoBonsai(21:17) Rollenverteilung und Arbeitsweise (25:26) Welche Tools und Technologien wurden eingesetzt? (30:33) Remote-Zusammenarbeit und Kommunikationswege (37:02) Experimente während des Hackathons (39:05) Wie geht es weiter?(44:26) Wie endete der Hackathon und was haben Malte und Maurice mitgenommen?(51:28) Picks of the DayAktuell sucht das Team noch mehr Unterstützung, insbesondere Coder, Designer und Sponsoren. Auf Devpost und GitHub könnt ihr euch tiefer einlesen und via Twitter oder Blog zu Maurice Kontakt aufnehmen. Maurice hat seine Erfahrungen auch in folgendem Artikel des Unstable Magazines geschildert: Maurice Hofmann (2020): Code Contra Corona. Im Hackathon die Masterarbeit verwirklicht. Erstmalig haben wir diese Folge über einen Livestream aufgenommen und ihr wart im Chat live dabei! Wenn ihr auch beim nächsten Mal Fragen stellen und kommentieren wollt, folgt uns auf Social Media und Meetup, um auf dem Laufenden zu bleiben. Picks of the Day Fabi: Git Tree Compare – Mit dieser Extension für Visual Studio ganz einfach sehen, welche Unterschiede es zwischen dem aktuellen Arbeitsverzeichnis und Branches, Tags oder Commits gibt. Maurice: Nehmt eure Ideen, die ihr so rumliegen habt, und macht was Ehrenamtliches daraus. Mal schauen, was passiert! Malte: Local Hack Day: Share am 11. April 2020 von der Major League Hacking. Streamt uns! Wann das nächste Live-Event stattfindet, erfahrt ihr über die folgenden Quellen und unsere Webseite. Schreibt uns! podcast@programmier.bar Folgt uns! Twitter Instagram Facebook Musik: Hanimo

Join Diogo and Joan as they discuss app development for Ubuntu Touch and Ubucon...

Don asked Randy about what he's working on, lately, and Randy exclaimed, "nothing fun," which actually turns out not to be true. Randy details the additional mix of people, communication, and risk management around mature application development and it becomes the setting for a larger-picture discussion on how things change with app dev as you age.

Maciej Gałkiewicz is the CEO at Ragnarson which is an agency that specializes in building web apps for startups and guiding them through the MVP development. In this episode we're going to discuss how he found a niche for his agency, builds systems around the company and why he believes that time & material pricing is the best option for startups building MVPs. Show-notes: http://entrepreneursinb2bsales.com/maciej-Galkiewicz/interviews  

In this episode of The Wired Educator Podcast, I interview Jakob Hansen. Jakob has more than ten years in education as an innovative educator and leader. He has now turned his attention to the future of education. He is an educational consultant helping schools now prepare students for the future. This is an amazing interview and conversation that will really get you thinking.  Jakob was one of the leading forces behind FlowFactory, Denmarks' first High School that was 100% based on Challenge Based Learning and cross-curricula, Real World projects, together with both local and international corporations and organizations (like LEGO Education, SamLabs and Danfoss). His mission is to inspire us to reinvent education ... to dare to think differently about learning and to aim higher and to see new creative possibilities for learning that are based on future trends instead of historical traditions. Jakob Hansen has a background in industrial and interaction design and has been teaching Design, Entrepreneurship and Coding and App Dev. (Swift coding in X code.) Last year Jakob left the classroom and works now with schools all around the world (South Africa, England, Ukraine, UAE, Germany, Denmark) as an independent consultant. The focus is on Challenge Based Learning, Leading Change and the Design of new Learning Spaces. Jakob is one of three co-founders of the new nonprofit organization toward2030.org. The mission is to give schools and decision-makers the opportunity to dream big and set big goals for where they want to be in 2030, a decade from now, by providing creative tools and facilitate workshops and bring ambitious schools across the world closer together. Mentioned in this episode: Follow Jakob on Twitter and Instagram at: @jakobesben and Instagram Jakob's company is called, The Friendly Disruptor - www.FriendlyDisruptor.com (website temporarily offline - working on a huge redesign.) Toward2030.org: www.toward2030.org (Will be online from the end of next week. (the 18 of Jan 2020)) Last chance to receive my eBook, The Greatest Year of Your Life, updated for 2020. This opportunity closes on January 15, 2020, and then the book goes on sale. To help you kick off the new year and to help you reach your goals and resolutions this year, I am giving away a free copy of my 64-page eBook, The Greatest Year of Your Life (2020 Edition) to everyone who signs up for my newsletter. Become more productive. Get things done. Level-up your leadership. Design a more dynamic life. All you have to do to receive the free copy is to sign-up for my free newsletter. Just click this link and enter your email. That's it. It's that simple. This eBook is available only until January 15, 2020. 2) Last chance to apply for coaching with me. This opportunity also closes on January 15, 2020. I am even giving away one seat away fro FREE. Would you like to work with me to help you achieve your goal of publishing a book, building a website, hosting a podcast, starting a business, becoming a speaker, or achieving another awesome life goal? Complete the following application before January 15, 2020. One lucky applicant will win free coaching. Here is the application: https://forms.gle/762GxbJ8b5oD8xEK9 3) I want to speak to your school or organization this year! I know January and February are two big months for organizations to start planning their professional learning and speakers for the year. I would love to work with your organization to level-up your leadership. To learn more about my speaking visit www.KellyCroy.com and www.WiredEducator.com. Last year I traveled as close as a neighboring town to work with a financial firm and as far as the Philippines to speak at an international education conference. I would love to speak at your event. No matter what the challenge, leadership is the solution! Sign-up for Kelly's newsletter here. Kelly Croy is an author, speaker, and educator. If you'd like to learn more about Kelly or invite him to your school or conference to speak please send him an email. • Listen to Kelly's other podcast, The Future Focused Podcast and subscribe. • Subscribe to The Wired Educator Podcast with over 150 episodes of interviews and professional development. • Visit Kelly's website at www.KellyCroy.com. • Looking for a dynamic speaker for your school's opening day? • Consider Kelly Croy at www.KellyCroy.com • Order Kelly's book, Along Came a Leader for a school book study or your personal library. • Follow Kelly Croy on Facebook.  • Follow Kelly Croy on Twitter.  •  Follow Kelly Croy on Instagram    

Wade Wegner has been focused on building developer tools and platforms for most of his career. Today, he is the SVP of Product for Platform at Salesforce and responsible products that are used by countless customers around the world. What Wade and his team focus on most is helping customers get more done faster so that they can put more of their energy into moving their business forward. On this episode of IT Visionaries, Wade explains how that’s possible with the Salesforce Customer 360 platform, and he shares what we can be excited about coming out of the Salesforce product team soon. Key Takeaways: The world of app development is focused on creating app factories Putting together different developers will lead to better results in app dev Constant delivery of product should be one of your main focuses   IT Visionaries is brought to you by the Salesforce Customer 360 Platform - the #1 cloud platform for digital transformation of every experience. Build connected experiences, empower every employee, and deliver continuous innovation - with the customer at the center of everything you do. Learn more at salesforce.com/platform

Carl & Kody share how they make learning a priority and get infatuated with customer needs through Product Management. Hear about making data driven decisions…Continue readingProduct Management: Outcome Focused Decision Making

SHOW: 426DESCRIPTION: Aaron and Brian talk to Mark Weitzel (@weitzlm, VP & General Manager, New Relic One at @NewRelic) about building effective developer platforms including lessons learned, best practices and trade offs to considerSHOW SPONSOR LINKS:The Cyberwire - Your security news connection.The Cyberwire daily podcastDatadog Homepage - Modern Monitoring and AnalyticsTry Datadog yourself by starting a free, 14-day trial today. Listeners of this podcast will also receive a free Datadog T-shirt[FREE] Try an IT Pro ChallengeCLOUD NEWS OF THE WEEK:KubeCon impressions from BrianAWS announced a bunch of new services prior to Re:InventGoogle Cloud acquires Cloud SimpleIBM continues to add functionality onto Red Hat OpenShift:IBM Spectrum BackupsIBM Cloud Pak for Hybrid Cloud SecurityIBM "Keep Your Own Key" (KYOK) for KubernetesSHOW INTERVIEW LINKS:New Relic OneMark's New Relic BlogNew Relic Developer ProgramSHOW NOTES:Topic 1 - Welcome to the show. Before we get into a broader discussion, tell us a little bit about your background. Topic 2 - Before we dig into the New Relic Developer Program, we wanted to get your perspective on what “developer” means these days - Is it AppDev, DevOps, Data Scientist, Business Analyst? How do you try and put personas around different “developer” needs?Topic 3 - One of the things I find in working with businesses that are going through transformational change (via technology) is how many don’t understand that their new world (“enabling developers”) will begin to look like a technology vendor’s approach to the market (“enabling developers”). Do you find your customers begin to adopt their internal programs to look like the program that you’ve rolled out with New Relic One? Topic 4 - What are some of the most important/critical aspects of the program, and how do you measure its progress, its success, or its areas to improve?Topic 5 - How did you think about balancing the need for content for newer developers (or new to the platform) vs. more expert-level developers? Topic 6 - How important is community to making the program a success, and helping it scale?FEEDBACK?Email: show at thecloudcast dot netTwitter: @thecloudcastnet

Learn why Shanghai Business School powers their innovation center with Apple technology — where students from every major come together to build iOS apps and bring real-world solutions to the problems they care about most.

Innovating ride sharing in Vancouver

Joan CiberSheep and Diogo Constantino - Introductory episode and presentation for this audiocast in which we talk about Ubuntu Touch app development.

Simon Reggiani is a multi-platform native and hybrid mobile developer with over a decade of experience launching apps on iOS and Android using Java, Kotlin, Objective-C, Swift, and React Native. Simon shares his opinions and insights based on his experience at Slack and other high-growth startups. He talks about when businesses should go native vs. hybrid, and how developers can make the leap from web app to mobile app development. See acast.com/privacy for privacy and opt-out information.

Blake Johnston is back for another episode and we talk about side hustles. Each of us have a little experience moonlighting and working on side projects, either for financial gain or as an opportunity to develop new skillsets.  Tyrel, Hayden, Casey and our guest Blake Johnston talk about our experiences and things we're working on now. http://friday.hirelofty.com/ https://facebook.com/fridaydeploy https://twitter.com/fridaydeploy Mentioned in this Episode Download your Facebook Information (facebook.com) Shipping 'Belonging' with GraphQL & Apollo at Airbnb (youtube.com)

Get ready to ‘rock the house’ as Apple HomePod is nearly here - listen for new details and our pre-order experience. We also welcome indie developer duo Ish and Heidi to discuss the challenges of coding and designing their iOS apps. Plus what happens when two podcast hosts meet for the first time? It’s an interstate initiation with Apple aptitude - it’s Apple Slice! Part of the Auscast Network More details at appleslice.com.au Check out Ish and Heidi’s work: Capsicum - https://twitter.com/capsicumapp Stamp Pack - https://twitter.com/StampPack Boomerang - https://twitter.com/BoomerangCheck

In Tech Focus we look at Microsoft Power BI.  We have been using Power BI to pull information from line of business application.  At Extreme we can see who has been entering their timesheets, who has been working with which customers and what billings each engineer has.  This updates in real time and display it on one of our monitors that is mounted on the wall.  This means that everyone can see how the team and each individual is performing. We look at the processes we use for both developing applications internal and for our customers.  The costs of software development have dramatically decreased and enable completely different business models to thrive because investments are so much lower. The process involves: Off the shelf vs custom built - Of the shelf is generally cheaper but it will have functionality for a whole range of business and some of your business process will need to change to match the off the shelf software.  Custom built or bespoke software will match exactly your business processes. Phone apps - are they worth the effort.  A lot of consumers have app fatigue.  They may find it in the appstore and install it, but a lot of apps get used once and the app is never opened again. Middleware - Breaking down the silos between your databases.  Your customer database, marketing database, financial database.  It can be very power taking data from one type of software and putting it into another. Business Process apps - taking the way that you run your business and putting it in the app.  This automates things, cuts down on user error and allows for automatic reporting.  These are some of the most powerful apps that small businesses build.  If you have great processes, you can sell your application with your IP.  For a plumber, they may service a 25km radius.  If you sell plumbing company software, it could be a global opportunity. Failure in app development. Not being sure of what you want or what your business processes are. Look at the track record of your developer.  They should have shipped decent sized processes.  We have built a booking system for Restaurants that is used in 11 countries and taken over $25,000,000 in bookings.  That gives our customers a bit more confidence that we can do what we are saying we can do. Make sure the application is made by a team, business analysis, design and development. Who can build the application for you: Fiverr - get a dev for just the process. Insource a developer - hire them for your team.  If you have only 1 developer and little experience in app dev, it is hard to manage your application development team. Hire a development team.  Either onshore or offshored, get the skills and the resources you need for the project. Look at the risk and the size of the project to see which path is right for you.  If your company relies heavily on IT it might be worthwhile to building a team. App Dev can help you to fundamentally change the way that you work and the profitability of your company. Some companies develop software and end up making more money by selling their application than out of their original business. It is a great way of monetising your intellectual property. Quote - Patton - Never tell people how to do things  Tell them what to do and they will surprise you with their ingenuity.

_Note: This episode was recorded in my classroom. Please excuse the audio issues we had at times. They were a result of recording in our school._ This is a very special episode I recorded in my classroom. Six of my 11th grade students shared their views on learning to code, the Swift language, the Swift playgrounds app, and other coding related topics. I was really excited to get their feedback and thoughts about this school year so that you could hear their insights. I would like to thank the students that appeared on this episode. I hope you enjoy this episode. Sorry for the audio issues. Show Links Swift Playgrounds - https://appsto.re/us/eHUj2.i Into to App Development with Swift curriculum Teacher - https://itunes.apple.com/us/book/app-development-with-swift/id1118577558?mt=11 Student - https://itunes.apple.com/us/book/app-development-with-swift/id1118575552?mt=11 You can find also find the show notes and other information on my blog: Swift Teacher Blog - http://www.swiftteacher.org/podcast

HeartScribe: 16 Year Old App Dev. Rohan Taneja, Interview The internet can be intimidating for those not used to it, and when it comes to healthcare, while many potential advantages are available using the newest technology, there are still obstacles.  Here on The Not Old Better Show we've talked a lot about the “age gap” that exists in the technology industry.  The fact that most tech workers are young people, and that technology often appears to be designed for young people. And, we've established, and data supports this, that by 2030, approximately 20% of people in the US with be over 65.  Maybe 20% doesn't sound like a lot to you.  Well, it happens to be about the same number of people in the US who own an iPhone today.  Which of these two groups do you think Silicon Valley spends more time thinking about? This seems unfortunate when you consider all of the things technology has to offer those of us 55+ in age.  Thankfully, some of this, appears to be changing, and  my guest today on The Not Old Better Show has created a smart, mobile tool to help gather and save our vital healthcare information, and do so simply and safely. “When I first started developing the app I went to a few senior centers and I realized the buttons were not big enough; it was like every other app out there. Most of the other apps are really hard for people who are over 60 or over 70 to use, but this but this app is for heart failure patients, who are usually over 60. That was when I realized the app needed to be a lot more catered towards older people, so I made the buttons bigger I made everything a lot simpler. I took out some features that made it a bit too complex and were not really necessary. I had to make it really easy to use for the older population who have heart failure and other chronic conditions," says Rohan Taneja, 16, developer of the HeartScribe app.  More information HERE, and you can find the app at Google Play (only, for the time being...iOS coming soon). Enjoy...BTW, Rohan encourages feedback, so please provide any directly HERE.

Welcome back to the dramatic conclusion of our discussion on the 12 factor app. This time we're talking dev/prod parity, logs, and admin processes. Oh, and Call of Duty! News […]

Welcome back to the dramatic conclusion of our discussion on the 12 factor app. This time we’re talking dev/prod parity, logs, and admin processes. Oh, and Call of Duty! News Thanks for the reviews! arathustra, lu S, Seb (from London), S Willowood, TheDarkKnight15, FreeAppsHunter Where do transforms go? UI or Middleware? Joe had surgery! Oopsy […]

Gary McGraw (@cigitalgem), CTO of the security giant Cigital, chats with us about how web developers, and software engineers in general, can best secure applications we are building today. We dive into best practices, team collaboration techniques, where to go for further information, and what companies like Cigital are doing for the web security community. Resources Cigital- http://www.cigital.com/ The Silver Bullet Podcast - http://www.cigital.com/silver-bullet/ Web Application Security Consortium - http://www.webappsec.org/ Software Security - Building Security In - http://www.amazon.com/Software-Security-Building-In/dp/0321356705 NodeGoat - http://nodegoat.herokuapp.com/login RailsGoat - http://railsgoat.cktricky.com/ Gary's books - http://www.cigital.com/~gem/books/ Charlie Miller Interview - http://www.cigital.com/silver-bullet/show-095/ OWASP - https://www.owasp.org/ Panelists Adi Chikara - ATG Lead at3Pillar Global Christian Smith - Open Source developer & Startup Enthusiast Chetan Karande - Senior Software Engineer at Omgeo   Erik Isaksen - UX Engineer at3Pillar Global Rob Simpson - Senior Front End Developer atCapco Nick Niemeir - JavaScript Agent Engineer at New Relic

Milbery's Mazlow's Hierarchy of Software Needs.  We are officially a year old today and have we got a gift for you.  Jim and Devin spend an hour dissecting Jim's controversial hierarchy of software needs. 

Jake Miles, freelance developer and senior analyst for Conde Nast, previews his new three-part tutorial series on Mastering Facebook application development with PHP, Rational Application Developer, WebSphere Application Server, and DB2.