Devops[RunAs Radio] The DevOps Handbook with Gene Kim http://runasradio.com/Shows/Show/510
- The DevOps Handbook is finally released! Richard chats with the one-and-only Gene Kim about the five years of effort that have gone into making the DevOps handbook. Gene talks about how the Handbook was supposed to come out before the Phoenix project, but as the scope of the book grew, they realized it needed more time. The benefit of time has been a ton of case studies and great detailed evidence of how automating workflows, instrumenting systems deeply and a culture of experimentation leads to better applications, happier employees and customers, and a better business all around. You need to read this book!
[Radio TFS] A New Year with Donovan Brown http://www.radiotfs.com/Show/129/ANewYearwithDonovanBrown
- Donovan is a Principal Program Manager for DevOps in the Developer Division at Microsoft, focusing on developer tools including Visual Studio Team Services and Team Foundation Server.
- In this episode Greg, Martin, Josh and Angela are joined by Donovan Brown to talk TFS, VSTS and, of all things, DevOps!
Programming and Testing[No Fluff Just Stuff] REST is Dead, Long Live the Web! http://blog.nofluffjuststuff.com/2015/12/28/podcast-rest-is-dead-long-live-the-web/
- REST is dead, long live the Web
[Full Stack Radio] Toran Billups - Test Driving the Front-end http://www.fullstackradio.com/49
[No Fluff Just Stuff] Professional Git with Brent Laster http://blog.nofluffjuststuff.com/2016/12/28/professional-git-brent-laster/
- He talks and trains in-depth on not only in Git and source control, but continuous delivery concepts, and a variety of different topics. He’s just published his book, “Professional Git,” by Brent Laster. It’s available on Amazon. We sat down to dive deep and talk all things Git
[Software Engineering Daily] Bots Podcast with Jon Bruner https://softwareengineeringdaily.com/2016/12/15/bots-podcast-with-jon-bruner/
- Over the next few years, bots will pervade our lives more and more. These smart, conversational text interfaces provide a new way of engaging with the computer systems that we have been mostly interacting with through web and mobile app interfaces for the last decade.
- Bots are a necessary complement to the voice interfaces of the future, because we don’t always want to talk to the computer, and natural language processing is not yet good enough to always translate our vocal request accurately. Bots are not toys, they aren’t trivial, and they aren’t going away any time soon.
[Complete Developer Podcast] Learning A Second Language http://completedeveloperpodcast.com/episode-67/
- Before starting to learn a new programming language you should take a few considerations. How different is the new language from your current one? Compare the envivornment, paradigm, syntax, and level of automatic operations between the languages.
- Tim Ferris wrote up twelve rules for learning a a new language. His rules were for a spoken language but they can also be applied to programming languages.
- Learn the right words, the right way.
- Learn cognates, things that are the same across languages.
- Interact daily in the language through spaced repetition in a controlled environment.
- Daily spoken practice.
- Look for free resources.
- Realize that experience makes it easier to infer rules.
- Learn to effectively use mnemonics.
- Embrace mistakes.
- Create Smart goals (Specific, Measurable, Attainable, Relevant, Time-Bound).
- Jump from conversational to mastery.
- Learn to sound more native through the use of idioms.
- Keep going until you actually get things down.
[Software Engineering Radio] Peter Hilton on Naming http://www.se-radio.net/2016/12/se-radio-episode-278-peter-hilton-on-naming/
- why naming is much harder than we think, why naming matters in programming and program comprehension, how to create good names, and recognize bad names, and how to improve your naming skills.
[Cucumber Podcast] Cucumber Anti-Patterns https://cucumber.io/blog/2016/05/09/cucumber-antipatterns
- Matt, Steve, and Aslak from the core Cucumber team discuss writing good gherkin and avoiding common pitfalls.
- We’ll unpick why it’s important to write your gherkin before you write the code, consider if you should ever delete scenarios, and give tips on incorporating your team’s different perspectives into maintainable, predictable cukes!
[Software Engineering Radio] Gerald Weinberg on Bugs Errors and Software Quality http://www.se-radio.net/2017/01/se-radio-episode-280-gerald-weinberg-on-bugs-errors-and-software-quality/
- Gerald Weinberg about software errors, the fallacy of perfection, how languages and process can reduce errors, and the attitude great programmers have about their work. Gerald’s new book, Errors: Bugs, Boo-boos, and Blunders, focuses on why programmers make errors, how teams can improve their software, and how management should think of and discuss errors. We learn why all programs are perfect (for something), quality can be judged only by the end user of the software, and computers act as “error amplifiers” for our own human imperfections.
Architecture[Software Engineering Daily] Reactive Microservices with Jonas Boner https://softwareengineeringdaily.com/2016/12/19/reactive-microservices-with-jonas-boner/
- For many years, software companies have been breaking up their applications into individual services for the purpose of isolation and maintainability. In the early 2000s, we called this pattern “service-oriented architecture”. Today we call it “microservices”.
- The reactive manifesto is a collection of principles for how to build applications. When the reactive manifesto is applied to the idea of microservices, we get reactive microservices, which Jonas and I discuss in today’s episode.
[Software Engineering Daily] Self-Contained Systems with Eberhard Wolff https://softwareengineeringdaily.com/2017/01/03/self-contained-systems-with-eberhard-wolff/
- Self-contained systems is an architectural approach that separates the functionality of a system into many independent systems. Each self-contained system is an autonomous web application, and is owned by one team. Communication with other self-contained systems or 3rd party systems is asynchronous where possible.
- As Eberhard Wolff explains in this episode, self-contained systems is not the same thing as microservices, but they are not mutually exclusive. Organizations often adopt a mix of architectural ideas, and it is worth understanding these different models so you can decide which of them to apply to your own projects.
[Software Engineering Daily] Evolutionary Architecture with Neal Ford https://softwareengineeringdaily.com/2017/01/05/evolutionary-architecture-with-neal-ford/
- Evolutionary architecture supports incremental, guided change as a first principle along multiple dimensions. A company with an evolutionary architecture is structured to evolve in response to changes inside the company (such as a decision to change the product) or outside the company (such as the emergence of Docker). Neal Ford is an architect at ThoughtWorks and one the creators of the evolutionary architecture concept.
[AWS Podcast] Serverless Special https://aws.amazon.com/podcasts/aws-podcast/#171
- Bryan Liston, Developer Advocate for AWS Serverless, speaks with Matt Weagle, Ant Stanley & Ben Kehoe. They discuss server less architectures, testing and other fun topics!
Agile, Teams and Business analysis[Mastering Business Analysis] Split Your Stories! https://www.acast.com/masteringbusinessanalysis/mba101-split-your-stories
- The problems big user stories can cause
- How big your user stories should be
- Why splitting stories helps create a shared understanding
- How just four splitting techniques apply to almost all stories
[Agile for Humans] Agile is a cancer http://ryanripley.com/003-agile-for-humans/
- Zach is an independent consultant who recently posted a provocative article called: “The Subversion of Agile: Agile is a Cancer”. We discussed his post, talked about what the cancer is in the community that needs to be removed about posts from others in the community about the “death of Agile”.
[Developing Up] The Four Attributes of a Great Development Team http://www.developingup.com/7
- The four attributes of a great development team:
- Positive attitudes
[Developing Up] The Importance of one-on-ones http://www.developingup.com/8
- Great developers need great support, feedback and communication. In today's episode we talk about the importance of regular one-on-one meetings for both developers and managers. We discuss how managers can establish and maintain successful one-on-one meetings. We then discuss how as a developer you can take ownership of and benefit from these meetings.
[Mastering Business Analysis] Using Behavior Driven Development for Better User Stories http://masteringbusinessanalysis.com/episode-023-using-behavior-driven-development-for-better-user-stories-interview-with-jeffrey-davidson/
- Better understand how to get better at user stories and how behavior driven development (BDD) helps create a shared understanding. We also discuss how to create the nirvana state of living requirements.
[.NET Rocks!] Punishment Driven Development with Louise Elliott https://www.dotnetrocks.com/?show=1406
- The beatings will continue until morale improves!
- Louise talks about getting rid of blame and punishment, whether self-inflicted or team-inflicted, so that the individual unique contributions and capabilities of every member of the team are valued. The conversation also dives into creating constructive incentives - not pitting team members or separate teams against each other, actually making sure everyone is focused on making sure the business is successful.
Other interests and stuff[Revisionist History] Blame Game http://revisionisthistory.com/episodes/08-blame-game
- How can we all make human error
- The simplest solution often is
- Cars with runaway acceleration. And what to do if it does. It can happen to you, honestly
- In the summer and fall of 2009, hundreds of Toyota owners came forward with an alarming allegation: Their cars were suddenly and uncontrollably accelerating. Toyota was forced to recall 10 million vehicles, pay a fine of more than $1 billion, and settle countless lawsuits. The consensus was that there was something badly wrong with the world’s most popular cars. Except that there wasn’t.
- “Blame Game” looks under the hood at one of the strangest public hysterias in recent memory. What really happened in all those Camrys and Lexuses? And how did so many drivers come to misunderstand so profoundly what was happening to them behind the wheel? The answer touches on our increasingly fraught relationship to technology and the dishonesty and naiveté of many in the media.
[TED Talks] How to gain control of your free time https://www.ted.com/talks/laura_vanderkam_how_to_gain_control_of_your_free_time
- There are 168 hours in each week. How do we find time for what matters most? Time management expert Laura Vanderkam studies how busy people spend their lives, and she's discovered that many of us drastically overestimate our commitments each week, while underestimating the time we have to ourselves. She offers a few practical strategies to help find more time for what matters to us, so we can "build the lives we want in the time we've got."
[TED Talks] Bring on the female superheroes! https://www.ted.com/talks/christopher_bell_bring_on_the_female_superheroes
- Why is it so hard to find female superhero merchandise? In this passionate, sparkling talk, media studies scholar (and father of a Star Wars-obsessed daughter) Christopher Bell addresses the alarming lack of female superheroes in the toys and products marketed to kids — and what it means for how we teach them about the world.
[Developer On Fire] Neal Ford - Architecting Appreciation http://developeronfire.com/podcast/episode-197-neal-ford-architecting-appreciation
[No Fluff Just Stuff] Lifelong Learning with Venkat Subramaniam http://blog.nofluffjuststuff.com/2016/11/16/lifelong-learning-venkat-subramaniam/