Community - From the Inside Out
By Yarko Tymciurak

_I came for the language, but I stayed for the Community_ --Brett Cannon, Pycon 2014 Why? What draws us to community? What makes a great Community? How do we contribute? I'll share some insights, some science, and some surprisingly broad principles. I'll share what contributes, what parts are similar to coding practices, and some ways you can contribute to a great Community feeling.

Sunday 12:45 p.m.–1:15 p.m. in Hays Cape

Community - From the Inside out

towards an attractive Community API

  • Everybody is drawn to Community?
  • list of talks, quotes, other communities which mirrored this;

  • Why is that?

  • evolution
    • benefits & shortcomings (community & congintion basics)
    • mirrored in biological structures (Panksepp)
    • the architecture of biology
    • cognition and feedback structures;
    • the interesting structures: play, joy/sadness, exploration
    • dynamic modulation
  • how widely favored (evolutionarily) is it?

    • bees, rats, chimps, us, ... (examples)
  • Why - a functional description

  • the limits of cognition, and the benefit of social sharing
    • Edelsons's checker shadow demonstration
    • Eagleman on more complex functions
    • how personal, encapsulated our experiences are
  • how the benefit works

    • code reviews
    • scientific method
    • work teams
    • open-source communities
    • open societies / governments
  • Skills:

  • encapsulation and structure in software (hey! it's like cognition!)
  • the parallels for Community interaction (and for architectural guidance too);
  • fundamental data structures;
  • explicitly aware == explicit benefits
    • the core API rule (encapsulation)
    • personal data structures
    • data structures vs. interfaces
    • channels (modes) of communication
    • their uses, their limits
      • how to switch channels
  • putting into practice in community

  • Where to go from here

  • Q/A

Yarko Tymciurak

I have been programming, starting with FORTRAN (1968), C (1979), and Python (1999). Before Python, I disliked perl, and liked Icon, ksh, awk (w/ awkcc).

From 2008 to 2016 I was a PyCon volunteer, organizer and volunteer coordinator of PyCon, the U.S. national Python conference.

I am a recipient of 2010 Python Community Service Award, and occasional open source contributor.

I've worked on commercial UNIX kernels, POSIX standardization, communications equipment, and mobile devices at Unisys, Bell Labs, Motorola, University of Chicago, and a few other places.

Besides coding, I've been interested in architectural methods, and team processes. I received a Motorola award for a formal technical review program delivered to more than 1,000 engineers whose core was team skills training. I have worked with psychologists for over 20 years in team dynamics and skills. Around the time Agile was getting started, I ran a team using an architectural pattern based on team skills, but applied to systems. As PyCon Volunteer Coordinator, I encouraged and watched positive community interaction take hold.

I like python mostly because it gets out of your way, and makes it relatively easy to express yourself clearly.

I have a BSEE in Computer Engineering from the University of Arizona, when Dr. Gerald Petersen was developing his interests in hardware description language. As an undergraduate, I worked running a Unix V6 lab for classes and research. I got into engineering as an escapee from a Bio major, and a summer turned 6 years at an auto parts store and working on pit crews. I ride a motorcycle.