Skip to main content

Interview with PyCon speaker Brian Jones


After a successful tutorial session in 2011, Brian Jones is back this year with a talk on a booming topic: mocking. Testing has always been fairly popular in the Python community, but it seems like more developers than ever are really on board with testing. The difference between unit testing and functional testing is getting more coverage. Test-driven development is becoming a more popular methodology. Continuous integration is getting easier to setup and use. It seems like every corner of the testing world is improving at a nice pace. Mocking in particular has been blowing up with more widespread use and more options than ever. Brian's talk, Fake It Til You Make It: Unit Testing Patterns With Mocks and Fakes, aims to help developers get to the next level of testing by sharing best practices in the test design.


While Brian has long been a fan of mocking, the last several years have seen enough mocking libraries produced to get him to switch from his home-grown tools to try what the community has to offer. Although he’s a former user of the Mox project, the choice of library for this talk will be the aptly named Mock. However, the choice of Mock is less about the library and more about being able to easily convey ideas behind mocking. "I suspect that Mock's 'action->assertion' approach to mocking will be more intuitive to pick up 'on the fly', in the course of a talk, than the 'record->replay' approach taken by other modules," says Brian.


"I want people to think of testing as being more like a fun little puzzle than...calculus," he said when asked what caused him to submit the proposal for this talk. Mocking, he feels, is a huge help in getting testing to fit inside the minds of newcomers to the arena. With the talk he hopes to introduce the techniques and the tools, then put it all together in practice. The 45-minute session includes several types of example applications, from a datetime abstraction library to a command shell program, to show how Brian’s best practices with test design and mocking can be used.


Speaking is just one of the fun parts of PyCon for Brian. In his second year on PyCon's program committee, he helped review a record number of talk proposals. Sometimes meeting two times a day, the program committee had a busy fall between online reviews and voting, then the various IRC-based discussions on later rounds of reviews. Being a part of the program committee for a second year allowed him to "further [his] conviction that the Python community is the most welcoming, open and inclusive group [he's] ever had the pleasure of being involved with."


When it comes to getting on-site at the conference, last year Brian volunteered some of his time to help out around the event. The evenings may be one of his favorite parts: he's a huge fan of the BoFs, or Birds of a Feather meetings. “I've been to conferences where I'm really just not that interested in *any* of the BoF sessions, but at PyCon '11 I actually had conflicts: I wanted to attend multiple BoFs in the same time slot," he says.


One of the best benefits he says of the conference is the ability meet up with the people he had been interacting with online for years. Now that he’s been to a PyCon in the past, meeting up with those same friends and meeting many more in 2012 is an incredible experience. In closing, he remarked that "The community around Python is unbelievable, and attending PyCon is a great way to be bombarded by that fact on a continual basis for a few days, which is good for the soul."


Be sure to check out Brian's talk on Friday March 9 at 2:55!

Comments

Popular posts from this blog

Hatchery Program Returns for 2019

PyCon is known around the world as the Python community’s premier event, attracting people from 39 countries. Outside of the main track of talks, PyCon is home to a growing number of events such as Young Coders, the Education Summit, Language Summit, Poster Session, and most recently the PyCon Charlas. The conference strives to be globally representative by promoting diversity and inclusion through these additional events and outreach programs. Our community works to approach these goals year on year. While we regularly receive requests to add events to PyCon, we have not had an established process for accepting and evaluating the community’s suggestions. By introducing the PyCon Hatchery Program in 2018, we took an initial step to introduce a long term process for evolving PyCon. What is our goal?We want to support our community and enable them to add events to PyCon that are important to our community. The long-term goals of this program are to support and grow sustainable programs th…

Pycon 2019 Call for Proposals is Open!

The time is upon us again! PyCon 2019’s Call for Proposals has officially opened for talks, tutorials, posters, education summit presentations, as well as the hatchery program PyCon Charlas. PyCon is made by you, so we need you to share what you’re working on, how you’re working on it, what you’ve learned, what you’re learning, and so much more.

Please make note of important deadlines for submissions:
Tutorial proposals are due November 26, 2018.Talk, Charlas, Poster, and Education Summit proposals are due January 3, 2019.
Who should write a proposal? Everyone! If you’re reading this post, you should write a proposal. PyCon is about uniting and building the Python community, and we won’t advance as an open community if we’re not open with each other about what we’ve learned throughout our time in it. It isn’t about being the smartest one in the room, so we don’t just pick all of the expert talks. It’s about helping everyone move together. “A rising tide lifts all boats,” if you will.

We…

PyCon 2018 Code of Conduct Transparency Report

The PyCon Code of Conduct sets standards for how our community interacts with others during the conference. For 2018 the Code of Conduct underwent an extensive overhaul, our procedures for reporting and responding to incidents were improved, and our on-site methods were improved. You can read more about the updates for 2018 here. Cumulatively these changes were meant to improve the safety, welcoming nature, and overall inclusivity of PyCon. Based on initial responses, feedback, and incidents reported this year we feel that we made progress on those goals. A Code of Conduct without appropriate reporting and response procedures is difficult to enforce transparently, and furthermore a lack of transparency in the outcomes of Code of Conduct incidents leaves the community without knowledge of how or if the organizers worked to resolve incidents. With that in mind, we have prepared the following to help the community understand what kind of incidents we received reports about and how the PyCon…