Skip to content

Latest commit

 

History

History
128 lines (83 loc) · 7.73 KB

README.md

File metadata and controls

128 lines (83 loc) · 7.73 KB

"By Developers" Training

As you've read in our Culture section, we're a company "For Developers". In order to achieve this everyone needs to be able to put themselves in the shoes of a developer by becoming one themselves. The purpose of this document is to provide a guide on how to acquire an engineering mindset through learning the basics of Computer Science and coding. Each sourcerer should block a 1-hour slot every day in their calendars to dedicate to this program. The quests should be completed in order, which will take you 21 weeks to achieve.

You will be assigned a mentor who will be able to help you with questions and problems. This mentor will be either someone from the engineering team or someone who has finished the program before already.

Quest 1: Setup your machine on Arch Linux

Why: By getting a good understanding of Linux you'll understand better how a computer works and you'll get to use sites like Stack Overflow on a frequent basis, which will allow you to get a better picture of the developer community.

Process: Follow all the steps on the Arch Linux Setup documentation to fully set up your work laptop. If you have questions on how to do something first google your question and try to find solutions to it on ArchLinux, StackOverflow or other sites. If you find yourself unable to solve your problem ask your mentor for help. When doing so, try to recollect the queries you used to look for the problem on the internet. This way, your mentor will help to improve the most important technique you’ll need while coding: your google-fu.

You should have received an invitation to Enki. Enroll in the Linux track and make sure you train every day, during the slot you have blocked, to become better at it and so you don't forget what you've learned.

Duration: 2 days

Resources:

Deliverable: Fully set-up laptop

Quest 2: Computer Science Basics

Why: Knowing the basics about how software and hardware interact is key to understanding development.

Process: Going through the course material (the optional pieces included) on CS101 by Stanford, as well as reading the rest of the provided documentation.

Duration: 6 weeks

Resources:

Deliverable: Stanford Certificate

Quest 3: Culture

Why: You can't be at source{d} without knowing about the technologies we're developing, the research we're publishing and the people on our office's walls.

Process: Reading through all of the provided documentation and doing further research on your own about the people and related topics that might have caught your attention.

Duration: 2 days

Resources:

Quest 4: Learning Python

Why: Now that you know the theory it's time for you to get your hands dirty and learn how to code. This track won't teach you how to become a developer, but rather how to code to be more efficient in your day to day.

Process: Reading through the book “Automate the Boring Stuff with Python”

Duration: 3 weeks

Resources:

Deliverable: Coding Challenge

Quest 5: Learn Data Science with Python

Why: Data Science is at the core of source{d}. Now that you know the basics of coding it's time to learn one more application of it: how to leverage data with Python.

Process: Going through the full course of Data Science with Python on Datacamp

Duration: 11 weeks

Resources:

Deliverable: Completion in Datacamp Dashboard

DLC: Extra Credits

Why: You just can't get enough, you've opened the Pandora Box and now can't close it ever again. You want to dig deeper into Unix, Python, Data Science or maybe learn some frontend.

Process: Combining books and other resources to dig deeper into coding.

Duration: Your whole life (or not, your choice)

Resources:

Deliverable: Participating in our Open Source Fridays