Java Hyd Team
746 subscribers
986 photos
39 videos
670 files
690 links
https://teamhydteam.my.canva.site/

Can visit us on our website 😊
Still working on it 😊
Download Telegram
You can copy the question and search on Google
Java Hyd Team pinned «You can copy the question and search on Google»
But logic you should understand
lot of candidates prepare well for the DSA round through Competitive Programming and get rejected.

It might be because they think the interview is just about writing the most efficient code fast.

But the interview is more about how one approaches and solves the problem.

You are expected to understand the problem, think clearly about it and ask questions to make it more structured and well-defined.

Once you have understood the problem and requirements, you can start to come up with a solution.

You need to make sure that you've considered the different scenarios along with the edge cases and that your solution is working perfectly.

Once the interviewer is satisfied with the solution, you start coding when they ask you to.

But, please keep these points in mind when you’ll start coding –

- Be very sure about the solution before you begin to code.
- Do not change the solution after you start to code
- Before you start coding, try to think about the overall structure.
- Try to keep the code modular.
- Dry run your code before telling the interviewer you’re done with the code.
- Try to find the failing test cases yourself instead of the interviewer doing it for you.

Preparing for interviews can be overwhelming but with Career Camp Freshers by Coding Ninjas, the process has never been easier!

1:1 Mock Interviews with industry experts and a dedicated placement team, all at your disposal.

Upskill yourself and land your dream job now. Go register yourself by clicking on the link in the first comment below.

Your dream job isn’t far away.
Popular interview question: how to diagnose a mysterious process that’s taking too much CPU, memory, IO, etc?

This diagram is from Brendan Gregg's book: Systems Performance.
Can use service provider for @service
Most of all it's going to be worth it...
Forwarded from SathyaReact
Forwarded from SathyaReact
Forwarded from SathyaReact
Bug with the delete keyword :-
It deletes the elements value but never deletes the memory occupied that's why length is the same
Forwarded from SathyaReact