I've had the fortune of knowing a lot of professional and casual coders over the years--(well, "fortune" if you call banging your head against the table at dinner a delight, while computer scientists and engineers trade woeful stories about that unintelligible bit of code their group member turned in that week) and the one thing that never ceases to amaze me is how common the complaint of poorly documented code crops up.
Designers new to the world of web development have probably noticed by now that serious coders, like computer scientists or electrical and computer engineers detest having their work in C++ and Python compared to scripting and styling languages like HTML and CSS, but the truth is that there are a few common lessons that designers should learn from these more experienced coders that you won't get monkeying around with scripts and bits of code from common online source guides like W3Schools.
That said, let's talk about properly documenting your code.
Designers new to the world of web development have probably noticed by now that serious coders, like computer scientists or electrical and computer engineers detest having their work in C++ and Python compared to scripting and styling languages like HTML and CSS, but the truth is that there are a few common lessons that designers should learn from these more experienced coders that you won't get monkeying around with scripts and bits of code from common online source guides like W3Schools.
That said, let's talk about properly documenting your code.
