Record your work

I am developer/code-reviewer/debugger/bug-fixer/architect/teacher/builder from dubai, uae
Search for a command to run...

I am developer/code-reviewer/debugger/bug-fixer/architect/teacher/builder from dubai, uae
No comments yet. Be the first to comment.
You Should Tell Yourself

A URL shortener is a proxy service that provides a mapping between the short and full representation of a URL. The short URL has the advantage of being small. The service can also provide useful analy

Listening to the Mel Robbins's podcast on regrets was a 'ear'-opener. One can have reqrets of action or inaction. 4 types of reqrets foundation - should've done the work boldness - should've taken t

We need to create a unique ID generator for our high-traffic web application, generating about 10K IDs/second. The IDs can't simply be monotonically increasing integers, which are good for data access
doing + telling

I saw the pertinent video by Chris Albon on Don't do invisible work at '22's normconf. He evangelizes broadcasting your work to know what value one provides which helps with career progression. Given we are forgetful animals, we need to physically log work so that we know what to broadcast.
The following snip via this is a command-line (zsh) utility that lets you record work items:
rw() {
WORK_FILE="${WORK_FILE:-$HOME/.work.log}"
BACKUP_FILE="$WORK_FILE.bck"
# head insert into backupfile
echo "`date +'%Y-%m-%d'` $@" | cat - $WORK_FILE > $BACKUP_FILE
# preserve simlink
cat $BACKUP_FILE > $WORK_FILE
}
~/.work.log -> ~/Google Drive/.work.logsymlinked off machine
Improvements:
have sections to log multiple work streams
sqllite instead of POT
optionally specify time spent in fractional hours from time of insertion