Voyage 29 is coming to a close & Voyage 30 is off to a strong start!
🏄♂️ Voyage 30 starts Sprint 2 today! Project teams are off to a strong start on their projects! Sprint 1 is about setting the projects foundation & Sprint 2 is when development starts to ramp up.
⛵️ Voyage 29 started Sprint 6 this week. This is the last week of this Voyage project. Teams are hard at work to complete work on the features that are part of their MVP, fixing pesky bugs, doing that final production deployment, & Celebrating their Success!
🚀 Voyage 31 starts on May 31. Don’t put off joining if you would like to leveling up your team & technical skills. Don’t wait - Take charge of your career today!
🏆 Check out the Morse Code communicator this Voyage 27 team created!
🎉🎉🎉 Congratulations to the following Chingus for reaching these milestones & goals!!!
- Congratulations Nellie for her talk on “Bringing K8s into port with visual learning” at Data on Kubernetes Day!
- Jaytula reached a milestone of 10K commits for a single GitHub repo. That’s dedication!
- Armando landed a software development position at Berlin-based start-up! He put in many long hours on projects to grow his skill to meet this major career event!
- Happy Birthday to Monikat & Tisdale. We hope you’ll have many more!
- And last, but certainly not least, a Happy Mothers Day to Developers who are also Mom’s! Growing both your kids and your careers is like having 2+ jobs and you are appreciated for your efforts.
“Does anyone have any experience with HackerRank’s tests? If you do, what would you recommend as the best way to prepare?”
“TIL about css mask-image for creating an alpha gradient”
“Today I learned to keep my developer notes from my old apps if I want to reference the live version. My voyage 9 app was live before Covid, thanks to Brian from my voyage 9 team. But the site is now gone and today I discovered all my local config data is gone with one of my dead hard drives. I didn’t keep any notes that I can find so I’m having to rediscover how to deploy the application. It’s a good refresher I guess.”
“TIL…Binary Search Trees…coded recursive versions of insertion, removal, search, and built an iterator (non-recursive).”
“Ugh it’s so unhealthy to sit all day, I’m trying to squeeze in exércise mid day but somehow always end up after work if I’m not too tired that is!”
“TIL how to use getters inside getters and use mapGetters efficiently. reducing 8 lines and much cleaner code!”
“But yeah, I would be happiest with a company that would send me a nice, practical coding assignment like “build this simple app that can actually be used in real life.”
“TIL (or relearned) that addEventListener doesn't set duplicate event listeners, unless the handler is an anonymous function. I totally forgot about this, and was able to remove about 5 lines of removeEventListener"
This isn’t code-related, but as app complexity and team size grows it is very important to keep product assets organized so all members of the team can easily and quickly find what they need!
The hardest part of a project is understanding what everyone on the team is working on at any point in time.
It’s important due to the dependencies between the components everyone are working on. Lack of information can result in these components not working as expected when they are brought together in a shared repo through your pull requests.
In this age of sophisticated project & team tools there’s no excuse for not sharing status with your teammates!
So, how do you solve this problem?
Set up & use a team channel to ask questions and report issues.
Monitor your team channel daily so you don’t miss updates from your team mates. Even better, see if there’s a time of the day where all team members can be available, even if it is only for a few minutes, to review status — just like a standup meeting!
Post your status at least every other day in the form of a text-based standup using this template:
My mood today:
Tasks I’m Working On:
Task #1 + expected completion
Task #2 + expected completion
Tasks I’ll Be Working On Next:
I Need Help With:
Question/Issue #1 — short description & what do you need
Question/Issue #2 — short description & what do you need
Remember that reaching your team goal is more about coordination and communication than it is about technology.
Chingu helps you to get out of “Tutorial Purgatory” by transforming what you’ve learned into experience. The experience to boost your Developer career and help you get jobs.
You can learn more about Chingu & how to join us at https://chingu.io