Web developers code in a minimum of four languages (HTML, CSS, JavaScript, and a server-side language), must produce a working result in several different browser implementations, and may work on the top of a custom software stack that they don't control.How should a code review take these things into account?Should a code review include all parts of a front-end project (HTML and CSS aswell), or just focus on the logic?How should a code review handle workarounds for browser- or stack-specific problems?
Should a code review be different for front-end web developers?
web development;code reviews
Code reviews should cover all the code - that certainly includes the JavaScript and HTML and probably even the CSS.If you don't have another person proficient in all areas, break the review down into sections so that each can be viewed by another language expert. If you don't have another expert someone will have to become proficient enough to be able to ask sensible questions.If there are any workarounds in the code then these should be checked more thoroughly than the the rest of the code to ensure that they only fire when they should and don't have an adverse affect on the rest of the code.