I work at a startup and when I started the job, my boss was concerned with the rate of progress. I'm the sole developer at the company and the only technical pe

I work at a startup and when I started the job, my boss was concerned with the rate of progress. I'm the sole developer at the company and the only technical person besides the CTO. My boss said that normally when he asks someone to dig a hole for him, he can see visible progress being made. He felt like that wasn't the case with my work. We took a service-oriented approach to building the software, so in the early days, my boss thought that no progress was being made because he couldn't "see" anything. He also wanted me to work between 40 and 60 hours a week, which I was doing until my overtime pay was taken away for "equity." I've gone off on a bit of a tangent here, but I'm of the opinion that non-technical founders should learn a thing or two about architecture and the current state of web/mobile development before hiring resources. Otherwise, we end up with silly analogies where people think programming is like typing up a short story in MS Word.