Learning paths

Welcome to the Learning Paths repository. Here you'll find all the alternatives to improve your current career by knowing the gaps in your technical background and the topics that will fullfil them.

You can also know the proper path if you want to start a different career or technology because the guides are group by seniority, starting from very low levels.

Repostory structure

In the root screen, you'll find the main technologies and subjects. Inside each one of them the README.md file will detail all the topics group by seniority and, optionally at the top, new folders with other subjects that are part of the main one.

Contact

Gabriel Guzmán - [email protected] / Skype: gabo_mza Gisella Tromer - [email protected] / Skype: gisetr

Content creation process

Create a pull request

1. Log into GitHub. You can use your personal account.
2. Go to the Learning Paths repository: https://github.com/belatrix/learningPaths
3. Fork the repository in your GitHub account by clicking the "Fork" button
4. This will open a popup to select where we want to fork it. Select the user's personal account
5. This process will create a fork of the repository in the user's account.
6. Apply all the changes in the forked repository
   • Create a branch to add the changes
   • You can use this editor to create/update the README.md files: https://stackedit.io/app
   • Github readme files syntax: https://help.github.com/articles/basic-writing-and-formatting-syntax
   • Commit and push the changes to the repository
7. Create the pull request from the original repo: https://help.github.com/articles/creating-a-pull-request-from-a-fork/
8. After the PR is requested, it's approved (or not) by the corresponding moderators

Synchronize the repositories

1. If you have already forked the repository in the past, you'll need to syncronize it before adding new changes.
2. Follow these guides:
   • https://help.github.com/en/articles/configuring-a-remote-for-a-fork
   • https://help.github.com/articles/syncing-a-fork/

Collaborators

These people helped us a lot in the initial drafts of the guides. Thanks a lot!

General Research

• Hansy Schmitt

Mobile

Android

• Lucas Farías
• Juan Manuel Rodríguez
• Evangelina Selman [email protected]

Mentors

• Guillermo Gutiérrez [email protected]
• Eduardo Medina [email protected]
• Carlos Piñan [email protected]

Flutter

• Sergio Bernal [email protected]

iOS

• Germán González [email protected]
• Gastón Grippi [email protected]

Mentors

• Mariano Cornejo [email protected]
• Arturo Gamarra [email protected]
• Luis Alonso Paulino Flores [email protected]

Backend

• Gabriel Guzmán [email protected]
• Evangelina Selman [email protected]
• Miguel Angel Toscán [email protected]
• Ever Valdés
• Ramiro Vargas [email protected]

Mentors

• Paulo Magnago [email protected]
• Gastón Marchetta

Front-End

• Gabriel Guzmán [email protected]
• Germán Moyano [email protected]

Mentors

• Tomás Merlo [email protected]
• Mariana Tapia [email protected]

Java

• Marcelo Fernández [email protected]
• Rodrigo Moreno
• Germán Moyano [email protected]

Mentors

• Paulo Magnago [email protected]
• Gastón Marchetta

.Net

• Gabriel Guzmán [email protected]

Mentors

• Federico Gómez [email protected]
• Mauricio Salafia [email protected]

QA

• Carlos Albornoz [email protected]
• Romina Babugia [email protected]
• Ramiro Gioia [email protected]
• Nahuel Melo [email protected]
• Ezequiel Porco [email protected]
• Juan Manuel Rodríguez
• Mariano Sosa [email protected]

Mentors

• Diego Villa [email protected]
• Miguel D'amore [email protected]

UX

• Nahuel Melo [email protected]
• Enrique Stanziola [email protected]

Mentors

• Bárbara Lipinski [email protected]
• Alejandro Spina [email protected]