2月份热点城市商品房销售价格延续总体稳定态势
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| 6 hours ago | comment | added | mclayton | @StephanKolassa - rather than create a ticket for the work yourself, you can go a step further and ask the original requester to submit it into your ticket tracking system themselves so that “my boss can track what I’m working on and how much time I’m spending on it”. I bet that’ll reduce the number of requests even more… | |
| 12 hours ago | comment | added | gidds | Mmm.? What OP's colleagues are effectively doing is delegating chunks of their work to OP — chunks that are probably much larger than they realise.? Whether OP is the right person to do that is a business decision; and to make that decision, the business needs to understand how much time and effort is involved. | |
| 13 hours ago | comment | added | Anketam | @StephanKolassa your fourth option about cost centers and budgets is worthy of its own answer. I have not been in a position to use finances to blunt these kinds of requests, but for those who can I expect it would be very effective. | |
| 13 hours ago | comment | added | Stephan Kolassa | +1. This is the correct answer, because what is relevant here is that the requests are slop, not that they are AI slop. This is the correct way of dealing with help vampires, whether their requests come from AI or NI. I'll suggest a fourth option: for anything that requires more than two minutes, reply with a request for a booking number, or for whatever else lets you charge your time against a cost center and a budget. Requests like this will dry up very quickly. (Just make sure any booking number that comes back actually exists and isn't hallucinated itself...) | |
| yesterday | history | answered | Anketam | CC BY-SA 4.0 |