4 ms·
Why assume that both positions are mutually exclusive? There's nothing wrong hiring a mediocre developer (or anything) so long as they aren't tasked with doing
by sbuttgereit 9y ago
Why assume that both positions are mutually exclusive?
There's nothing wrong hiring a mediocre developer (or anything) so long as they aren't tasked with doing something that needs more skill is fine: I've done it myself in the past and will do so in the future. When that something escalates into something that does require more, it can be sad or disappointing to see what the less skilled or less caring person did. Conversely, it can be wonderful to see someone that is a true accomplished craftsman at work, even on banal projects and they should be lauded... if that is snobbish, fine, count me in.
Finally here's a clown that is also a talented musician: https://www.youtube.com/watch?v=O3O1XojnTag https://www.youtube.com/watch?v=O3O1XojnTag
- blowski 9y agoWho decides how much skill a given task needs?
- sbuttgereit 9y agoAt the end of the day whoever it is that is deciding that there is need they will have filled. This can be different from the person that will be the intended beneficiary of the task, or different from the person that will execute or oversee the execution of the task. Of course, this means the adjudication may happen after the fact, but it doesn't change who was initiating the action to make something "a task" and whether or not that person is satisfied with the outcome. In the professional world, I call this "the person signing my check". (Edit: ok, ok, there can be superseding criteria as well... mostly in areas where life/safety issues are at play).