|
I think this job posting is running up against the difference between an employee and a partner. This isn't really unique to software, so I'll use the example of the dying American family farm. I grew up on a small farm, for most of the time it was owned by four men, all related by blood. They each individually took full responsibility for the business, and were never off the clock. If something needed doing -- planting a field, fixing a tractor, feeding livestock -- they got it done. They didn't quit working when the work was done, because the work was never done. They momentarily paused when they were too exhausted to continue. If there was an emergency at three AM -- livestock escaped, water main broken, building on fire -- they got out of bed and dealt with it without delay. They were partners. Occasionally, mostly during harvest, these farmers employed a few farm hands. These farm hands were contracted to do a specific job, like buck hay. They bucked hay for a certain number hours, and then went home. If something went wrong outside their purview, like a tractor breaking down, they informed one of the four farmers, who dealt with it. If there was a disaster at three AM, they were not summoned. They were employees. It would have been easy for these farmers to expect the farm hands to act like farmers. After all, the farmers worked all day and some nights, did anything that needed to be done. But the farmers were partners in their business, and the farm hands were employees. Expecting employees to behave like partners just makes you a bad boss. I think it is important for a small business, when growing, to remember the difference between partners and employees, and if you're hiring employees -- and not adding a partner -- to remember to treat them as employees, and not expect them to act like a partner in a business they have no interest in. |