Permalink
Switch branches/tags
Nothing to show
Find file Copy path
Fetching contributors…
Cannot retrieve contributors at this time
125 lines (64 sloc) 11.4 KB

Table of Contents

PyLadies-BLR Dojo

Q: Who are you?

We are Pyladies-Bangalore.

Q: What is the Pyladies-Dojo all about?

Our goal is to create a friendly atmosphere for female programmers and encourage them to share and learn with the Foss community. The first attempt to kick-start dojo's that would onboard female programmers to work with Python was in 2010, so the forthcoming dojo sessions will be a continuation of the informal Python learning sessions, akin to the DojoRio meetups in Brazil where they apply the "small acts manifesto".

Q: Why does this group exist? Are men welcome? Why is Pyladies having a Python Dojo?

The short, the code dojos are for female programmers. The long, we are passionate about Python and programming, either use or want to learn Python in a collaborative environment. One of our goal(s) is to share and learn Python, tips and tricks to improve our programming-fu. The focus is on the learning process, as we take small steps towards the solution and try to focus on good development practices.

Since our target audience is Women (incl. those who identify as one) and their friends, with limited (or no) programming experience, our events are welcoming and respectful of anyone interesting in programming. ATM, we are not very strict about gender, so men (ref. caveat note below) who want to volunteer, contribute or learn Python are welcome to attend the dojo. Register and RSVP via our Meetup page to help us manage the venue logistics.

Caveat:: If the number of male attendees dwarfs the female programmers, for future dojo sessions, we might change this policy to align with our primary priority - viz., encouraging female Python programmers.

Q: Are Pyladies events (workshops, meetups, hackathons, sprints) bound by the CoC?

YES. The CoC is mandatory for any event that is funded by grants from the PSF. That said, all the Pyladies dojo events are bound by the Python-CoC, in addition to which we expect all attendees to follow our own Code of Conduct.

Q: How can I help/volunteer?

We are always looking for volunteers, space and sponsors for our events. If you wish to host an event in a different part of Bangalore, or in another Indian city, do [pyladies-blr@python.org] for details on how to kickstart this process.

DOJO

Q: When and where is it held?

On Saturday at CIS, Bangalore. Besides the space and free-wifi, CIS will also provide us with snacks and tea/coffee, etc.. Thank you CIS!

NOTE : While you are inside the CIS (or Thoughtworks office) for any Pyladies hosted event, we suggest the following:

  • Please do not enter into the main office work area.
  • You are free to roam around the event and dining area (please cleanup after yourself) during the event.
  • Avoid disturbing people in the office:: dont talk loudly, or be noisy, lower the mobile ringtones, etc..
Thanks!

Q: What should I bring? Is there a ToDo list?

CIS will have coffee/tea/water and light snacks on hand, but you are free to bring your own water and snacks, along with the following:

  • Your enthusiasm to learn and share knowledge.
  • A laptop computer with a compatible network card, to enable you to connect to the CIS wi-fi network.
  • Python, Virtual environment, Git, and your favorite editor already set up on your laptop running either, a Linux distribution, Mac or Windows. If it runs something else, that's cool, but you might run into issues with the workshop. It is important that you bring a computer you can program on, rather than a tablet or mobile phone.
  • If you have a github account, please list it in your meetup profile (or any other public site), else create a new account and tell us about it.

Q: How much do these weekly Dojo sessions cost?

Its FREE, but you will need to register and RSVP via our Meetup page. This helps us keep an eye on the logistics, decide if we should request for a larger room, etc..

Q: How is the dojo structured? Are you replicating structured courses that MOOC's (Udacity, Coursera, ...) offer?

Not really. We may have a broad agenda for a particular day, which goes out via the mailing list announcements. Other than that, there is no curriculum, or fixed CS syllabi that we follow because no two learners are the same. If you are the curious kind, always tinkering and trying to learn something new, this is your chance to team up with like-minded women in a shared space to write code and help each other learn.

Because the dojo's are an informal learning environment, you will learn and share knowledge by:

  • going over the fundamentals of Python - LPTHW, dive into python, etc...
  • experiment with code and not be afraid to make mistakes.
  • hacking on any FOSS project: fix bugs, write documentation, write tests, contribute new features, ... are all collaborative attempts that will give us an opportunity to learn from experienced programmers within the FOSS communities.
  • breaking existing code, debugging and learning to re-assemble the same - it will help you understand the existing architecture.
  • pairing up with other programmers to practice concepts through bite-sized lessons.
  • reverse engineering and stepping through the existing code base to see how it was solved.
  • solving problems bottom up as well as top down.
  • working on specific algorithms or a random programming challenge
  • reading others code and experimenting with your system to see what happens if you break it.
In toto, first, you will define the problem to be solved and then code, and discuss the ideas, algorithms, alternatives, choices, etc.. The keywords being: People, Sharing, Knowledge, Learning together, Ideas, Foss, Algorithms, Constructions.

The Dojo environment is meant to be a collaborative effort, hence, every skill level is welcome. We are not replicating or competing with MOOC's, nor do we compete with one another - each individual has a different approach to learning and we would like you to build on that. If you want to learn Python programming or want to work with others Foss code, we'll help you find a path to learn it.

Q: Can I start thinking about projects before the event? I have some suggestions for your meetups...

Yes, your suggestions are welcome. Write to the Pyladies-BLR mailing list or add your tutorial ideas on the https://github.com/svaksha/pyladies-dojo/blob/master/Kata.mediawiki wikipage, that serves as the placeholder for topics that can be picked up for future events.

Q: Can we form a study group around MOOC (Udacity, Coursera, ...) courses

All the MOOC courses have a honor code that participants are required to sign and adhere to. Everyone should write code that can be shared, aka. free and open source software (FOSS). The honor code prohibits students from sharing code while our dojo encourages code sharing akin to Foss projects, hence unethical to do any group work around MOOC courses.

MISCELLENEOUS

Q: What time do I need to get there? Can I walk-in late?

If you are new to Python and/or need help with installation issues, we suggest that you come in a few minutes early. This will help the volunteers keep you in pace with the rest of the group. That said, you can walk-in later but if you are too late you will miss out on interesting learning bits as the dojos will not be meeting for more than 3 hours each week, albeit individuals may stay back to continue working until the host closes for the day.

Q: Will there be any lectures, discussions, talks, etc.. ?

Not in the near future.

Dojos are all about you getting a hands-on experience with Python programming and the focus is on the practical than the theoretical. When you write code, as opposed to listening to someone talk for 30 minutes about what "foo" package does, you are learning to build something that is important to you.

As a long term objective, in future, we may think about (occasionally) hosting guest speakers interested in conducting workshops and/or sprints for their FOSS projects. If you are a core-dev for any Python package and want to conduct workshops to introduce newbies to bug-squashing, feel free to talk to us. We would love to have you conduct programming workshops and sprints at the dojos.

Q: Are there any teachers and do you give any certificates?

No, and NO - we definitely do NOT hand out pieces of paper. We are not an Institute, nor a commercial entity in the training or education business and dont do commercial certifications. Pyladies is a volunteer effort and we have no teachers, only facilitators:: Annapoornima Koppad, Sunita Venkatachalam, Svaksha and other fellow attendees, who will be around to help each other learn Python. Yeah, the facilitators, like you are learners too!

Q: I don't own a laptop. Can I attend the Dojo?

Folks that dont have laptops are also welcome - at CIS we cannot provide machines to work on but you can watch others code, ask questions, learn by pair programming, etc.. In future, if we use the Thoughworks office as our venue, they might be able to arrange for spare machines (subject to confirmation).

Q: I don't know how to code. Can I attend the Dojo? But, I dont know "xyz"?

You are welcome to attend if you are willing to invest the time and energy to learn Python. Its OK to *not* know something so long as you want to learn how to code. Nobody will mock you for not groking Python decorators, or publicly saying “I dont know”. Besides, all Pyladies events are bound by the Python-CoC, in addition to which we expect all attendees to follow our Code of Conduct.

Q: I dont have a CS degree / I'm not an Engineer, can I learn to code?

A piece of paper should not limit your potential, so if you can put in the effort to learn Python, then you can definitely learn to code. We are mere catalysts that provide a free space, wifi, and like-minded Pythonistas, with you putting in the hard work to become a good programmer.

Nobody is born a talented programmer, that comes from practice and that is exactly what you will be indulging in. Nobody knows your work as well as you do and when you interact and explain your work, or why a particular part of the code isnt working, you have learned to debug your own code while learning how to construct a problem-set logically.

Being a good developer is as much about documenting your code, as it is about helping, collaborating, teaching and learning. Here is an interesting read on how to kick the Imposter syndrome and another on how to become a better developer.