POPULARITY
20 episodes with jeff meyerson
3 episodes with jeff meyerson
4 episodes with jeff meyerson
5 episodes with jeff meyerson
2 episodes with jeff meyerson
In memory of Software Engineering Daily Founder, Jeff Meyerson. 1988 – 2022 The post An update about SED from Jeff's family appeared first on Software Engineering Daily.
In memory of Software Engineering Daily Founder, Jeff Meyerson. 1988 – 2022 Jeff founded Software Engineering Daily in 2015 and hosted the podcast until 2022. He was willful, hard working, and a strong advocate for self-direction. To hear more about what Jeff was like, please listen to Remembering Jeff Meyerson with Erika Hokanson. If you’d The post An update about SED from Jeff's family appeared first on Software Engineering Daily.
Eric Anderson (@ericmander) and Erika Hokanson (@erikawh0) remember the life of Jeff Meyerson, creator of the influential podcast Software Engineering Daily. He passed during the summer of 2022. Still, his work lives on - thousands of episodes, talks, music, a book, and a community of dedicated listeners and engineers whose lives were touched by Jeff's dreams. Software Engineering Daily is still running, and you can listen to new episodes right here or wherever you get your podcasts. Subscribe to Contributor on Substack for email notifications, and join our Slack community! Links: Software Engineering Daily Software Engineering Radio The Prion (Soundcloud) (Spotify) You Are Not A Commodity Move Fast: How Facebook Builds Software People mentioned: Pranay Mohan (@pranaymohan)
Jeff Meyerson speaks with Jon and talks about the alignment of technology in entrepreneurship. Connect with Jon Dwoskin: Twitter: @jdwoskin Facebook: https://www.facebook.com/jonathan.dwoskin Instagram: https://www.instagram.com/thejondwoskinexperience/ Website: https://jondwoskin.com/LinkedIn: https://www.linkedin.com/in/jondwoskin/ Email: jon@jondwoskin.com Get Jon's Book: The Think Big Movement: Grow your business big. Very Big!
Jeff Meyerson, entrepreneur, musician, technologist, and author of the acclaimed "Move Fast: How Facebook Builds Software", discusses the stranglehold Big Tech has on developer tools and how the future of software development may be quite different from the present.Listen and learn...What Jeff learned about sales from playing pokerHow Facebook builds software... and how it can avoid being evil Why React is the "Linux of the frontend of the web"The development tools Jeff's most excited aboutWhy Zuck's not a good leaderWhat Jeff will tell Zuck when they finally meet References in this episode..."Move Fast: How Facebook Builds Software" on AmazonJeff on TwitterSoftware Engineering DailyJanelle Shane's great book
Jeff Meyerson is the host of Software Engineering Daily and author of the book, Move Fast: How Facebook Builds Software. I am not a software engineer, and I enjoyed this book. I enjoyed it because it is a book about management and strategy more than it is about building software. Any business and any team can learn lessons from how Facebook organizes the entire organization around speed. Everything. Culture. Tools. Processes. And even how people join teams. After you read this book, you will think differently about how you might organize your team or company. More about Jeff:His book: Move Face: How Facebook Builds Software - https://www.amazon.com/Move-Fast-Facebook-Builds-Software-ebook/dp/B093HMJ4KB/ref=sr_1_1?dchild=1&keywords=move+fast&qid=1628641198&sr=8-1His podcast: Software Engineering Daily - https://softwareengineeringdaily.com/ Get on the email list at helpingsells.substack.com
Stackblitz CEO Eric Simons and Jeff Meyerson discuss a serious vulnerability in React. Also available on Dropbox, please download this. https://www.dropbox.com/s/9u0m52xj04vqggc/React%20Vulnerability%20with%20Eric%20Simons.mp3?dl=0 The post React Vulnerability with Eric Simons appeared first on Software Engineering Daily.
Facebook is one of the most successful companies in the world, and Jeff Meyerson, the Founder of Software Daily, spend two and a half years talking to Facebook's top engineers to discover how they fit product, culture, and strategy together to succeed. Jeff joined Dev Interrupted to give us the founding story of Software Daily, the secrets to success at Facebook he learned while writing his new book Move Fast: How Facebook Builds Software., the inside scoop on his new company SuperCompute, and his secrets to leveraging his pokers skills in business and in software engineering. Join our Discord Community ►► discord.gg/devinterruptedOur Website ►► devinterrupted.com/Want to attend the New Leaders of Remote Work Panel? https://linearb.io/new-leaders-remote-work-panel/Want to try LinearB? ►► Book a LinearB DemoHave 60 seconds? Review the show on Apple Podcasts
https://www.linkedin.com/in/jeff-meyerson-05275716/ https://www.amazon.com/Move-Fast-Facebook-Builds-Software-ebook/dp/B093HMJ4KB
Facebook CEO Mark Zuckerberg told employees recently that the company's long-term goal is to "bring the metaverse to life" — helping to create an interconnected world of physical, virtual and augmented reality spaces that will reshape the way we work, interact with each other, create new things, and generally experience life. So how exactly will Facebook approach such an audacious plan? A new book called "Move Fast: How Facebook Builds Software" doesn't delve into the metaverse, specifically. But in looking at Facebook's engineering practices — the way the company makes stuff — the book examines the digital DNA of the social network, sheds new light on its most infamous motto, and explains the inner workings of a company that wants to reshape the human experience, again. Facebook influences the engineering culture and economy not just in its hometown of Menlo Park, Calif., but also in its development offices in the Seattle area, where it employs 7,000 people. And of course, ultimately, Facebook's internal practices end up influencing people around the world who use its products. On this episode of the GeekWire Podcast, we talk with the author of the book, Jeff Meyerson, the longtime host of the Software Engineering Daily podcast, about the ways Facebook, Microsoft, Amazon and Google make things, and what those different approaches tell us about where they're taking us. Audio editing by Curt Milton, theme music by Daniel L.K. Caldwell. See omnystudio.com/listener for privacy information.
This week on the podcast I chat with the endlessly fascinating Jeff Meyerson. Jeff is the author of Move Fast, he's written 7 albums (The Prion on Spotify), he was a professional Magic: The Gathering player, a professional poker player, a software engineer at Amazon, he's currently a prolific podcaster, and the founder of countless projects, including Supercompute and Rectangle.This conversation really stretched my mind and introduced some concepts, such as the wooden computer, that I had never encountered before. I hope you enjoy this conversation as much as I did!More from Jeff- Move Fast: How Facebook Builds Software- Software Daily- The Prion - SimulationFind the full transcript and more at BYLT.co/jeff-meyersonAs always, this episode of Starting Now is brought to you by BYLT. At BYLT we help you get started online. Whether you want to start a blog or a business head on over to BYLT.co to get started.Subscribe to Starting Now on Apple Podcasts, Spotify, or wherever you listen to podcasts. Also watch the video interview on YouTube.And, finally, if you're enjoying our podcasts and care to learn more about us, at SPYR we build minimalist businesses and we help you start your own at BYLT.———————————————————————Some of the links above may be affiliate links which means that I earn a small commission from qualifying purchases at no additional cost to you.
In this episode we discuss the new Move Fast book, as well as many aspects of the current state of software engineering. Daliana Liu interviews Jeff Meyerson, host of Software Daily and author of Move Fast. This interview was also recorded as a video podcast. Check out the video on the Software Daily YouTube channel. The post Move Fast with Jeff Meyerson appeared first on Software Engineering Daily.
In this episode we discuss the new Move Fast book, as well as many aspects of the current state of software engineering. Daliana Liu interviews Jeff Meyerson, host of Software Daily and author of Move Fast. This interview was also recorded as a video podcast. Check out the video on the Software Daily YouTube channel. The post Move Fast with Jeff Meyerson appeared first on Software Engineering Daily.
In this episode we discuss the new Move Fast book, as well as many aspects of the current state of software engineering. Daliana Liu interviews Jeff Meyerson, host of Software Daily and author of Move Fast. This interview was also recorded as a video podcast. Check out the video on the Software Daily YouTube channel. The post Move Fast with Jeff Meyerson appeared first on Software Engineering Daily.
In this episode we discuss the new Move Fast book, as well as many aspects of the current state of software engineering. Daliana Liu interviews Jeff Meyerson, host of Software Daily and author of Move Fast. This interview was also recorded as a video podcast. Check out the video on the Software Daily YouTube channel.
Love it or hate it, Facebook has done incredible things. Although a lot of narrative stories have been told about the company, little has been said about its strategies, until now. Jeff Meyerson ... The post Move Fast: Jeff Meyerson appeared first on Author Hour.
Today's guest is Jeff Meyerson, host of the Software Engineering Daily Podcast. Max and Jeff talk about his talk last year “You are not a commodity” to software engineers, the assembly line mentality, remote work, and podcasting in general.
Welcome to another episode of Develomentor. Today's guest is Jeff Meyerson. Jeffrey Meyerson is the creator and host of the podcast Software Engineering Daily (@software_daily). He is also the founder of FindCollabs, a platform to find collaborators for ventures.Jeff definitely took a non-traditional path to software engineering. Before getting his degree he played poker professionally for 3 years and then became a poker coach!Post-college, he worked at a number of software companies including Amazon and eBay as an engineer. Pretty quickly, Jeff realized that he prefers to work for himself. These days he is a podcaster, founder, and investor. Click Here –> For more information about tech careersIn this episode we’ll cover:Why did Jeff start his tech podcast, Software Engineering Daily? How does it make money?What should you do if you feel out of place in tech? Is it worth it getting a remote job so that you can have more flexibility?Where is the podcast space headed? Is it saturated or is there still room to grow?Additional ResourcesSoftware Engineering Radio - Podcast by Robert Blumen. https://www.indiehackers.com - A good place to learn how to start a small businesshttps://www.indiehackers.com/podcast/114-jeff-meyerson-of-software-engineering-daily - Interview with Jeff Meyerson about podcasting!Charles Max Wood – From Programmer to Full-Time Podcast Wiz - Episode 31 of DevelomentorYou can find more resources in the show notesTo learn more about our podcast go to https://develomentor.com/To listen to previous episodes go to https://develomentor.com/blog/Follow Jeff MeyersonTwitter: @the_prionFollow Software Engineering Daily @software_dailyLinkedIn: linkedin.com/in/jeff-meyerson-05275716/Follow Develomentor:Twitter: @develomentorFollow Grant IngersollTwitter: @gsingersLinkedIn: linkedin.com/in/grantingersoll
Johanna Rothman on Programming Leadership, Thomas “Tido” Carriero on Product Love, Adam Davidson on Lead From The Heart, Josh Wills on Software Engineering Daily, and Amitai Schleier on Programming Leadership. I’d love for you to email me with any comments about the show or any suggestions for podcasts I might want to feature. Email podcast@thekguy.com. And, if you haven’t done it already, don’t forget to hit the subscribe button, and if you like the show, please tell a friend or co-worker who might be interested. This episode covers the five podcast episodes I found most interesting and wanted to share links to during the two week period starting January 20, 2020. These podcast episodes may have been released much earlier, but this was the fortnight when I started sharing links to them to my social network followers. JOHANNA ROTHMAN ON PROGRAMMING LEADERSHIP The Programming Leadership podcast featured Johanna Rothman with host Marcus Blankenship. Marcus started out by asking Johanna why it is important to think about managing ourselves. Johanna says that when we don’t manage ourselves, we don’t have the capability to manage other people. For example, if we insist on micro-managing people, they cannot grow and we prevent them from doing their best work. Marcus asked her what micromanagement has to do with managing ourselves. Johanna says that micromanagement comes from fear. You need to learn to manage yourself to manage this fear and reduce your need to micromanage. She says the reason the first book is about managing yourself is that if you can avoid doing the things that make people feel badly, you can create an environment where people can excel. They talked about surveys and Marcus asked Johanna’s opinion on anonymous versus named survey responses. Johanna says that when you have a culture where there is a lot of blaming and micromanagement and little coaching, she would recommend an anonymous survey. Marcus talked about how technical managers often know how to do the work itself very well and he asked Johanna when this can trip us up. One way it trips us up, she says, is that people on the team don’t get a chance to practice if the manager is writing code instead of managing. Second, when you have not been in the code in a while, you do not know what it looks like anymore. Marcus asked how managers can get time to think in today’s high time-pressure environments. Johanna says that if you are spending a lot of time in meetings, you should be looking at whether you can delegate any of those meetings to the people doing the work. This delegating is not sloughing off your responsibilities, but making sure you are not part of a team that you are not supposed to be a part of. Apple Podcasts link: https://podcasts.apple.com/ca/podcast/becoming-better-manager-means-starting-yourself-johanna/id1461916939?i=1000460138590 Website link: https://programmingleadership.podbean.com/e/becoming-a-better-manager-means-starting-with-yourself-with-johanna-rothman/ THOMAS “TIDO” CARRIERO ON PRODUCT LOVE The Product Love podcast featured Thomas “Tido” Carriero with host Eric Boduch. Tido oversees all of engineering, product, and design at Segment. Segment provides customer data infrastructure or CDI, helping companies collect, unify, and connect data about their own interactions with their customers. It gives these companies a unified view of their customer data across all channels. When he joined Segment, Tido was blown away by how robust the ecosystem was and by the attractive idea of empowering business teams, marketing teams, and product teams by installing application tracking once and being able to turn on integrations with the flick of a switch. Often, he says, a lot of business and marketing and less technical folks are blocked from doing the best job they could do because of tough integration problems that Segment solves. Segment naturally has a lot of adjacencies. They touch critical customer data and they need to decide whether to use that to empower engineering, marketing, or others. This requires being clear at the beginning of the year that they will pick two or three bets as an organization to focus on. Eric asked Tido what product leaders often do wrong. Tido says the biggest mistake product leaders make by far is not looking in the mirror and making an honest assessment of where things are. Getting attached to an idea makes it harder to give it a critical look. Often, you’re only a small pivot away from a valuable product. As the leader of an organization, he sees his job as creating a culture where failure is not just okay but celebrated. If people are getting slapped on the hand for failure, they will just get even more committed to their first ideas. Healthy teams that seriously innovate look at the data and are willing to pivot when it tells them unpleasant things. Apple Podcasts link: https://podcasts.apple.com/ca/podcast/thomas-tido-carriero-joins-product-love-to-talk-about/id1343610309?i=1000459980786 Website link: https://www.spreaker.com/user/casted/edited-tido-joins-product-love-mp3 ADAM DAVIDSON ON LEAD FROM THE HEART The Lead From The Heart podcast featured Adam Davidson with host Mark C. Crowley. Adam Davidson is the creator of the Planet Money podcast and is staff business writer at The New Yorker. He has a new book called The Passion Economy. The theme of the book is that choosing your career used to mean choosing between work that makes your heart sing and work that pays well but disconnects you from your passions, but the new world order demands that we follow our passions and pursue work that leverages both our talents and our interests. Adam’s grandfather worked his entire career in a ball bearing factory and only made a good living by working double shifts. He believed that people who follow their passions go nowhere in life. Adam’s father was the opposite. Making money was far less important to him than following his dream of performing as a Broadway actor. These two men represent the dichotomy of having to choose financial success or your passion but not both. The people of Adam’s father’s generation and his grandfather’s generation had to choose between a life of passion and a life of financial success, but people today, Adam says, are lucky. They are lucky for the reasons that terrify us. Adam says, “All of these forces that have done so much damage to the stability of the 20th century economy also provide exactly the tools that allow us to figure out what we uniquely love and are good at and find those people, even if they’re thinly spread all over the country or all over the globe, who also crave what it is we can provide and are willing to pay for it.” Mark summed up the book as being about combining your training and expertise with a personal passion to find your own niche. According to Adam, some people take a total left turn and go into a completely different field later in their lives, but the most successful people he has met combine their passion with the skills they have previously acquired. Apple Podcasts link: https://podcasts.apple.com/ca/podcast/adam-davidson-new-rules-for-thriving-in-twenty-first/id1365633369?i=1000462188105 Website link: https://blubrry.com/leadfromtheheartpodcast/54035306/adam-davidson-the-new-rules-for-thriving-in-the-twenty-first-century/ JOSH WILLS ON SOFTWARE ENGINEERING DAILY The Software Engineering Daily podcast featured Josh Wills with host Jeff Meyerson. Josh Wills was the director of data engineering at Slack when Slack was building out a solution to scaling its data infrastructure. When the first analysts at Slack were hired, their only option was to spin up their own little databases that had cached copies of Slack’s main transactional database. Eventually, Slack hired data engineers that built systems that could scale up what an analyst could do. They built up a lot of infrastructure involving Airflow jobs producing Parquet files on S3 that were queryable through tools like Presto and it was, according to Josh, a “ghost city” for a while. All the while, the analytics team was still using the existing infrastructure of ETL jobs running on the transactional database. It wasn’t until Slack started aggressively hiring analysts, data scientists, and engineers from the Googles, Facebooks, and Twitters of the world that they had people who knew how to use the stuff Josh and his team were building. Jeff asked how the various design philosophies coming from the new hires from Google and Facebook got resolved. Josh said it got resolved by him making all the decisions. There were a million things to do, so the design direction was often the result of whoever was the first mover. If Josh had it all to do over again, he would do many things differently, but he knows that nobody would appreciate it because they would have never experienced the inferior designs. It is hard to appreciate the pain that something saved you. Most of your good decisions are invisible and taken for granted while your bad decisions cause pain and suffering forever. Apple Podcasts link: https://podcasts.apple.com/ca/podcast/slack-data-platform-with-josh-wills/id1019576853?i=1000462100792 Website link: https://softwareengineeringdaily.com/2020/01/10/slack-data-platform-with-josh-wills/ AMITAI SCHLEIER ON PROGRAMMING LEADERSHIP The Programming Leadership podcast featured Amitai Schleier with host Marcus Blankenship. Amitai talked to Marcus about his fork of qmail called notqmail. Qmail is a Unix program for running an email server that, unfortunately, hasn’t been updated in twenty years and has a number of rough edges. Over the last twenty years, Amitai has invested time into softening qmail’s rough edges through improved package management. More recently, Amitai started thinking about getting the people who are working on their own forks of qmail to collaborate on a single fork. The first step was getting some advice. A key piece of advice came from Llewellyn Falco. Llewellyn said, “Qmail already has a lot of nice seams and interfaces. Without too much more work and risk, you could add a couple more seams so that whatever modernization is required could be done as plugins or extensions. The next problem to think about is egos. Not all ideas are going to win.” He then gave Amitai the best piece of advice: “Whatever you do, offer yourself to other programmers to get their code converted to extensions first. As to which implementation of a particular new feature is to be incorporated, that decision is not your call. Take as extensions as many implementations as people want to give and let users decide.” Marcus asked about how to influence a group of people on a project without being coercive. Amitai says that he discovered years ago that when a situation is a little confused, his default response is to seek to lower his perceived social status. Otherwise, he cannot influence the way he wants to if he’s a big shot that people are supposed to listen to. Apple Podcasts link: https://podcasts.apple.com/ca/podcast/collaboration-and-notqmail-with-amitai-schleier/id1461916939?i=1000462047766 Website link: https://programmingleadership.podbean.com/e/collaboration-and-notqmail-with-amitai-schleier/ LINKS Ask questions, make comments, and let your voice be heard by emailing podcast@thekguy.com. Twitter: https://twitter.com/thekguy LinkedIn: https://www.linkedin.com/in/keithmmcdonald/ Facebook: https://www.facebook.com/thekguypage Instagram: https://www.instagram.com/the_k_guy/ YouTube: https://www.youtube.com/c/TheKGuy Website:
Jeff Meyerson, host of Software Engineering Daily, and the founder of FindCollabs (a place to find collaborators for open source software) joined the show to talk about living in San Francisco, his thoughts on podcasting and where the medium is heading, getting through large scale market changes. We talk at length about his new project FindCollabs, the difficulty of reliably finding people to collaborate with, the importance of reputation and ratings systems, and his invite to this audience to check out what he’s doing and get involved.
Jeff Meyerson, host of Software Engineering Daily, and the founder of FindCollabs (a place to find collaborators for open source software) joined the show to talk about living in San Francisco, his thoughts on podcasting and where the medium is heading, getting through large scale market changes. We talk at length about his new project FindCollabs, the difficulty of reliably finding people to collaborate with, the importance of reputation and ratings systems, and his invite to this audience to check out what he’s doing and get involved.
Esther Derby on Drunken PM, Justin Searls on Maintainable, Lena Ross and Dr. Jen Frahm on Agile Uprising, Dr. Nicole Forsgren on Screaming In The Cloud, and Courtland Allen on Software Engineering Daily. I’d love for you to email me with any comments about the show or any suggestions for podcasts I might want to feature. Email podcast@thekguy.com. And, if you haven’t done it already, don’t forget to hit the subscribe button, and if you like the show, please tell a friend or co-worker who might be interested. This episode covers the five podcast episodes I found most interesting and wanted to share links to during the two week period starting October 28, 2019. These podcast episodes may have been released much earlier, but this was the fortnight when I started sharing links to them to my social network followers. ESTHER DERBY ON DRUNKEN PM The Drunken PM podcast featured Esther Derby with host Dave Prior. Dave asked about Esther’s new book, “7 Rules for Positive, Productive Change: Micro Shifts, Macro Results” (https://www.amazon.com/Rules-Positive-Productive-Change-Results/dp/1523085797). She says it is a guide for people who need to bring change to their organizations, whether or not they have “change management” in their title. Esther told the story about getting a call from a company that had sent everyone to three days of Agile training, but then mandated that the company-wide process would now be “Agile” and any changes would need to be approved by the software engineering process group. They solidified things when they knew, if not the least, very little. She thinks these kinds of stories keep happening because we are suffering from a hangover of mechanistic thinking where we view our organizations as machines and we can just install a change like swapping out a part. Esther says that often when people try to create change, they don’t think enough about what they want to retain. This reminded me of something Tom DeMarco wrote in his book Slack when talking about vision: “Successful change can only come in the context of a clear understanding of what may never change, what the organization stands for. This is what Peter Drucker calls the organization’s culture. Culture, as he uses the term, is that which cannot, will not, and must not change.” She also says that people forget that they are not working on a blank slate. Whatever they do, they are putting it on top of existing traditions, reward structures, policies, and patterns of relationship, and the new thing is going to interact with that in unpredictable ways. They talked about cognitive empathy and being able to explain something like the Agile Manifesto to somebody who hasn’t experienced traditional project management. Esther talked about a client in the Dominican Republic that mostly hires people straight out of school and is particularly adept at collaboration because they haven’t had years of being rewarded for individual accomplishments take away their natural desire to work collaboratively. She likened this to the traits that are often associated with Millennials and how these are actually good traits to have. Apple Podcasts link: https://podcasts.apple.com/ca/podcast/7-rules-for-positive-productive-change-w-esther-derby/id1121124593?i=1000449914205 Website link: https://soundcloud.com/drunkenpmradio/7-rules-for-positive-productive-change-w-esther-derby JUSTIN SEARLS ON MAINTAINABLE The Maintainable podcast featured Justin Searls with host Robby Russell. Robbie started by asking Justin what he thinks makes for a well-maintained codebase. Justin evaluates codebases as his job, so he has a process he follows. He starts outside-in. He looks at common things like the readme or other documentation and evaluates how easily he can get up-and-running. This is important because it says something about how often they on-board new people and whether they improve this aspect of their process. The second thing he looks at is what dependencies the codebase is using. He checks that dependencies are up-to-date and whether there are many or few dependencies. He tries to identify whether the team tends to rely on third-party libraries frequently or build their own. Next, he evaluates application-specific aspects of the codebase. If it is a web application, for example, he will evaluate the complexity of the routes. He’s checking that things are named clearly and kept small and whether the team prioritizes organization or not. After he feels that he has his bearings, he looks at statistics like churn to identify hotspots like god objects. That’s just what he gets from looking at the code. He says you can learn a lot from how the team communicates too. High-performing teams, he says, describe what their system does in humble, plain language, whereas the more technical and convoluted a team makes their applications sound, the more likely the team is attempting to imbue their application with unearned significance and this ends up creating barriers to understanding. Justin says that, as he has gotten further removed from the details of software delivery, he has begun to empathize with product managers and business managers for whom words like refactoring and technical debt have become four-letter words because all they’ve ever heard these words used for is excuses for why work isn’t getting done. Justin says that many programmers are often thrust into roles of professional responsibility well in advance of their ability to cogently and calmly understand and describe exactly what a system is doing. The combination of a high-pressure environment with a shaky understanding of the fundamentals of the software the engineer just built limits their ability to explain why things are taking longer than expected without resorting to language like technical debt. He calls this “obfuscating the conversation up a layer.” He talked about the challenges he faced when the industry transitioned around 2011 from largely co-located teams to asynchronous GitHub-based workflows and eventually to using tools like Slack for communication. He said that he didn’t realize at first just how much textual communication is read differently from being in a room with somebody. Apple Podcasts link: https://podcasts.apple.com/ca/podcast/justin-searls-learn-to-understand-the-runtime/id1459893010?i=1000453441400 Website link: https://maintainable.fm/episodes/justin-searls-learn-to-understand-the-runtime-C6e05XWb LENA ROSS AND DR. JEN FRAHM ON AGILE UPRISING The Agile Uprising podcast featuring Lena Ross and Dr. Jen Frahm with host Andy Cleff. They started the conversation by talking about John Cutler’s blog post, “The Patient Change Agent” (https://medium.com/hackernoon/the-patient-change-agent-fd8548f04777) that caused Jen to rethink change resilience. Jen was running resilience workshops at a client at the time and was using Lois Kelly’s work on “change muscles” (http://foghound.com/blog/2016/3/29/build-the-change-musclesbuild-the-change-muscles). A particularly fearless change agent in the workshop told her she had it all wrong: she was using resilience from the perspective of “bracing for change” but needed to be working with resilience in the sense of “renewal”. Jen talked about the distinction between the Agile coach and the organizational change agent. The Agile coach is product development team-focused while the organizational change manager works beyond that. She sees many Agile coaches that do not address the impacts of releasing whatever the team is producing to operations. Andy asked his guests how they bring executives on board in supporting Agile transformations. Jen says she sees executives trying to do full Agile transformations company-wide and they are struggling to understand how much involvement they should have. These leaders need to find someone they trust who has the technology domain expertise to help them. Lena added that, in the last two years, she has seen that leaders are starting to understand enterprise agility. The old practices that served them well in the past aren’t cutting it anymore. They are realizing that they need to reach out and ask for help. Andy pointed out that asking for help and admitting they don’t know something requires a great deal of vulnerability from executives and asked Lena and Jen how they, as consultants, bring this about. Jen says you need to start by meeting with executives one-on-one and you need to be able to role model vulnerability in front of them. You use strength-based language to make them feel safe and you bring in threads from the conversations you’ve had with others so that they know they are not alone. She has also found a lot of success by running breakfasts with the executive team after she has already established trust. These breakfasts serve as safe environments where she role models and facilitates conflict and constructive conversations. Andy said it sounds like Jen is building empathy at the leadership layer. Jen agreed that it is empathy, but added that it is invitation-based. She doesn’t tell people that they must have the conversation; she invites them to consider the concepts. She then spoke about recently rethinking the notion of empathy as a result of mindful self-compassion training. Apple Podcasts link: https://podcasts.apple.com/ca/podcast/empathy-and-resilience-in-leadership/id1163230424?i=1000451652567 Website link: http://agileuprising.libsyn.com/empathy-and-resilience-in-leadership DR. NICOLE FORSGREN ON SCREAMING IN THE CLOUD The Screaming In The Cloud podcast featured Dr. Nicole Forsgren with host Corey Quinn. This was the second part of a conversation with Dr. Forsgren. In the first part, they discussed the latest State of DevOps report. This episode focused more on the new cloud-specific section of the State of DevOps report. She quickly summarized what the overall report found about high and low performers and listed several things low performers can do to become high performers: invest in continuous delivery and automation, work in small batches, invest in observability and monitoring, develop a generative culture, and finally, make use of cloud computing. The big problem with cloud computing, she says, is that so many people keep redefining “cloud” in a million ways. Without a precise definition of what it means to use “the cloud”, there is no way to be able to give a statistically significant answer about whether and by how much it improves an organization’s performance. So she chose to use the NIST definition for cloud computing and its five characteristics. Measured this way, elite performers are twenty-four times more likely to be executing on all five characteristics. Compared to the total number of organizations that say they are using cloud computing, only 29% of them are meeting all five characteristics. Nicole started describing the five characteristics. The first is on demand self-service. You have to be able to automatically provision your compute resources without human interaction. You can’t be putting them behind a “service down” ticket that you wait for someone to approve. The second is broad network access - can you access it from multiple devices? The third is resource pooling - are the provider resources pooled in a multi-tenant model where resources are dynamically assigned on demand? The fourth is rapid elasticity - can you handle a Black Friday situation? The fifth is measured services - systems can automatically control, optimize, and report resource use and that’s all you’re paying for. She notes that these are all architectural outcomes, design outcomes, and automation outcomes. Regardless of whether you are on public cloud, private cloud, or even a mainframe environment, you can still improve your software delivery performance by architecting your infrastructure with these outcomes in mind. Apple Podcasts link: https://podcasts.apple.com/ca/podcast/five-characteristics-that-define-cloud-nicole-forsgren/id1361244178?i=1000452015823 Website link: https://share.transistor.fm/s/3e21ecc7 COURTLAND ALLEN ON SOFTWARE ENGINEERING DAILY The Software Engineering Daily podcast featured Courtland Allen with host Jeff Meyerson. They talked about the changes to Courtland’s Indie Hackers business that occurred over the past three years. The first was that three years ago, there was no Indie Hackers podcast. There was just the website. Today, the podcast is bigger than the website. Also back then, Indie Hackers was its own business and today it is part of Stripe. Courtland talked about how Indie Hackers went from a media company to a platform and community. The core of any community, he says, is people who are empowered and able to help each other out. Indie Hackers is all about people starting internet businesses and helping each other overcome the challenges of doing so. To start Indie Hackers, Courtland followed the Reddit playbook. He created a forum, made a bunch of fake threads, made a bunch of fake accounts, talked to himself a lot, occasionally trapped a real person into a conversation with three Courtlands, and before long there were two, then three people talking to a bunch of Courtlands. Eventually, it becomes self-sustaining. His recommendation is to shrink time and space around the community so that it feels active and lively. You want to restrict space around your community online for the same reason that if you’re having a party for only ten people, you don’t hold it in an auditorium. Offline communities are usually easy to restrict in both time and space; you have a meeting time and a place. If you’re going to have a poker game on Wednesday night at six, even if nobody is participating in this poker community any other time, if everyone is at the game on Wednesday, it feels like a lively community. To achieve the same feel online, instead of creating a forum or a message board, do something like posing a question every Friday that community members answer. People will observe a thriving community even if it has only fifteen or twenty people. Apple Podcasts link: https://podcasts.apple.com/ca/podcast/indie-hackers-3-years-later-with-courtland-allen/id1019576853?i=1000452268869 Website link: https://softwareengineeringdaily.com/2019/10/04/indie-hackers-3-years-later-with-courtland-allen/ LINKS Ask questions, make comments, and let your voice be heard by emailing podcast@thekguy.com. Twitter: https://twitter.com/thekguy LinkedIn: https://www.linkedin.com/in/keithmmcdonald/ Facebook: https://www.facebook.com/thekguypage Instagram: https://www.instagram.com/the_k_guy/ YouTube: https://www.youtube.com/c/TheKGuy Website:
We are republishing a podcast from the freeCodeCamp Podcast as a weekend episode. Jeff Meyerson is the creator and host of the Software Engineering Daily podcast. Jeff grew up in Texas. He spent most of his childhood playing competitive strategy games like Magic: the Gathering. This lead him to making a lot of money – The post freeCodeCamp’s Quincy Larson interviews Jeff Meyerson appeared first on Software Engineering Daily.
Quincy interviews Jeff Meyerson, the creator and host of the Software Engineering Daily podcast. Jeff grew up in Texas, played competitive poker, and ultimately worked as a software engineer at Amazon. We talk about how he got into tech, how left Amazon to become an entrepreneur, and the many lessons he learned along the way. Follow Jeff on Twitter: https://twitter.com/the_prion And subscribe to software engineering daily: https://softwareengineeringdaily.com
Host: Charles Max Wood of JavaScript Jabber Joined by Special Guest: Jeffrey Meyerson Jeffrey Meyerson, founder of FindCollabs and host at Software Engineering Daily joins Charles Max Wood for a discussion about latest trends in the developer world, ways of monetizing podcasts, and finding ads for podcasts. Jeffrey shares how he started to host podcasts and how he became The post JavaScript Jabber with Jeff Meyerson appeared first on Software Engineering Daily.
Will Larson on Greater Than Code, Marcus Blankenship on Software Engineering Radio, Sonal Chokshi on Software Engineering Daily, Roman Pichler on Being Human, and Dave Thomas and Andy Hunt on Hanselminutes. I’d love for you to email me with any comments about the show or any suggestions for podcasts I might want to feature. Email podcast@thekguy.com. And, if you haven’t done it already, don’t forget to hit the subscribe button. This episode covers the five podcast episodes I found most interesting and wanted to share links to during the two week period starting September 2, 2019. These podcast episodes may have been released much earlier, but this was the fortnight when I started sharing links to them to my social network followers. WILL LARSON ON GREATER THAN CODE The Greater Than Code podcast featured Will Larson with hosts Jessica Kerr, Arty Starr, and Rein Henrichs. Will talked about systems thinking, specifically referencing Donella Meadows’ Thinking in Systems: A Primer. As a sixteen-year-old, he was exposed to systems thinking by his economics professor father. They talked about how to bring about change in complex systems and Rein brought up Virginia Satir’s change model. They talked about various forms of dysfunction, with an example being tasks that are marked as completed by developers without first doing the work of validation. Will’s own example is that executives never miss their goals; they just redefine the goals so that they hit them. There is a certain level of seniority where you can never be held accountable because you are the accountability function. Getting back into the topic of how to change complex systems, Will referenced the book, The First 90 Days as a great explanation of the need to go slow and observe before you try to change things. He says that the “great man theory” has been out of style for decades in the study of history, but is still in style in tech as the most causal way to understand how change works and also the most comforting. Rein talked about how the heroic individual myth is the other side of the coin to the scapegoat. Just as you pile all the blame onto the scapegoat, you pile all the credit onto the hero. He says that cultures that engage in hero myth-building are also likely to engage in scapegoating. Will says he himself has not seen much scapegoating at the companies he works at, likely because those cultures were unwilling to hold folks accountable for their work, but he has seen the hero myth at every company he has worked. Will then spoke about the 10x engineer myth. Will says he meets people who have been in tech for six or seven years who have the idea that they are almost done with their career. It may be due to the “senior engineer after two years” phenomenon where the career path is not well-defined and a lot of companies don’t know how to take advantage of the skills of people with 15 to 20 years of experience. A second reason is that the industry is an overwhelming and draining environment and people choose to opt out of it. As a result, we have very few engineers who have been around long enough to witness the long-term consequences of their brilliant ideas. Apple Podcasts link: https://podcasts.apple.com/ca/podcast/142-modeling-constraints-in-human-systems-with-will-larson/id1163023878?i=1000446345964 Website link: https://www.greaterthancode.com/modeling-constraints-in-human-systems MARCUS BLANKENSHIP ON SOFTWARE ENGINEERING RADIO The Software Engineering Radio podcast featured Marcus Blankenship with host Travis Kimmel. They talked about motivation, specifically motivation of engineering teams. Marcus says that motivation is the desire to get things done and every engineer coming out of school is motivated from day one. If you get one of these people hired onto your team and, two years later, they are demotivated, suffering from PTSD, scared to offer ideas, and figuring they are just a cog in a machine, your problem is your company or your team, not the engineer you hired. Marcus says he is doing secret research on motivation as he is now interviewing candidates for a job and asking them why they are looking to leave their current job. Nobody says, “Pay.” Often the answer is a lack of alignment with their boss or their company, resulting in the engineer losing the desire to contribute because of a relationship problem. These engineers are not stick-in-the-muds that are angry they don’t get to use COBOL anymore. Something happened where instead of having their ideas valued and heard and being part of the discussion, they somehow got disconnected from their boss. In the seventies, Marcus says, researchers discovered a strong correlation between positive employer-employee relationships and the amount of job satisfaction, quality of work, turnover intentions, and amount of promotions. We are thirty-five years into a few thousand scientific studies that continue to prove that the relationship one has with one’s supervisor matters more than any other factor when it comes to job performance and job satisfaction. Marcus says that a supervisor’s one true job is to create a trusting relationship with the people that report to you. Travis shared his own experience in having one-on-ones with his supervisors that felt to him like they were trying to artificial manufacturing a relationship because there was no indication of what the goal of the meeting was. Marcus says that good one-on-ones are bi-directional. One-on-ones in which the boss just gets status updates from the subordinate and gives new marching orders are often dissatisfying for both parties. Another flawed kind of one-on-one is where it is all about the employee. Such one-on-ones are not effective and neither party likes these either. Marcus suggests that we apply to our one-on-ones the same Agile thinking that we apply to our work. Every month, at one of your one-on-ones, do a retro on the one-on-one. Talk about why you are doing them, what value you’re getting from them, and how to make them better. They talked about psychological safety. Marcus says a lot of managers don’t realize that they are not in a good position to measure psychological safety based on their own gut. He says tools like Claire Lew’s knowyourteam.com, officevibe.com, and other anonymous survey tools can help. When we become a manager or team lead that has you supervising or leading, we forget that we are in a position of power. Travis added that leaders need to be careful about what they say casually so that it doesn’t get taken as a mandate. Apple Podcasts link: https://podcasts.apple.com/ca/podcast/episode-374-marcus-blankenship-on-motivating-programmers/id120906714?i=1000445260176 Website link: https://www.se-radio.net/2019/07/episode-374-marcus-blankenship-on-motivating-programmers/ SONAL CHOKSHI ON SOFTWARE ENGINEERING DAILY The Software Engineering Daily podcast featured a16z podcast host Sonal Chokshi with host Jeff Meyerson. Jeff started out by asking why a VC firm decided to start a podcast. Sonal says that a16z has always had a culture of writing, blogging, and sharing ideas. This led them to develop an editorial operation from which the podcast naturally followed. Jeff asked what lessons from blogging apply to podcasting. Sonal sees podcasting as the next evolution of blogging because of its similar intimacy and a similar feeling of authenticity. The difference, she says, is that podcasting is a community and a movement. Sonal talked about her favorite a16z episodes, including an episode on emojis. She loved it because everybody understands how to use emojis but there is a lot of deep tech and governance involved in making emojis possible. That episode, she said, encapsulates the whole a16z podcast: the intersection of technology, people, politics, context, culture, and humanity. Jeff brought up a16z’s connection to Mike Ovitz’s Creative Artists Agency. Having read Ovitz’s book and noticed how it portrays Ovitz as a workaholic, Jeff asked Sonal how she finds balance while drinking from the addicting technological firehose. Sonal says there is a lack of nuance in the debates about screen time and work/life balance. Apple Podcasts link: https://podcasts.apple.com/ca/podcast/a16z-podcasting-with-sonal-chokshi/id1019576853?i=1000446547922 Website link: https://softwareengineeringdaily.com/2019/08/09/a16z-podcasting-with-sonal-chokshi/ ROMAN PICHLER ON BEING HUMAN The Being Human podcast featured Roman Pichler with host Richard Atherton. Richard asked Roman what a product manager is. Roman says a product manager is someone who takes an idea and helps bring it to life, launch it, make it successful, and keep it successful. Richard asked about the distinction between a product manager and Scrum’s notion of product owner. Roman sees the product owner as a product management role, but methodologies like SAFe have redefined the product owner to be a tactical role, misunderstanding the intention behind the role and the practicalities such as answering questions from the dev team, refining backlog items, and answering support and sales questions. He says there is too much focus on the details and this risks losing sight of the big picture. To do a good job for users and for the business, Roman says it is helpful to have people looking after digital assets with the right qualifications, skills, organizational support, authority, and autonomy. He says the term “mini-CEO” appeals to some product people because it indicates that product people need a certain level of authority, but a CEO would have marketing and sales functions under their control and product people do not. Richard asked what talents Roman had to develop to be a great product person. Roman started out as a programmer and began to help business groups come up with new products. What helped him most was to boost his own understanding of how business works and the second most important element was letting go of being interested in how digital products work and focusing instead on who benefits from them. Apple Podcasts link: https://podcasts.apple.com/ca/podcast/72-to-manage-products-is-to-care-with-roman-pichler/id1369745673?i=1000446514943 Website link: http://media.cdn.shoutengine.com/podcasts/4081235a-554f-4a8f-90c2-77dc3b58051f/audio/9b2501e7-e618-46f6-8f41-abd69c871211.mp3 DAVE THOMAS AND ANDY HUNT ON HANSELMINUTES The Hanselminutes podcast featured Dave Thomas and Andy Hunt with host Scott Hanselman. Scott started by asking whether Dave and Andy knew at the time they wrote the Pragmatic Programmer 20 years ago that they were writing what would become a seminal work. Dave said that both of them were stunned by its success. The book was intended as a way to clarify their own thoughts based on their experiences as consultants in which their clients all had the same kinds of problems: inconsistent builds, the shipping of untested code, and impossible-to-change designs. Scott asked about the importance of the name of the book. Andy said that there was a strain of thought at the time the book was written that was dogmatic and they deliberately pushed against such approaches. Dave pointed out that this was harder on their readers because it forced them to figure out for themselves what works for them. They got into a discussion of what kind of educational background one needs to be a successful programmer. Dave revealed that he is currently teaching classes at SMU to, he says, corrupt the youth by teaching them things like functional programming, and because traditional computer science education is poorly serving the industry and the student. People are coming out of university with tens or hundreds of thousands of dollars of debt and, in terms of their value in the industry, they are not much different from people who are coming out of eight-week bootcamps. He teaches third or fourth year undergraduates and graduate students and he has found that none have been shown any form of testing. He would much rather hire someone who had the right attitude, was smart, and who could talk to people and he could show such a person how to code while on the job. Andy added that he gets the feeling that most computer science programs are there to teach you to become a professor of computer science rather than a problem-solver. What Andy says people need to learn, and what university education is not providing, are problem-solving skills. Apple Podcasts link: https://podcasts.apple.com/ca/podcast/pragmatic-programmer-celebrates-20-years-dave-thomas/id117488860?i=1000446461596 Website link: https://hanselminutes.simplecast.com/episodes/the-pragmatic-programmer-celebrates-20-years-with-dave-thomas-and-andy-hunt-VBmLw9lP LINKS Ask questions, make comments, and let your voice be heard by emailing podcast@thekguy.com. Twitter: https://twitter.com/thekguy LinkedIn: https://www.linkedin.com/in/keithmmcdonald/ Facebook: https://www.facebook.com/thekguypage Instagram: https://www.instagram.com/the_k_guy/ YouTube: https://www.youtube.com/c/TheKGuy Website:
Jeff Meyerson (@the_prion) is the host of Software Engineering Daily, a popular podcast that averages 20,000 downloads a day. It's also a successful business that generates close to $60,000/month in advertising revenue. Jeff joined the show to talk about the business of podcasting: What goes into producing an episode? How do you ask great questions? What's the best way to grow your listenership and land lucrative advertising deals? And what lessons from podcasting apply more broadly to all indie hackers?Transcript, speaker information, and more: https://www.indiehackers.com/podcast/114-jeff-meyerson-of-software-engineering-daily
In this episode Will Larson, author of An Elegant Puzzle: Systems of Engineering Management, speaks with Uma Chingunde of Stripe and Jeff Meyerson of Software Engineering Daily about engineering management. Will was also featured on SE Daily recently. An Elegant Puzzle is an excellent resource on management techniques and strategies for scaling software organizations. Will’s writing draws from The post An Elegant Puzzle Virtual Book Club appeared first on Software Engineering Daily.
Sponsors Netlify RxJS Live Panel Aimee Knight AJ O’Neal Charles Max Wood With Special Guest: Jeff Meyerson Episode Summary Jeff Meyerson is the host of the Software Engineering daily podcast and has also started a company called FindCollabs, an online platform for finding collaborators and building projects. Jeff started FindCollabs because he believes there are all these amazing tools but people are not combining and collaborating as much as they could, when so much good could be accomplished together. FindCollabs is especially useful for working on side projects. The panelists discuss the problems encountered when you try to collaborate with people over the internet, such as finding people who are facing similar and gauging interest, skill, and availability. Thankfully, FindCollabs has a feature of leaving reviews and rating your partners so that users can accurately gauge other’s skill level. Users can also leave comments about their experience collaborating with others. The only way you can show competence with an interest is to contribute to another project. FindCollabs is also a good place to look for mentors, as well as for Bootcamp graduates or people going through an online coding course. If you are part of an organization, you can create private projects. The company plans to expand this feature to all users in the future.The panelists talk about their past experiences with collaborating with other people. Jeff talks about his podcast Software Engineering Daily and how it got started and the focus of the podcast. As someone working in technology, it is important to stay current on up and coming technology, and listening to podcasts is an excellent way to do that. Jeff talks about where he thinks podcasting is going, especially for programmers. The panel discusses some of the benefits of listening to programming podcasts. Jeff talks about how he is prepping Software Engineering Daily for the future. He shares the audience size for Software Engineering Daily and some of the statistics for his different channels. Jeff has also released an app for Software Engineering Daily, and he shares some information on how it was written. Finally, Jeff gives advice for people who want to use FindCollabs and some of the next steps after creating a profile. Click here to cast your vote NOW for JavaScript Jabber - Best Dev Podcast Award Links FindCollabs Greenlock Telebit SwingCycle Software Engineering Daily Follow DevChat on Facebook and Twitter Picks Aimee Knight: Burnout and the Brain AJ O’Neal: Saber’s Edge from Final Fantasy by Distant Worlds Greenlock on FindCollabs Telebit on FindCollabs Charles Max Wood: Adventures in Machine Learning on FindCollabs Adventures in Virtual Reality on FindCollabs Adventures in Python on FindCollabs Adventures in Java on FindCollabs Air conditioning MFCEO Project Jeff Meyerson: Follow Jeff @the_prion Listen Notes Linbin’s Podcast Playlist Hidden Forces Podcast
Sponsors Netlify RxJS Live Panel Aimee Knight AJ O’Neal Charles Max Wood With Special Guest: Jeff Meyerson Episode Summary Jeff Meyerson is the host of the Software Engineering daily podcast and has also started a company called FindCollabs, an online platform for finding collaborators and building projects. Jeff started FindCollabs because he believes there are all these amazing tools but people are not combining and collaborating as much as they could, when so much good could be accomplished together. FindCollabs is especially useful for working on side projects. The panelists discuss the problems encountered when you try to collaborate with people over the internet, such as finding people who are facing similar and gauging interest, skill, and availability. Thankfully, FindCollabs has a feature of leaving reviews and rating your partners so that users can accurately gauge other’s skill level. Users can also leave comments about their experience collaborating with others. The only way you can show competence with an interest is to contribute to another project. FindCollabs is also a good place to look for mentors, as well as for Bootcamp graduates or people going through an online coding course. If you are part of an organization, you can create private projects. The company plans to expand this feature to all users in the future.The panelists talk about their past experiences with collaborating with other people. Jeff talks about his podcast Software Engineering Daily and how it got started and the focus of the podcast. As someone working in technology, it is important to stay current on up and coming technology, and listening to podcasts is an excellent way to do that. Jeff talks about where he thinks podcasting is going, especially for programmers. The panel discusses some of the benefits of listening to programming podcasts. Jeff talks about how he is prepping Software Engineering Daily for the future. He shares the audience size for Software Engineering Daily and some of the statistics for his different channels. Jeff has also released an app for Software Engineering Daily, and he shares some information on how it was written. Finally, Jeff gives advice for people who want to use FindCollabs and some of the next steps after creating a profile. Click here to cast your vote NOW for JavaScript Jabber - Best Dev Podcast Award Links FindCollabs Greenlock Telebit SwingCycle Software Engineering Daily Follow DevChat on Facebook and Twitter Picks Aimee Knight: Burnout and the Brain AJ O’Neal: Saber’s Edge from Final Fantasy by Distant Worlds Greenlock on FindCollabs Telebit on FindCollabs Charles Max Wood: Adventures in Machine Learning on FindCollabs Adventures in Virtual Reality on FindCollabs Adventures in Python on FindCollabs Adventures in Java on FindCollabs Air conditioning MFCEO Project Jeff Meyerson: Follow Jeff @the_prion Listen Notes Linbin’s Podcast Playlist Hidden Forces Podcast
Sponsors Netlify RxJS Live Panel Aimee Knight AJ O’Neal Charles Max Wood With Special Guest: Jeff Meyerson Episode Summary Jeff Meyerson is the host of the Software Engineering daily podcast and has also started a company called FindCollabs, an online platform for finding collaborators and building projects. Jeff started FindCollabs because he believes there are all these amazing tools but people are not combining and collaborating as much as they could, when so much good could be accomplished together. FindCollabs is especially useful for working on side projects. The panelists discuss the problems encountered when you try to collaborate with people over the internet, such as finding people who are facing similar and gauging interest, skill, and availability. Thankfully, FindCollabs has a feature of leaving reviews and rating your partners so that users can accurately gauge other’s skill level. Users can also leave comments about their experience collaborating with others. The only way you can show competence with an interest is to contribute to another project. FindCollabs is also a good place to look for mentors, as well as for Bootcamp graduates or people going through an online coding course. If you are part of an organization, you can create private projects. The company plans to expand this feature to all users in the future.The panelists talk about their past experiences with collaborating with other people. Jeff talks about his podcast Software Engineering Daily and how it got started and the focus of the podcast. As someone working in technology, it is important to stay current on up and coming technology, and listening to podcasts is an excellent way to do that. Jeff talks about where he thinks podcasting is going, especially for programmers. The panel discusses some of the benefits of listening to programming podcasts. Jeff talks about how he is prepping Software Engineering Daily for the future. He shares the audience size for Software Engineering Daily and some of the statistics for his different channels. Jeff has also released an app for Software Engineering Daily, and he shares some information on how it was written. Finally, Jeff gives advice for people who want to use FindCollabs and some of the next steps after creating a profile. Click here to cast your vote NOW for JavaScript Jabber - Best Dev Podcast Award Links FindCollabs Greenlock Telebit SwingCycle Software Engineering Daily Follow DevChat on Facebook and Twitter Picks Aimee Knight: Burnout and the Brain AJ O’Neal: Saber’s Edge from Final Fantasy by Distant Worlds Greenlock on FindCollabs Telebit on FindCollabs Charles Max Wood: Adventures in Machine Learning on FindCollabs Adventures in Virtual Reality on FindCollabs Adventures in Python on FindCollabs Adventures in Java on FindCollabs Air conditioning MFCEO Project Jeff Meyerson: Follow Jeff @the_prion Listen Notes Linbin’s Podcast Playlist Hidden Forces Podcast
Stephane Kasriel on Unlearn, Melissa Perri on Build by Drift, Will Larson on Software Engineering Daily, April Dunford on Product Love, and Claudio Perrone on Agile Atelier. I’d love for you to email me with any comments about the show or any suggestions for podcasts I might want to feature. Email podcast@thekguy.com. This episode covers the five podcast episodes I found most interesting and wanted to share links to during the two week period starting July 22, 2019. These podcast episodes may have been released much earlier, but this was the fortnight when I started sharing links to them to my social network followers. STEPHANE KASRIEL ON UNLEARN The Unlearn podcast featured Stephane Kasriel with host Barry O’Reilly. Barry asked Stephane about what unlearning he has had to do as CEO of Upwork. Stephane said that when Upwork started, they developed software in a waterfall process. Development cycles were long and it was frustrating for people. When the product failed in the field, the level of investment was high and everybody would be pointing fingers at everybody else. When they switched to an Agile model, there was a lot of unlearning to be done. They stopped trying to specify everything up front and instead tried to build minimum viable products, get feedback from customers, and iterate quickly. When they went looking for Agile trainers in 2012, it was hard to find anyone willing and able to train Upwork’s remote teams. Many trainers at the time told them that being Agile meant being colocated. Today, there are many companies doing distributed Agile development and some best practices have been built up and shared. I liked what Stephane had to say about company values. He said that what you don’t want as a value is one in which you are a good person if you have it and you are a bad person if you don’t. You want instead to have values that say, “This company is not for everybody. If you don’t believe in these values, there are plenty of companies that more closely match your values and you should go there. But if you want to be here and you want to be successful, you should be excited about this company’s values.” Apple Podcasts link: https://podcasts.apple.com/ca/podcast/ceo-school-and-the-future-of-work-with-stephane-kasriel/id1460270044?i=1000443495925 MELISSA PERRI ON BUILD BY DRIFT The Build by Drift podcast featured Melissa Perri with host Maggie Crowley. Maggie started out by asking Melissa how she defined the build trap she references in her book Escaping The Build Trap (https://www.amazon.com/Escaping-Build-Trap-Effective-Management/dp/149197379X/). Melissa says that the build trap is a situation an organization finds itself in when it gets too concerned with how many features it is shipping and not concerned enough with the value for the customer and the business that those features are producing. She says that these businesses fail to retrospect on the impact that the features they shipped had on customers and the business. Maggie asked how companies get into the build trap in the first place. Startups, Melissa says, don’t typically have this problem, but as they scale and get more money, the distance to customers increases, they talk to customers less, and have more runway. They tend to go into an execution mode where they just keep asking themselves, “What’s the next thing we can build?” and forget to go back to their customers and make sure that what they build for them is producing value for them. Maggie described the challenges Drift faces in having teams that locally optimize for particular features and Melissa says this comes back to how the company thinks about strategy. Small companies don’t need a strategic framework but, as you scale, you want all the new teams you are creating to move in the same direction and a strategic framework can help with this. Maggie asked what Melissa prescribes when she consults with a company that is stuck in the build trap. Melissa instead gave an answer on how she assesses a company before making a prescription. She first looks for how the company sets strategy and how it deploys it. Second, she looks to see if the company has the right people in the right roles. She also looks at whether the company has the right processes to learn from customers and incorporate feedback. Next, she looks at product operations, such as a cadence for revisiting decisions and the right data infrastructure to support decisions. Last, she looks at culture and how people are incentivized. Maggie asked what Melissa would change first if the company had problems in all of those areas. Melissa says that she starts by making sure the company has good product leaders and product managers who can learn from those leaders. Many companies had product leaders who didn’t start in product management themselves and can’t train or help the product managers. As Maggie points out in this podcast, this echoes what Marty Cagan said when she had him as a guest in an earlier episode. I referenced that Build by Drift episode in the 14th episode of this podcast, named Safety Is Not A Priority. Melissa says she spends a lot of time translating what the teams are working on into something that executives can get behind because executives don’t care about the list of features that the teams are shipping; they care about what those features are going to do. Melissa says that storytelling in these situations is about relating your story to the goals people care about. Apple Podcasts link: https://podcasts.apple.com/ca/podcast/whats-the-build-trap-what-does-it-mean-for-product-managers/id1445050691?i=1000443704053 Website link: https://share.transistor.fm/s/fbfcff04 WILL LARSON ON SOFTWARE ENGINEERING DAILY The Software Engineering Daily podcast featured Will Larson with host Jeff Meyerson. Jeff started by asking whether Will thinks Google, where they once had a very flat management hierarchy, could work with no managers today. Will said that today’s hyper-scaling companies are so fast-growing that you need people to help manage that growth while dealing with tools and systems that are constantly becoming out of date. Jeff asked about the psychological ramifications of working in an environment of rapid growth. Will said that the best part of rapid growth is every week you raise your head and look around and see some really smart, talented person who is sitting next to you and wasn’t there the week before and can help. During change, he says, you have to stay open. Don’t try to control the change but you can help to facilitate it. You should be aware of your needs and take action to ensure those needs are being met so you can be the person you want to be for longer, rather than peaking in your first months in a role. Apple Podcasts link: https://podcasts.apple.com/ca/podcast/elegant-puzzle-with-will-larson/id1019576853?i=1000441481446 Website link: https://softwareengineeringdaily.com/2019/06/14/elegant-puzzle-with-will-larson/ APRIL DUNFORD ON PRODUCT LOVE The Product Love podcast featured April Dunford with host Eric Boduch. April talked about product positioning. She says that many treat the product positioning exercise as a Mad Libs-style template to be filled in. The actual thinking of how to position your product is often ignored. She says that the first thing you have to do is get a handle on what the real competitive alternatives to your product are in the minds of your customers. For many startups, their real competitor is Excel, or hiring an intern, or doing it manually. Next, she says, is to look at what you have feature-wise that the competitive alternatives do not. This is usually a giant list of things. As you go down this list, you ask yourself what value for customers each feature enables. She says that an interesting thing happens at this point: the value tends to theme out. There are usually two or three big buckets that three quarters of your features fall into. Those buckets get you to your differentiated value. That, she says, is your secret sauce. She uses the analogy of building a fishing net specifically for tuna. You have a choice. You can travel to the part of the ocean where you will find tuna and see if your net works or you can go to the part of the ocean where there are all kinds of fish, throw the net in, and see what you pull up. People at startups often think that a certain segment of the market is going to love their product, but they might be surprised to learn that there is a segment that they didn’t even think of that is actually dying for their product. You don’t want to get the positioning so tight that you exclude those people. You want to keep it loose, cast the net wide, and see what happens. April says she doesn’t believe in product-market fit. She says that nobody has given her a good answer to the question, “How do you know you got product-market fit?” You may have a product that people like, but if you don’t know why, you don’t know if it’s at risk of going away or tapping out its market. She asks, “If I can’t measure when I have product-market fit, why am I even trying to get product-market fit?” Apple Podcasts link: https://podcasts.apple.com/ca/podcast/april-dunford-joins-product-love-to-talk-about-product/id1343610309?i=1000441988263 Website link: https://soundcloud.com/productcraft/april-dunford-joins-product-love-to-talk-about-product-positioning CLAUDIO PERRONE ON AGILE ATELIER The Agile Atelier podcast featured Claudio Perrone with host Rahul Bhattacharya. Claudio talked about his Popcorn Flow model. He says that Popcorn Flow is based on a pragmatic anti-fragile philosophy and starts from the idea that inertia is our enemy and provides a set of principles and steps to fight inertia in organizations. I saw Claudio give a presentation on Popcorn Flow at the Agile Testing Days 2017 conference, so I was excited to find him being interviewed on a podcast. Popcorn Flow applies ideas from The Lean Startup to organizational change. As an entrepreneur, Claudio realized that in entrepreneurship you are dealing with an environment of extreme uncertainty and, as an Agile coach, he saw the same kind of environment of uncertainty in how people react to change. Lean Startup deals with environments of extreme uncertainty by running frequent experiments. Popcorn Flow applies the same approach of frequent experimentation to organizational change. Popcorn Flow is most known for its decision cycle of seven steps from which the POPCORN acronym is derived: Problems & Observations Options Possible experiments Committed Ongoing Review Next These steps are visualized like a Scrum board or Kanban board. Claudio gave an example of running through the seven steps for the problem of poor quality code: Problem: poor quality code Options: pair programming, test-driven development Possible experiments: pair program for three days and see if the code is better and see if we want to continue with the practice Committed: put a review date on the calendar for evaluating the results of the experiment Ongoing: Track the experiment as it proceeds Review: The experiment is not finished until you review it. Compare the reality against the expectation and discuss what you learned and what are you going to do next. Next: The review may indicate that you do not know enough yet, so you may choose to persist, launch a new experiment based on what you learned, or revisit the problem. I liked what Claudio had to say about Agile: “I felt it was about being humble. If we knew the perfect way of developing software, we would use the perfect way. It is because we don’t know that we start with what we have and we continuously inspect and adapt.” Claudio also talked about some of the principles of Popcorn Flow: If change is hard, make it continuous: borrowing ideas from continuous integration and delivery, replace big change programs with small incremental change and do it all the time. Small bets, big payoff (the venture capitalist principle): when you run a lot of experiments, it doesn’t matter that you failed. What matters is how much does it cost to fail and how much do you gain when you win. It is not ‘fail fast - fail often’, it is ‘learn fast - learn often’: without feedback, your experiments are not small bets and you are not experimenting; you are committing to what should instead be an option. Apple Podcasts link: https://podcasts.apple.com/ca/podcast/episode-9-experimentation-popcorn-flow-claudio-perrone/id1459098259?i=1000443480071 Website link: https://rahul-bhattacharya.com/2019/07/02/episode-9-experimentation-and-popcorn-flow-with-claudio-perrone/ FEEDBACK Ask questions, make comments, and let your voice be heard by emailing podcast@thekguy.com. Twitter: https://twitter.com/thekguy LinkedIn: https://www.linkedin.com/in/keithmmcdonald/ Facebook: https://www.facebook.com/thekguypage Instagram: https://www.instagram.com/the_k_guy/ YouTube: https://www.youtube.com/c/TheKGuy Website:
In this week’s episode of the Data Show, we’re featuring an interview Data Show host Ben Lorica participated in for the Software Engineering Daily Podcast, where he was interviewed by Jeff Meyerson. Their conversation mainly centered around data engineering, data architecture and infrastructure, and machine learning (ML). Here are a few highlights: Tools for productive […]
Jocelyn Goldfein on Software Engineering Daily, Michael Bolton on Engineering Culture by InfoQ, Dave Snowden on Engineering Culture by InfoQ, Ben Orenstein on Software Developer’s Journey, and Claire Lew on Greater Than Code. I’d love for you to email me with any comments about the show or any suggestions for podcasts I might want to feature. Email podcast@thekguy.com. This episode covers the five podcast episodes I found most interesting and wanted to share links to during the two week period starting June 10, 2019. These podcast episodes may have been released much earlier, but this was the fortnight when I started sharing links to them to my social network followers. JOCELYN GOLDFEIN ON SOFTWARE ENGINEERING DAILY The Software Engineering Daily podcast featured Jocelyn Goldfein with host Jeff Meyerson. Jocelyn talked about joining Facebook after having spent years at VMWare delivering shrink-wrap software that had a release cycle on the order of years. Witnessing the cadence at which Facebook delivered new releases firsthand, it appeared to her like Facebook was defying the laws of physics. The cost of a release had shrunk to nearly zero. She says that companies that start life developing for native, that is, developing shrink-wrap software like that of VMWare, never really shake off the culture of developing for native. These cultures define a good engineer as someone who can estimate precisely and deliver predictably and it is all because the cost of a release in that native software world is so high. She talked about the often unacknowledged tradeoff between productivity and predictability. She also talked about the flexibility the engineers obtained by shipping more frequently. Not having to hit infrequent, high-risk release windows meant that engineers could stay “on the balls of their feet” and, say, have the news feed team help the photos team because they were not going to miss some “huge release date in the sky” by shuffling tasks and reprioritizing. By the way, I love Jocelyn’s colorful metaphors. She said that being able to move people around fungibly to unblock each other ends up being a “turbo button for the entire organization.” She says that the combination of removing deadline pressure and continuously integrating new features behind feature flags into the single branch that all of Facebook ran on allowed the engineers to be agile and to “reserve the right to wake up smarter and make a better decision tomorrow” based on actual usage. This is in contrast to many software teams that spend so much time making a perfect product before they finally get feedback that they become both psychologically committed to their design and physically committed to it (through a hard-to-change code base). At Facebook, the “concrete was still wet” until incredibly “late in the game.” The architecture and the release process at Facebook let them “jettison some sacred cows,” specifically, the notion of deadlines and the idea that you only get feedback at the end. She says that Mark Zuckerberg has many gifts but one of his superpowers is to be able to admit when he was wrong. She says she doesn’t think people can reliably distinguish good innovative ideas from bad ideas without trying them out first and she believes Facebook has been innovative because their architecture, release process, and values system allowed them to take risks. She says, “Facebook’s genius is not that it is right any more than anybody else. It is that it tries experiments at a higher velocity than anybody else and it purges the ones that don’t work faster than anybody else. It is no surprise that, in the end, the deep-seated challenges for the company have been problems that don’t show up immediately — problems where the downsides were incredibly lagging indicators.” Apple Podcasts link: https://podcasts.apple.com/us/podcast/facebook-management-with-jocelyn-goldfein/id1019576853?i=1000438147913 Website link: https://softwareengineeringdaily.com/2019/05/15/facebook-management-with-jocelyn-goldfein/ MICHAEL BOLTON ON ENGINEERING CULTURE BY INFOQ The Engineering Culture by InfoQ podcast featured Michael Bolton with host Shane Hastie. Shane started by asking Michael whether testing is blasé today. Michael said that you can choose to look at it that way but nothing is more fascinating to him than testing, which he defines as evaluating products by learning about them through exploration and experimentation. He also says that testing is focused on a question that nobody else is interested in asking or answering, which is: Are there problems that threaten the on-time successful completion of the project or that threaten the value of the product? Michael sees his job as helping people get comfortable with the process of looking for problems that threaten value so that managers can find out whether the product they have is the product they wanted. In response to a question from Shane, Michael brought up a conversation in which someone said that you often look at a piece of software and think to yourself that it couldn’t have an effect on human life or health or safety. But you don’t know how people are going to use your product. A developer of Microsoft Excel might think, “Nobody’s going to die if there is a bug in Excel.” Somebody could easily lose a mortgage due to a bug in Excel and when a product is used as ubiquitously as Excel, you are not going to see the knock-on effects of the risk. He talked about the problem of needing to maintain a critical distance to spot the problems that arise from complexity. He said that unit tests may demonstrate that the individual units of a program can all be individually reliable, but they would not demonstrate that the overall product is safe. He gave an example from Nancy Leveson’s Engineering a Safer World of a chemical reactor in which the software that controlled the flow of water and catalysts into the reactor was designed to leave all control variables as-is and sound an alarm in response to a fault. This sounds reasonable, but a situation occurred in which a fault was triggered just after the catalyst was added to the reactor. The cooling water flow had not yet ramped up and fault policy meant that it stayed at this low level as the system got hotter and hotter. The reactor overheated, the release valve lifted, and the contents of the reactor were discharged into the atmosphere. This illustrated how putting simple things together into a complex thing creates complex problems we are not great at anticipating. The solution he says is to experiment with the system in the same way Hook, Boyle and their contemporaries in the 1600s were doing: putting the system into conditions that are not normal so as to reveal surprises. It is the tester’s job, Michael says, to be professional skeptics. The problem, he says, is that the critical distance of a good tester is bound together with social distance. Nobody wants to receive bad news and testers are often the people delivering the bad news, creating social distance from the rest of the team. The social challenge for testers is to help people appreciate getting the bad news. Apple Podcasts link: https://podcasts.apple.com/ca/podcast/michael-bolton-on-the-testing-mindset/id1161431874?i=1000438906048 Website link: https://soundcloud.com/infoq-engineering-culture/interview-michael-bolton DAVE SNOWDEN ON ENGINEERING CULTURE BY INFOQ The Engineering Culture by InfoQ podcast featured Dave Snowden with host Shane Hastie. After asking Dave to introduce himself, Shane asked about the liminal aspects of the Cynefin “model” and Dave made the correction that Cynefin is actually a framework rather than a model because it doesn’t seek to represent the world but to give a perspective on the world. Dave explained that regarding liminality, Cynefin started with five domains and a set of dynamics for moving between domains but this confused people, so they introduced liminal zones to represent this state of transition. He pointed out that the Scrum framework holds things in the liminal state between complicated and complex long enough to get them right and this is a strength of Scrum. They talked about the need to run parallel safe-to-fail experiments when in the complex domain and Dave gave three examples. The first was to break people up into trios and spin off 30 or 40 trios to look at a problem in their spare time over a week. The second example was to create a prototyping team and put them with users for a day to build a prototype and then pass the prototype on to another team charged with improving it without the original user input. The third example was to do continuous mapping of unarticulated needs and, when they get statistically significant clusters, put small prototyping teams on each cluster. Dave told a story about creating a fake infographic about a cybersecurity breach in one industry, giving it to employees in a different industry, and asking them to tell a story about why it couldn’t happen to their company and a story about what they would do if it did. He then analyzed these stories to look for complacency. More generally, he would use this technique and look for outliers because, when you want to create significant change, you need to look to the outlier groups rather than the dominant groups. Shane pointed out the contrast between this technique and common requirements-gathering techniques and Dave responded that requirements-gathering allows bias to creep in after the first few interviews. Apple Podcasts link: https://podcasts.apple.com/ca/podcast/dave-snowden-on-liminality-in-cynefin-moving-beyond/id1161431874?i=1000438021618 Website link: https://soundcloud.com/infoq-engineering-culture/dave-snowden-on-liminality-in-cynefin-and-moving-beyond-agile-to-agility BEN ORENSTEIN ON SOFTWARE DEVELOPER’S JOURNEY The Software Developer’s Journey podcast featured Ben Orenstein with host Timothée Bourguignon. They talked about Ben’s academic challenges, his initial lack of maturity, his discovery of Ruby and then Rails, and his growth as a software developer under the tutelage of his former boss and mentor. Tim asked Ben what he would be looking for in a junior developer to have as a mentee and Ben answered that he would look for something like grit (the ability to push forward and not get too discouraged) because the kinds of problems we face as software developers require grit to get through and this never really goes away as you become more senior and experienced. Apple Podcasts link: https://podcasts.apple.com/ca/podcast/51-ben-orenstein-advises-us-not-to-worry-too-much/id1079113167?i=1000439883363 Website link: https://www.buzzsprout.com/190346/1195571 CLAIRE LEW ON GREATER THAN CODE The Greater Than Code podcast featured Claire Lew with hosts Janelle Klein and Sam Livingston-Gray. The panelists asked Claire the standard “What is your superpower?” question and, after answering, she turned the question around to them. They then entered the topic of bad bosses in which Claire told her own story and then got Janelle and Sam to tell their own bad boss stories. Sam told the story of his experience with a command-and-control CEO and this led to a discussion about when motivating through fear is and isn’t effective. Sam related this to a book by Courtenay Hameister called Okay Fine Whatever that describes the negative effects of stress on one’s ability to be creative. This reminded me of the section of the book Switch by the Heath brothers about the burning platform concept and how negative emotions stifle creativity. Claire pointed out another problem with command-and-control leadership is that it disregards the belief that people are ever intrinsically motivated. She says that while there has been a shift to leaders being told they need to inspire people rather than command and control them, there is still an implicit reference to control. People say things like you need to “empower” people. She hates that word. She says people are already empowered. Leaders need to create an environment that lets their people do their best work and then just get out of their way. Apple Podcasts link: https://podcasts.apple.com/ca/podcast/132-distilling-the-hailstorm-with-claire-lew/id1163023878?i=1000440034174 Website link: https://www.greaterthancode.com/distilling-the-hailstorm FEEDBACK Ask questions, make comments, and let your voice be heard by emailing podcast@thekguy.com. Twitter: https://twitter.com/thekguy LinkedIn: https://www.linkedin.com/in/keithmmcdonald/ Facebook: https://www.facebook.com/thekguypage Instagram: https://www.instagram.com/the_k_guy/ YouTube: https://www.youtube.com/c/thekguy Website:
Matt makes his return! What do vendors mean by “multi-cloud” and “digital transformation.” Could Ben Thompson’s aggregation theory apply to the public cloud? We discuss all of this and offer more advice on tacos. Relevant to your interests Google open sources ClusterFuzz (https://techcrunch.com/2019/02/07/google-open-sources-clusterfuzz/) With new security tools, Google looks to reduce the impact of data breaches (https://siliconangle.com/2019/02/05/google-looks-reduce-impact-data-breaches-new-security-tools/) CNCF Dev Stats Dashboards (https://k8s.devstats.cncf.io/d/12/dashboards?refresh=15m&orgId=1) CNCF Annual Report (https://www.cncf.io/wp-content/uploads/2019/02/CNCF_Annual_Report_2018.pdf) Amazon Dropping out of NYC (https://boingboing.net/2019/02/14/amazon-drops-new-york-hq2-plan.html) Ultimate Software Sells for $11 Billion - Workforce (https://www.workforce.com/2019/02/07/ultimate-software-sells-for-11-billion/) The fundamental problem with Silicon Valley’s favorite growth strategy (https://qz.com/1540608/the-problem-with-silicon-valleys-obsession-with-blitzscaling-growth/) Full Q&A: Alex Blumberg and Matt Lieber explain why they sold Gimlet to Spotify (https://www.recode.net/2019/2/7/18214941/alex-blumberg-matt-lieber-gimlet-spotify-deal-acquisition-peter-kafka-media-podcast-audio-interview) Microsoft begs you to stop using Internet Explorer (https://www.engadget.com/2019/02/08/microsoft-internet-explorer-technical-debt/) Chef Hires Cloud Industry Veteran Goldfarb (https://www.geekwire.com/2019/chef-hires-cloud-industry-veteran-brian-goldfarb-chief-marketing-officer/) Exponent Podcast on Gimlet Media (https://exponent.fm/exponent-162-why-exponent-isnt-on-spotify/) Sponsors Plastic SCM - Get your t-shirts at http://plasticscm.com/sdt. - Listen to the New Stack Makers Interview (https://thenewstack.io/plastic-scm-mergebots-version-control-for-ci-cd/) with Plastic SCM Founder Conferences, et. al. ALERT! DevOpsDays Discount - DevOpsDays MSP (https://www.devopsdays.org/events/2019-minneapolis/welcome/), August 6th to 7th, $50 off with the code SDT2019 (https://www.eventbrite.com/e/devopsdays-minneapolis-2019-tickets-51444848928?discount=SDT2019). 2019, a city near you: The 2019 SpringTours are posted (http://springonetour.io/). Coté will be speaking at many of these, hopefully all the ones in EMEA. They’re free and all about programming and DevOps things. Free lunch and stickers! Feb 12th to 13th, 2019 - SpringOne Tour St. Louis (https://springonetour.io/2019/st-louis). $50 off the code S1Tour2019_100. Mar 7th to 8th, 2019 - Incontro DevOps in Bologna (https://2019.incontrodevops.it/), Coté speaking. Mar 13th, 2019 - Coté speaking at (platform as a product) (https://www.meetup.com/Continuous-Delivery-Amsterdam/events/258120367/) - Continuous Delivery, Amsterdam. Mar 18th to 19th, 2019 - SpringOne Tour London (https://springonetour.io/2019/london). Get £50 off ticket price of £150 with the code S1Tour2019_100. Mar 21st to 2nd, 2019 (https://springonetour.io/2019/amsterdam) - SpringOne Tour Amsterdam. Get €50 off ticket price of €150 with the code S1Tour2019_100. ChefConf 2019 (http://chefconf.chef.io/) May 20-23 Get a Free SDT T-Shirt Write an iTunes review of SDT and get a free SDT T-Shirt. Write an iTunes Review on the SDT iTunes Page. (https://itunes.apple.com/us/podcast/software-defined-talk/id893738521?mt=2) Send an email to stickers@softwaredefinedtalk.com (mailto:stickers@softwaredefinedtalk.com) and include the following: T-Shirt Size (Only Large or X-Large remain), Preferred Color (Gray, Black) and Postal address. First come, first serve. while supplies last! Can only ship T-Shirts within the United State SDT news & hype Join us in Slack (http://www.softwaredefinedtalk.com/slack). Follow us on Twitter (https://twitter.com/softwaredeftalk), Instagram (https://www.instagram.com/softwaredefinedtalk/) or LinkedIn (https://www.linkedin.com/company/software-defined-talk/) Listen to the Software Defined Interviews Podcast (https://www.softwaredefinedinterviews.com/). Check out the back catalog (http://cote.coffee/howtotech/). Brandon built the Quick Concall iPhone App (https://itunes.apple.com/us/app/quick-concall/id1399948033?mt=8) and he wants you to buy it for $0.99. Send your postal address to stickers@softwaredefinedtalk.com (mailto:stickers@softwaredefinedtalk.com) and we will send you a free laptop sticker! Recommendations Brandon: Who is Michael Ovitz (https://www.audible.com/pd/Who-Is-Michael-Ovitz-Audiobook/B07DJZBDK4?qid=1549912230) and the Jeff Meyerson interview (https://www.softwaredefinedinterviews.com/80) Matt: Pecans. Criminally underrated nut. Coté: Bring duffle bag on every trip Surveillance Capital (https://www.amazon.com/Age-Surveillance-Capitalism-Future-Frontier/dp/1610395697) Photo credit (https://twitter.com/dellcam/status/1096138088307396608?s=21)
Jeff Meyerson is the host of Software Engineering Daily (https://softwareengineeringdaily.com/). We talk about his career and what led him to start a daily tech podcast for software engineers. We also talk about current trends in cloud computing and Jeff recounts his career as professional poker player. Topics: Darknet Diaries Chartbreakers Episode (https://darknetdiaries.com/episode/27/) Who Is Michael Ovitz? (https://www.audible.com/pd/Who-Is-Michael-Ovitz-Audiobook/B07DJZBDK4) Where to find Jeff Software Engineering Daily (https://softwareengineeringdaily.com/) Jeff Meyerson (https://jeffmeyerson.com/) @the_prion (https://twitter.com/the_prion) Special Guest: Jeff Meyerson.
Jeff Meyerson is the host of Software Engineering Daily (https://softwareengineeringdaily.com/). We talk about his career and what led him to start a daily tech podcast for software engineers. We also talk about current trends in cloud computing and Jeff recounts his career as professional poker player. Topics: Darknet Diaries Chartbreakers Episode (https://darknetdiaries.com/episode/27/) Who Is Michael Ovitz? (https://www.audible.com/pd/Who-Is-Michael-Ovitz-Audiobook/B07DJZBDK4) Where to find Jeff Software Engineering Daily (https://softwareengineeringdaily.com/) Jeff Meyerson (https://jeffmeyerson.com/) @the_prion (https://twitter.com/the_prion) Special Guest: Jeff Meyerson.
Jeff Meyerson is the host of Software Engineering Daily (https://softwareengineeringdaily.com/). We talk about his career and what led him to start a daily tech podcast for software engineers. We also talk about current trends in cloud computing and Jeff recounts his career as professional poker player. Topics: Darknet Diaries Chartbreakers Episode (https://darknetdiaries.com/episode/27/) Who Is Michael Ovitz? (https://www.audible.com/pd/Who-Is-Michael-Ovitz-Audiobook/B07DJZBDK4) Where to find Jeff Software Engineering Daily (https://softwareengineeringdaily.com/) Jeff Meyerson (https://jeffmeyerson.com/) @the_prion (https://twitter.com/the_prion) Special Guest: Jeff Meyerson.
Show: 380 Description: Brian talks with Jeff Meyerson (@the_prion, Host of @software_daily) about the state of Cloud-native application development heading into 2019.Show 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-shirtShow Interview Links:Software Engineering Daily - https://softwareengineeringdaily.comShow Notes:Topic 1 - Happy New Year. Tell us a little bit about your background, and what motivates you to continue to dig into every aspect of Cloud-native application development?Topic 2 - Developers have lots of opinions and approaches to building software. Have you seen much in terms of commonality or consistency about how developers are building cloud-native applications?Topic 3 - What are some of the areas that developers really love today, and some areas where developers are really frustrated?Topic 4 - A decade ago, it was all about the LAMP stack. We hear about the MEAN (Mongo, Express, Angular, Node) stack, but also lots of discussions about things like Kafka and more real-time applications. Are you seeing trends around application stacks, or is it really about lots of options now as applications move to microservices (and serverless)?Topic 5 - SED covered quite a few aspects of Machine Learning in 2018. What are some of the things you’ve learned about ML usage and how it’s impacting application developers?Topic 6 - What are some of the topics that you’re really interested to explore in 2019?Feedback?Email: show at thecloudcast dot netTwitter: @thecloudcastnet and @ServerlessCast
Jeff Meyerson hosts Software Engineering Daily, a similar podcast to our own that publishes new episodes weekdays.
Software Engineering Radio - The Podcast for Professional Software Developers
Phillipp Krenn talks with SE Radio’s Jeff Meyerson about Elasticsearch, a scalable search index. The conversation begins with a discussion of search, how it compares to database queries, and what an inverted index is. Phillipp introduces Wikipedia as an example that runs throughout the episode because Wikipedia uses Elasticsearch to power its full-text search. A […]
Software Engineering Radio - The Podcast for Professional Software Developers
Phillipp Krenn talks with SE Radio’s Jeff Meyerson about Elasticsearch, a scalable search index. The conversation begins with a discussion of search, how it compares to database queries, and what an inverted index is. Phillipp introduces Wikipedia as an example that runs throughout the episode because Wikipedia uses Elasticsearch to power its full-text search. A discussion of Elasticsearch’s scalability ensues, including basic terminology and an explanation of other applications of Elasticsearch.
Software Engineering Radio - The Podcast for Professional Software Developers
Morgan Wilde talks with SE Radio’s Jeff Meyerson about the LLVM compiler toolchain. They begin with a discussion of how a compiler works and how compiled code executes against different processor architectures. Using the JVM as a model for interoperability, they move on to how LLVM is a system that optimizes an intermediate representation (IR), […]
Software Engineering Radio - The Podcast for Professional Software Developers
Morgan Wilde talks with SE Radio’s Jeff Meyerson about the LLVM compiler toolchain. They begin with a discussion of how a compiler works and how compiled code executes against different processor architectures. Using the JVM as a model for interoperability, they move on to how LLVM is a system that optimizes an intermediate representation (IR), which is similar to the Java bytecode: every programming language that compiles down to IR can leverage the same optimizations of that IR. The conversation concludes with a discussion of applications of LLVM and the future of the ecosystem.
Guest: Jeff Meyerson @the_prion Full show notes are at https://developeronfire.com/podcast/episode-211-jeff-meyerson-software-and-business-for-humans
Software Engineering Radio - The Podcast for Professional Software Developers
Jeff Meyerson talks with Frances Perry about Apache Beam, a unified batch and stream processing model. Topics include a history of batch and stream processing, from MapReduce to the Lambda Architecture to the more recent Dataflow model, originally defined in a Google paper. Dataflow overcomes the problem of event time skew by using watermarks and […]
Software Engineering Radio - The Podcast for Professional Software Developers
Jeff Meyerson talks with Frances Perry about Apache Beam, a unified batch and stream processing model. Topics include a history of batch and stream processing, from MapReduce to the Lambda Architecture to the more recent Dataflow model, originally defined in a Google paper. Dataflow overcomes the problem of event time skew by using watermarks and other methods discussed between Jeff and Frances. Apache Beam defines a way for users to define their pipelines in a way that is agnostic of the underlying execution engine, similar to how SQL provides a unified language for databases. This seeks to solve the churn and repeated work that has occurred in the rapidly evolving stream processing ecosystem.
Software Engineering Radio - The Podcast for Professional Software Developers
Jeff Meyerson talks to Idit Levine about Unikernels and unik, a project for compiling unikernels. The Linux kernel contains features that may be unnecessary to many application developers--particularly if those developers are deploying to the cloud. Unikernels allow programmers to specify the minimum features of an operating system we need to deploy our applications. Topics include the the Linux kernel, requirements for a cloud operating system, and how unikernels compare to Docker containers.
Software Engineering Radio - The Podcast for Professional Software Developers
Jeff Meyerson talks to Idit Levine about Unikernels and unik, a project for compiling unikernels. The Linux kernel contains features that may be unnecessary to many application developers–particularly if those developers are deploying to the cloud. Unikernels allow programmers to specify the minimum features of an operating system we need to deploy our applications. Topics […]
Software Engineering Radio - The Podcast for Professional Software Developers
Jeff Meyerson talks with Brian Brazil about monitoring with Prometheus, an open source tool for monitoring distributed applications. Brian is the founder of Robust Perception, a company offering Prometheus engineering and consulting. The high level goal of Prometheus is to allow developers to focus on services rather than individual instances of a given service. Prometheus is based off of the Borgmon monitoring tool, widely used at Google, where Brian previously worked. Jeff and Brian discuss the tradeoffs of choosing not to replicate our monitoring data. In some situations, the monitoring system will lose data because of this decision. Other topics that are discussed are distributed consensus tools, integrations with Prometheus, and the broader topic of monitoring itself.
Software Engineering Radio - The Podcast for Professional Software Developers
Jeff Meyerson talks with Brian Brazil about monitoring with Prometheus, an open source tool for monitoring distributed applications. Brian is the founder of Robust Perception, a company offering Prometheus engineering and consulting. The high level goal of Prometheus is to allow developers to focus on services rather than individual instances of a given service. Prometheus […]
Software Engineering Radio - The Podcast for Professional Software Developers
Jeff Meyerson talks to Haoyuan Li about Alluxio, a memory-centric distributed storage system. The cost of memory and disk capacity are both decreasing every year–but only the throughput of memory is increasing exponentially. This trend is driving opportunity in the space of big data processing. Alluxio is an open source, memory-centric, distributed, and reliable storage system enabling data sharing across clusters at memory speed. Alluxio was formerly known as Tachyon. Haoyuan is the creator of Alluxio. Haoyuan was a member of the Berkeley AMPLab, which is the same research facility from which Apache Mesos and Apache Spark were born. In this episode, we discuss Alluxio, Spark, Hadoop, and the evolution of the data center software architecture.
Software Engineering Radio - The Podcast for Professional Software Developers
Jeff Meyerson talks to Haoyuan Li about Alluxio, a memory-centric distributed storage system. The cost of memory and disk capacity are both decreasing every year–but only the throughput of memory is increasing exponentially. This trend is driving opportunity in the space of big data processing. Alluxio is an open source, memory-centric, distributed, and reliable storage […]
Software Engineering Radio - The Podcast for Professional Software Developers
John Purrier talks with Jeff Meyerson about OpenStack, an open-source cloud operating system for managing compute resources. They explore infrastructure-as-a-service, platform-as-a-service, virtualization, containers, and the future of systems development and management.
Software Engineering Radio - The Podcast for Professional Software Developers
John Purrier talks with Jeff Meyerson about OpenStack, an open-source cloud operating system for managing compute resources. They explore infrastructure-as-a-service, platform-as-a-service, virtualization, containers, and the future of systems development and management. Cloud service providers like Amazon, Google, and Microsoft provide both infrastructure-as-a-service and platform-as-a-service. Infrastructure-as-a-service gives developers access to virtual machines, servers, and network infrastructure. […]
Software Engineering Radio - The Podcast for Professional Software Developers
Slava Akhmechet and Jeff Meyerson discuss RethinkDB, an open source database for the real-time Web. RethinkDB pushes data to the application rather than requiring the application to poll the database for updates. The discussion begins with the question of why databases need to be rethought–why is it better to build JSON-pushing into the database layer […]
Software Engineering Radio - The Podcast for Professional Software Developers
Ben Hindman talks to Jeff Meyerson about Apache Mesos, a distributed systems kernel. Mesos abstracts away many of the hassles of managing a distributed system. Hindman starts with a high-level explanation of Mesos, explaining the problems he encountered trying to run multiple instances of Hadoop against a single data set. He then discusses how Twitter uses Mesos for cluster management. The conversation evolves into a more granular discussion of the abstractions Mesos provides and different ways to leverage those abstractions.
Software Engineering Radio - The Podcast for Professional Software Developers
Ben Hindman talks to Jeff Meyerson about Apache Mesos, a distributed systems kernel. Mesos abstracts away many of the hassles of managing a distributed system. Hindman starts with a high-level explanation of Mesos, explaining the problems he encountered trying to run multiple instances of Hadoop against a single data set. He then discusses how Twitter uses […]
Software Engineering Radio - The Podcast for Professional Software Developers
Shubhra Kar of StrongLoop talks to Jeff Meyerson about Node.js. Node allows for server-side JavaScript. Shubra and Jeff explore why Node is so important from three standpoints: isomorphic JavaScript, the single-threaded-concurrency model, and the “API economy.” Isomorphic JavaScript apps have their own control and viewing logic, but they share the state and specification of the […]
Software Engineering Radio - The Podcast for Professional Software Developers
Flavio Junqueira is the author of Zookeeper: Distributed Process Coordination. Flavio and Jeff Meyerson begin by defining ZooKeeper and talking about what ZooKeeper is and isn’t. ZooKeeper can be thought of as a patch against certain fallacies of distributed computing: that the network is secure, has zero latency, has infinite bandwidth, and so on. With […]
Software Engineering Radio - The Podcast for Professional Software Developers
Jeff Meyerson talks to Jun Rao, a software engineer and researcher (formerly of LinkedIn). Jun has spent much of his time researching MapReduce, scalable databases, query processing, and other facets of the data warehouse. For the past three years, he has been a committer to the Apache Kafka project. Jeff and Jun first compare streaming […]
© 2020-2025 Ivy Podcast Discovery LLC
