DEV Community


Chingu Weekly — Vol. 143

Jim Medlock
I manage Operations at Chingu, Inc. We help bridge the knowledge you have gained via your learning activities and the experience employers seek through global remote team projects. Come join us.
Originally published at Medium on ・4 min read

Chingu Weekly — Vol. 143

Voyage 29 comes to a close, but Voyage 31 is preparing to set sail

Photo by John Schnobrich on Unsplash

News, Shout-outs & Showcases

🏄‍♂️ Voyage 30 starts Sprint 3 today! Project teams are making steady progress towards their goal of completing a Minimum Viable Project (MVP) for the project they’ve chosen to build.

⛵️ Voyage 29 came to a close yesterday. Projects will be reviewed this week and Completion Certificates will be distributed on May 23. BUT the most important task remaining is for teams to congratulate themselves on the experience they’ve gained and to celebrate their success!

🚀 Voyage 31 starts on May 31. The Solo Project deadline is on Tuesday May 25th, so don’t put off joining so you can build experience needed to get Developer jobs. Don’t wait — Take charge of your career today!

🏆 Check out the travel app this Voyage 29 team created!

🎉🎉🎉 Congratulations to the following Chingus for reaching these milestones & goals!!!

  • Congratulations tamsO for starting a Full Stack Developer job at an educational non-profit organization last week!
  • Monikat landed an internship as a Full Stack Developer. Well done!!!
  • Well done Nellie who has advanced to the next round of technical interviews on her job search!
  • And congratulations to all Voyage 29 participants on completing your Voyage!

Photo by James Wainscoat on Unsplash

Overheard in Chingu

“TIL our old overlay banner was centered using a big function in JS, and kept responsive by running that function on resize. I guess some people hate CSS so much that they actually end up writing styles in JS.”

“That moment when you realize how global your product is, when you get a bug like: Text x does not look good on RTL languages”

“TIL you can extend null in a JS class”

“Yea i guess it’s good if you don’t set everything on fire. That’s the first step”

“TIL Go. I mean, I have started learning Go some time ago mostly from examples but today I decided to devour a book from start to end to actually learn it well. I must say it’s so easy, the syntax is so minimal but you can do a lot with it: a.) If you’ve done TS, the concept of interfaces and types just comes without explanation b.) If you’ve programmed and used pointers in other programming languages, it’s pretty straight forward c.)If you’ve worked with Workers / Worker Threads in Node.js, the concept of Goroutines and channels is similar (without all the boilerplate required in Node.js) —Loving it”

“Only wimps make coffee with water. Real Devs just munch on coffee beans. Organic of course”

“TIL we can use delete operator to delete an object property.”

“I’ve been answering mails and slack all day, literally. Oh and few meetings. I feel like I’m slacking but I’m actually highly busy lmao”

“TIL MongoDB Compass 1.22 and later has an integrated shell at the very bottom. Quite convenient in case you don’t already a mongo client handy. If you haven’t updated since May 2020, this might be a reason to do so.”

“You know that you’re old when you start to run training sessions at work and you’re the teaching person, not the listening person”

Resources of the Week

Most of us git rebase. But, what about git squash???

Quote of the Week

“Rome Wasn’t Built in a Day”

A common issue teams run into in the first few sprints of a project is adding too much functionality too soon.

The impact of adding too many features too quickly is getting stuck implementing technical details (and hitting issues) before they are needed.

Keep in mind that the Minimum Viable Product (MVP) process, supported by an Agile methodology, builds a working product in each sprint. Your product in early sprints will be very simplistic, but each sprint builds on what you’ve done in previous sprints.

The product you deliver at the end of each sprint doesn’t have to be perfect, but it does need to deliver some functionality.

It’s okay if the product you deliver at the end of Sprint 2 consists of a project structure, the basic technical stack, and a “Hello World” screen. That’s actually a great starting point since it lets team members add new features to a common foundation.

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

Discussion (0)

Forem Open with the Forem app