3 ms·
A clear difference between a carpenter and a programmer is the liability inherent in the work. A carpenter can't just produce a minimum viable product that just
by belorn 12y ago
A clear difference between a carpenter and a programmer is the liability inherent in the work. A carpenter can't just produce a minimum viable product that just happens to break down as soon as a bird land on it, or leaks water as if it was constructed like a sieve. Hiring a carpenter is a comparable safe thing to do, as the worst thing a lawful carpenter can do is overcharge his clients/employer.
A programmer on other hand is not liable for anything. If it breaks or leaks information at the easiest provocation, then its not the programmer who might loose money. All risk is put on the employer or customer, and as such, it becomes their responsibility to identify and test a programmer before spending money. As a result, you get questions which are mostly irrelevant to the task at hand, but which might sorts out high risk vs low risk.
If I hired a carpenter under those conditions, I would ask what brand of paint they buy. If its an expensive one, it might hint towards a professional.
- sopooneo 12y agoYour logic makes sense, but it seems like every high school I've ever been in or heard about that had just recently been built leaked rain like a sieve.
- Spooky23 12y agoThat's because of flawed design usually. Architects cook up these lovely stylish renderings that the school boards find inspiring (particularly since it isn't their cash), which often involve flat or complex roofs. Fast forward to the post-construction era, and that inspiring building now has 10 inches of water or ice on the roof. Water being water, it eventually gets in, usually around flashing.
- icebraining 12y agoSo if a salaried carpenter does a shoddy work, does the employer get reimbursed? I find that very hard to believe.