Topics include automated testing, testing strategy, software engineering practices, packaging, Python, pytest, data science, TDD, continuous integration, and software methodologies.
Also anything I think helps make the daily life of a software developer more fun and rewarding.
Hosted by Brian Okken.
pip : "pip installs packages" or maybe "Package Installer for Python"
pip is an invaluable tool when developing with Python.
You can use pip to install Python packages from pypi.org, or a different index, or a local directory.
The way pip installs from a local directory is about to change, and the story is fascinating.
What flavor of TDD do you practice?
In this episode we talk about Classical vs Mockist TDD, Detroit vs London, Static vs Behavior, Inside Out, Outside In, Double Loop TDD, BDD, FDD, Tracer Bullets, Rules of TDD, Team Structure, Lean TDD and so much more.
Software development processes create value, and have waste, in the Lean sense of the word waste.
Lean manufacturing and lean software development changed the way we look at value and waste.
This episode looks at lean definitions of waste, so we can see it clearly when we encounter it.
Should your code be DRY or DAMP or something completely different?
How about your test code? Do different rules apply?
Wait, what do all of these acronyms mean?
We'll get to all of these definitions, and then talk about how it applies to both production code and test code in this episode.
When learning data science and machine learning techniques, you need to work on a data set.
Matt Harrison had a great idea: Why not use your own Twitter analytics data?
So, he did that with his own data, and shares what he learned in this episode, including some of his secrets to gaining followers.
Iterative processes that include writing test code and production code together, such as TDD, help make coding fun. Gio Lodi, author of TDD in Swift, joins the show to discuss Test Driven Development, software workflows, bottom up vs top down, rapid feedback, developer vs customer facing tests, and more.
pre-commit started as a framework for running linters and code formatters during git actions via git hooks. It's grown and expanded and now supports an extensive list of languages and actions and manual running of actions. But even at it's core, it's great for letting computers nitpick about whitespace and formatting, so that code reviews can focus on architecture and design.
Anthony Sottile discusses pre-commit, for using locally by developers, and pre-commit...