I one time notice that strict job descriptions are incredibly rare. I've only really seen them on factory floors. For laughs I ask a bunch of people in the same function to describe their job. Having asked this a few times it was fun to chat about how different their idea was from their colleagues. Some of them were surprisingly clueless. They thought their job was the stuff that currently consumed most of their time.
I think in programming we've learned (the hard way) that fuzzy input should be rejected. Stuff should do exactly what it says on the can. No mather how sophisticated, if a date object returns political opinion they are not parsed.
Perhaps one day we can do modular job descriptions or functional employment. Accurate task descriptions with actual specs. Well formed execution and response text. The most professional people I've worked with were already strict about what everyone's job was.
I think in programming we've learned (the hard way) that fuzzy input should be rejected. Stuff should do exactly what it says on the can. No mather how sophisticated, if a date object returns political opinion they are not parsed.
Perhaps one day we can do modular job descriptions or functional employment. Accurate task descriptions with actual specs. Well formed execution and response text. The most professional people I've worked with were already strict about what everyone's job was.