This is what a lot of people miss about "AI will replace" programmers narrative.

When converting from a traditional process to an electronic one, half my job is twisting people's arms and playing mind reader trying to determine what they ACTUALLY do day-to-day instead of the hypothetical offical, documented, process.

Some of the workarounds that people do instead of updating the process are damn right unhinged.

▲

iugtmkbdfil834 2 hours ago | parent [-]

Without going into details, just recently I was able to get pretty decent business requirements from group manager, but it seems the only reason I was able to get somewhat decent idea of what they actually do, is because there was certain level of trust since we worked together previously so there was no need to bs one another. I openly stated what I thought is doable and he seemed to understand that I need to know actual use cases.

edit: Otoh, my boss is kinda giving up on automating another group's process, because he seems to be getting a lot of 'it depends' answers.

	▲	Someone1234 an hour ago \| parent [-]
		I will say, in a lot of cases, they aren't BS-ing/lying with intent. Just the general way their minds work seemingly isn't compatible with the very idea of laying out the process in its entirety (inc. the warts/hacks/workarounds). So what ultimately winds up happening is, you'll roll out the process according to the official way, and then it is drip-drip-drip of changes as you find out the real-world version.