After successfully passing the Case Interview I recently wrote about, I then went through the next and much more difficult step, a Role Play interview, something I never faced before and I actually failed. I won’t bother you once again about the importance of failing and how valuable is to fail and learn from our mistakes, but I can obviously not advice you neither on how to successfully pass a Role Play interview, because I effectively didn’t. However, often a negative experience can teach us more than a positive one, because failure pushes you to think it over and over, to repeat each and every scene of the interview in your mind and try to understand where and when did you make the fatal mistake or the one which in the end decided the verdict. That’s why I want to share my experience here, hopefully worth to read, and I therefore have few tips to write down.
Let’s firstly and quickly define what a Role Play Interview is. A Role Play Interview is a simulated working scenario which will require the candidate to solve some awkward situation in a short time frame (10-15 minutes) applying his/her problem solving, communication, management skills. Actors are often hired to play such a scenario and you would be asked to perform right in front of your interviewers, there ready to observe, note, evaluate. It isn’t anything you would feel comfortable with indeed, and I personally wouldn’t choose candidates based on their acting abilities, but it definitely tests pressure resistance, experience, reasoning, creativity.
Among the diversity of possible questions or often endless hiring steps a candidate could go through, the Case interview is probably the most annoying one or at least it could seem so if not well prepared: an odd and unrelated question that needs a reasonably quick answer while trying to show interest yet handling pressure and stress, that is, almost a nightmare. Interviewers would always justify Case interviews in the name of problem solving skills, thinking patterns, creativity and self-control, but I would personally never prompt such a type of questions, I would rather prefer to find some vacancy related scenario, even pushing it to a certain limit, closer to the Case interview style, but still reasonably consistent with expected competencies and expectations. Mount Fuji questions (another name for the same category) are normally reserved for leadership or management positions, but they could also be used when hiring developers and you can’t do much against them, if you are on the other side of the desk you simply have to solve it, somehow.
Are you developing your project using the NetBeans Platform & Ant? Are you willing to use AspectJ to use AOP? You do not know how to integrate the AspectJ compiler into the builds of NetBeans?
If your answer is yes, this post is for you.
I decided to write this technical post because I have been struggling some time before to find this solution, and so I would like to share it.
Tell the story
Sometime ago I had to face the integration of AspectJ into a Rich Client Application implemented with NetBeans Platform source code. The first decision taken it was to integrate AspectJ at the level of the compilation, so to create already compiled source code that contains the AOP.
The main question was so, how to integrate this post compilation with the netbeans ant compilation files.
We are a bit busy recently and that’s why the blog hasn’t seen any article during this month so far. Running after private priorities and professional projects, and then tasks, appointments, social life and job ambitions, yet unexpected propositions and scheduled plans, as part of our daily life, often a daily fight indeed. And it’s not easy to refactor our attitudes and behaviours towards deadlines and related pressure. Thinking of such a common every day plot, I enjoyed drawing the scene below in my (never enough) free time. Just try not to lose the focus on what might be left into the darkness, forgotten inclinations and key wishes.
During the last decade the term SOA has become a fuzzy over-used word. Lot of vendors have put the “SOA compatible” certificate on their products completely forgetting that SOA does not refer to a particular product or technology, but at the way you use those technology to achieve certain goals.
So it often happens that talking with Software Architects they are SOA experts simply because they used a lot of web services in their application. But let’s say clearly that only using web services does not make us an SOA expert!
A deeper look in the context
We must admit that the argument is hot; there are plenty of books, candidate official definitions and methodologies for developing an SOA. In this post I refer to the contribution that Thomas Erl has given to this subject, since I have been studying for some certifications using his books and courses.
I would start by introducing few important concepts:
- Web Services
- SOAP & WSDL