Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
gridspy
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
71 ms
·
751.
▲
by
gridspy
16y ago
It is unfortunate how much programming is replicated by hundreds of businesses, not shared and then thrown away 3-10 years later. Thank god for open source and the corresponding increase in code sharing.
752.
▲
by
gridspy
16y ago
Thats how you know that you are really needed.
753.
▲
by
gridspy
16y ago
Even a 1/10 hit rate is sufficient. You get 10 questions from the website, return the results and one of them leads to your spam comment being posted. You then repeat that process thousands of times.
754.
▲
by
gridspy
16y ago
Apparently it was hammering those pages, reloading multiple times.
755.
▲
by
gridspy
16y ago
Awesome questions! Will we set a minimum price threshold? Probably the major reason why we are considering selling the company at this point is because we are great at creating products but pretty poor at selling them. Stephen and I are b
756.
▲
We almost sold Gridspy
(blog.gridspy.co.nz)
6 points
by
gridspy
16y ago
|
3 comments
757.
▲
by
gridspy
16y ago
Sounds like you have a solid idea of where you are going. Well done. Doing the overtime to justify the new hire sounds like a good, low risk approach. Congrats on putting in the hard yards now to enjoy the growth soon. :) Don't do it too lo
758.
▲
by
gridspy
16y ago
Thank god. Finally a startup role model I really can aspire to. As father to two cute toddlers, This overtime ramen stuff is totally unobtainable. Thanks!
759.
▲
by
gridspy
16y ago
I got a sore right wrist during a Diablo 2 weekend, and it persisted for about 4 years. In the end I had to get a chair of the right height, a desk of the right height and a wrist rest. Take it seriously, the most important thing is an ergo
760.
▲
by
gridspy
16y ago
You only want to grow your business based on sustained clients with a lot of work. Do it very slowly and carefully, one of the most common ways for a business to fail is to get too big, too fast. Are you totally certain that you will have a
761.
▲
by
gridspy
16y ago
The trick is learning to say no. Once you have too much work you can pick your clients. Then you can do the most interesting work at the best rate for the most reliable clients.
762.
▲
by
gridspy
16y ago
I think it is much easier to do one job single-minded 80 hours a week than it is to do a 40hr and a 20hr job. When you have one job, you don't have to shift focus. It's great to hear that you are loving your job. When I have a decent progra
763.
▲
by
gridspy
16y ago
I managed to code about 20 hours a week for 6 months, while also working parttime. I blogged about it - http://blog.gridspy.co.nz/2010/02/part-time-entrepreneur.htm... - Great HN reaction here: http://news.ycombinator.com/item?id=1150061
764.
▲
by
gridspy
16y ago
It would be awesome if you could start from an existing web-page and work from there.
765.
▲
by
gridspy
16y ago
"Thinking about people directly" misses the benefit of an objective, well-defined third-party evaluation (i.e googlebot). If you think about "people" directly, I would imagine that those people, in your mind, all browse the web with your we
766.
▲
by
gridspy
16y ago
I don't commit anything with "Talked to client" "Wrote email" "Made blog entry" "Spent 60 minutes wasting time doing X" Also, the gaps in the timeline are just as telling. I always feel that little bit guilty returning from HN and seeing a
767.
▲
by
gridspy
16y ago
... And windows will be locked out of the datacenter until they create ARM-compatible versions of windows. Next thing you know Windows runs on both ARM and x86 (with x86 emulation for applications) and pushes x86 out of the commercial / dom
768.
▲
by
gridspy
16y ago
I imagine that a great number of people who hang out on HN feel the same way, myself included. It is great to see PG giving back to the community in such a sustainable, profitable way. He has created a product that entrepreneurs want.
769.
▲
by
gridspy
16y ago
This geo-engineering reminds me of this article on Darwin's terraforming of some volcanic islands. http://www.bbc.co.uk/news/science-environment-11137903 It is a really good idea. I wonder how well it would work.
770.
▲
by
gridspy
16y ago
Actually I think this just raises the bar - "Look, it only took 2 hours * 2 weeks to make something useful." Now everyone who has been slaving away for >24 months to make their own end-to-end power monitoring solution feels slightly lam
771.
▲
by
gridspy
16y ago
Possibly ruled out because : Access to the Prediction API is currently by invitation only. To request access and learn about the access process, sign up on our waitlist. http://code.google.com/apis/predict/docs/getting-started.htm...
772.
▲
by
gridspy
16y ago
Personally, I keep a timesheet on when I started and finished working on something, for instance Tue 19/10/2010 | 15:40:00 | 17:10:06 | 1:30:06 | Looking at admin interface for sensor daetails. Trying to fix None issue, seems to be related
773.
▲
by
gridspy
16y ago
I also loved the demo. I particularly liked the fresh database every time. I suggest that you run a background process that always ensures you have say 5 demo databases 'ready to go' so you can dish them out with no delay when a user clicks
774.
▲
by
gridspy
16y ago
I've added Gridspy (be fun to have a companion) http://desksnear.me/workplaces/87-gridspy-office
775.
▲
by
gridspy
16y ago
Useful to know. Thanks for the clarification.
776.
▲
by
gridspy
16y ago
Yes, I noticed this inactivity when I started working with Orbited. However, I always assumed you had reached a natural conclusion and stopped.
777.
▲
by
gridspy
16y ago
I think chargify could get a long way with a $5-10/mo 10 customers max plan. Just enough for developers to get their feet wet, with a nice paywall to keep out the non-serious.
778.
▲
by
gridspy
16y ago
As one of many users of Orbited. Thankyou. I wish I had time or money to contribute more. I'm hoping to donate to those projects (such as Django, Orbited, Twisted) that are essential Gridspy when we break even. If your curious, I have a sim
779.
▲
by
gridspy
16y ago
It seems more likely that the scientist re-writing the code would blame their own implementation or some part of the input data. A lot of time might be wasted going down that path too.
780.
▲
by
gridspy
16y ago
That is essentially what memcached should be doing now.
More ›