I'll trust your criticism. But the perfect shouldn't be the enemy of the good. If this was the best/first way for them to act, then I wouldn't be too hard on them. If you attempt to help and they get all defensive, then "No Quarter". 8^)
But semi-auto isn't half-assed in the general sense. I think once you get the data into publishable form humans need to do some verification, even if that bottlenecks the process. The last thing you want is some bug in the fully automatic stack to produce misleading output. There may even be an argument for a few eyeball bottlenecks in the toolchain, if for no other reason than scaffolding for when/if the final verification step fails. On 3/30/20 12:04 PM, Jon Zingale wrote: > Semi-auto is a little like half assed. For what would > get the data directly to database or even a csv file > in 5 lines, there is a whole lot of node infrastructure > setup to take screenshots and post to s3 buckets. > And for there to be 27 contributors, the project appears > like it could use some direction. -- ☣ uǝlƃ ============================================================ FRIAM Applied Complexity Group listserv Meets Fridays 9a-11:30 at cafe at St. John's College to unsubscribe http://redfish.com/mailman/listinfo/friam_redfish.com archives back to 2003: http://friam.471366.n2.nabble.com/ FRIAM-COMIC http://friam-comic.blogspot.com/ by Dr. Strangelove
