WTLDBD&D ?
Out of context: Reply #4
- Started
- Last post
- 6 Responses
- UndoUndo0
I dont think you need to understand the server side of things apart from the point of view of designing for every scenario that the developer will program for. a login system is a good example, their is the login page, the error nsg when the details are incorrect, the user isnt regd, the acc hasnt been validated, the reminder form etc.
being a designer/developer and also working with other designers this is often overlooked and I ususally use the style to get the job done and then confirm it with the designer.
other common mistakes are when the designer uses an id for a style on an element that will be repeated (id's should only be used once, classes can be used more than once), its qute frustrating when you have to go through and find all instances of an id and change them to classes, then re test in the browser etc.
above all i would say you pay for what you get and the more experience the better the developer (in theory) Ive seen alot of developers work where there is absolutely no consideration for the misuse of the system by hackers to gain access and its totally open if the (wrong) person came along. if he's been working on billing systems then he should know how to sanistise his data.
good luck
sorry for the long post!