The previous programmer left the site in a pretty unusable state, and it's hard for me to change anything. I am new to web design, so I don’t know if my skills are inconsistent with this kind of job or normal in the real industry to have websites like these
<head>
<script src=..>
document.all
<div>
<td>
T-SQL for xml auto
I am very confused about the state of the application itself. Should I learn about the intricacies that he developed and continue to work on it, or should I start rewriting everything? What I am very puzzled with is the lack of alternatives - and is this the usual way when web projects are processed in the real world or is this an exception?
Any suggestions, any pointers are welcome. Thanks
No, it is unacceptable in this industry that people continue to write code that is not supported.
- , . , -, ( 1 ).
, "", Ford-T , . , , , - , " ".
, , , , . (asp.net MVC) , .
( ), . , , , , . , , .
, . - ( ) - . , , , . - elses, , . , .
, , , , , , , , . , .
MVC3 XSLT / MVC. Razor XSLT- , .
- MVC ( XQuery Json, ) .
. .
, 6-7 . . , . . , ? , , "" " , ".
, , . , . , . , , , .
In addition, working on small parts will help you become better acquainted with the project and the needs of the business, so when you begin to rewrite, you will have a better perspective.