Firstly, markup is not code, if it's something like javascript or actual code, yeah I don't want them messing with it either. Markup however is quite literally

Firstly, markup is not code, if it's something like javascript or actual code, yeah I don't want them messing with it either. Markup however is quite literally exactly what they should be messing with. Secondly, they hand you a PSD with a design, that's tedious but easy enough. You can farm it out to someone who just does HTML/CSS and as another comment on this thread notes, that's a very high competition low margin market. I don't have a real problem with that, but the initial designs are never the finished product, there are iterations all the time, and the way I've seen them iterate is "oh we need an edit / delete / create button for this particular widget here, it needs to be aligned over here, no we need to move it six million times to decide, I don't know, use your intuition" like I should have some kind of intuition about design issues. They're designers, they handle appearance and aesthetics, I have no interest in it whatsoever, I don't want to iterate six million psd's into their html/css counterparts, and I sure as hell don't want to have to handhold the designer at the stage the implementation is already finished and they decide they want to modify pixel margins and such. The time spent handholding the designer on my current project vs actually doing my job and writing code is 70/30 in favour of handholding the designer. This is flat out ridiculous and I refuse to believe it ought to be par for the course because they couldn't be bothered to learn something as utterly basic as css and html. I didn't even want to learn them myself because I didn't see it as a coding issue but just ended up learning it by osmosis because it's not complex at all.