Why I Don’t Talk to Google Recruiters

Re:Why I Don’t Talk to Google Recruiters by PhineasRex on Tuesday February 21, 2017 @07:10PM (#13701565)

Where I work our core rendering algorithm which runs several times on every page load used naïve string concatenation. When I initially wrote it I knew string concatenation was inefficient but never got back to it and for 99.9% percent of cases it didn't matter! We finally hit that 0.1% case and after optimizing the algorithm, it didn't make a dent on our overall performance numbers at all.

The biggest impact to our performance has been switching one JSON serialization library for another, no algorithmic knowledge needed, just basic benchmarking skills.

[ Parent | on HN ]

Re:Why I Don’t Talk to Google Recruiters by stcredzero on Tuesday February 21, 2017 @07:19PM (#13701620)

Your one anecdote obviously proves everything once and for all. The biggest recent performance gains in my personal project had to do with switching to WebRTC and switching libraries.

Knowing when you can just slap in the naive string concatenation and move on is also a useful result of the right skills. If you had better profiling tools/skills, I posit that you wouldn't have had to do the useless optimization.

[ Parent | on HN ]

Re:Why I Don’t Talk to Google Recruiters by cagmz on Wednesday February 22, 2017 @01:30AM (#13703529)

What made you reimplement the rendering algorithm and/or switch JSON libraries (eg were these changes backed by data/measurements)?

[ Parent | on HN ]