Understand Your Code

When the student is ready, the master appears. ~Buddhist Proverb

As engineers, we write code and work on infrastructure; even the infrastructure is written in code. But do we know what we’re even doing?

The process of solving a problem is the following:

  1. Write the requirements for the problem
  2. Design out the flow
  3. Write the first iteration of the solution
  4. Get stuck by an error
  5. Go on StackOverflow to find your error
  6. Copy and paste

In our bootcamp, there’s been many occurrences of someone solving a problem, presenting it to the class, and then being speechless when asked what a specific line does.

If we don’t know what we’re doing, what do we do when a problem occurs from that unknown line? Look up that problem again on StackOverflow. Seems like a recursive tech debt.

We as engineers should know every line we write and if we don’t, find that library and dive deeper to see what it really does.

We’re engineers, developers, and creators; not copy-pasters.

Which one do you want to be?

If you’re interested in hearing more about the exciting work we do at GO-JEK, hit me up on LinkedIn or apply on our site. We’re always hiring :)