Worrying won’t change what’s written for you.
Surrender, smile, and watch God work it through.
Don’t overthink - it’s all happening for good.
That’s the beauty of His plan. That’s how it should.
@NerdPiJJO I don't have any issue with on-site interviews. I am just unsure why I wasn't selected, as I answered all the questions asked and my interview rounds went genuinely well. Perhaps they were looking for a different skill set. Anyway, leaving it to God's plan.
It really hurts when u had given your best,cleared all the rounds..still didn't get the offer letter especially for which u have travelled on-site multiple times for rounds...but that's life... trusting God,I m sure he must have a better plan for me....may be a bigger opportunity
went to clg to submit my project report, couldn't submit due to some reasons
but went to library and saw a guy from my class grinding alone since morning, no distractions, no one to talk to, just pure focus for placements
genuinely got motivated
To shrink the array dynamically, we'd have to pre-count unique letters, creating a "chicken-and-egg" problem that takes double the work.Keeping it at 26 is microscopic for computer memory, 100% predictable, and lets us use instant math (char - 'a') to find our chair. Simple wins!
I was practicing a classic DSA problem today: Removing all duplicate letters from a string using recursion (e.g., "success" ➡️ "suces").But while solving it, a big question hit me about memory optimization... 🤔👇
The standard solution uses a boolean array of size 26 to track which lowercase letters (a-z) we’ve already seen.I thought: "Wait, if the string is short, isn't a fixed size of 26 a waste of space? Why not dynamically size it based on the string length?" 🧐 (2/4)
26 IS the optimization!Think of it as 26 permanent chairs outside a party—one for each alphabet letter. If we make fewer chairs to save space (say, 5 chairs), what happens when the letter 'z' shows up? It looks for chair #25, finds nothing, and the program crashes! 💥 (3/4)
Descriptive commit messages are a must as a developer.
It shows how your project was built layer by layer, and it really helps when you need to undo a commit, remove a feature etc.
It keeps your work organized. It's a small habit but definitely a best practice.
#Commit#Logs