31–36 of 36 posts
We have many software programs that need to be run in sequence to transform a set of data from one form (on the order of tens to hundreds of GB) into a bunch of different output file formats. At some points the tools need to be run linearly, and at other points there are a few tools that need to be run in a branched fashion and then their outputs are combined in some complicated way using the next tool. Some of these…
It's not fully automate, but I frequently find myself having to do a lot of one off shell tasks, which are not quite worth the effort of writing a bash script. While some command is running I would like to start enqueing the next command. Technically I could write one command like this and go get a coffee: cd dir1 && task1 && cd ../dir2 && task2 some arg && etc But then the task would only start executing when I'm do…
Earlier quoted context omitted.
Meetings / stand ups We have recently automated stand ups, so the what I did yesterday/what I will do today/blockers are all pulled from Jira so now we only discuss major sprint goals and how to unblock any blockers...this reduces the meeting to just the important stuff
nice Does this mean keeping all status up to date in Jira? would you mind sharing how you do this?
Finding something to join meetings in my place, and record anything I was needed for, if anything.
It's not fully automate, but I frequently find myself having to do a lot of one off shell tasks, which are not quite worth the effort of writing a bash script. While some command is running I would like to start enqueing the next command. Technically I could write one command like this and go get a coffee: cd dir1 && task1 && cd ../dir2 && task2 some arg && etc But then the task would only start executing when I'm do…
do.sh stuff &
wait; do-other-stuff.sh -123 &
wait; cd ../; do-something-else.sh