Julia's coding blog - Practice makes perfect

From January 2015, she started to practice leetcode questions; she trains herself to stay focus, develops "muscle" memory when she practices those questions one by one. 2015年初, Julia开始参与做Leetcode, 开通自己第一个博客. 刷Leet code的题目, 她看了很多的代码, 每个人那学一点, 也开通Github, 发表自己的代码, 尝试写自己的一些体会. She learns from her favorite sports – tennis, 10,000 serves practice builds up good memory for a great serve. Just keep going. Hard work beats talent when talent fails to work hard.

Sunday, December 27, 2020

Behavior interview: Case study - website crashed in 2020

Dec. 27, 2020

Introduction

It is toughest project to work on called behavior interview. What I like to look into and what I should think carefully before I have to answer the question. I like to do a small case study on one question.

Case study

What is difficult project work on? Why it is difficult? What have you done? What have you done differently if you can?

First and most important, I think that I should choose project in less than six months. And I have to think about what is difficult.

First I should say that it is website crash. It crashed and a few people noticed that right away, 4:00 PM to 6:00 PM sometime.

What makes it difficult?

I stay on the job 10 years. I did not take ASP.NET certification, and I did not finish IIS administration book at all. I have working knowledge but it is not testable. I did not have any crash issue in last three years. I almost assume that the website is a money making machine, I do not need to do a lot of maintenance; Everything goes smoothly.

Certainly it is not too tough for me to solve it in less than two weeks. I just quickly identified the issue to restore the website. And I like to take some extra time to review a lot of things before it is fixed.

Here is the list of things I worked on:

Event viewer - IIS server - try to see if there is any serve issue
Database - Review cache mechanism, and all product features on this business website
Work with browser - why it is not working, inspect -> I found something interesting -> html code was broken
I did turn off cache for websiteMainMenu table, next day I got complaint that the website was so slow to respond. -> I should make changes no one noticed.
I quickly fixed the cache issue to restore product feature, and I also found the issue the missing close div issue.
Lesson learned: I can quickly figure out how things work in less than two weeks, I tried to identify so many possible factors, over 100 of them. I learn to fix them.
I wish that I can do better and make some update as well.