The Design of a Programming Project

Jordan Dains
3 min readOct 27, 2020

When either starting out or becoming a pro, the programming life will always keep this common problem… the design of a project. Everyone has gone through it. The agony of time, design, and keeping the peace with those around you. The question being asked is “How do you work effectively, but also maintain your sanity while working on a project?” We will begin to explain some popular and personal designs that could improve you and your group’s project.

Among the most renowned and undervalued design method used in aiding for a project is pseudocode. Pseudocode is defined as “a notation resembling a simplified programming language, used in program design.” or “computing.” Its function is to explain machine text or problems in a human/plain text understanding. The pro of this design is it becomes a great help to those starting out in code who don’t fully comprehend the concept or problem being presented. This lacks those who have the experience and are looking for a more advanced design aid.

A very popular industry design aid is Waterfalling. “The Waterfall project management entails mapping out a project into distinct, sequential phases, with each new phase beginning only when the prior phase has been completed. The waterfall system is the most traditional method for managing a project, with team members working in a linear fashion towards a set end goal.” The pro to waterfalling is it makes your group focus at the step in front and not scale how big or small your project is. This lacks in dividing and conquering the project instead it certains the focus on a single problem/goal.

I personally have dealt with the madness of a project and I’ve tried to maintain the fairness of the workload and ideals, by also effectively completing it in a timely manner. It began with a pool of ideas to slowly but surely be narrowed down to a minimum of six. This would eventually lead to someone’s idea being cut from the list which in turn disengages their passion for completing the project. To keep fairness instilled I used an online roulette wheel inputting the idea’s and spinning from the lot. Now not everyone can be happy with the roulette selection, but all can understand that their idea is being discredited. The next order of business is dividing the workload. I proposed that we split the front-end and back-end of the project and would come together to form our masterpiece. This design seemed to fit the work that we are doing and could be altered to work for any scenario.

Lastly, here’s a few resources that could help you or your team in the struggle of designing a project.

Steven Nguyen’s Mod-5 Project: https://www.youtube.com/channel/UCkcGZP407UGOj26I5axev4w/videos

Project Management Application: www.monday.com/

Sources-

Title image: https://www.uxweb-design.com/wp-content/uploads/2019/10/Web-design-1.jpg

Pseudocode: https://www.merriam-webster.com/dictionary/psuedocode https://cdn.lynda.com/video/90472-147-635182861185610073_338x600_thumb.jpg

Waterfall: www.wrike.com/ https://miro.medium.com/max/1200/1*SffL0Y7YxWoQ1Cf9GpRVEA.png

Roulette Wheel: https://blog.tcea.org/wp-content/uploads/2019/03/Screen-Shot-2019-03-15-at-3.36.29-PM.png

--

--

Jordan Dains

Hi, my name is Jordan Dains. I am writing blogs on Medium about any aspect of technology.