How i overcame my most recent learning challenge

It seeks to challenge ones original beliefs about something. It seeks to make one go through the needed process of learning new ideas, unlearning the old ones, and re-learning the already learnt ones. With it, one feels either like a winner or a learner rather than a failure. It is Growth Mindset.

Code testing is a platform where your written code is subjected to tests either by the developer locally such as using frameworks like mocha or jasmine or by an external body or framework. Continuous integration on the other hand in collaboration with code testing seeks to ascertain if your new features or chores is fit to be absorbed into your already validated and tested code.

Coming across code testing and continuous integration for the first time in my first two weeks of my challenge was a “challenge” to my original belief about writing code which only seeks to rely on debuggers and manually tracking errors by myself in written codes. Being a person that seeks to understand rather than imitate, i sort to uphold my growth mindset practice by choosing to search for documentations to understand the reason both concept exist in the first place and their advantages to ones coding experience. With my findings, it had a lot of advantages and made a lot of sense to me, hence, making me to adopt both concepts.

Related posts:

The figure of a clown trapped in its body has been flickering through popular imagination since Chaplin swallowed a whistle in the historic scene from City Lights (1931). Not being able to control…

After high school graduation, you don’t get the ultimate “college experience” in Lebanon. You usually don’t pack your bags, say goodbye to your parents and travel to another city. It’s either Beirut…

Each year I push aside whatever I’ve been reading and go revisit several books that are important to me personally, as well as to my career. I was recently re-reading (or maybe just skimming and…