And the first key, critical moment, of Pre-Success, that no one will appreciate but you — is when you get 10 Unaffiliated, Paying Customers. I don’t mean friends of your investors, or your old co-workers or boss. I don’t even mean folks you hustled at some conference or meeting (well done, there, though. But that’s prospecting, which is something else.).
No, I mean 10 customers that Just Came in Through the Ether. A raw, unaffiliated, lead, that somehow found you on their own, kicked the tires, and now — is actually paying you. Every month.
Because here’s the thing. 10 customers may not seem like much. We called these guys “Beer Money” in the early days at EchoSign. 10 customers was $200 a month. Didn’t really pay the bills on 4 engineers and 3 other guys.
It took us more than a few months to get them. They were not just 10 but 300. We got them because we gave the product away for unlimited use and watched them use it. Once we were convinced that they were using it regularly and heavily, we started asking them to pay. And they did.
Getting unaffiliated customers (without prospecting) is not easy. But it is one of the best validations that your product can do something useful for someone.
Read this great post for more information on the importance of these 10.
XPrize is offering $15 million to build tablet apps that help kids teach themselves.
The goal is to help the 250 million school-age children in the world who can’t read or write. Contestants will build apps that kids can use on their own — because many of these kids don’t have access to the “unscalable” resources of teachers and schools.
The prize all ties into a philosophy known as self-organized learning — where kids learn autonomously by figuring out technology for themselves — that’s popular with the TED crowd. And of course, the other big idea is that contests are a peculiarly effective way of motivating people.
Keller said he anticipated that the winning app would use an artificial intelligence approach to figure out what an individual kid knows and does not know.
A few thoughts:
- The kids (targeted by this effort) cannot read or write. So you need to starting points may be different (speech, images).
- Kids should use these apps on their own. This means the apps need to be engaging and evoke curiosity constantly (the game community can contribute a lot).
- Since there will be no teachers involved, this would encourage peer based learning (and students playing the role as teachers)
- You cannot make any assumptions about what they know or what language they speak.
- The app is supposed to use AI approach. So you need to use AI to mimic a teacher or a self learner or a combination of both.
- To come up with a reasonable solution, you need to understand how kids learn. That, in itself, is a fascinating area of exploration.
- Kids don’t have access to “unscalable” resources (like teachers and schools). That points to tablets with long battery life, solar chargeable or something that requires hand cranked power. This is not actually the app quality but the need of the underlying platform. This also means, schools cannot the platform for distribution of apps or devices. Hopefully that will be a different challenge.
Rural India and countries in Asia and Africa will certainly benefit from the outcomes. No matter which app wins, we will get a lot of great ideas for self-organized learning. That is bound to change education as we know it.
Dr. Michael Stonebraker is a legend in the database world. He was the architect of Ingres, Postgres, Vertica, Illustra, Cohera, Streambase, H-Store and VoltDB. In this interview, he dives deep into database technologies. He talks about evolution of databases and certainly provokes you to think about the technology, the industry and how application needs are driving development in database technologies. A few nuggets from the interview.
- The traditional (row oriented) database technology is becoming obsolete
- The database market is at a tipping point
- DB market can be viewed as three segments – data warehouse market, OLTP market (both new and old) and a potpourri of other stuff
- The potpourri consists of various types of NOSQL, Graph databases, Column Stores, In Memory databases
- Databases currently spend 90% on overheads and only 10% on value producing work (big Gasp!)
- The overhead consists of – feeding buffer pool, mapping buffer pools to disk, lock management, logging, multi-threading
- There are ways to reduce these overheads using shared data structures, removing the record level locking, implementing multi-version concurrency, logging commands instead of data changes, using replication, getting rid of buffer pools, getting rid of expensive multi-threading, optimistic concurrency control etc.
- He talks about Distributed concurrency vs eventual consistency
- Most database books cover traditional database architectures. He advocates teaching – column stores, in memory databases, array databases and graph database architectures.
- He talks about embarrassingly parallel databases
- VoltDB evoloved from HStore prototype from MIT
- Applications are multiplayer games, high speed OLTP
- Some examples of NewSQL databases – Hana from SAP, Hekaton from Microsoft, SQLFire by VMWare, NeuroDB, NetSQL
- Most of the db systems written in the past year are open source
He takes a lot of digs at the closed source sales models. Deep dive into databases is an intoxicating topic and this was a great interview. Thanks to IEEE Software Engineering Radio folks for their indepth, high quality interview questions.
Here is a link to Dr Michael Stonebraker on Current Developments in Databases
- I was lucky to spend a lot of time in late 80s and early 90s reading Michael Stonebraker’s papers.
- I met him twice (once when I attended an RDB seminar at Palo Alto and once when we walked into Illustra offices (we built the ODBC driver for Illustra in my previous startup)
- I have been following him when I was working on complex event processing and looking at Telegraph (built on top of Postgres) and Streambase
- I lost touch even though I kept hearing about Vertica and other developments
- Michael Stonebraker inspires me and lots of other data geeks like me
Some great tips for startups on How To Survive Your First Year: Picking The Right Advisor
Prepare for your meetings preferably with a list of questions
First, find successful, independent advisors who have achieved what you want to. Whether they have bootstrapped a small business to profitability, scaled a business to serve customers around the world or have been acquired by a conglomerate, they are worth talking to. Instead of asking to ‘pick their brain’, prepare for your meetings like you would prepare for a presentation to potential investors. You will be surprised at the results – advisors are very helpful when you value their time, ask targeted questions and follow up with them.
You may not like what you hear (as advise). Don’t be defensive, listen to the point of view and try to understand the context in which the advice is given.
The ‘right’ advice will make you feel uncomfortable, move you to action and potentially, change the course of your life.
A great advisor helps you focus on understanding what matters most, even when in retrospect, it seems like very simple advice.
Think about the advice before you start acting on it. Understand that:
Not every piece of advice is a pearl of wisdom.
Predicting the future is hard and risky. Predicting the future in the computer industry is even harder and riskier due to dramatic changes in technology and limitless challenges to innovation. Only a small fraction of innovations truly disrupt the state of the art. Some are not practical or cost-effective, some are ahead of their time, and some simply do not have a market. There are numerous examples of superior technologies that were never adopted because others arrived on time or fared better n the market. Therefore this document is only an attempt to better understand where technologies are going. The book Innovators Dilemma and its sequels best describe the process of innovation and disruption.
Nine technical leaders of the IEEE Computer Society joined forces to write a technical report, entitled IEEE CS 2022, symbolically surveying 23 potential technologies that could change the landscape of computer science and industry by the year 2022. In particular, this report focuses on:
- Security cross-cutting issues
- The open intellectual property movement
- Massively online open courses
- Quantum computing
- Devices and nanotechnology
- 3D integrated circuits
- Universal memory
- Networking and inter-connectivity
- Software-defined networks
- High-performance computing (HPC)
- Cloud computing
- The Internet of Things
- Natural user interfaces
- 3D printing
- Big data and analytics
- Machine learning and intelligent systems
- Computer Vision and Pattern Recognition
- Life sciences
- Computational biology and bioinformatics
- Medical Robotics
You can find the comprehensive report here.
CB Insights recently parsed 101 post-mortem essays by startup founders to pinpoint the reasons they believe their company failed. On Thursday the company crunched the numbers to reveal that the number-one reason for failure, cited by 42% of polled startups, is the lack of a market need for their product.
The post Why startups fail is worth a read.
I came across this interesting thread – How did you get your first Python job?
Many ideas in this thread apply to finding other software jobs when you don’t have prior job experience to show. Some of the techniques (from this thread and others):
- Create useful apps (in your favorite language) and give them away.
- Work on open source projects. I know a few people who were hired by open source project teams.
- Create a YouTube video explaining how you developed this software and how it works.
- Tweet that you are interested in working on your favorite language – Python/Ruby/PHP/Java
- Try to find companies that use your favorite language and try to get internships while still in college.
- Try to get some part time assignments in your favorite language. You can do this even when you are in college.
- Participate in discussion forums and answer questions with code samples. These questions will give you problems to work on. Solving these problems help others and let you learn.
- Create a web presence (about.me is a great resource) and mention what you do. Keep them updated.
- Blog about your efforts. Include code snippets, pointers to your github pages. Tweet these blog posts (or make them your email signature)
Keep following this thread nd other similar threads on Quora for more ideas.