Friday, 30 June 2017

Damo's June 2017 Podcast Highlights

I subscribe to many podcasts, you can see the list as it was in 2015 here: Developer podcasts v2. I'm keeping a podcast blog here of the episodes that I find interesting or useful in some way.

Architecture and Devops

[The Changelog] The Serverless Revolution for javascript programmers

  • Pam Selle at OSCON about the serverless revolution happening for JavaScript developers
  • Gain a general understanding of serverless and possible architectures
  • Serverless computing—using platforms like AWS Lambda, Google Cloud Functions, or Azure Functions—takes your microservices architecture and brings it into a new age of operations. Why maintain a server when you can run your code on-demand? Combine this power with Node.js and JavaScript-powered applications, and you have an amazing combination in your hands.
  • Pam Selle offers an overview of serverless computing, including why it’s so revolutionary and where to get started, and explains how you can use it to power your apps at a fraction of the usual cost of compute using a JavaScript-dominant architecture.

[Run As Radio] DevOps in 2017

  • How is DevOps evolving? While at the DevOps Enterprise Summit in London, Richard sat down with Nicole Forsgren to talk about her latest data finding and analysis on DevOps. 
  • The conversation starts with a discussion about making good reports, including who the data is collected from. Ideally you'd want a fully random data set, but as Nicole explains, that's not possible - you have to go with as large a set as possible. In the case of the 2017 report, that's 3200 survey responses

[arrested devops] When The Levee Breaks With Jeff Smith And Mark Imbriaco

  • Who owns your availability?

Programming and Testing

[Developing Up] The Art of the Code Review

  • Great developers continually seek to improve the code they work on and write. In this episode we discuss how you can use code reviews to help yourself and your team become better developers.
  • Types of code reviews
    • Formal “Code Review”
    • Part of the QA process
    • Automated reviews
    • Pair programming
    • PR reviews
  • Benefits of code reviews
    • Project benefits
    • Team benefits
    • Reviewee benefits
    • Reviewer benefits
  • Guidelines
    • No bad attitudes
    • Set goals
    • Less is more
    • Annotate
    • Document

[Programming Throwdown] Code Reviews

  • Why?
    • Get another pair of eyes
    • Teach others about what you do
  • What Not to do
    • Become a road block to work
    • Let reviews linger
    • Let it become about only style
    • Have only some people do reviews
  • How?
    • Email
    • In-person
    • Web tools
    • Phabricator
    • Gerrit
    • Gitlab/github
  • Rules
    • All changes must be approved by someone
    • Readability
    • +1 vs +2 or similar
    • To push anyways, there's an emergency mode
    • Keep line count down

[Hansel Minutes] Inside WebAssembly with Mozilla Fellow David Bryant

  • the last few decades of the web and how it's all about to change with the advent of WebAssembly.
  • Is JavaScript the new "metal?"

[CodeChat] The Latest, Greatest Features of C# 7.0

  • C# version 7.0 is totally a thing and with it come a number of cool features like tuples and deconstruction. According to Mark, none of the enhancements are earth shattering or code breaking, but they will eventually change the way you author your project.

[JavaScript Jabber] NPM 5.0 with Rebecca Turner

  • Rebecca Turner, tech lead for NPM, a popular Javascript package manager with the worlds largest software registry.
  • Learn about the newly released NPM 5 including a few of the updated features.

[Complete Developer Podcast] Laws of Programming

  • In any field, there is a lot of hard-won knowledge that the more experienced attempt to impart to those with less experience. Depending on the field, these things may be expressed as old sayings, or laws. They typically aren’t really hard and fast rules, but rather are general tendencies that have been observed over time. Programming, like any other field, has those and many of them are well worth learning.
  • Amongst others:
  • Pareto Principle - For many phenomena, 80% of consequences come from 20% of the causes.
  • Brook’s Law - Adding manpower to a software project will make it later.
  • Conway’s Law - Any piece of software reflects the organizational structure that produced it.
  • Moore’s Law - The power of computers doubles every 24 months OR The number of transistors on an integrated circuit board will double in about 18 months.
  • Knuth’s Optimization Principle - Premature optimization is the root of all evil.
  • Hofstadter’s Law - It always takes longer than you expect, even when you take into account Hofstadter’s law
  • Law of Demeter - This is also known as the law of least coupling.
  • Hanlon’s Razor - Never ascribe to malice that which can adequately be explained by stupidity.
  • Dunning-Kruger Effect - Unskilled persons tend to mistakenly assess their own abilities as being much more competent than they actually are.
  • Postel’s Law - Be conservative in what you do, be liberal in what you accept from others.

[Cucumber Podcast] Fast Tests

  • Everyone knows fast tests are valuable, so why do so many companies abide slow ones?
  • What is 'fast'?
  • how to make them so?

[Cucumber Podcast] BDD in Banking


[scrum master toolbox] Vasco Duarte on what #NoEstimates means for Agile

  • What is #NoEstimates about for the author of the first #NoEstimates book?
  • What can we learn from Vasco’s journey that led him to find #NoEstimates

[Agile in 3 minutes] Do

  • Special guest Lanette Creamer asks: When the word “Agile” implies action, why is there still so much talk?

[Agile in 3 minutes] Pace

  • Amitai asks: How much do you demand of yourself and others?
  • SustainablePace
  • FortyHourWeek
  • OverTime

[Agile in 3 minutes] Influence

  • Amitai asks: How often do people do as you suggest?
  • Power (social and political)
  • Social influence
  • Power Versus Authority

[developing up] Task Estimation Techniques

  • Estimating is hard. In fact, estimating is sometimes considered one of the hardest aspects of development. 
  • While for reasons beyond your control you can never guarantee the accuracy of our estimates, you can control how well you deliver and defend the estimates you provide.

[cross cutting concerns] Arthur Doler on Retrospectives

  • Retrospectives and how to make them better.


[Eat Sleep Code] How Your Brain Works Against You

  • How do our brains interpret cause and effect
  • The ways in which your brain wants to think of things as narratives
  • All the tricks it does to save itself from having to think
  • Arthur shares his perspective on cognitive bias and how it effects the software development process.

[Noah Kagan Presents] Arnold Schwarzenegger's Total Recall - Book Report

  • Have a crystal clear vision and intention.
  • Remove all distractions.
  • Write down your goals.
  • Surround yourself with the best.
  • Reps Reps Reps Discipline.
  • Don't limit yourself.
  • You have to sell.
  • Attitude.
  • Make opportunities happen.
  • Stay hungry.
  • Listen to feedback.
  • Be na├»ve and follow your curiosity.

[Decrypted] This Man’s Murder Might Get Solved by Amazon’s Alexa

  • As we surround ourselves with more and more of these internet-connected devices, Nico and Aki will discuss how our data should be used and why consumers should care. 
  • Its as scary as you think it might be.

No comments:

Post a Comment