Tips on how to write a resume for web developer/engineer

I’ve been screening a lot of resumes these days to fill out one open position in our team. However, most of resumes that I reviewed writes about what projects were about and what role the candidate was on.

I rejected most of those resumes and sent back to recruiter.

Resume is a representation of you as an developer/engineer. As an engineer, don’t you want to discuss how you solve an puzzle instead of telling me what the puzzle was all about, what the rule the puzzle had, and so on?

I am looking for a resume that shows me how you solved an issue, how you improved performance, why you chose this approach over that approach, and so on.

In summary, I’d like to see more details on how and why you do.

pulling query string in node.js

in web development, pulling data from query string is the basic and fundamental task. In node.js, the syntax is like this:

you can actually test my test app here:

JavaScript String.replace with regex

I often use String.replace in JavaScript whenever I have to use JavaScript. Today was the day that I ended up with using it for my work. I know that String.replace supports regular expression to match your string, but I was not clear if I could use “capturing groups” and “quantifiers”. As I guessed, I was able to use quantifiers in the replace string like the sample below:

Initial Page Load – FE Performance Tuning

1. Introduction

Why is the site performance so important? The poor site performance impacts company’s revenue and user’s engagement.

  • Shopzila: 5 seconds speed up resulted in a 25% increase in page views, 10% increase in revenue, a 50% reduction in hardware, and a 120% increase traffic from Google.
  • Amazon: every 100ms of latency cost them 1% in sales
  • google: extra .5 seconds in search page generation time dropped traffic by 20%
  • a broker could lose $4 million in revenues per millisecond if their electronic trading platform is 5 milliseconds behind the competition.
  • facebook: regardless of site speed, users spend around the same amount of time on facebook, which means if the site is running slowly users are going to be seeing fewer pages in the same amount of time.

So the conclusion is that fast site is better.

Continue reading