Chingu Weekly — Vol. 138
Tags: softwaredevelopment, webdev
Published: 2021-04-12 13:18:21

---
title: Chingu Weekly — Vol. 138
published: true
date: 2021-04-12 13:10:03 UTC
tags: softwaredevelopment,webdevelopment
canonical_url: https://medium.com/chingu/chingu-weekly-vol-138-878c5864042e
---

### Chingu Weekly — Vol. 138

Voyage 28 is a wrap, but Voyage 30 is on the horizon!

![](https://cdn-images-1.medium.com/max/1024/1*EhLXQuMtZrRw_UQGnNptIg.jpeg)<figcaption>Photo by <a href="https://unsplash.com/@colepatrick?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Cole Patrick</a> on <a href="https://unsplash.com/s/photos/mist?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption>

### News, Shout-outs & Showcases

**🏄‍♂️**  **_Voyage 30 starts on May 3!_** To take part to boost your Developer career sign up at [chingu.io](https://chingu.io)

⛵️ **_Voyage 29 starts Sprint 2 today_**. Sprint 1 lays the foundation for the team project, but Sprint 2 is when the coding starts. It‘s always exciting to see teams first steps at turning their concepts into code.

🚀 **_Voyage 28 ended yesterday_**. Teams worked hard during this Voyage and it’s exciting to see what they’ve built. Like this team’s app!

![](https://cdn-images-1.medium.com/max/1024/1*QUWc2QotkvOdfvevcRE-Fg.png)<figcaption>Chingu Voyage 28 — Geckos Team #5</figcaption>

🎉 **_Congratulations_** Chingus!!!

- Congratulations jmwebdev on your 1 year work anniversary! It’s great to see Chingu’s not only reach their goals, but to excel at them.

> _Well done Chingu’s on these significant milestones in your careers as Developers!_

### Overheard in Chingu

“TIL…CSS Grid and created a painting of an artist “Mondrian”. Source Code : [https://github.com/ryanbest99/mondrian-painting](https://github.com/ryanbest99/mondrian-painting) Link : [https://mondrian-css-grid.netlify.app/](https://mondrian-css-grid.netlify.app/)”

“ES6+ makes our lives much easier but still good to know how things work under the hood as you may be asked in a future interview, if nothing else. Understanding initializing, declarations and event loop are good to know (but I wouldn’t loose any sleep over it — sometimes showing you are simply aware is good enough).”

“Whatever happened to strict mode? Did ES6 send it to the dustbin of history?”

“TIL…Adding a ‘wakeup’ API route to a BE server hosted in Heroku and calling it when the FE is loaded shortens the time users have to wait for a dormant Heroku server to start. I did this in a Sapper module on the FE, but it could also be added to a ServiceWorker.”

“TIL…stacks, queues, linked lists….worked all day on a problem so insert, remove, retrieve, and search…all recursively…and iterated through the list. Also this was a sorted list. FINALLY!”

“I have graduated from boot camp a few months ago and I have my first interview next week. If anyone can share their interview preparation technics that would be great. I am confused and need some guidance.”

“I personally find Redux the most difficult part of understanding a React app and it make following a component’s logic difficult at times. Not to mention bugs around Redux can be very tricky. I agree with his take: Avoid it if you can and if you need to use it make sure you use it well.”

### Resources of the Week

Check out Ben Awad’s YouTube channel. He keeps his videos short, informative and funny. If you are getting into React and trying to learn more React, you’ll find it to be a good resource.

[Ben Awad](https://www.youtube.com/c/BenAwad97/videos)

### Quote of the Week

![](https://cdn-images-1.medium.com/max/1024/0*y852O_feVR9-KT4t.jpg)

#### Teamwork is Hard

As projects get underway teams begin to realize that technology is the easy part of a project. The hard part is working effectively and in harmony as a team.

This is especially true you haven’t had a lot of team experience. _You don’t know what you don’t know until you know it_, which is why we believe it’s important for individuals and teams to reflect on their workflow and how they deal with problems when they are encountered.

Problems and conflict will occur and it’s important to not ignore them. Reflecting on them starts by asking hard questions.

- What occurred?
- How was it discovered?
- What were the different options, alternatives, or opinions on how best to resolve it?
- Did conflict arise when deciding which solution to pursue?
- Was the discussion civil and respectful? If not, when did it become difficult and why?
- Did everyone on the team have the opportunity to express their thoughts
- Were everyone’s opinions given thoughtful consideration? Did I listen to what others had to say?
- Was I open to other opinions or was I constrained by my ego?
- What could the team and I do differently to manage situations such as this?

To get the most from this type of reflection:

- Define the shared outcome you want to achieve
- Conduct your discussion objectively, dispassionately, and without ego
- Practice active listening (see [https://tinyurl.com/m64qch3)](https://tinyurl.com/m64qch3))
- Agree on what you will do differently

### Before you Go!

> _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_](https://chingu.io/)

* * *