Gain experience as a Developer: Chingu Voyage 33 teaser & how to get started

Chance - Aug 12 '21 - - Dev Community

So you don’t freak out before we start

Photo by Muhammad Raufan Yusup on Unsplash

🔥 This article will help you get oriented and ready for your remote team Voyage experience! Don’t feel like you have to read & watch everything (you won’t be able to).

(Note: this article is a part of Chingu onboarding. If you haven’t applied yet you can do so at https://chingu.io/).

Table of Contents

  1. Welcome to the Chingu community!
  2. Why Chingu exists and how can it help me?
  3. Roadmap — Schedule, What’s next & how can I start?
  4. What’s the solo project quality check?
  5. What can I expect from a Voyage?
  6. How can I best prepare for the Voyage?
  7. Want to be SUPER prepared? Check these out from past members
  8. Project showcases from past Chingu teams!

1 — Welcome to Chingu!

So, you’re going to be joining a Chingu Voyage? Here’s a welcome from the community. 😃

2—Why Chingu exists and how can it help me?

So you’ve been conditionally accepted to a Chingu Voyage?

Guess what?!

Not only are you now on a path to accelerate your learning, meet new developer friends from across the world, and gain experience working in a team, you’ll also be contributing to Chingu’s Moonshot mission of…

Helping unlock the world’s tech talent through collaboration!!!! 🚀

Since 2016, Chingu has helped people get jobs at companies like Amazon, Facebook, Microsoft, and even Freecodecamp!

Chingu exists to help people from around the world come together to build together & reach their goals. Chingu members gain confidence in their skills, finish actual projects for their portfolio, and gain experience working in real remote teams (these are all things employers happen to love 😉 ).

Here’s a few videos of Chingu members:

3— Roadmap: What’s next & how can I start?

Step 1: Read this article

Step 2: Join the Chingu Discord server (the invite link can be found in your onboarding email).

Step 3: Answer the question: Do I have a completed solo project I can submit?

Step 4a): If yes , submit that project via the Project Submission Form (this form can be found in your Chingu onboarding email).

Step 4b): If no , the first step is to build a solo project & submit it. You can find solo projects to build here.

Step 5: Receive feedback on your project & add the Voyage launch date to your calendar!

Schedule for Voyage 33

There are 2 due dates to keep in mind when getting started.

Solo project submission due date : August 24, 2021

Voyage team launch date : August 30

Each Voyage team project lasts 6 weeks.

Note: Each month we launch a new batch of teams working on projects. This is usually around the beginning of the month.

4— What’s the solo project quality check?

In order to maintain quality of teams we require members to submit a completed solo project to be checked before being added to a team.

Some members will join Chingu and have a completed project they can submit right away. For others, this will be an opportunity to finally finish a project from start to finish! 🚀

If you don’t already have a solo project, we recommend building one of these.

Here are some quotes by past members who completed their first solo project:

I finished my first project :) that was amazing.😃

It was a great step in getting me out of tutorial hell. I didn’t realize how much this has hurt my growth until recently.

I learned SO MUCH. It made me feel certain I was able to move on to the next stage (a Voyage team project), and it allowed me to sharpen my Git skills. I am finally seeing the light at the end of the tutorial purgatory tunnel, as I had to complete the project without having a reference guiding me along. I would do a “solo project” every month tbh.

It was an important test. Now that I have successfully completed a project I feel I have what it takes to be a developer.

It really forced me to use skills that I had learned but not really applied

5 — What can I expect from a Voyage?

Be surrounded by curious builders from around the world

Chingu attracts developers & PMs from around the world. You’ll be surrounded by ambitious learners who share your goals!

Gain experience in a remote software team

People underestimate the skills involved in working in a remote software developer team. Git/Github, merge conflicts, PRs, coordinating tasks, communication nuances, etc. are all a big part of building projects. This is why employers want to hire people with experience.

Get out of your comfort zone

Let’s also not forget: you will be challenged to level-up your skills. This is not a tutorial where you can lazily follow through. Participating in a Chingu project (solo or team) is not easy.

Joining Chingu = getting out of your comfort zone.

Confidence & a shiny portfolio

You can also expect that if you show grit, you’ll come out with a shiny new project for your portfolio (some teams even build nonprofit projects or projects that create value for others).

6 — How can I prepare for this Voyage?

🔥A) Learn the basics of git/github

When we ask experienced members what the number one way to prepare for a team project is, they all say: Learn the basics of git/github!

If you’re new to git, do this→Learn Git basics in 15 minutes

Set up Git on your computer

These Git articles (written by the legendary Chingu Francesco Agnoletto) shall be your guide! Also: see Francesco’s video on git below for more.

🔥B) Learn and begin to practice these essential Soft Skills

30 principles to level-up your Soft Skills

(Note: if you learn these principles and how to apply them, they’ll change your life).

7— Want to be SUPER prepared? Check these out from past members!

Below are some articles and videos from past members. Feel free to check any of them out.

🔥Here is an app & experience walkthrough by @paulywall from Voyage-8 (shout-out to GECKOS-TEAM-07!!)

🔥 Here is another app & experience walkthrough by the wonderfully energetic @Sabrina!! (Big shout-out to Geckos-Team-04!!)

🔥 Here is another app walkthrough by @jane Lee from Voyage-8 🔥 (Shout-out to Bears-team-12!!)

🔥 Francesco Agnoletto on how to use Git/Github in a team setting

🔥@oliver & @Dan, on Pair-Programming Tips (& a mini Demo)

Ben Kandelaars on his experience/team workflow in a Voyage (they reverse-engineered Airbnb!)

🔥Vannya, on being a Project Manager and Team Developer

Van Tabbert on the importance of building Momentum in remote teams.

https://medium.com/media/9e5dc5d48802c399b994fade793aa073/href

🔥

ziggysauce article on his Voyage team experience

Also, here is an article he wrote after he got a job!

🔥

Sarah Schneider on her experience in a Voyage team:

Six things I learned in six weeks on a Chingu Voyage Build2Learn project

🔥

Eun Park’s article on her experience in a Voyage team:

Stress and insecurity: a newbie’s first remote dev team experience

🔥

Matthew Burfield on his code adventure

How I got a mid-level front end developer role in just 8 months

🎆 If you get any of these 5 Chingus on your team, you just hit the remote dev lottery

8 — Past Project Showcases

Thousands of developers, designers and PMs from 140+ of the world’s countries have come together to build. Here are some project showcase articles.

🚀 To achieve great things, two things are needed: a plan, and not quite enough time

🚀 Project Showcase — Yes, 50+ more code projects from hungry learners leveling up their skills!

🚀 Let’s Build-to-Learn — 250+ projects from coders around the world

🚀 Chingu Mini Project Showcase — 106 developer projects from people around the world

🚀 Build, hack, learn: 230+ developer projects from the Chingu cohorts

🚀 Say no to tutorial purgatory

🚀 One project at a time, we build to learn

🚀 Never stop building

🚀 Build, hack, learn: 50+ remote developer projects from the Chingu cohorts to start your day off right

🚀 The Winter Chingu Project Showcase

🚀 The Fall Chingu Project Showcase

🚀 The Spring/Summer Chingu Project Showcase

I CAN’T WAIT TO START!!


. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .