In the last days I have been following quite extensively Anthony Sottile’s channel anthonywritescode. Anthony is behind the pre-comit framework, which I love because it prevents me from commiting too much silly mistakes and also pytest, which is the de-facto standard for #Python testing.
A few of the things I learned about:
- How a register based execution could result in 10% faster #Python code (RegCPython)
- How you can secure #Python with audit hooks
- How you can use parametrized pytests
Another channel I started watching was Dave Farley’s channel Continuous Delivery. I started with his video about Object Oriented Programming vs Functional Programming, because I am always on the look for some good rant :) But actually it was a quite decent comparison, which ranted most about the people picking sides. Because I liked this video I also watched Why Pull Requests Are A Bad Idea, which is making the following argument:
- Continuous delivery is basis for high quality software
- Continuous delivery is only worth being called continuous if there is at least one change per day
- You can’t release unreviewed code.
- It’s not feasible to have a PR on every little commit.
- Therefore, PRs kill continuous delivery -> Hence, PRs are bad!
He argues in favor of pair programming instead, because there is no alternative. In my experience I really like pair programming sessions, but on the other hand it´s not so easy to organize my whole day around that. Maybe I should try this a little bit harder.
The last one I watched from Dave Farley is about Test Driven Development (#TDD) or more specifically the The 3 Types of Unit Test in TDD But it is more general an argument for #TDD.
Actually, it´s not all about tech, because I also like to laugh about videos…