HarrietJones

12 ms·

91.
by HarrietJones 14y ago
Good article, though I don't agree with it all. It is harder to grow software than it is to initially build it. Preconceptions bite you on the ass, data structures don't allow for new features, side effects multiply. You don't need to learn
92.
by HarrietJones 14y ago
Though point 4 should be rewritten as "If you find yourself writing the same thing twice, DO be lazy and carry on, put the code in a single place and call it from where you need it."
93.
by HarrietJones 14y ago
Advice: Make something for yourself first. If you've enough space, you can invite others afterwards. But coworking space is like Open Source software. It's fun doing it for other people, but it'll be the most rewarding when you're doing it
94.
by HarrietJones 14y ago
My rule of thumb: If the API contains a version number it its URL, then the developers have considered how people will use their service after they add new features, and it's probably good to use. e.g. http://myservice.com/v1/doathing U
95.
by HarrietJones 14y ago
I'll watch this. As long as the main protaganist is some kind of Hero.
96.
by HarrietJones 14y ago
I created a simple website alert-if-down service ( http://pingdipong.com ), and it's just started paying for its own hosting. I wouldn't call it profitable. It's not paying anybodies wage. It's not covering the cost of advertising. It's be
97.
by HarrietJones 14y ago
What I should have done is posted the fact that I'm doing the same to Hacker News. I'm guessing that if his blog gets enough traction, he'll succeed. Not because the product is great, but because this "10k GBP - can I make money" sideprojec
98.
by HarrietJones 14y ago
I'm sort of doing this. I'm 4 months in, I've had one scrapped project, one failed project and one project which isn't really taking off. I'll be watching this with interest.
99.
by HarrietJones 14y ago
It is a great idea. I shall be copying it for my own web monitoring site.
100.
by HarrietJones 15y ago
Interesting that you say what's wrong with the code, but don't actually say how it should be done right.