Sorry, that first paragraph should read:
----------------------------

A really basic design that passes is not what most people really want.
As for what we do want, the reply question would be, how do I make a
site that is usable and beautiful?


On Feb 4, 2:42 pm, Adam Meehan <adam.mee...@gmail.com> wrote:
> Its a really basic design that passes is not what most people really.
> As for what we do want
> the reply question is but its nearly impossible to answer. The reply
> question would be, how
> do I make a site that is usable and beautiful?
>
> The problem is design instinct. Some people have it, some don't. Many
> developers don't, myself
> included, and they want to learn to *emulate* it. As I don't think its
> possible to learn instinct.
> That said, I imagine their are many good designers out there who don't
> have classical design
> instinct, but learned and trained off others work. Ultimately there is
> a scale of design ability
> and we all for along it somewhere.
>
> Its difficult to nominate a specific design problem worth work-
> shopping. If you can find a specific
> problem you want to solve then its likely technical and hence just
> needs technical instruction,
> different from design.
>
> I think those in need of help would like to just observe a good
> designer doin their thang, and we
> can extract the techniques and patterns and add them to our pallete of
> learned design tips. Then
> later apply with variation to our own problems. Like a makeover in
> QEFTSG, we want to watch
> rather than dobbing ourselves in for the makeover.
>
> Its also not to say we don't know when we see something we like, but I
> think most of us would like to
> stop drawing so heavily on existing design and make sites which are
> more individual and appropriate
> for the problem being solved by the site we are making.
>
> The argument against all this is, let designers design and coders
> code. But the stubborn polymath
> (or desire to be one) in most geeks refuses to give up. Plus tips are
> useful for low budget projects
> or solo developers not looking to spend on designers.
>
> And no I won't be submitting my site for a makeover because I am a
> coward.
>
> Adam
>
> On Feb 3, 11:49 pm, Brodaigh <broda...@gmail.com> wrote:
>
> > To quote someone from the meta-discussion, "I would be interested in seeing
> > a "design eye for the developer guy" type of session."
>
> > I'm just wondering.. I'm interested in- what are the main design problems
> > non-designy people are experiencing?
>
> > I myself am a designy-type, which gives me my own set of problems. One of
> > which is, I'm trying really hard to improve, everything, all the time! Plus
> > a few little quirky,* verging on a mental disorder *things.
>
> > Like, if CSS totally gripes you?? I want to know why. This is your
> > opportunity to get it off your chest and go vent! Sort of a bitch-session if
> > you will.
> > Open the flood gates!
>
> > What's stopping you from making a really basic design that also passes' for
> > your app?
>
> > -Brodaigh
>
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby 
or Rails Oceania" group.
To post to this group, send email to rails-oceania@googlegroups.com
To unsubscribe from this group, send email to 
rails-oceania+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/rails-oceania?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to