So, you got this person’s resume and it isn’t bad. You interviewed them and they passed. However, you’re still not sure if they’re a good fit for the position. Before rushing into deciding to accept the candidate, you can always share a post-interview challenge.
I’ve never held any convictions. You know, these absolute certainties about life and things in general.
I am 99.99% sure about things, a lot of things! But never been “absolutely certain” about any of them.
And that made all the difference.
I’ll jump right into it: As an interviewer, ask all your questions strictly in the past tense. That’s simply all what’s there to it. Convert all your questions about technical knowledge, work experience, team work, attitude, even those IQ tests and hypothetical questions. Convert all of them into the past tense. Almost every single aspect of the interview should be in the past tense.
Think about this:
I started writing this post as a short guide to start a dialogue on volunteering culture and encourage people to explore and volunteer more. Eventually, it grew to become a long article depicting my life in the past ten years. It’s a bit too personal for me and what I intended my blog to be about, but I do trust you 🙂
I have been involved in volunteering activities since 2007 and I feel now is the time to share some experiences on why I did it and why it was so important to me that I’m still doing it till now.
Originally, volunteering was never my first choice. I can now say that It started by mistake. Continue reading
Although Hadoop might be the first thing to come in your mind when you think of processing large data sets, it is not always the best solution for your Big Data problems.
Hadoop might be the right choice for batch-processing big data, but when it comes to real-time data processing there are other architectures and tools to consider. This TechTalk shows the need behind solving real time data problems and explains the Lambda architecture, covering Druid as an example, and the simpler and less expensive “relay model”.
The talk is recorded in arabic as a JOSA TechTalk event on Jan 31st, 2015.
In this tutorial, we will create a plugin to take two parameters field name and a numeric factor and multiply them together. Then, we will use the output of this plugin as a custom scorer.
Each ElasticSearch Plugin should contain (at least) two classes: A factory class and a class to implement the functionality
Recently, we were discussing moving away from out good ol’ Solr-based search engine to a more distributed environment on top of ElasticSearch, first thing I did is listing all the features I was actively using in Solr and compare them one-to-one with their ElasticSearch counterparts. I’m listing my full comparison below.
Note that this list is not a comprehensive list of all Solr features, rather it’s a realistic view of a live Solr setup.