Recent searches
Search options
Tips to prevent maintainer burnout from the beautiful soup maintainer. A single maintainer managing a package will millions of users
*ask users to contribute issues before a pr
* practice defensive programming. Use warnings to point to common user mistakes
@leahawasser These are remarkably good, thanks for sharing!
@scheidegger of course!!
@leahawasser he sure is beautiful
@tillmanreuter 
he sure creates beautiful tools too! 
The text from @leonardr 's slide:
My boundaries after twenty years
I probably won’t respond to your support request
- (Unless it looks like you hit a bug.)
I practice defensive coding (especially using `warnings.warn`)
- Provides automatic support for common mistakes
I practice software hygiene (unit tests, type hints)
- Gives me confidence that I can come back after a break
Bug reports > pull requests
[1/2]
Courtesy is even more important than usual
I’m *interested* in the quality of my dependencies (lxml et al)
- I’ll file bugs but won’t try to fix them
I’m *committed* to the quality of the beautifulsoup4 package
- If I walk away or die, the current release should work for a long time.
[2/2]
@brainwane @leonardr THANK YOU sumana!! i just updated the alt tag with your text! i was trying to live "toot" to capture the awesomeness and couldn't keep up with the alt tags + also paying attention to the talk / timing / my job helping inessa run the summit!
this is my first summit that i've helped run!! i learned a lot!
@leahawasser I just want to share this zine that Leonard made. Seems like my kinda people: https://www.crummy.com/software/BeautifulSoup/zine/
@eamon thank you for sharing this!! i hadn't seen it before! his talk was really great.
@leahawasser gosh I bet. Jealous I can't be there!