WYSIWYG or Hand Code?
- Started
- Last post
- 72 Responses
- wo
Hand code all the way!
What is your preference?
- jevad0
Unfortunately the reality of budgets and deadlines means that more often that not it's DW over HC.
- wo0
True.
However I find that DW is so sloppy that I end up correcting most of the markup.
Not to mention, most Hand coders can propagate code fast enough that the time is not really an issue.
- angelus350
I agree.. With using editors to boost productivity any day. I do what's in the client's best interest.
"Mr. Client, we would prefer programming your entire 100 page website manually so that it adds 40 hours or so to your bill so that we can feel more justified that we "hand" coded your website. Is that okay?"
I don't think so. I don't believe that hand coding creates a "better" product, in fact, it's my opinion that is plain and simply is a waste of time when you can generate the same results with an editor and save time. I understand the necessity of touching up things here and there by using a plain text editor but to generate large amounts of redundent code by typing it over and over again is silly to me.
I'm sure someone will disagree with my opinion, but that's why it's MY opinion. I'll defend it until someone can change it.
- atle0
I aggree with you, angelus35. Handcoding is a waste of time, unless you type as fast as lightning.
I can't think of one good reason to code the entire web page "by hand". Only to fix some small issues here and there, that's enough. The rest I leave up to dreamweaver...
- wo0
Good points!
As long as the finished work is clean, the process really does not matter.
It all starts with a healthy work ethic, and a eye for detail.
- angelus350
... and if you can hand code a table with 10 rows and 10 columns faster than I can plop one into Dreamweaver then you're in the wrong industry, you should be making "Teach Yourself Typign" VCD's or something because you'd be typing like 600 WPM.
- Biofreak0
i start out with DW and then come in afterwards and clean up any extra code shit.
works for me. i say do both, but then again... whatever works for you.
- sp0
there is nothing wrong with using and editor, as long as you actually know how to hand code, and you know proper xhtml and design techniques.
the problem is when you get kiddies with DW who don't know the first thing about proper markup and call themselves a 'designer'.
carpenters know how to use a hammer, even though a nail gun is quicker.
as far as DW. when it begins outputting clean, compliant code then i will use it more.
until then, hand-coding is much more efficient.
and, for the record, again, tables aren't for layout.
this proves my point exactly. people rely on software more than on actually knowing what they're doing.
and, if your client has a choice between reaching a larger market for their site, i would think revenue and usage would outweigh and extra 20 or so hours to make sure the product you are producing is correct.
and who actually creates 100's of pages for a site individually? that is what backend programming is for.
learn php, perl or python.
- mitsu0
i have to admit, i've never actually seen or used a WYSIWYG editor.
- mrdobolina0
I think handcoding an entire site is kindof archaic, why re-invent the wheel?
- sp0
that analogy doesn't really relate, though?
when handcoding, you don't re-invent anything, you are using the same markup that an editor uses - except you, as the designer have greater control over it.
re-inventing the wheel would mean each of us wrote a new form of html everytime we built a site.
the use of proper xhtml when coupled with standards produces common code.
- Finnegan0
obviously, when you handcode, you don't type EVERYTHING OUT. There is a lot of copy and pasting going on...
- mrdobolina0
I dont have time, and honestly the client doesnt know the difference anyway. Testing makes sure that the site works in all browsers. just my opinion.
- mitsu0
"I think handcoding an entire site is kindof archaic, why re-invent the wheel?"
if you build web-based applications, you hand-code entire sites. especially when each application is totally unique from every other one you develop.
you'd hate windows programming. there isn't much hand holding there.
- Epictive0
I guarantee you I can make a 40 page website and go back in and fix the few mistakes Dreamweaver makes in a lot less time then it would take anyone to code the whole thing by hand.
-A
- sp0
why is there a misconception that handcoding means 'writing everything line by line'?
but, the question is would that site work across all platforms and all browsers?
bet not.
plus, to agree with the web services comment...when you get into real development - such as delphi, perl, python, even php you don't have wysiwyg editors.
- sp0
plus, if a designer can't work unless he has dreamweaver, then he doesn't have the skill to be doing it in the first place.
- Leifer0
Does it really fucking matter? Who gives a shit, as long as the job gets done. The clients don't have a clue about how a site is built and don't really care, as long as it works for them.
- wo0
Well put sp! The ability to use the software does not make a good designer.
It all starts on paper.
- unknown0
From the sites I see everyday you only need either method to
make a 100% table with alignment set to middle... and stick a flash movie in it.