I started programming about 5 years ago. Ironically, only in the last year of my computer science degree. I was also made aware of the likes of and at the same time. I remember naively brute-forcing every single problem that I would come across on these platforms and later wonder why it would give me a TLE Error. Hackerrank Hackerearth I wouldn't actually think of solving the problem then, but just do as said in the question and follow the initial intuition. The concepts of time and space complexity were equally alien to me as my approach to solve these. I wouldn't bother to look up the internet either about what really goes on in the code but just solve it. How stubborn! Coming from a background where I took the CS degree just for the sake of it, with no real knowledge, needless to say, it's obvious that I knew nothing about real software development and how companies run. I was injudicious enough to believe that I can brute force myself into the companies that would come for jobs just like this. It continued for a while until something happened which changed me, once and for all. While I continued with my foolish approach, I stumbled upon problem and I was in for a ride. I read the problem description and thought how easily I can solve it, by, obviously brute forcing it. this And I did! And below were the results. And this was my submission. { { count = ; ( i=a;i<=b;i++){ number = i; currentDigitValue = ; sumOutputValue = ; sumSqOutputval = ; (number != ) {
				currentDigitValue = number % ;
				number = number / ;
				sumOutputValue = sumOutputValue + currentDigitValue;
				sumSqOutputval = sumSqOutputval + ( currentDigitValue * currentDigitValue);
			} s1 = isPrime(sumOutputValue); s2 = isPrime(sumSqOutputval); (s1 == && s2 == ){
				count++;
			} { ;
			}
		} count;
	} { res1 = ; (a == ){
			res1 = ; res1;
		} (a == ){
			res1 = ; res1;
		} { ( z = ;z<a;z++){ (a%z == ){
					res1 = ; ;
				} {
					res1 = ;
				}
			} (res1 == ){ res1;
			} { ;
			}
 
 
		}
	}
} public class Solution static long luckyNumbers ( a, b) long long long 0 for long long long 0 long 0 long 0 while 0 10 10 boolean boolean if true true else continue return static boolean isPrime ( a) long boolean true if 1 false return else if 2 true return else for long 2 if 0 false break else true if true return else return false As usual, I kept wondering why would this happen but this time, for once I decided to do something about it. So I did the obvious and sought help from the community. And they responded as well. And then it hit me hard! Wha-at!? My code would take 316 years to execute. How’s that even possible? I was shocked and desperate to get this fixed. Someone in the thread also suggested, the problem would need a 3D-DP approach to be solved, a term I had never heard of. This was it. This incident propelled my curiosity and changed things in a way I'd have never imagined. As the saying goes. . . All it takes, is a little push. It's needless to say that things didn't change for me overnight but It took a great amount of hard work to lift myself from the dirt I was in. Most importantly, it needs you to be curious about things. The day you stop being curious about it, you stop learning. It's been so long since then, and I've really come ahead in my career but thinking about the incident, I wonder where I would've been if this wouldn't have happened with me. I'm sure all of you would've been there too. What are your stories? P.S: Oh! Did I mention that I was able to solve the same problem a few years later with all the test cases. Did you solve it too? Share your solutions.

Read My Stories

Too Long; Didn't Read

Make resilience your competitive advantage

Why My Code Would Take 316 Years to Execute

About Author

Comments

TOPICS

THIS ARTICLE WAS FEATURED IN

Related Stories

Untitled Story

10 Things Everyone Should Know About Machine Learning

10 Repositories that Will Transform the Way You Approach Technical Interviews

10 (Free) Data Structure and Algorithm Courses Junior Developers Should Explore

10 Data Structure & Algorithms Books Every Programmer Should Read

The Noonification: How to Develop a DSL in Kotlin (12/12/2023)

10 Things Everyone Should Know About Machine Learning

10 Repositories that Will Transform the Way You Approach Technical Interviews

10 (Free) Data Structure and Algorithm Courses Junior Developers Should Explore

10 Data Structure & Algorithms Books Every Programmer Should Read

The Noonification: How to Develop a DSL in Kotlin (12/12/2023)

Light-Mode

Classic

Newspaper

Dark-Mode

Neon Noir

Minty

HN StartUps