The New Best Practices https://thenewbestpractices.com The New Best Practices is a podcast about the process of creating software. Thu, 15 Nov 2018 12:00:00 -0400 hourly 1 en-us Really Good Podcast The New Best Practices episodic The New Best Practices ross-hunter@ross-hunter.com The New Best Practices is a podcast about the process of creating software. The New Best Practices is a podcast about the process of creating software. Ross Hunter ross-hunter@ross-hunter.com https://thenewbestpractices.com/images/stamp-logo-light.png The New Best Practices https://thenewbestpractices.com Hugo -- gohugo.io Learning & Teaching Git https://thenewbestpractices.com/episodes/learning-teaching-git/ Thu, 15 Nov 2018 12:00:00 -0400 https://thenewbestpractices.com/episodes/learning-teaching-git.mp3 The New Best Practices Git is essential to our work as software developers, but it can be a tough technology to interact with. In this episode we discuss things that are good to know, and good to teach our team, so that we can all play happily together in version-control wonderland. Git is essential to our work as software developers, but it can be a tough technology to interact with. In this episode we discuss things that are good to know, and good to teach our team, so that we can all play happily together in version-control wonderland. Git is essential to our work as software developers, but it can be a tough technology to interact with. In this episode we discuss things that are good to know, and good to teach our team, so that we can all play happily together in version-control wonderland.   ]]>37:46 Requirements https://thenewbestpractices.com/episodes/requirements/ Thu, 30 Aug 2018 12:00:00 -0400 https://thenewbestpractices.com/episodes/requirements.mp3 The New Best Practices How do we keep track of requirements? We talk about user stories, test cases and more. How can we know that we have completed a particular feature? How do we keep track of requirements? We talk about user stories, test cases and more. How can we know that we have completed a particular feature? How do we keep track of requirements? We talk about user stories, test cases and more. How can we know that we have completed a particular feature?  

Outline

]]>52:56 Delivery https://thenewbestpractices.com/episodes/delivery/ Sun, 20 May 2018 12:00:00 -0400 https://thenewbestpractices.com/episodes/delivery.mp3 The New Best Practices How do we deliver software? We talk about git branching strategies, as well as automated and non-automated testing and deployment. How do we deliver software? We talk about git branching strategies, as well as automated and non-automated testing and deployment. How do we deliver software? We talk about git branching strategies, as well as automated and non-automated testing and deployment.  

Outline

  • Definition of delivery: “Putting software where someone can use it.“
  • Branch from develop, or branch from master?
  • Why not just commit to master?
  • Don’t deploy a development environment.
  • qa, test and uat are bad branch names.
  • You should automate the deployment of PR branches.
  • Understand a feature before start it.
  • Software is bad.
  • Developers should be manually testing during code review.
]]>53:3 Learning New Things https://thenewbestpractices.com/episodes/learning-new-things/ Fri, 30 Mar 2018 12:00:00 -0400 https://thenewbestpractices.com/episodes/learn-new-things.mp3 The New Best Practices In this episode we talk about learning new things. We discuss what got us interested in software in the first place, and how those original motivations still color how we approach learning. Should we learn new things just because we read about them on Hacker News? Should we dive deep and become an expert in a field, or is it just more fun to do new and different things? In this episode we talk about learning new things. We discuss what got us interested in software in the first place, and how those original motivations still color how we approach learning. Should we learn new things just because we read about them on Hacker News? Should we dive deep and become an expert in a field, or is it just more fun to do new and different things? In this episode we talk about learning new things. We discuss what got us interested in software in the first place, and how those original motivations still color how we approach learning. Should we learn new things just because we read about them on Hacker News? Should we dive deep and become an expert in a field, or is it just more fun to do new and different things?  

Outline

]]>49:55 Monorepo https://thenewbestpractices.com/episodes/monorepo/ Thu, 01 Mar 2018 12:00:00 -0400 https://thenewbestpractices.com/episodes/monorepo.mp3 The New Best Practices Should your company put all of your code in one repository? What are the advantages and disadvantages of one vs. many source code repositories? Should your company put all of your code in one repository? What are the advantages and disadvantages of one vs. many source code repositories? Should your company put all of your code in one repository? What are the advantages and disadvantages of one vs. many source code repositories?  

Outline

]]>37:54 Code Review https://thenewbestpractices.com/episodes/code-review/ Sat, 20 Jan 2018 12:00:00 -0400 https://thenewbestpractices.com/episodes/code-review.mp3 The New Best Practices In this episode, we talk about version control systems, pull requests, asynchronous work, automated checks, and accepting criticism. We also cover all possible parts of code review - early pull requests, pre-review comments, diff review, and manual testing. In this episode, we talk about version control systems, pull requests, asynchronous work, automated checks, and accepting criticism. We also cover all possible parts of code review - early pull requests, pre-review comments, diff review, and manual testing. In this episode, we talk about version control systems, pull requests, asynchronous work, automated checks, and accepting criticism. We also cover all possible parts of code review - early pull requests, pre-review comments, diff review, and manual testing.  

Outline

]]>36:13 Code Comments https://thenewbestpractices.com/episodes/code-comments/ Fri, 19 Jan 2018 12:00:00 -0400 https://thenewbestpractices.com/episodes/code-comments.mp3 The New Best Practices How often should you leave code comments? Is it necessarily a failure to express yourself clearly in the code? Are code comments the best way to communicate with your team? Are your comments helpful, or just cathartic? How often should you leave code comments? Is it necessarily a failure to express yourself clearly in the code? Are code comments the best way to communicate with your team? Are your comments helpful, or just cathartic? How often should you leave code comments? Is it necessarily a failure to express yourself clearly in the code? Are code comments the best way to communicate with your team? Are your comments helpful, or just cathartic?  

Outline

  • Definition of comments: “Metadata in source code that describe what code fails to communicate. Some languages and frameworks opt to use the mechanism of comments as formal documentation for code, but these two concepts should be separated.“
  • Strive to make code self-documenting
  • Formal Documentation vs. Code Comments
  • Using tests to document your code
  • Considering strong types as a type of documentation
  • Docstring Tests
  • The value of documenting types
  • Worthless comments should be avoided
  • Don’t use comments to “vent” your emotions
]]>54:01 YAGNI https://thenewbestpractices.com/episodes/yagni/ Thu, 18 Jan 2018 12:00:00 -0400 https://thenewbestpractices.com/episodes/yagni.mp3 The New Best Practices Are you building custom software? Are you adding extra features to work tool? Maybe You Arent Gonna Need It. In this episode we debate using off the shelf software vs. building your own. Is your company actually selling software? What is your business model? We also discuss unnecessary complexity in software and the impact this can have on quality. Are you building custom software? Are you adding extra features to work tool? Maybe You Arent Gonna Need It. In this episode we debate using off the shelf software vs. building your own. Is your company actually selling software? What is your business model? We also discuss unnecessary complexity in software and the impact this can have on quality. Are you building custom software? Are you adding extra features to work tool? Maybe You Arent Gonna Need It. In this episode we debate using off the shelf software vs. building your own. Is your company actually selling software? What is your business model? We also discuss unnecessary complexity in software and the impact this can have on quality.  

Outline

]]>1:00:54 Points https://thenewbestpractices.com/episodes/points/ Wed, 17 Jan 2018 12:00:00 -0400 https://thenewbestpractices.com/episodes/points.mp3 The New Best Practices What are points in Software Developement? Join our hosts as we discuss how points can both useful and harmful when developing. In this episode we cover what points are, their relationship to velocity and how they help with estimates. What are points in Software Developement? Join our hosts as we discuss how points can both useful and harmful when developing. In this episode we cover what points are, their relationship to velocity and how they help with estimates. What are points in Software Developement? Join our hosts as we discuss how points can both useful and harmful when developing. In this episode we cover what points are, their relationship to velocity and how they help with estimates.  

Outline

  • Software development is not a “game”, i.e. you aren’t aiming to get more points
  • Points give you a reference for how your people, process & technology are working together
  • Velocity therefore is a function with these inputs
  • Estimation is possible through a “Stable Velocity”
  • Estimates aren’t meant to be used to hide behind
  • Fixed estimates aren’t really possible as the number of variables in a project consistently change
  • Developers need to deteremine their lifestyle. Maybe using points is not the right thing for your team
]]>27:54