Comment by sho_hn
1 day ago
I've been having some similar thoughts lately about some application spaces being more harmful than others.
Coding, for example, seems somewhat benign, because code has to fulfil clear metrics: Either it works or it doesn't. Either it performs or it doesn't. As long as you are able to provide those metrics, you can to some extent treat it as a black box without losing much from a system view (lifecycle, long-term maintenance, keeping things working, broader qualified efficiency like re-use are of course other stories).
But on the other hand, delegating decision-making and thinking to models feels plain harmful to me. I have so many stories around me from office settings these days: "We have to pre-pone meeting XYZ, and we don't have enough time to prepare, so I made this AI analysis <power point deck>". This was then mis-prompted to fit a foregone conclusion, no one has time to do it or capacity to refute a 2000 word slop deck (except by slopping back), and crazy stuff becomes plan of record. This is really going to be a problem for organizations ...
> pre-pone
That is an Indian English word, most non Indian English speakers are not familiar with it. reschedule or bring forward would be more appropriate for a global audience.
I'm not Indian, and I see it used quite a bit by non-Indians :-)
I also don't think it's difficult to understand given the prevalence of "post-pone".