Non-functional requirement

Yeah, the blueprint for surviving the forty-five-minute interview.

Second, we will dive into the brutal art of gathering non-functional requirements or NFRs.

Which is where most people fail.

Explicitly where the text states most senior candidates outright fail.

Defining the primary schemas, identifying the core entities, establishing relationships.

But the critical evaluation point here is the rationale.

You must defend your database choice against the NFRs you gathered in step one.

And it goes way beyond just the generic SQL versus NoSQL debate.

It's gotta, you know, calculate financial matters, you know, for, for someone or manage financial matters.

But, like, I call them the NFRs, the things that software needs to do no matter if the software is accounting software or, you know, management software for, for fantasy football.

Um-

Yeah

When you instead have this AI super intelligence, so to speak, that is just, like, moving at, like, light speed, right, through your application.

It, it...

We're in this kinda middle space right now in the evolution of these technologies where we've designed a lot of these programs to support and achieve their NFRs with, uh, human users, using them in human ways-

Yeah