Why My Code Would Take 316 Years to Executeby@gauravshankar
467 reads

Why My Code Would Take 316 Years to Execute

tldt arrow
Read on Terminal Reader

Too Long; Didn't Read

Gaurav Shankar QA turned Back-end @Freshworks has written a series of stories about programming. He started programming about 5 years ago. He was naively brute-forcing every single problem that he would come across on platforms and later wonder why it would give him a TLE Error. After a few years, he was able to solve the same problem with all the same test cases. He is now working at Freshworks as a QA-turned-Back-end QA.

Company Mentioned

Mention Thumbnail
featured image - Why My Code Would Take 316 Years to Execute
Gaurav Shankar HackerNoon profile picture

@gauravshankar

Gaurav Shankar

Learn More
LEARN MORE ABOUT @GAURAVSHANKAR'S EXPERTISE AND PLACE ON THE INTERNET.
react to story with heart

RELATED STORIES

L O A D I N G
. . . comments & more!
Hackernoon hq - po box 2206, edwards, colorado 81632, usa