I consolidate all my pictures (DLR and several family phones), rotate them according to the camera sensor, and store them in directories by date/time taken. Then I print out a list of what's left in the source directory (usually empty directories and a movie or two). I use jhead and bash.
I also scripted a git check-in of my mGSD tiddlywiki. which has all my work and home TODO stuff in it.
When developing, I usually just use the up-arrow in the CLI (Linux) to repeat similar commands unless it's something I don't do frequently. Things like "clean and compile code, create jar file, move jar file, restart webserver" can all be done on one line - storing that in bash history is a sort of automation, I guess.
I'd call that "7 years experience". If you're going to take a C++ job, just let them know there will be a short ramp-up period. If they're a good employer, they'll be fine with that. If they'll be a shitty employer, they'll not offer you the job and you didn't want it in the first place because they would make your life hell.
I consolidate all my pictures (DLR and several family phones), rotate them according to the camera sensor, and store them in directories by date/time taken. Then I print out a list of what's left in the source directory (usually empty directories and a movie or two). I use jhead and bash.
I also scripted a git check-in of my mGSD tiddlywiki. which has all my work and home TODO stuff in it.
When developing, I usually just use the up-arrow in the CLI (Linux) to repeat similar commands unless it's something I don't do frequently. Things like "clean and compile code, create jar file, move jar file, restart webserver" can all be done on one line - storing that in bash history is a sort of automation, I guess.