We're sorry but this page doesn't work properly without JavaScript enabled. Please enable it to continue.
Feedback

Why You Should Consider Getting a Python Pet Project

Formal Metadata

Title
Why You Should Consider Getting a Python Pet Project
Title of Series
Number of Parts
115
Author
Contributors
License
CC Attribution - NonCommercial - ShareAlike 4.0 International:
You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal and non-commercial purpose as long as the work is attributed to the author in the manner specified by the author or licensor and the work or content is shared also in adapted form only under the conditions of this
Identifiers
Publisher
Release Date
Language

Content Metadata

Subject Area
Genre
Abstract
If you are managing developer teams or departments a pet project may be a helpful tool to stay out of your developers hair and learn about the technologies used in your department without blocking your developers to babysit you. If you are like me and have a development background, you will want to get your hands dirty and start fixing bugs and implementing stories. However, this can have many negative side effects. Breaking established rules is easier in a leadership position and sets a bad precedent. By becoming a last instance for each technical decision you take away personal identification with the work of your engineers. It may also lead to distrust. With this talk, I want to share some of my experiences in that regard.