4 ms·
> So, why don’t just go and ask people what is their problem, and how you could solve it? [...] Elasticsearch. It was born when Shay Banon tried to build a too
by michaelt 6y ago
> So, why don’t just go and ask people what is their problem, and how you could solve it? [...] Elasticsearch. It was born when Shay Banon tried to build a tool to search his wife’s cooking recipes.
It's a cute anecdote, but I honestly have no idea how you would get from "my wife wants to organise her recipes" to "my wife wants a distributed multi-tenant schema-free json document full text search engine"
- j45 6y agoLess about cute, and more about being able to understand the complexity that underpins seemingly simple problems. Solving problems that people have that they're willing to solve badly enough to pay for is a great spot for first time entrepreneurs to begin. That early on, the idea doesn't matter as much as the frameworks and skills you learn about how to support any idea to reality.
- heavenlyblue 6y agoIt’s not about cute but about a person who is a software engineer and who’s privileged enough to afford not to have a job for enough time to only do open-source for a while.
- j45 6y agoI haven't worked on open source while unemployed myself but I might have missed something above in the article.
- eschulz 6y agoYou're right, the anecdote does not give enough guidance on how to create a successful startup that provides a solution for the users. Even though people face certain problems and challenges on a daily basis, they often don't fully understand these problems and have not been able to envision a solution. “If I had asked people what they wanted, they would have said faster horses.” -Henry Ford
- em-bee 6y agothis quote keeps getting used as an example of not talking to users, but i think the interpretation is wrong. henry ford seemed to know that people wanted faster transportation. how did he know that? the thing is that you are not asking people how they would solve their problems, but instead ask them what the actual problem is. instead of asking: what would make your work easier? -> faster horses. ask: what is the biggest problem in your work? -> horses are to slow. once you understand the actual problem, you may come up with a solution that is beyond what people can imagine. if people didn't want faster transportation, cars may not have taken off. but i think that kind of problem was pretty obvious, so there wasn't a big need to ask.
- eschulz 6y agoYou're right. The quote should not discourage talking to users, but it should encourage true communication about the challenges that users face. In agreement with you, an important point is that most all of us are unable to articulate the specific problems we face everyday, and therefore we absolutely can't just tell some smart industrialist or software engineer how they can apply their skills to solve our problems.
- wallflower 6y ago> JAXenter: You started Compass, your first Lucene-based technology, in 2004. Do you remember how and why you became interested in Lucene in the first place? > Shay Banon: Reminiscing on Compass birth always puts a smile on my face. Compass, and my involvement with Lucene, started by chance. At the time, I was a newlywed that just moved to London to support my wife with her dream of becoming a chef. I was unemployed, and desperately in need of a job, so I decided to play around with “new age” technologies in order to get my skills more uptodate. Playing around with new technologies only works when you are actually trying to build something, so I decided to build an app that my wife could use to capture all the cooking knowledge she was gathering during her chef lessons. > I picked many different technologies for this cooking app, but at the core of it, in my mind, was a single search box where the cooking knowledge experience would start a single box where typing a concept, a thought, or an ingredient would start the path towards exploring what was possible. > This quickly led me to Lucene, which was the defacto search library available for Java at the time. I got immersed in it, and Compass was born out of the effort of trying to simplify using Lucene in your typical Java applications (conceptually, it simply started as a “Hibernate” (Java ORM library) for Lucene). > I got completely hooked with the project, and was working on it more than the cooking app itself, up to a point where it was taking most of my time. I decided to open source it a few months afterwards, and it immediately took off. Compass basically allowed users to easily map their domain model (the code that maps app/business concepts in a typical program) to Lucene, easily index them, and then easily search them. > That freedom caused people to start to use Compass, and Lucene, in situations that were wonderfully unexpected. Imagine already having the model of a Trade in your financial app, one could easily index that Trade using Compass into Lucene, and then search for it. The freedom of searching across any aspect of a Trade allowed users to convey this freedom to their users, which proved to be an extremely powerful concept. > Effectively, this allowed me to be in the front seat of talking and working with actual users that were discovering, as was I, the amazing power that search can have when it comes to delivering business value to their users. Oh, and btw, my wife is still waiting for that cooking app. Now, 10 years later, it is the basis of Elasticsearch. https://jaxenter.com/elasticsearch-founder-interview-112677.html https://jaxenter.com/elasticsearch-founder-interview-112677....
- RcouF1uZ4gsC 6y agoMaybe his wife is super technical and actually said, "I want a distributed multi-tenant schema-free json document full text search engine so I can more easily organize my recipes"