ComCoding

Communication, community, and complexity all fall under one term I like to call ComCoding (yep, I made that up). Communication establishes a medium for ideas to pass on to one another; it plays an important role in overcoming problems and obstacles when help from others is needed. With communication comes community; whether it be online coding communities or your group of fellow co-workers, community opens the door to an abundance of resources above and below. Complexity can directly relate to an elaborate piece of code or serve as a representation to the obstacles bound to occur through hours of programming. Below are a few personal experiences outlining ComCoding.

No computer programmer knows everything and therefore often times I find myself asking questions to others more knowledgeable in a specific area. In one scenario, I had to ask an instructor to explain addEventListener() and how it was being used within a block of code; not only did this help me better understand what event listeners were, but also taught me ways to implement such code in future projects.

In another scenario, there was a time where I was dealing with a difficult colleague. To deal with this colleague, I kicked him out of the group banishing him from any future communication. I’m lying that’s a fib. Instead of forcing a fellow colleague out our group, I decided to walk him through the steps required to obtain the final product I had envisioned; by doing this, I helped that person understand the problem that had upset them and provided him resources to deal with similar problems in the future.

One major obstacle I came across during a project was a key feature failing to work as intended. I had done many research on the problem and had narrowed it down to several choices of cause. After hours of stabbing at the problem, I took a break and asked an instructor for help. Hoping this would help refresh my ideas to tackle the obstacle, I later discovered that even with an instructor’s help the problem still wasn’t fixed. In a final effort to find a solution, I posted a thread on StackOverflow describing my problem. With StackOverflow being such an valuable resource, I was able to receive an answer from the coding community and finally tackle the problem.

Sometimes communication isn’t communicated well enough. This time, I had assigned a group to create a comment div and complete the styles and formatting for it. The final product they had brought to me was the exact opposite of what I had envisioned, clearly showing a lack of communication. To handle this, I pulled them aside to talk to them clearly about the design and layout I had in mind; making it even clearer, I drew out what I wanted from them rather than trying to verbally explain. Within a few days, they brought back to me a perfect comment div displaying a better form of communication between the both of us.

Tell me about a time you had to work on several projects at once. How did you handle this?

Whenever I work on multiple projects at once, I split each project into manageable tasks focusing on each, one at a time. For example, when I was tasked to start the layout of an app while balancing another side project, I split the coding into bite-sized pieces. For the app, I split it into 4 main parts, three different indexes and once stylesheet; for my side project, I set up minor checkpoints to accomplish before I moved on. This allowed me to easily flip back and forth between two different projects without screwing up one another.