Podcast appearances and mentions of ben halpern

Did you know that global food production puts enormous environmental pressure on our planet? Join Food Sleuth Radio host and Registered Dietitian, Melinda Hemmelgarn, for her interview with Ben Halpern, Ph.D, marine ecologist and conservation scientist at the Bren School of Environmental Science & Management at UC Santa Barbara. Halpern discusses his recent paper titled: “The Environmental Footprint of Global Food Production,” and describes four pressures of food production: greenhouse gas emissions, freshwater use, habitat disturbance, nutrient pollution; he also discusses the costs and benefits of “efficient” food production. Related resource: IPCC: https://www.ipcc.ch/srccl/chapter/chapter-5/ Related website:  The Environmental Footprint of Global Food Production:https://www.rootsofchange.org/wp-content/uploads/Environmental-impact-of-Global-Food-Production.pdf 

Some folks promote local food. Others swear by veganism. But what is the most environmentally-friendly diet? And does it really matter what we eat? Or are there bigger fish to fry when it comes to climate activism?Outside/In is trying out a new segment called This, That, Or The Other Thing. It's all about the little decisions we make to try and build a more sustainable world—whether they have any effect, and what we can do instead if they don't. For our inaugural edition, we're focusing on food. From Brazilian beef and tofu tacos to food waste and composting, host Nate Hegyi talks with experts to understand how our choices impact the planet… and how we can make a difference in our communities. Featuring Umair Irfan, Tamar Haspel, and Ben Halpern. SUPPORTOutside/In is made possible with listener support. Click here to become a sustaining member of Outside/In. Subscribe to our FREE newsletter.Follow Outside/In on Instagram or Twitter, or join our private discussion group on Facebook LINKSGive a listen to Tamar Haspel's podcast, Climavores.Vox reporter Umair Irfan wrote about how individual action actually does matter in the fight against climate change. Scientists at the University of California, Santa Barbara put together a big study on the cumulative environmental pressures of different foods. Want to tackle food waste? The Environmental Protection Agency has a great, down-to-earth guide on what you can do.  CREDITSHosted, reported, produced, and mixed by Nate HegyiEdited by Taylor Quimby with help from Justine Paradis, Jessica Hunt, and Felix Poon.Rebecca Lavoie is our Executive ProducerMusic by Blue Dot Sessions, Sven Lindvall, El Flaco Collective, Future Joust, Spring Gang, Eight Bits, and Awlee.Our theme music is by Breakmaster Cylinder.Outside/In is a production of New Hampshire Public Radio

UCSB ecologists have mapped the environmental impacts of global food production, analyzing how different food industries impact the planet. KCSB's Frankie Newton sat down with one of the researchers, Ben Halpern, to learn about the findings and their implications.

This week, we feature one of our favorite episodes of our sister podcast, DevDiscuss, where hosts Ben Halpern and Julianna Tetreault talk about creating beautiful data-driven essays with Michelle McGhee and Russell Goldenberg, Journalist-Engineers at The Pudding. Show Notes DevDiscuss (sponsor) CodeNewbie (sponsor) Avalanche (sponsor) The Pudding Polygraph Svelte Gabriel Florit - On Responsive Design and Data Visualization Who's in the Crossword? We investigated 200 crackers to learn about food allergies and labelling. Warning: may contain troubling results The Birthday Paradox The Gyllenhaal Experiment Life After Death on Wikipedia We couldn't get an artificial intelligence program to win the New Yorker Caption Contest Nothing Breaks Like A.I. Heart OpenAI Human Terrain An Interactive Visualization of Every Line in Hamilton Reconstructing Seven Days of Protests How you play Spades is how you play life D3.js GitHub: The Pudding Datawrapper Flourish The Pudding: Our Resources

Robby has a chat with Ben Halpern, the creator of Dev.to and a Co-Founder of Forem, a platform that Dev.to is based on. Ben shares from his experience, that well-maintained software needs to have a clear purpose and context that's available as one is reading it and within the documentation as needed while also being flexible for future evolution. When it comes to dealing with the common challenge of naming variables and functions when we write, Ben says a glossary is fundamentally important.He then introduces us to Dev.to, shares the story of how they opted to open source the underlying platform, and what they needed to be ready to share it with the public. He also talks about how that open source software evolved out of Dev.to and became a core aspect of their financial success. Ben advises engineers to avoid overcorrecting each time they start up a new software project. And for those of us who may be considering open-sourcing our software, Ben will enlighten us on the things we should consider beforehand (In particular, security). Tune in to our conversation for that and more!Book Recommendations:Creative Quest by QuestloveHelpful LinksBen's TwitterBen on GitHubBen on Dev.toForem WebsiteForem on GitHubDev.to CommunityAlso…follow Robby on Dev.to!Subscribe to Maintainable on:Apple PodcastsOvercastSpotifyOr search "Maintainable" wherever you stream your podcasts.

Today we're bringing our appearance on DevDiscuss right here to The Changelog. Jerod and I guested their launch episode for Season 7 to talk about deeply human stories we've covered over the years on this podcast. For long-time listners this will be a trip down memory lane and for recent subscibers this will be a guided tour on some of our most impactful episodes. Special thanks to Ben Halpern and Christina Gorton for hosting us. Check out their show at dev.to/devdiscuss

Today we're bringing our appearance on DevDiscuss right here to The Changelog. Jerod and I guested their launch episode for Season 7 to talk about deeply human stories we've covered over the years on this podcast. For long-time listners this will be a trip down memory lane and for recent subscibers this will be a guided tour on some of our most impactful episodes. Special thanks to Ben Halpern and Christina Gorton for hosting us. Check out their show at dev.to/devdiscuss

In this episode, we talk about deeply human stories in software with the hosts of The Changelog podcast, Adam Stacoviak and Jerod Santo. Show Notes Microsoft 30 Days to Learn It (DevDiscuss) (sponsor) DevNews (sponsor) CodeNewbie (sponsor) New Relic (sponsor) Vultr (sponsor) Changelog The Sass Way Five years of freeCodeCamp with Quincy Larson Oh my! Zsh. with Robby Russell Pure Charity A Protocol for Dying A Protocol for Dying with Pieter Hintjens The ZeroMQ Process: C4 Leading Leaders Who Lead Engineers with Lara Hogan Maintainer Week Every Commit is a Gift Open Sourcing the DEV Community with Ben Halpern

In this episode, Ben and I talk about the conception of CodeLand, last year's CodeLand, which had to switch to a virtual conference due to covid-19, and the biggest differences between CodeLand 2020 and CodeLand 2021. Registration for CodeLand is pay-what-you-want -- starting at $0. Grab your CodeLand 2021 ticket today at codelandconf.com. That's codelandconf.com. Show Links DevDiscuss (sponsor) DevNews (sponsor) Cockroach Labs (sponsor) Retool (sponsor) CodeLand 2021 (sponsor) CodeLand 2021

No matter where in the world you live, your life is affected by the ocean. But many of our oceans are sick, and have been so for a while. So what's keeping them from bouncing back to full health? Well, it's partly down to not agreeing on what a healthy ocean actually looks like that makes it hard to settle on the best course of action. But things might be about to change, albeit slowly.New science-based tools like the Ocean Health Index offer comprehensive assessments of the social, economic, and environmental conditions of an ocean.In this episode, Susa Niiranen talks to Ben Halpern the creator of the Ocean Health Index, and Thorsten Blenckner, a researcher at the Stockholm Resilience Centre who with his team has developed a spin-off called the Baltic Health Index.Together, they explore what it takes to restore an ocean to good health, and to what extent these new assessments can help us reach our goals.More information, including links to mentioned publications: www.rethink.earth/making-our-oceans-healthy-again/ See acast.com/privacy for privacy and opt-out information.

How to ride a bicycle…(Coach vs Consultant)Say you're learning how to ride a bicycle:A consultant would ride the bicycle for a while, and write you a "how to" manual. A coach would have you get on the bicycle and walk alongside you, guiding you through the process until you felt confident enough to ride on your own. “… Hire a consultant when you need an expert who can teach you a process or method. Hire a coach when you want to discover yourself.” - Leanne Wong.In today's podcast we're having a discussion all about coaching with the renowned coach Ben Halpern.Listen & Enjoy!

We do a crossover episode here with DevDiscuss and CodeNewbie talking about and role playing different soft skills, because this topic of soft skills is so important that we thought both of our audiences could benefit from it. To talk about these skills and to help us show what they can look like, we will be joined by artist and educator, Kristen Palana, and Liana Felt, senior people operations manager at Forem. Show Links TwilioQuest (sponsor) DevDiscuss (sponsor) DevNews (sponsor) Ambassador Labs (sponsor) Rudderstack (sponsor) New Relic (sponsor) Soft Skills & Career Success: How to Be Excellent at Work

In this episode, we talk about what are the core skills you need to go from developer to entrepreneur with Ben Halpern, co-founder of Forem, which acquired CodeNewbie in 2020. Ben talks about getting into development with entrepreneurship on the brain, building DEV and now his new venture, Forem, and what skills he looks for when hiring developers. Show Links TwilioQuest (sponsor) DevDiscuss (sponsor) DevNews (sponsor) Ambassador Labs (sponsor) Rudderstack (sponsor) New Relic (sponsor)

Dev.to has become one of the most popular places for developers to write about engineering, programming languages, and everyday life. For those who have not seen it, DEV is like a cross between Twitter and Medium, but targeted at developers. The content on DEV ranges from serious to humorous to technically useful.DEV contains a set of features which appeal to a developer community, such as the ability to embed code snippets in a post, but for the most part the entire app is generalizable to other types of communities. Hence, the motivation for “Forem”. Forem is an open source project to make it possible to spin up instances of communities that are like DEV, but for other communities such as mixed martial arts, or doctors.Ben Halpern is the creator of DEV and Forem, and he joins the show to talk about the DEV Community and his long-term goals for what the DEV team is building.

Dev.to has become one of the most popular places for developers to write about engineering, programming languages, and everyday life. For those who have not seen it, DEV is like a cross between Twitter and Medium, but targeted at developers. The content on DEV ranges from serious to humorous to technically useful. DEV contains a The post DEV and Forem with Ben Halpern appeared first on Software Engineering Daily.

Dev.to has become one of the most popular places for developers to write about engineering, programming languages, and everyday life. For those who have not seen it, DEV is like a cross between Twitter and Medium, but targeted at developers. The content on DEV ranges from serious to humorous to technically useful. DEV contains a The post DEV and Forem with Ben Halpern appeared first on Software Engineering Daily.

Dev.to has become one of the most popular places for developers to write about engineering, programming languages, and everyday life. For those who have not seen it, DEV is like a cross between Twitter and Medium, but targeted at developers. The content on DEV ranges from serious to humorous to technically useful. DEV contains a The post DEV and Forem with Ben Halpern appeared first on Software Engineering Daily.

Ben Halpern and Jess Lee are the co-founders of Dev.to, an online community dedicating to helping the developer community communicate. They've been described as a social network for software developers, where anyone from novices to experts can create a blog post to share their ideas. They worked on the site for a long time as a side project, and after they launched, the unexpected and overwhelmingly positive responded they received encouraged them to turn it into their full-time job. Part of what makes Dev.to so appealing is that it's been designed to be fast. The site is designed to take advantage of caching at POP centers, so that individuals around the world can access the content as quickly as possible. Since the project is also open sourced, they've been able to receive contributions from over 500 individuals, ensuring that no bug goes unseen. Dev.to also considers community health to not just be essential to the business, but also a value woven into the company and the product. Their focus on education and strong moderation tooling has helped them build trust in their users. Users feel safe when the site actively minimizes aggressive language. The future of Dev.to is shaped by the feedback they receive, but in many instances, they allow the community to thrive without too much administrative interference. Links from this episode Dev.to is a community of software developers getting together to help one another out. CodeNewbie is a supportive, international community of people learning to code. DevDiscuss is a podcast from CodeNewbie that shares stories from people on their coding journey. CodeLand Conf is a community-first remote conference.

As an industry, tech is not well equipped to accept when people change their names. This problem effects a range of people, including those who have a change of marital status. However, it can especially effect the security of those who are survivors of domestic violence, and those who are trans, who have to suffer through deadnaming by their tech accounts. This constant barrage of deadnaming can be very psychologically and emotionally harmful. DevDiscuss hosts Ben Halpern and Jess Lee speak with Penelope Phippen, director at Ruby Central, and author of the DEV post, "Changing your name is a hard unsolved problem in Computer Science," about this issue and what can be done to make it better. Show Links Digital Ocean (sponsor) MongoDB (sponsor) Heroku (sponsor) TwilioQuest (sponsor) Ruby RSpec Rails Ruby Central RubyConf RailsConf RuboCop Go Format Changing your name is a hard unsolved problem in Computer Science Falsehoods Programmers Believe About Names GitHub One Medical Whipping Girl: A Transsexual Woman on Sexism and the Scapegoating of Femininity GLAD SheCodes LivingSocial Rubyfmt

(October 3, 2018) Rick catches up with DEV co-founders Jess and Ben to discuss the results of their community survey into the state of web development.  Learn about the survey → https://goo.gle/2zck6T6  Explore the results on BigQuery → https://goo.gle/2YD3rCA 

(Originally aired on YouTube on July 25, 2018) Rick chats with Jess and Ben, co-founders of DEV, an online community for developers to share ideas, collaborate together, and learn from each other. Jess and Ben talk about what DEV is, the inspiration behind it, and what they've learned from their community about the state of web development.  Join the community → https://dev.to Take the survey → https://dev.to/survey

Chris Ferdinandi on Greater Than Code, Ben Orenstein on Maintainable, Susan Rice on Coaching For Leaders, Courtland Allen on Software Engineering Unlocked, and Matt Stratton on Hired Thought. 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 March 16, 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. CHRIS FERDINANDI ON GREATER THAN CODE The Greater Than Code podcast featured Chris Ferdinandi with hosts Rein Henrichs and Jacob Stoebel. Chris is a proponent of plain vanilla JavaScript. He says that modern web development has grown so much in scope and complexity that it makes it difficult for beginners to get started and it can negatively impact the performance of the web for users in ways that developers with fast machines don’t always feel. One of the reasons things are the way they are today, Chris says, is because a lot of backend developers migrated to the front end because that was where the exciting stuff was happening and they brought with them their approaches and best practices. The front end, however, is a very different medium. In the back end, you have control over how fast the server is, when things run, the operating system, etc. On the front end, you have none of this. People are accessing what we build on a variety of devices that may or may not be able to handle the data we’re sending and may have unpredictable internet connections. If a file fails to download or the user goes through a train tunnel and we’ve built things in a modern JavaScript-heavy way, the whole house of cards falls apart on these users. Chris would like people not to abandon JavaScript altogether, but to be a little more thoughtful about how we use it. Modern web development involves a few things: frameworks, package managers, and doing more and more things (such as CSS) in JavaScript. All of this JavaScript has the effect of slowing down performance because 100KB of JavaScript is not the same as 100KB of CSS, a JPEG, or HTML because the browser needs to parse and interpret it. Because of these performance problems, single page apps have become more popular. But now you’re recreating in JavaScript all the things the browser gave you out of the box like routing, shifting focus, and handling forward and back buttons. You’re solving performance problems created by JavaScript with even more JavaScript, which is the most fragile part of the stack because it doesn’t fail gracefully. If a browser encounters an HTML element it doesn’t recognize, it just treats it as a div and moves on. If you have a CSS property you mis-typed, the browser ignores it. But if you mistype a variable in JavaScript, the whole thing falls apart and anything that comes after that never happens.  For Chris, a better approach to web development is one that is more lean and more narrowly-focused on just the things you need. His first principle is to embrace the platform. For example, a lot of people don’t realize that DOM manipulation that used to be really hard years ago is really easy these days in vanilla JavaScript. Also, many of the things that JavaScript was required for in the past can be done more efficiently today with HTML and CSS. He also says that we need to remember that the web is for everyone. Because we are often using high-end computers, the latest mobile devices, and fast internet connections, we forget that this is not the experience for a majority of web users. We build things that work fine on our machines but are painfully slow for the people who actually use the things we build. They ended their discussion with reflections. Chris’s reflection was about learning JavaScript and web development for the first time. He says that people learning shouldn’t be made to feel like they need to dive in to the latest trends, but should instead find a way to learn the fundamentals. Apple Podcasts link: https://podcasts.apple.com/ca/podcast/170-the-case-for-vanilla-javascript-with-chris-ferdinandi/id1163023878?i=1000466076138 Website link: https://www.greaterthancode.com/the-case-for-vanilla-javascript BEN ORENSTEIN ON MAINTAINABLE The Maintainable podcast featured Ben Orenstein with host Robby Russell. Ben believes that, in a maintainable codebase, the code should match how you think about the world. When speaking about the domain with your teammates, do you use the same terminology that the code uses? Do you use the term “user” but the code uses the term “customer”? Getting your terms consistent is a specific case of a more general principle of implicit and explicit knowledge. Maintainable systems have as much knowledge put into them as possible so that they become sources of truth. Ben’s definition of technical debt is a technical shortcut you took intentionally after weighing it against alternatives and deciding it was worth it in the short team with the eventual intention of eliminating it. He says it is hard to get time on a schedule dedicated to cleaning up technical debt, so it is your professional responsibility to clean it up as you go. Ben says that asking permission to clean up technical debt as you deliver a feature is like asking permission to do your job well. He says that the idea of “We’ll go fix this later” never happens and, if you don’t believe him, grep your codebase for the string “TODO”. Apple Podcasts link: https://podcasts.apple.com/ca/podcast/ben-orenstein-someday-well-go-clean-that-up-doesnt-work/id1459893010?i=1000466511242 Website link: https://maintainable.fm/episodes/ben-orenstein-someday-well-go-clean-that-up-doesnt-work-_fGCpf6F SUSAN RICE ON COACHING FOR LEADERS The Coaching For Leaders podcast featured Susan Rice with host Dave Stachowiak. From the time she was seven, Susan would hear her parents fighting loudly and violently when she was trying to sleep at night. When the fighting got scary and out of control, Susan would step in. Sometimes that meant talking them down and sometimes that meant separating them. The mediation she did with her parents taught her how to interact with parties who were intractably opposed. This developed in her a lack of discomfort with conflict, disagreement, and argument. She said that this helped her to be willing to stand up and not be conflict-averse. This reminded me of the Buster Benson episode of Lead From The Heart I summarized in my last article. Dave asked Susan about a section of her book Tough Love in which she described some feedback she received from former congressman Howard Wolpe when she was Assistant Secretary of State. He warned her bluntly that she would fail as Assistant Secretary if she did not correct course and she came to agree with that. She was only thirty-two at the time and had never held a position like this before. In 1998, six months into her tenure, a series of crises hit. Africa’s “first world war” broke out and, then in August of 1998, Al Qaida attacked the American embassies in Kenya and Tanzania, killing twelve Americans and over two hundred Kenyans and Tanzanians. This was both a horrific loss and a policy blow for those who were working on Africa at the time. Rather than addressing the pain they were all feeling head on, her approach to dealing with it was to charge through it as she did her parent’s divorce. This wasn’t a leadership style that would work in that context and Howard Wolpe gave her the tough love she needed at the time. Over the Christmas holiday, she reflected on what he had told her and realized that he was right. She had to be more patient. She had to be more respectful and solicitous of other people’s views and perspectives. Dave asked what she did first to make this change in her leadership style. Susan says she started by being more humble. She brought people into decision-making even if their recommendations were not ones that she ultimately accepted. She says, ”You can get a long way leading a team, even if many members of the team don’t actually agree with the direction you’re steering towards, if they feel that their advice, perspective, recommendations have truly been heard and appreciated.” Dave asked how she ensures in meetings between high ranking officials that everyone is genuinely heard even when she doesn’t agree with everything they are saying. She says it is not just what happens when you’re sitting around the meeting table. It comes down to the preparations going into the discussion: the quality of the paper that lays out the issues and the actions and the coherence of the agenda. Managing the meeting, though, is the hardest part. You have to make sure the options are given due consideration and everybody gets a chance to express their judgment. Apple Podcasts link: https://podcasts.apple.com/us/podcast/456-how-to-be-diplomatic-with-susan-rice/id458827716?i=1000466472793 Website link: https://coachingforleaders.com/podcast/be-diplomatic-susan-rice/ COURTLAND ALLEN ON SOFTWARE ENGINEERING UNLOCKED The Software Engineering Unlocked podcast featured Courtland Allen, founder of the Indie Hackers podcast and community with host Dr. Michaela Greiler. Michaela asked Courtland what was different about Indie Hackers compared to the earlier startups he had founded that made for its success. He said that for Indie Hackers, his notion of a business idea changed. Back in 2009, if you asked him about a business idea, he would have described a product idea and wouldn’t have been able to say much about how to get the product in customer’s hands, how much to charge for it, or even who the customer was. With Indie Hackers, he was thinking about all aspects of the business. She asked whether the original Indie Hackers idea was to build a community. Courtland said that while there was no desire to do a podcast at first, he always had a plan to build a community. He had multiple phases for Indie Hackers to go through to get to where he wanted it to be. Phase one was a blog where people who wanted to earn financial and creative freedom though revenue-generating side projects could go to find interviews Courtland had done with people like themselves. He figured these blog readers would subscribe to his newsletter and from there he would build a community forum where people could help each other. Somewhere along the line, the podcast was added based on community demand. Michaela asked how Courtland managed to keep Indie Hackers successful as a business when similar communities are struggling. Courtland believes that there are a few principles behind the success of Indie Hackers. The first is that you are much more likely to generate meaningful revenue quickly if you are charging for something that each customer is willing to pay a lot of money for. Regarding building a successful community, you have to start with your marketing. A community is a chicken-and-egg problem where the whole value of a community is the people inside it, making it really hard to start from nothing. With Indie Hackers, he started with content that brought in the people who could form the community. Courtland had thousands of people coming to the website before he turned it into a community. Another example is dev.to. Its founder, Ben Halpern, spent years just growing his Twitter account, tweeting funny jokes and helpful tips for developers. When he launched his community, he was able to advertise it from his Twitter account. A second thing you need to build a community is to seed it with discussions. As Courtland also described in an episode of Software Engineering Daily that I summarized in “Lighting Up The Brain and Joining A Gym”, he started his community by having conversations with fake accounts that were secretly also himself. Ben Halpern kickstarted the dev.to community with discussions with his friends. Choice of topic is critical too. You want a topic that you can talk about forever. The dev.to community’s topic is software engineering. It is the perfect topic because lots of people are learning and trying to learn from each other and there are countless issues and frameworks to talk about. Similarly, there are countless topics and subtopics around founding companies. As Courtland also said on Software Engineering Daily, you also need to think about the timing for when people get together and the space your community takes up. If you throw a party in a small room, you only need ten people to make that party feel like a success, but if you throw it in a football stadium, you need forty thousand people for it to feel like a success. It is the same with an online community. If you constrain it by saying something like, “Our community is just one discussion thread every Sunday at 3:00pm,” then even with ten people, that community can feel like it’s thriving. He talked about how he got advertisers interested in Indie Hackers and how he eventually got Indie Hackers acquired by Stripe and now no longer spends time selling ads. Not much has changed, he says, now that he is an employee of Stripe because Indie Hackers and Stripe were aligned from the beginning. Michaela asked why he decided, despite his desire to write as little code as possible, to create custom software for the Indie Hackers forum when he could have chosen third-party forum software. Courtland said he wanted Indie Hackers to have a strong brand and it is hard to have a strong brand if the thing you’re building looks like everything else. So he put a lot of time making the community unique. He spent a lot of time on the name of the community and the design of the website, all in support of having a strong brand. Apple Podcasts link: https://podcasts.apple.com/ca/podcast/starting-profitable-business-in-six-weeks-courtland/id1477527378?i=1000465925620 Website link: https://www.software-engineering-unlocked.com/episode-12-profitable-business-courtland-allen/ MATT STRATTON ON HIRED THOUGHT The Hired Thought podcast featured Matt Stratton with host Ben Mosior. Since his move from Chef to PagerDuty, Matt’s focus has shifted from software delivery and infrastructure code to incidents and outages. Ben brought up Matt’s talk “Fight, Flight, or Freeze — Releasing Organizational Trauma.” Matt’s motivation for creating this talk was his own treatment for PTSD and a discussion with J. Paul Reed where they kept seeing similarities between Matt’s experiences and what companies go through when they experience an incident. Trauma occurs when our response to something is ineffective. Two people can have a similar experience and it can be traumatic to one person and just a bad day for the other. We respond to perceived trauma physiologically the same way as actual trauma. Events that are reminiscent of trauma that occurred to Matt as a child trigger him to have the same physiological response today. Organizations do the same thing. An organization that has an outage that is similar to an event that happened before and, say, cost them a million dollars a minute, will react the same way. Just as an adult re-experiencing a childhood trauma because of a triggering event shouldn’t necessarily respond the same way, an organization needs to learn how to respond differently to these similar stimuli. Matt talked about the window of tolerance beyond which you become activated and have an unhealthy response. He says that it can get spiky or you can get stuck-on or stuck-off. If you are stuck-on, you have anxiety and other symptoms. If you are stuck-off, there is lethargy. In an organization, we can get into a hyper-aroused state fearing any type of change, getting into analysis paralysis, or becoming over-vigilant. None of these states are healthy and they trickle down into the emotional health of employees. The good news is there are things we can do to help the organization be better. Ben added that a lot of therapy is about building up the language to describe what is happening so that when it happens or when you are reflecting back later, you can share the experience and develop skills to lengthen your window of tolerance. Matt talked about how in cognitive behavioral therapy we try to identify when a distortion occurs, knowing that the feeling we experience is not something we can change, but our response to it can be changed. In an organization, we can do the same thing. Matt is striving to excise the word “prevention” from his vocabulary and instead become more resilient when something bad happens. For a person, this can mean that you can have something happen and then you can get back inside your window of tolerance quickly. For an organization, this means that an incident can happen and we can restore service and get on with business. We need to normalize incident response. It is not an anomaly to have an incident. The irony is that we’ve gotten worse at responding to incidents as we’ve gotten better at distributing on call. Back in his days as a sysadmin, Matt was on call constantly and incident response was business as usual. Today, if you are doing a healthy on call rotation with developers on call in their own domain, you can be on call for a year and experience just two incidents. Then, when you have an incident, you freak out. You don’t want to be trying to remember how to do incident response and you don’t want to think of the response process as an exceptional thing that we only sometimes do. Ben connected this to the book The Fifth Discipline. He says we always feel like we have to do something in response to something bad happening. The other thing the book points out is that whenever you are doing an intervention, yes, you may have short term actions that buy you time, but at all times, you need to be building capabilities. When you normalize incident response and you regularly show people what it looks like to work together in a high-pressure situation, you learn to respond to incidents in healthy ways. Matt says we need to run our failure injection exercises and game days like real incidents. This is also an opportunity to train your incident commanders. In these scenarios, we know what’s wrong and we can bail out at any time. Then, when a real incident occurs at 2:00am some morning, the people who did the exercise associate the real incident with the calm exercise they did in the office on an afternoon. Sometimes there are people who want run an exercise and not tell the incident response team what’s wrong. Matt has to explain to these people that it is not an exercise in troubleshooting or to stress test your people. You don’t need to inject stress into the people who work for you. You want to do the opposite. When we are doing incident response all the time as part of the regular cadence of work, when a real incident occurs, we will associate it with the positive physiology of our response during the exercise. That means we should treat every incident the same, even false alarms. If you get a few minutes into responding to an incident and realize it is a false alarm, finish it out as an incident. Get on the bridge and do as you would in a real incident. Apple Podcasts link: https://podcasts.apple.com/ca/podcast/6-organizational-resilience/id1479303584?i=1000466488009 Website link: https://hiredthought.com/2020/02/24/6-organizational-resilience/ 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:

Podcast Description “Democratizing and meritocracy and those things are not just not a step forward. They are the right idea in the most ignorant way. They are coming from the perspective of trying to ‘do right’ but not applying any actual complex thinking towards what ‘doing right’ is.” Ben Halpern is the founder of DEV Community (dev.to), a social network for all software developers to learn from one another and grow together. Additional Resources Dev Community Black girls in US pushed out of school over racist and sexist school dress codes The 'Adultification' of Black Girls: Less Protection, More Discipline Admitting the Harm I Caused As An Educator Twitter Ben Halpern Become a #causeascene Podcast sponsor because disruption and innovation are products of individuals who take bold steps in order to shift the collective and challenge the status quo. Learn more > All music for the #causeascene podcast is composed and produced by Chaos, Chao Pack, and Listen on SoundCloud. Listen to more great #causeascene podcasts full podcast list >

Ben Halpern is best known for building the DEV community, centered around https://dev.to. During our conversation, we talked about his journey from marketer to developer and from developer to founder. Ben shared with me why he uses the title Webmaster and a little bit about his upbringing and unique world-view. Ben's Incredible Website: http://benhalpern.com/

On-call can come in different shapes and sizes. Sometimes it's a group of developers who are attacking a problem to keep other developers afloat. That's what Ben Halpern and the team at the DEV Community are up to. Founder of DEV, Canadian, generalist software developer who writes a lot of Ruby. Transcript: https://aka.ms/AA5r8ja https://dev.to/ben https://twitter.com/bendhalpern

Recording date: 2019-05-21 John Papa @John_Papa Ward Bell @WardBell Dan Wahlin @DanWahlin Ben Halpern @BenHalpern Resources: Dev.to Searching for Sleep on Dev.to Dev.to on GitHub John on Medium John Papa on dev.to "How I Write Articles" by John Peacock release article Peter Frank - co-founder - on dev.to Jess Lee - co-founder - on dev.to Top Tags Code Climate Code Climate score on dev.to Web Storage Fastly Preact Ali Spittel Emma Wedekind RegEx Cheat Sheet Anna at dev.to Anna's post on joining the dev.to team dev.to vs Medium Comparing Medium to dev.to Why technical blogs belong on dev.to Serverless app design by John Papa dev.to API Someone to follow Mary Roach / @Mary_Roach Ananya Neogi / CSS Can Do That Timejumps 01:01 Learning about sleep 02:49 Guest introduction 03:50 What is Dev.to? 07:15 What's the business model for Dev.to? 10:45 How do you keep going with a project long term? 17:41 Sponsor: IdeaBlade 18:40 Badges on Github repos 24:42 What technologies are being used to build dev.to? 28:46 What's the userbase size? 30:14 What does a registered user get on Dev.to? 37:09 April Fool's joke gone awry 55:43 Someone to follow

Abadesi is back to talk to Ben Halpern, creator, founder, and webmaster of DEV, an online community where developers share ideas and help each other grow. He is also behind @ThePracticalDev on Twitter and runs DEV alongside his two other co-founders, Jess Lee and Peter Frank. Fun fact: Ben is a Canadian who moved to NYC to join a startup and never left. He spoke to Aba from Brooklyn. In this episode we talk about: Why you need to lead by example when you're building an online community and how your behavior as a founder on the site can be more effective in setting a tone than complicated rules. How DEV manages their distributed team, the advantages of working from home, and being honest with yourself about when you need to take a break from your work as a founder, even if it's not easy to do. His love for open source, his predictions for future trends on the web and his very unique personal website, which is a throwback to the web of years past. We also talk about his love for Tiles, the surprising usefulness of Android's Measure app, and why Ben says if you're not using a password manager, you're “not living your digital life to the fullest.” We’ll be back next week so be sure to subscribe on Apple Podcasts, Google Podcasts, Spotify, Breaker, Overcast, or wherever you listen to your favorite podcasts. Also, big thanks to AngelList and FreshBooks for their support.

The DEV Community is a platform where developers share ideas, programming advice, and tools. Ben Halpern started it after running an extremely successful Twitter account creating humorous tweets for developers. One way to describe DEV Community is as a cross between Medium, Stack Overflow, and Reddit–but it has its own personality, so I recommend checking The post DEV Community with Ben Halpern appeared first on Software Engineering Daily.

When Ben Halpern (@bendhalpern) decided to start another business, he set a very unusual expectation: He gave himself 10 years to succeed. In this episode, we discuss how Ben's patient approach and obsession with understanding things from his users' point of view helped him grow as massive following on Twitter and parlay that into fast-growing online community for developers.Transcript, speaker information, and more: https://www.indiehackers.com/podcast/069-ben-halpern-of-dev-to

We talk with Ben Halpern the founder and webmaster of dev.to — a community for developers to talk about software. Last Wednesday they open sourced the codebase of the dev.to platform, so we wanted to talk through all the details with Ben. We talked through the backstory, how Ben realized this could become a business, how the team was formed, their motivations for open sourcing it and why they didn’t open source it from the start, the technical stack, and their vision for the future of the site.

We talk with Ben Halpern the founder and webmaster of dev.to — a community for developers to talk about software. Last Wednesday they open sourced the codebase of the dev.to platform, so we wanted to talk through all the details with Ben. We talked through the backstory, how Ben realized this could become a business, how the team was formed, their motivations for open sourcing it and why they didn’t open source it from the start, the technical stack, and their vision for the future of the site.

Ben Halpern knows a lot about founding and growing online communities responsibly. He joins us to share his knowledge and experience from turning a popular Twitter handle into the Dev.to online community platform.

Anil Dash joins us for hosting duties again this week along with co-founders Jess Lee and Ben Halpern of the Practical Dev. Topics include Shabbat elevators, Failure, and racist AI.

Anil Dash joins us for hosting duties again this week along with co-founders Jess Lee and Ben Halpern of the Practical Dev. Topics include Shabbat elevators, Failure, and racist AI.

In today's episode, I talk with Ben Halpern. You may know him from his tweets as @ThePracticalDev. Ben also is the founder of dev.to, a site for developers to share knowledge and culture with one another. Check out dev.to to learn a bit more about what Ben has created!

In today's episode, I talk with Ben Halpern. You may know him from his tweets as @ThePracticalDev. Ben also is the founder of dev.to, a site for developers to share knowledge and culture with one another. Check out dev.to to learn a bit more about what Ben has created!

Ben Halpern, founder of The Practical Dev and other tech startups, explains how he began learning to code after studying marketing in college. He also shares advice for beginners, teaching themselves how to code.

Bot fraud, the New York tech scene, RethinkDB and open source; these topics and more are discussed in today’s episode. Two of the most popular guests return to the show to explore a variety of topics. Ben Halpern is the creator of The Practical Dev, a massively popular Twitter account and blog that you may The post Topic Roundtable with Haseeb Qureshi and Practical Dev’s Ben Halpern appeared first on Software Engineering Daily.

Bot fraud, the New York tech scene, RethinkDB and open source; these topics and more are discussed in today’s episode. Two of the most popular guests return to the show to explore a variety of topics. Ben Halpern is the creator of The Practical Dev, a massively popular Twitter account and blog that you may The post Topic Roundtable with Haseeb Qureshi and Practical Dev’s Ben Halpern appeared first on Software Engineering Daily.

Ben Lesh and Tracy Lee interview Ben Halpern, the "voice" behind the famous twitter handle, @ThePracticalDev.  Did you know you can tweet The Practical Dev about your javascript homework? This podcast gives us a fun and quick view into what it's like behind the scenes as The Practical Dev. Learn about the organization and its the future.  Hear stories about run-ins with Tim O'Reilly, the JavaScript community, and how why Sebastian McKenzie once blocked Jay Phelps on Twitter. Hint: It was Sam Saccone's fault. Find more podcasts, videos, trainings and online conferences at http://modern-web.org or follow us on Twitter @modernweb_.

Most programmers spend lots of their time reading content about software. Since our field changes so rapidly, engineers consume news and editorials voraciously, trying to keep up with the impossibly fast pace. The Practical Dev is a collection of blog posts, editorials, and interviews that was created to help with that end. Ben Halpern is The post Software Editorialism with Practical Dev’s Ben Halpern appeared first on Software Engineering Daily.

Most programmers spend lots of their time reading content about software. Since our field changes so rapidly, engineers consume news and editorials voraciously, trying to keep up with the impossibly fast pace. The Practical Dev is a collection of blog posts, editorials, and interviews that was created to help with that end. Ben Halpern is The post Software Editorialism with Practical Dev’s Ben Halpern appeared first on Software Engineering Daily.

Dr. Benjamin Halpern is a Professor in the Bren School of Environmental Science and Management at the University of California Santa Barbara and Chair in Marine Conservation at Imperial College London. He also serves as the Director of the Center for Marine Assessment and Planning (CMAP) at UC Santa Barbara and as a Research Associate at the National Center for Ecological Analysis and Synthesis (NCEAS). Ben received his PhD in Ecology, Evolution, and Marine Biology from the University of California Santa Barbara. Afterwards, he held a joint postdoctoral fellowship at the National Center for Ecological Analysis and Synthesis and the Smith Fellowship Program sponsored by The Nature Conservancy. He then worked as a Research Biologist at the Marine Science Institute and was a Center Associate of the National Center for Ecological Analysis and Synthesis before accepting his current positions. Ben is here with us today to tell us about his journey through life and science.