Difference between revisions of "Talk:2565: Latency"

Explain xkcd: It's 'cause you're dumb.
Jump to: navigation, search
Line 17: Line 17:
 
: There are tools for such automation (they're usually called either workflow or orchestration tools) and have been for decades, but they tend to be ''really'' fragile. If the services being orchestrated aren't aware of it, it is very easy for them to change things and break the coordination in a way that just fails silently. BTDT. --[[Special:Contributions/172.70.85.73|172.70.85.73]] 15:46, 8 January 2022 (UTC)
 
: There are tools for such automation (they're usually called either workflow or orchestration tools) and have been for decades, but they tend to be ''really'' fragile. If the services being orchestrated aren't aware of it, it is very easy for them to change things and break the coordination in a way that just fails silently. BTDT. --[[Special:Contributions/172.70.85.73|172.70.85.73]] 15:46, 8 January 2022 (UTC)
 
: There are many organizations where such automation workflow just _cannot_ happen because the IT or upper management will ignore the users request to integrate X with Y. Can be due to anything from incompetence, to relying on 3rd party vendors that don't offer any support, to financial reasons ("too expensive"), to power struggles, or all of the above. [[User:Ralfoide|Ralfoide]] ([[User talk:Ralfoide|talk]]) 19:01, 8 January 2022 (UTC)
 
: There are many organizations where such automation workflow just _cannot_ happen because the IT or upper management will ignore the users request to integrate X with Y. Can be due to anything from incompetence, to relying on 3rd party vendors that don't offer any support, to financial reasons ("too expensive"), to power struggles, or all of the above. [[User:Ralfoide|Ralfoide]] ([[User talk:Ralfoide|talk]]) 19:01, 8 January 2022 (UTC)
 +
:: In my experience, company can more easily afford unqualified person spending day on something than me, the programmer, half hour. It gets less clear if the thing needs to happen repeatedly, but still, my time is costly and my list of tasks I need to work on endless. -- [[User:Hkmaly|Hkmaly]] ([[User talk:Hkmaly|talk]]) 01:41, 9 January 2022 (UTC)

Revision as of 01:41, 9 January 2022

Ha! Welcome to my life. Just thought to check if there was a new xkcd yet (at 04:45, GMT) after spending the last five hours messing semi-manually with some geodata. Ok, the first three hours was in the text editor looking at the raw JSON file, and the next two was writing a Perl script to redo everything I had already done (and more, but not yet everything I will eventually want to do) without the fallible human element. Once the fallible human element has polished the script up to account for unforseen circumstances. 172.70.85.73 04:51, 8 January 2022 (UTC)


what is SCAPDFATIAT OH what is says in the Comic

Right, Someone Copies and Pastes From a Thing Into Another Thing 172.70.210.183 05:36, 8 January 2022 (UTC)


I can relate to this. In fact, i use 2 computer screens just for that: I copy data from software X, screen 1 to quickly paste it into software Y, screen 2. 162.158.183.232 06:09, 8 January 2022 (UTC)


I suspect that "cumshots" in the last paragraph is either a (very lame) joke or an incidence of spam. Either way, please remove it! Thanks.

Often the reason for the SCAPDFATIAT step is that A Thing has no direct connection to Another Thing. So someone has to design a way for them to communicate to get the human out of the loop. Unless this process is done frequently, it doesn't reach the top of the priority list. Barmar (talk) 13:48, 8 January 2022 (UTC)

There are tools for such automation (they're usually called either workflow or orchestration tools) and have been for decades, but they tend to be really fragile. If the services being orchestrated aren't aware of it, it is very easy for them to change things and break the coordination in a way that just fails silently. BTDT. --172.70.85.73 15:46, 8 January 2022 (UTC)
There are many organizations where such automation workflow just _cannot_ happen because the IT or upper management will ignore the users request to integrate X with Y. Can be due to anything from incompetence, to relying on 3rd party vendors that don't offer any support, to financial reasons ("too expensive"), to power struggles, or all of the above. Ralfoide (talk) 19:01, 8 January 2022 (UTC)
In my experience, company can more easily afford unqualified person spending day on something than me, the programmer, half hour. It gets less clear if the thing needs to happen repeatedly, but still, my time is costly and my list of tasks I need to work on endless. -- Hkmaly (talk) 01:41, 9 January 2022 (UTC)