4 ms·
I appreciate that it's not exactly an earth-shattering problem, but "about 2 minutes" is a huge underestimation. I think "an hour or so" is still pretty optimis
by MicahWedemeyer 14y ago
I appreciate that it's not exactly an earth-shattering problem, but "about 2 minutes" is a huge underestimation. I think "an hour or so" is still pretty optimistic but at least possible. At that point the $10/mo for the Pro plan starts to look pretty competitive to writing your own.
- koide 14y agoHow come $10/mo is competitive with one hour ONCE?
- MicahWedemeyer 14y ago$150/hr for a good developer means this thing can run for a year and still be cheaper. Any improvements or enhancements they add you basically get for "free" over that time. Plus, I have yet to see the feature that requires coding once and never needs touching again. When I upgraded my app from Rails 2 to Rails 3, there were all sorts of 1-offs like this that I had to tweak and fiddle to get working right again. It takes well over an hour just to remember what you were thinking when you originally wrote it.
- meaty 14y agoNot if you design it well and comment it properly...
- meaty 14y agoVersus piss around with integration (any software engineer knows this is a time sink), breaking API changes, subscription management and billing, PATRIOT act data protection issues (what happens if PI data is in the request?) as we're in the UK, the risk that one day you disappear off the planet and finally actually throwing client confidential information by email. It actually took 47 minutes looking at my work log and if I remember a lot of that was making the error page look nice. It doesn't add up. sorry. In the build vs buy debate the time versus money theory rarely applies.