- As you read through these guides, you can get an idea for how code is written at the respective companies.Why do we need styleÂ guides?For one main reason: Everyone writes code differently.
- Thatâs all fine and dandy as long as we each work on our code.
- But what happens when you have 10, 100, or even 1,000 developers all working on the same codebase?
- Style guides are created so new developers can get up to speed on a code base quickly, and then write code that other developers can understand quickly and easily!
- Review our standards and practices so that you can be familiar with important topics like milestones, the Elon-Musk-bot, communication guidelines and how NOT to make your team-mates angry.Table of ContentsWhy the Chingu Voyage cohort exists [1 min]Schedule [1 min]Standards + The Builder’s Pledge [3 min]Essential skills to learn before you start [10–200 min]The Build-2-Learn Project Roadmap (Acts+Milestones) [1 min]Why the Chingu-Voyage cohort existsThe Chingu-Voyage cohort exists to give motivated learners a community, environment and challenge to accelerate their skills, be accountable, as well as an opportunity to gain experience in a remote dev team.Why is this important?There are more people learning to code (and competing for jobs) than ever before.
- Put simply: the Voyage cohort is where people build projects.Voyage-2’s ScheduleSeptember 15 — Prep Packet goes outSeptember 21 — Voyage-2 StartsSeptember 24 — Teams launchOctober 3 — Act 1 finished due-dateOctober 10–15 — Sprint 1 due-dateSprints will continue until the project is finished.November 10 — Showcase for finished MVPsSome projects may take more time to complete.
- Those practices (seen below) are now our standards.All members are expected to do a check-in twice a week (NEW TO VOYAGE-2)The check-in style we encourage is:What I did in the last few days?What I’m working on in the next few days?Is there anything blocking my path?I can’t stress enough how important consistent communication is for remote dev projects.
- For anyone new to a Chingu B2L project, this will probably be the biggest skill you learn (regardless of what your team builds).
- The Build-2-Learn Project Roadmap (Acts+Milestones)In Voyage-2, each Build-to-Learn project will have 3 Acts and each act with have 5–10 milestones for the team to complete before they can get to the next act.Act 1 — Project SetupAct 2 — Code sprints (repeat until MVP)Act 3 — Closure+ShowcaseACT 1 = Start button, ACT 2 = the circle, ACT 3 = the mountain-topNote: when the cohort launches you’ll get a document that shows in detail what each milestone is, including any resources we have for that milestone, any examples of the milestone from former teams and due dates for each Act.That’s it, you’re all set!Have fun preparing for the Voyage-2 cohort!
Review our standards and practices so that you can be familiar with important topics like milestones, the Elon-Musk-bot, communication guidelines and how NOT to make your team-mates angry. The Chingu…
Continue reading “Voyage-2 Prep — Overview of what you need to know – Chingu – Medium”
- The goodies it brings — abstract and concrete classes, types, interface, enums are hard to resist.As we started on the development of the app, I thought it would be a good idea to put our learnings here in a series as it not only will help us document our tasks but would also help other react-native learners and developers.In this series, we will document step-by-step each task that we work on during the development of this app, right from the initial project set-up to its final implementation and release to the app store.What app we are going to developThe app we would be developing would be a simple photo albums app, where user can create an album and add photos to its from his/her mobile.Tech-stack to be usedUI using react-native + TypescriptStorage — Azure DocumentDBREST API using node.js, Azure DocumentDB Node APIAuthentication — oAuth (Facebook and Google)Targeted platformsIn its first version, we are planning to target only Android platform simply because couple of us in the team don’t own a Mac Book and apple doesn’t allow to develop iOS apps from any other operating system.Github RepoOur LimitationsWe are all learners of react/react-native, also this being a side project that we all will work on in our spare time, we are anticipating the project to go on a bit slow pace.Functional Testing — we don’t have a QE Automation expert in our team yet, so for most of its part Functional testing would be manual3.
- Environment — for the UI app, we will use emulators on our local system to test our code.
- Being a mobile app, it would be released to Android Playstore and thus we don’t need to maintain any servers for the UI app4.
- So stay tuned, more stories to come soonInterested in joining us in this wonderful journey?we’ll be glad to have you in our team, pls email to us at firstname.lastname@example.org with a little bit about yourself
Couple of weeks back, I and some of my friends, started on a side/hobby project to learn reactJS. We decided on developing a mobile app with react-native just because the idea of developing a native…
Continue reading “Introduction – Developing a native mobile app with React-Native and Typescript – Medium”