People talk about ideas as being worthless, etc. No, they're not. You can't get an oak tree with a mustard seed. But there's a big difference between even oak trees. Idea and execution are the same thing, just two ends of a continuous line.
The films La Femme Nikita and Point of No Return have nearly the exact same plot. The former is one of the greatest action films ever made; the latter is one of the worst.
That whole "build something people want" is only for people who want to make money. And honestly, if what you want is to make money, be a dentist.
People waant Facebook and Twitter and Farmville. But they need core technological innovation. They need better ways to work with data. You did the right thing, Andrew. It wasn't a waste of time. And I won't stop either, because the world has far too much of what it wants and far too little of what it needs.
I've compulsively weaned myself off the "solve a problem" mentality because it gets in the way of building truly innovative products, IMO.
And if all you want is to build something just for the fun of it, don't start a company. You'll lose money, time and nerves. There really are only to options when building something. Either build something people want (and if somebody built it before you did, build a better version - see: Altavista, Yahoo and others vs. Google) or build something, and then make people want it (see: iPad). But don't start a company to build something just so you can satisfy your professional curiosity. That's what side projects are for.
I think I understand your point. AltaVista is nowhere and google is.....
I am also a fan of the original (the french version) Nikita - great shootouts.
I'd suggest that if this product wasn't a success you either didn't understand how end-users currently use spreadsheets as a 'poor man's database' or the marketing let you down.
I still very much like the idea of being able to build lists from web based API's with only a handful of lines of Javascript.
You built something that was supposed to be an Excel clone, but you didn't implement the editing functionality?
Isn't that pretty much 99% of the point of Excel? I mean yes, people do use Excel to share data as well, but most scenarios involving shared Excel spreadsheets involve multiple people editing the same spreadsheet, and then generating reports out of it.
That's where the pain is, and that is what I had assumed you were aiming at. If not, then what did your system do exactly?
(Also, build lists from web based API's with only a handful of lines of Javascript isn't Excel, either)
Edit: I see further down you noted that your system was desktop based software. A web-based Excel/database hybrid isn't a big requirement list, but I'm not convinced you are covering a whole lot of it..
We built it a a desktop application too which I think was a mistake. Getting people to download and install things is hard.
As an analyst/controller I work with Excel every day, let me know if you want to know about issues with Excel, there are tons of problems to solve.
Our core business case is to address the problems of distributed business processes implemented in spreadsheets. We want to continue to offer the flexibility of the spreadsheet paradigm whilst addressing the most weaknesses of the current paradigm.
This short video (when its finished) will be the centerpiece of the new release: http://vimeo.com/25937882
Point is, there must be a market out there for some functionalities that Excel does not have, it also should not be that difficult to build such a solution (call it a hunch, but I think with nosql that should be really easy to do). But the whole thing requires stopping thinking logically (of course excel makes no sense) and start thinking business(ly) (how do I get people to understand and use my solution).
I think it's only when you make a complete rewrite from the bottom up in another paradigm that you can extend the power while retaining the usefulness.
True, but again, look at the users. People with very poor IT knowledge and very scared of change. Any new solution pointing at this market will have to:1) be as easy to use as excel; 2) much better than excel (why change otherwise?).
I think that being better than excel overall is impossible, but looking into specific businesses and uses it should be.
Personally, I have been giving it a lot of thought and I can't come up with a complete better solution. But other (Palo, Hyperion) seems to make money on solutions that do not change the excel paradigma.
We disagree.
The base of users with knowledge of Excel is very large. Most organizations have a built in base of knowledge of Excel. Why swim upstream and go against that. Try to make Excel work in that environment.
Take a look at www.excelcube.com. It may be helpful.
Have you looked at google fusion table and google refine? These are powerful tools in same space for non-enterprise applications.
Most/many hedge funds manage billions of dollars on the back of very complicated excel spreadsheets, mostly because the "talent" understand excel and can bend it to their needs.
But auditing these things is an utter nightmare, which version was used to lose a million here or a million there. Is it still on bobs laptop? How can I reuse code?
By providing a excel like front end and a centralised, versionable, auditable back end, they got a lot of interest going.
The space is still very wide afaik, but I have been out of the City for some years now.
(In fact you could take a similar approach to any CFO's office)
Jane Street is very unusual in having such an advanced technology management set up (IIRR OCaml, directors review the code before production etc etc)
It might be that the lesson pertains here, too.
I only ever played with it, but it seemed like a great piece of work, and was all coded in Smalltalk (Seaside).
I will be presenting this at the Seedcamp in London later in the year. I am really exciting about the project, so I wont be giving anything away here! Unless PG wants to get in touch directly...
They're really saying, "I love Excel".
Don't forget it's only a tip of iceberg. Users will complain more about missing features after you built something users have cared about.
http://www.youtube.com/watch?v=yuSDU0JiI2c
Stupid name - NeoGopher.
The basic idea was that with 10 to 15 lines of Javascript you could bring back results from any XML or JSON web based API and display it as a list. You could then link any row or cell to any other list.
In a way it was like a reinvention of the old "gopher" protocol which allowed the user to navigate from one data list to another.
The site is gone now.
The question is though, what problem does it solve? It was very hard to explain to people why they would need it or care about it.
Spent a year developing it and spent alot of money on it. For nothing in the end. A very cool technology and I still like it alot.
Lesson: build something people want, or that solves a real problem. Don't build a solution looking for a problem.