Skip to main content

My First 'Not Yet'

I took the 219 assessment about 2 months ago. Kevin administered the test. It was a problem solving question whereby you are required to solve a problem using javascript while talking through the steps.

The problem looks relatively simple, so I wrote some test cases and pseudo-code. I then proceeded to code the solution. 30 minutes passed, I was pretty confident my solution was right. It solve 5 of the test cases I wrote. I thought I nailed it. I decided to add in a few test-cases just because I have some time left. One of the test cases doesn't produce the required output.

It was alright, this kind of things happens sometimes. I decided to tweak my code here and there, thinking it will produce the required output for that particular test case. To my horror, it didn't. Another 15 minutes passed. I begin to panic a little. I remember asking Kevin 'do I have to time myself for the test'. It was funny now when I think back. Of course I do, it was a 1 hour test.

It turns out there was a fundamental flaw in my solution. I decided to change my strategy at the 50 minutes mark. I was frantically trying to save my assessment. Being in panic mode really messes up your thought. The new solution doesn't even come close to solving the problem, it doesn't even solve any of the test cases.

Finally, time is up. I replace my old solution as the submitted solution. I remember telling Kevin 'This is the best solution I had'. I thought that maybe satisfying some of the test cases might land me a B or a C , but still a pass. It didn't. It was a 'Not Yet'.

I was stunned at first. I am not sure how to react. After a while, bad thoughts creep up. I remember telling myself a few things

- 'Did Kevin judge me based on the disaster second solution or the first one ?'
- 'If it is the first one, then it is not fair, I get a fail for failing only one test case ? I should received a pass , maybe a B or C'.
- 'I failed one time, I could fail another and another time'
- 'I am going to get my revenge, I won't study course 210 properly'
- 'Kevin is cruel bad person'. (sorry Kevin XD)

Times like this is crucial. It is important that you get your attitude right when you met with stumbling blocks, because if not, you will just give up. I took a brief break.

Yes, getting a 'Not Yet' will be tough, especially if you have a passing streak you'd hate to break. But had if Kevin passed me, I would still not learn my lesson. And this flaw would carry over to future course and my future career. It is better to faced the harsh reality now than later.


Comments

Post a Comment

Popular posts from this blog

Problem Solving - Refactored

I am going to outline how I approach problem solving. The relative importance and the amount of effort/time required for each is stated as a percentage beside each topic. I borrowed some idea from George Polya's How to Solve It Thoroughly Understand the Problem (30%) When encountering hard problem , you need to deeply understand the problem at hand. Take a paper and list down all known facts and data and what the question is trying to find. Sketch out the problem if applicable. Visualize the problem in your head. A lot of times, we only have to understand the problem well, then the solution will obvious. Have a Plan (20%) You need to have an outline of how you are going to tackle the problem. You need to have a logical pathway that will ultimate produce outcome (nothing to do with coding syntax yet). Without a plan, you are just randomly poking around and got lucky. No hard problem ever gets solved without a plan. Plan using pseudo-code, pen & paper or flowchart. Use wh...
5 comments
Read more

Sharing my Weakness

It makes sense to know about your weakness and do something about it. Here are my known weaknesses uncovered during my time in Launch School. 1. I don't like to refactor my code   - Your first draft will not be perfect. It works but it may not be efficient/readable/best practices. You final code will almost always be better than your first draft. - It is easier to separate the task between writing code that works and refactor later to make it efficient/readable/best practices. - If you refactor your code often, over time you will discover your bad habits and change it. 2. I don't like to read other people's code - There are more good programming practices in other people than in you (especially for beginners like me). - To be good , you need to know more than one pathways to solve a programming problem (and there are always more than one way). Then you can judge their merit. - Reason for dislikes    1. It is considerably harder to read code than to write one (...
1 comment
Read more

My Burnout Experience

I want to share with you my experience of burning out. After registering with Launch School, I am extremely excited about my programming journey. I studied for 10 to 12 hours a day, memorizing fact, trying out practice problems, understanding programming concepts. It was fun and exciting and I love seeing myself growing from nothing in programming to something more. After about 3 months, thing starts to change. I started noticing myself paying less attention to details. I find myself skimming through the course material. I skip "Further Exploration" in the practice problem. I am more interested to study just to pass the assessment rather than truly mastering the concept. It was a gradual burning out process but I continue to study for 10 to 12 hours a day through sheer grit. It felt like doing house chore or working a day job that you don't like. One particular morning I woke up, and I remember this deep feeling of dread because I can anticipate that the next 10 to 1...
Post a Comment
Read more