Gartner exclusion of elasticsearch and apache solr [closed] - elasticsearch

Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 6 years ago.
Improve this question
Why is that Gartner excludes Elasticsearch and Apache Solr in magic quadrant?
Aren't they enterprise search engines?

This post (opensource Versus Gartner Quadrant)) is very good and shows that the focus of Gartner is mainly on technologies coming out of big blues companies.
Magic quadrant is to help buy a solution, not to help buy a free solution.
Even if nosql is well used, robust, and huge today, Gartner Analyst - Donald-Feinberg does not think it is a quadrant choice for non webapps.
One exception is Redis.
I have participated in a Gartner event, and could say that it's mainly a vendor place. If you have big revenues, you can appear in the quadrant, otherwise forget it! Solr, ElasticSearch are great products even if not appearing in the Quadrant ! ;)

Related

Acceptable Ratio for Dev hours vs. Debugging hours? [closed]

Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
On a recent project, with roughly 6,000 hours of development, a little over 1,000 hours has gone towards "debugging"/"fixes"... does this sound to be acceptable, high or low??
I also understand that this is a rather dynamic question, while also requesting a rather simply answer, however, I'm just looking for a rough estimate/average based on past project experiences : )
Grateful for any and all input~!!
Pressman (2000) gives 30-40% as the total amount of project time for integration, testing an debugging, so your figures look a little low - but it depends on how you calculate it!

Find plagiarism in bulk articles [closed]

Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 9 years ago.
Improve this question
I have a 20,000 collection of master articles and I will get about 400,000 articles of one or two pages everyday. Now, I am trying to see if each one of this 400k articles are a copy or modified version of my collection of master articles (a threshold of above 60% plagiarism is fine with me)
What are the algorithms and technologies I should use to tackle the problem in a very efficient and timely manner.
Thanks
Fingerprint the articles (i.e. intelligently hash them based on the word frequency) and then look for statistical connection between the fingerprints. Then if there is a hunch on some of the data set, do a brute force search for matching strings on those.

What do these mysterious "Business Intelligence" software do anyway? [closed]

Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 12 years ago.
Improve this question
What do these mysterious "Business Intelligence" software do anyway ?
They're not really mysterious. BI or Business Intelligence software is just a term that groups software with a particular goal like OLAP and report generators. SSRS and Crystal Reports are some examples, among many others.
And the requisite wiki article...
In a nutshell, the goal of BI is: aggregating and presenting data to help executive decision making.
In a business, the role of a CEO is to stay on top of pretty much everything that is happening in a company. Some data you can get off of standardized reports, but sometimes you have an intuition, and need to actually dig through the data in arbitrary ways, while not really being able to learn SQL. BI is there to fill that role. It is there to do a better job then the CEO actually exporting a bunch of reports into excel, then massaging the data there.

Wizard pattern and other GUI patterns for infrequent, complicated task [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 9 years ago.
Improve this question
We are thinking of using a Wizard pattern to help a user complete a task.
The Wizard pattern seems to solve our problem. We are also interested in what human factors research might have to say about the basic problem of a non-expert user needing to accomplish an infrequent and complicated task-–-are there other, possibly better paradigms for doing this than a wizard?
You posted this question over two years ago and no one has offered a better interaction design pattern than the wizard.
That looks like an answer to me.

Looking for the article on appreciating software developers [closed]

Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
I've read a long time ago an article about why managers should appreciate the devs., and there was analogy drawn to the 7 samurais movie: that a company can't really offer much to an engineer, and that the engineer chooses to help the company -- like the samurais helped the villagers.
I thought that was on joelonsoftware.com, or codinghorror.com; but the search did not bring any result. Does it ring a bell to anyone? Anyone?
It's from Joel's book "Smart and Gets Things Done". Section is entitled "Treat Them Like Samurai".
A quote:
The village is your team. The samurai are the programmers who, you hope, will come solve your problems, bringing their talent and expertise in exchange for, maybe, a bowl of rice. You may be poor and hopeless, but you sure as heck know how to show some respect for the samurai who is going to save your behind.
Nothing about Samurai, but another 3 articles from Joel that relate to management/developer relations.
Field Guide to Developers
Development Abstraction Layer
Two Stories

Resources