# I am the Watcher. I am your guide through this vast new twtiverse.
# 
# Usage:
#     https://watcher.sour.is/api/plain/users              View list of users and latest twt date.
#     https://watcher.sour.is/api/plain/twt                View all twts.
#     https://watcher.sour.is/api/plain/mentions?uri=:uri  View all mentions for uri.
#     https://watcher.sour.is/api/plain/conv/:hash         View all twts for a conversation subject.
# 
# Options:
#     uri     Filter to show a specific users twts.
#     offset  Start index for quey.
#     limit   Count of items to return (going back in time).
# 
# twt range = 1 18
# self = https://watcher.sour.is/conv/uy2hfma
Do-nothing scripting: the key to gradual automation – Dan Slimmon
Do-nothing scripting: the key to gradual automation – Dan Slimmon
Do-nothing scripting: the key to gradual automation – Dan Slimmon
@prologic Yep, we do use that approach at work. 👌 I wasn’t convinced at first, either, but I’m beginning to see the benefits.
@prologic Yep, we do use that approach at work. 👌 I wasn’t convinced at first, either, but I’m beginning to see the benefits.
@prologic Yep, we do use that approach at work. 👌 I wasn’t convinced at first, either, but I’m beginning to see the benefits.
@movq I'm trying to build something like this at my work. Do you have a library of such procedures or are the scripts/binaires built for one proc at a time?
@movq I'm trying to build something like this at my work. Do you have a library of such procedures or are the scripts/binaires built for one proc at a time?
@movq I'm trying to build something like this at my work. Do you have a library of such procedures or are the scripts/binaires built for one proc at a time?
These are my thoughts currently (from IRC):


[10:40:20]  <prologic> Thinking about writing a do nothing framework in Go
[10:41:10]  <prologic> One in which consumers can define their procedure in their own repo
[10:42:07]  <prologic> And users can of the tool can execute any procedure that the binary has imported
[10:42:58]  <prologic> And eventually implement Run() to turn steps from manual ones to automated ones gradually
[14:51:34]  <xuu> Like for mocking against?
[14:51:43]  <xuu> Not sure I follow
[16:03:04]  <prologic> xuu basically for reducing the activation energy to complete otherwise manual procsses
[16:03:14]  <prologic> where you can gradually turn them into automated processes
[16:03:29]  <prologic> https://blog.danslimmon.com/2019/07/15/do-nothing-scripting-the-key-to-gradual-automation/
These are my thoughts currently (from IRC):


[10:40:20]  <prologic> Thinking about writing a do nothing framework in Go
[10:41:10]  <prologic> One in which consumers can define their procedure in their own repo
[10:42:07]  <prologic> And users can of the tool can execute any procedure that the binary has imported
[10:42:58]  <prologic> And eventually implement Run() to turn steps from manual ones to automated ones gradually
[14:51:34]  <xuu> Like for mocking against?
[14:51:43]  <xuu> Not sure I follow
[16:03:04]  <prologic> xuu basically for reducing the activation energy to complete otherwise manual procsses
[16:03:14]  <prologic> where you can gradually turn them into automated processes
[16:03:29]  <prologic> https://blog.danslimmon.com/2019/07/15/do-nothing-scripting-the-key-to-gradual-automation/
These are my thoughts currently (from IRC):


[10:40:20]  <prologic> Thinking about writing a do nothing framework in Go
[10:41:10]  <prologic> One in which consumers can define their procedure in their own repo
[10:42:07]  <prologic> And users can of the tool can execute any procedure that the binary has imported
[10:42:58]  <prologic> And eventually implement Run() to turn steps from manual ones to automated ones gradually
[14:51:34]  <xuu> Like for mocking against?
[14:51:43]  <xuu> Not sure I follow
[16:03:04]  <prologic> xuu basically for reducing the activation energy to complete otherwise manual procsses
[16:03:14]  <prologic> where you can gradually turn them into automated processes
[16:03:29]  <prologic> https://blog.danslimmon.com/2019/07/15/do-nothing-scripting-the-key-to-gradual-automation/
@prologic Some people at work have made this:

https://github.com/seibert-media/automatix

You put the “commands” in a YAML file. It’s Python and deals a lot with our corner cases. 🥴 Not sure if you want to use it as it is.

(Personally, I’d remove the YAML stuff altogether.)
@prologic Some people at work have made this:

https://github.com/seibert-media/automatix

You put the “commands” in a YAML file. It’s Python and deals a lot with our corner cases. 🥴 Not sure if you want to use it as it is.

(Personally, I’d remove the YAML stuff altogether.)
@prologic Some people at work have made this:

https://github.com/seibert-media/automatix

You put the “commands” in a YAML file. It’s Python and deals a lot with our corner cases. 🥴 Not sure if you want to use it as it is.

(Personally, I’d remove the YAML stuff altogether.)
@movq Thanks ! I'll take a look 👌
@movq Thanks ! I'll take a look 👌
@movq Thanks ! I'll take a look 👌