On Tue, Mar 24, 2009 at 10:49 PM, Greg D. [email protected] wrote:
Convince them of what? That pencil and paper or a simple wireframe
app isn’t good enough?
It may be in first world countries, but not exactly in countries that
have experienced 30 years of civil war.
It’s been my experience clients want to see your past work and talk to
your references. They care not for how fast you can scaffold an app
together at Starbucks.
Well, it has been my experience that in first world countries that
seems to be the case. Not quite in third world countries. There are
quite a lot of cases where the client does not care to know about what
you have done before, but about what you are going to develop for
them. I have had several cases where they were not that impressed with
what we had done before, but when we showed them a quick prototype
with a quick touch of graphical user interface, then they were
actually all excited about it. It’s funny, but it does happen. We just
have to learn to adapt.
Yup. Assuming everyone uses the same thing is an obvious mistake to
anyone giving it more than a moment’s thought.
I can only imagine how many times “Works on MySQL, ship it!” has
probably been declared at 37signals.
If you think about it, MySQL is a sort of de facto standard for web
applications.
All the best,
Fidel.
On Tue, Mar 24, 2009 at 7:02 PM, Marnen Laibow-Koser
[email protected] wrote:
Huh? Have you actually created more than one Rails app?
Heh… Yeah… I’ve created way more than one Rails app.
Wasn’t it a
pain to put in the same stuff again each time?
Copying some files from one Rails app to another is not difficult.
Why 3 times? Just upgrade as necessary when you need to – i.e., the
next time you use the template.
It’s just a number I threw out there. But yeah, it might very well be
4 or 5 times, especially now that I think about that one Rails app I
upgraded from 1.0 to 2.2 last month.
–
Greg D.
http://destiney.com/
Greg D. wrote:
[…]
Rails templates seems a fairly useless feature to me personally. I
don’t write very many throw away apps
I haven’t played with templates much yet, but my impression is that
they’re not only about throwaway apps. I have about 6 plugins and gems
that I throw into almost every app I create, and I’d love to have an
easy command to do that for me. I gather I’m not alone in this; witness
the existence of things like Blank and Bort.
I agree with you that throwaway apps are a waste of time – if I want to
impress a client, I’ll put together a prototype using the same
technology I plan to use on the final product. Anything else is
wasteful and feels dishonest to me.
so when I weigh the time it
takes me to configure a new Rails app versus the time it’d take me to
paste all those files into a template… I really feel like I’d come
out ahead by just not doing it.
Huh? Have you actually created more than one Rails app? Wasn’t it a
pain to put in the same stuff again each time? Or did you create your
own app template or fork a repo?
And do you really expect anyone to think the Rails template API will
remain unchanged for more than the current Rails release?
No, and that’s a good point. But it doesn’t make templates useless.
Even if I
did make a template I bet I’d have to upgrade it three times before
the next time I’d go to use it.
Why 3 times? Just upgrade as necessary when you need to – i.e., the
next time you use the template.
–
Greg D.
http://destiney.com/
Best,
Marnen Laibow-Koser
[email protected]
http://www.marnen.org