Popular posts

I am not very sure if this is the hardest bug - lets say this is my recent hardest bug I dealt with.

I was working on a page that made heavy use of jQuery and used dynamic visualization tools to represent data in various formats : donut charts and sortable, searchable, editable tables. This page had about 21,000 lines of code separated into partials using handlebars. Initially, the page took 4.53s to load.I debugged every section of this page and implemented all sorts of performance improvement measures to reduce the page load time to less than 1s.

This part of my job was an eye opener for me in the sense how all the common programming mistakes committed earlier , when combined together in a page, were able to make such an impact on the performance.

Some highlights were:

1. Implementing general JS best practices (whatever results we obtain from a little research over the internet: ex- avoid dom tree traversal on same nodes over n over, get rid of unused links to external scripts, place CSS & JS correctly, avoid document ready unless there is no alternative)
2. Researching why people hate jQuery and debugging/ avoiding those areas! :P . For example, remove $.each and replace with <arrayElement>.forEach() (This easily saved me 1.5 sec for about 50 $.each references )
3. Used timeline & CPU profiling tools in chrome 57 extensively (upgraded to chrome 58 in between to leverage 'performance' tool).