![]() If you run into the same question, tell your interviewer that it’s a very broad concept. In this blogpost let us walk through six important concepts. Tip: Think out loud and if you don’t know something, at least say you’d like to learn it. It is the interviewee’s job to think out loud. ![]() The interviewer could not see this and actually, we can’t blame him for that. He didn’t see that the interviewee was trying to form a definition in his head of all the notions he had on this subject. Instead, he experienced an awkward moment of silence. What the interviewer expected to hear, was enthusiasm and eagerness to learn. And then in 2003, Eric Evans would not have needed 560 pages to write a book about it. If this was not the case, everyone would apply Domain-Driven Design flawlessly. It is difficult to answer that question with conviction. What would you have said? It’s hard to come up with a great definition of such a broad concept like Domain-Driven Design, isn’t it? Where do you even begin? Everything went rather well - until - unfortunately, the interviewer asked: “ What is Domain Driven Design?” During the interview, it felt like the interviewer shared the same ideas about software development and their product looked promising. The workday had come to an end and afterwards, I would attend an interview with a potential new client.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |