We build websites for people. Design and Dev. Mostly custom WordPress or other basic CMSs. I think people mostly pay us to solve their problems, not write code. I spend probably half the time on any given project talking and listening and figuring out how to best build something rather than actually building.

This is one of my oldest clients and this particular site has been a messy abortion since the get go. They recently moved over to Kentico which is the worst site to build anything in. And they wanted us to start development before all features were decided. This led to features like Parrallax and floating navigation being added after we had already QA'd the site once.

I don't typically work like this but he pays by the hour for the work and typically it's in and out stuff.

Html in itself isn't hard. Css in itself isn't hard. Doing it correctly and with foresight is hard, especially in a collaborative environment. Anyone can write a page of html easily and cleanly. No one can edit a page of html and add new feature and change existing features 10 times over 10 weeks with 3 other people doing the same thing and a client adding copy and not fall into the easy trap of adding to and overriding, rather than correctly implementing and going back to remember how stuff is laid out or addressed.