4 ms·
-> download 1000 files using curl, then validate their checksum, then build stuff -> take an almost-CSV report generated by one piece of software, remove a bun
by inetknght 7y ago
-> download 1000 files using curl, then validate their checksum, then build stuff
-> take an almost-CSV report generated by one piece of software, remove a bunch of extra garbage at the top to turn it into an actual CSV file, then send the CSV file to data analysis pipeline.
-> join two CSV files selecting columns 2,3 from one file and 4,5 from the other file, keyed on column 1 from both files. like excel but for CSV files sized in hundreds of megabytes
-> take a bunch of CSV files and pump them into a rabbitmq queue
-> query whether a queue is empty. if so, start a new analysis job. if not, sleep another hour
-> grep for data in a directory to find specific files containing that data, then point those paths to another service
I can go on all day. CLI tools are far more wieldy than GUI tools IMO. CLI tools give me a generally-stable interface (or at the very least, a straightforward method of parsing and adapting to changes) and usually have _way_ better documentation than GUIs.
- shay_ker 7y agoMany of these actions seem like something you'd just never do in GUI though? Except maybe some of the CSV stuff.
- m_mueller 7y agoSee, there is a reason don't do this in a GUI. For a short while it looked like Apple's Automator would get there. Maybe Microsoft can crack this in a couple of years if they go nuts with python as a GUI scripting language with native OLE support.
- jankiehodgpodge 7y agoPowershell is already there.
- inetknght 7y agoAll of these actions are things which can be done in a GUI, just definitely not at the scale mentioned... certainly not at the scale mentioned and in a time-efficient manner
- shay_ker 7y agoRight exactly, they'd just be unreasonable to do in a GUI. But what about Google Docs? Admin tasks? Emails? Slack? Code review? Calendar meetings?