designer or tech wizard.
Out of context: Reply #16
- Started
- Last post
- 29 Responses
- ilmarine0
some things i'd like to add.
sometimes i am the coding part of the team and sometimes i'm the designing part of one. clients always want pages that look like print (for html) or pages that look like movies or actual programs (for flash). when a designer gives me his design for coding (html), and it contains all those wacky gradients, dropshadows, collapsible menus and whatnot, and this has already been approved by the client, you all would learn a lot of new and extremely explicit vocabulary if you were in my room. i mean, this isn't even actionscripting, it's simple html. and if you are a a webdesigner and don't know the simple rules of html compatibility and the works then are you really in the right job.
sometimes the most important aspect of getting a project is the fact that you proposed to do it with the smallest amount of time and for the smallest amount of money. if this 'smallness' comes out of the fact that you and the programmer or you as the programmer know how to convert even the geekiest design ideas into a working code, then this is only a good thing. but the cornerstone of this conversion is almost always the designer who knows what is possible from the programming aspect of the project even if it strains the limits of reality.
the breaking point : you have to know what is your actual limit. i know that if i was given a tight deadline i could build a custom content management system but i would hire someone to build a shopping cart with visa support or a system to convert information from a gprs to the web format. on the other hand, i also know that if the project required a custom cms i would get all the money.
in conclusion : knowing the tools of the trade (web building) is always a good thing. and the more you resemble a tech wizard, the better for you. of course you'd have to know which deadlines to set ;)