Jake’s posterous: Just Do It: Move to Silicon Valley
I'm 99.9% sure I'm not moving. The above link is an interesting post though.
Probably the biggest thing I miss by staying were I'm at is finding people that you can really discuss entrepreneurial issues with. I've only found one regarding ProximityCast. He knows who he is and I appreciate him. Thank you!
Even moving to Silicon Valley doesn't guarantee success, it just increases its probability.
I'm facing other obstacles now that even a move to Silicon Valley probably wouldn't help me clear. If I was younger and my situation was different, I'd probably go for it and make the move, so I guess I'm on both sides of the above excerpt; ouch.
Such is Life
Ciao
Thursday, June 24, 2010
Wednesday, June 16, 2010
Facing some hard facts
1). I had big dreams for ProximityCast being a very useful Location Based Tool. I did get to build what I think was a nice prototype, but it didn't gain the traction I had hoped for with my bootstrapping attempt to move forward.
2). My current physical health does not allow me to put the time and effort in that ProximityCast deserves.
3). I'd consider selling it to someone that has the ability to cause it to meet its full potential, but I'm a lousy salesman and the thing from my reading that most purchasers of websites are looking for is "how much traction does the site have?" While I believe ProximityCast is a real diamond in the rough with a lot of potential, it really has no traction.
4). Working by myself things have moved too slow. There is a lot of competition with Location Based Sites. I would love to be a player and compete, but I have to face my health issues, my lack of resources, and my inability to generate traction.
So what am I going to do?
Originally ProximityCast was designed for using Latitude and Longitude only. I added GeoCoding as a courtesy to those not yet totally comfortable and familiar with latitude and Longitude. For this service I relied on Google's GeoCoding API Service. When Google upgraded their GeoCoding Service, it crashed ProximityCast. I could do the coding necessary to update to Google's new guidelines, then ProximityCast would work until Google changed their code again. Also if ProximityCast by some freak miracle did gain traction, Google only allows so many geocoding requests a day which would shut ProximityCast down once the limit was reached. So, I'm going to return ProximityCast back to where ONLY latitude and longitude can be used as a Cast Initiation Point. And I think I will provide a link to someone else's geocoding site like GPS Visualizer: Quick Geocoder so that those who want or need to use a street address can use the linked site to produce Latitude and Longitude for a street address and then copy and paste the produced coordinates into ProximityCast's "Cast Initiation Point".
That's the current game plan. Hopefully I can have ProximityCast back up and functional soon.
Good thing it is only a hobby and I took my wife's advice not to mortgage the house to have it built.
Ciao
2). My current physical health does not allow me to put the time and effort in that ProximityCast deserves.
3). I'd consider selling it to someone that has the ability to cause it to meet its full potential, but I'm a lousy salesman and the thing from my reading that most purchasers of websites are looking for is "how much traction does the site have?" While I believe ProximityCast is a real diamond in the rough with a lot of potential, it really has no traction.
4). Working by myself things have moved too slow. There is a lot of competition with Location Based Sites. I would love to be a player and compete, but I have to face my health issues, my lack of resources, and my inability to generate traction.
So what am I going to do?
Originally ProximityCast was designed for using Latitude and Longitude only. I added GeoCoding as a courtesy to those not yet totally comfortable and familiar with latitude and Longitude. For this service I relied on Google's GeoCoding API Service. When Google upgraded their GeoCoding Service, it crashed ProximityCast. I could do the coding necessary to update to Google's new guidelines, then ProximityCast would work until Google changed their code again. Also if ProximityCast by some freak miracle did gain traction, Google only allows so many geocoding requests a day which would shut ProximityCast down once the limit was reached. So, I'm going to return ProximityCast back to where ONLY latitude and longitude can be used as a Cast Initiation Point. And I think I will provide a link to someone else's geocoding site like GPS Visualizer: Quick Geocoder so that those who want or need to use a street address can use the linked site to produce Latitude and Longitude for a street address and then copy and paste the produced coordinates into ProximityCast's "Cast Initiation Point".
That's the current game plan. Hopefully I can have ProximityCast back up and functional soon.
Good thing it is only a hobby and I took my wife's advice not to mortgage the house to have it built.
Ciao
Subscribe to:
Posts (Atom)