The '|' on the subhead needs more spacing b/w the two phrases, consider using some other form of visual separation.
The big text fields with small font look weird (& small dropdowns, uneven design).
The labels are also misaligned.
Consider using something like: http://www.blueprintcss.org/
As mentioned before, needs serious design love but while doing so seriously consider your target marget and design appropriately. Coders generally don't like prose, keep text brief.
Justified text looks weird, and I'm sure I'm not the only programmer that despises being called a coder. I am not a coder and I don't write codes. I'm a computer programmer or software engineer.
I think it only looks weird here because the text looks dense and unapproachable. Too much text, too little visual breaks. Justification is only accentuating that problem.
Personally, I find well-hyphenated justified text easier to read than ragged-right text. It is bothersome when a justification algorithm puts too much space between too few words, but that's what hyphenation is for. To the dyslexics and others who are distracted by the rivers of whitespace that run through justified text, are you never bothered by rivers of whitespace in ragged-right text?
Although, strictly speaking, "I write codes" may not be wrong, since, at root, it refers to "I write programming codes", i.e. the codes used to convert human-language statements of intent into stuff that computers can "understand" and execute. But my reference was more to the current usage, which is "my code", not "my codes", for "my programs" or "programs written by me".
I think you're referring to commonly accepted _usage_, not "correctness", when you say "code is always singular". The phrase "I write codes" (as in, "I write programming codes for a living)" is definitely okay/correct, IMO (for the reason given in my previous comment above) - though no experienced programmer with a good command of English would use it in normal conversation, because it's not colloquial. I was referring more to a situation like if he/she is talking to a layman and happens to use such a phrase, to describe his/her work. Remember, I said "strictly speaking" - and strictly speaking (in other words, pedantically), I don't think there is anything wrong with that statement.
But overall, I get your point. For a similar yet contrasting example, consider this real statement of an ex-boss of mine: "I can tell you what code to write, but I can't write _a code_!" which was both BS and grammatically wrong, of course :-) He did not stay my boss for long ...
The '|' on the subhead needs more spacing b/w the two phrases, consider using some other form of visual separation.
The big text fields with small font look weird (& small dropdowns, uneven design). The labels are also misaligned.
Consider using something like: http://www.blueprintcss.org/ As mentioned before, needs serious design love but while doing so seriously consider your target marget and design appropriately. Coders generally don't like prose, keep text brief.