The only way is to practise regularly. "Studying" like a few days before the interview schedule is not going to help

And most importantly, ask such prospective employers why they need an intermediate to advanced level of skill set when it comes to DSA. They probably don't know better and think they are cool for no reason. Most of such employers will only offer you jobs where you need to build some kind of frontend/backend that doesn't require you to build everything from scratch

Plot twist - someone (magically) found your fix and raised a PR and got it merged. The boss says the fix didn't work and wants to debug further

Look at the PR?

So, not only do they not do anything productive but they also end up working in some wrong direction proving to be destructive enough

it is kind of 50-50 in my experience. Most are able to talk a few things about the stuff they put in their CV. Around half of the candidates can answer basic questions without any lack of clarity. Around 20% can go beyond and probably less than 5% look fully qualified for the job opening

Bombed as in awful? Or awesome?

And time to rewrite history

Dictate your words to a voice translation kit 😐

It is Friday already!

I haven't heard until now. Looks advanced!

😳

I don't want to hear anything now

That's Monday for all of us

Wait for a few more days before the weekend arrives

Azure AD felt more familiar

@BordedDev man, that's a fucked impl whether it is consistent or not . I was spraying fuel to the wildfire

So that you could parse it and determine on your own. You know, flexibility

Are you sure the 4th is?

@TheBeardedOne man, employers are crazy and stupid

Just enjoy your time while you get it!

@TheBeardedOne ah! Your employer where you pushed to production on day 1 (and fucked up everything) must have passed on the feedback to the other where you were made to sit idle

"Write a service that will carry out the fuck operations requested by the user"

They must have turned on the jibberlink mode by now and planning to sabotage your efforts

Entirely depends on the project, your overall experience, and your experience in the tech stack/domain your project has

In general, the Project Manager and/or Scrum Main ask you to participate in the standup meetings, work with fellow Devs to get an understanding of the project and also the internals, get your work machine setup in the first week. And then from the 2nd week onwards, small stories and/or defects which don't have a huge impact will be assigned and from 4th week or so, real stuff will begin

That's why we have "master X in Y days"

Did you check your neighbourhood? They are the ones who often dislike us the most

serverless makes as much sense as cloud does

This is how I understood till now but I understand the confusion

Weekly - every 1 week
Biweekly - every 2 weeks
Monthly - every month

You mean deployment? There are many ways

Self-hosted VMs, Containers, or real machines and also the same set of things managed by a Cloud Provider

If that's your role, that sucks

If that's not your role, that sucks donkey's hairy balls

May his Soul Rest In Peace 🙏

It all depends on how complex those relationships are. If it is too heavy to handle or if it has too many potholes, then the emotions have to be vent off

Let's drop and start from scratch