DEV Community

Jim Medlock for Chingu

Posted on • Originally published at Medium on

Chingu Weekly 111

Congratulation to Explorer Cohort #1

Shout-outs & Showcases

Photo by Pablo Heimplatz on Unsplash

🎉 Congratulations to those in the Explorers Cohort #1 who submitted a Solo Project for evaluation! You did it!!!

📜 We have provided constructive feedback to everyone who submitted their project and Completion Certificates will be sent out this week

🏃🏽‍♀️🏃‍♂️🏃🏿‍♂️🏃‍♀️ Voyage 22 Chingu’s are working on completing their projects in Sprint #6 this week — The final sprint of this Voyage!

🎉 Congratulations to GreatDeveloper66 & Jasterix who are both starting new Developer jobs! A lot of hard work went into achieving this milestone.

Overheard in Chingu

Photo by James Wainscoat on Unsplash

There’s a reason my kids are so messed up….ME

It looks good. one question, did you add the pubspec.yaml file or it came by default? just wondering if you need it at the moment

It’s International Talk Like a Pirate Day on the 19th. There is no holier day on the Developer calendar

GitHub question — I have a project with *.md files that link to other *.md files and I’m doing the work in the development branch. When I pull these changes into the master branch, I assume that these links will not update as right now they state github(dot)com/username/project-name/blog/development/ where development is the branch name. is there a way to fix this, or will I have to update the master branch directly once I do the PR?

Sooooooo stardew people text me so I can create a gaming group, but probably no gaming before weekend on my end. Want to try crusaders king tonight

Hi everyone, are there any guides/checklists/best practices to help developers be more effective in doing Code Reviews?

Unless I’m missing something, the only way a mobile app could really outdo a PWA is if they offer things PWA can’t do. Idk what the status is on that

Ahhh, god this page looks incredibly awesome and it is.. not build on React? O_o

TIL do something good and tell about it helps you alot in live. I sponsored some Flutter GitHub projects and now my YT channel gonna be announced in a Flutter related book

Well we have to work overtime to meet deadlines sometimes

Yeah it is too large for browser, you should use Webworkers. Ideally, you should paginate the output if possible or process this on the backend

When you accidentally get a HDD drive instead of SSD and the only option to cancel is to call them. “Ok.. might as well find a use for this” XD

Chingu of the Week

🧑‍💻🧑🏿‍💻🧑🏻‍💻🧑🏽‍💻👩🏿‍💻👨🏽‍💻 Reginam, silentkdev, SorenG, ZumDeWald, Christin, & jmwebdev who have formed a working group to design & develop the Chingu Quiz app!

Resources of the Week

Frontend Design Checklist —


Technical Writing courses for Engineers

Technical Writing | Google Developers

Quotes to Go

Photo by Brett Jordan on Unsplash


Perfection is the first step to failure!

Developers are by nature very detail-oriented individuals. It’s a required trait since the apps we create must meet the requirements imposed on us by both users and the technologies we use.

But, the downside occurs when your attention to detail turns into perfectionism. Our definition of perfectionism is devoting attention and attention to details associated with a task, before they are needed.

Welcome changing requirements, even late in development.

This is where an Agile Methodology can be your best friend.

The Agile Manifesto values “Responding to change over following a plan” and one of the 12 Agile Principles is: Agile processes harness change for the customer’s competitive advantage.

Timing is critical since it’s important to do the right thing at the right time. Some practical tips include:

  • Create simple app components based on what you currently know and add to them as new details surface in later sprints.
  • Don’t let what you’ve already created lead to resistance to change. Your code is the means to a goal, not the goal itself.
  • Design and write your code assuming that it will need to be modified and enhanced.
  • Treat your backlog as a “living” document. Continuously groom it in each sprint as new details are found.
  • Don’t hide your status from the team. Information should be freely and openly shared (including problems!) since all teammates are equally responsible for reaching the MVP.

Start simple and add complexity as needed!

Before you Go!

You can learn more about Chingu & how to join us at

Top comments (0)