I finished the Git Immersion tutorial that I started yesterday. I really enjoyed the way that the material was presented, and though I was a little lost near the end (mostly in how the commands exactly worked, not the concepts) I thought that it was a good introduction to how to work with version control software.
I only catastrophically destroyed my repo once (more like needed to redo five minutes of work), and I figured out exactly what not to do when I'm managing my own work. (For future reference: hard resetting to the beginning of the tutorial is not a recommended course of action.)
Backups: always a good idea.
From this I've decided that my next project is going to be putting together some of my basic fasta file scripts into a toolkit, which will give me the opportunity to both clean out my junk drawer of code and also put some of my newly found version control knowledge to use.
Most of the rest of the day will be spent tinkering with this before I have to go home. School starts next week and I want to enjoy the most of what time I've left. I'm pretty sure that will mostly be playing Dota2 and writing, but we'll see what that brings!
Friday, January 9, 2015
Thursday, January 8, 2015
Post-Break Clean Up
Spent most of work today learning how to use git from a couple of different sites while my tree building software ran. I think I'm going to try and get a repo set up on GitHub that contains some of the tools I've developed so I can easily work on them and transfer them to new computers.
(I'm using this tutorial here, and it seems pretty good for a crash course.)
Most of what I have currently is just pipeline Bash scripts or really specific data manipulation python code. It'll be a good exercise to go through and empty out my junk drawer and see what actually useful code I have lying around. I know most of it is just adaptors and widgets, but maybe there'll be something interesting I can dust off and clean up.
I've learned so much in the past year, I'm just a little worried to look back on my code and see how awful it was/is. It'll be good to review it and move forward I think. More like mid-winter cleaning than spring cleaning, but I think that's probably for the best to get it out of the way before classes start to get too intense.
Probably going to spend the rest of the day catching up on reading literature for my thesis with the all important coffee break at 4. (Not that I haven't had enough coffee today... probably should have made a half pot instead.)
(I'm using this tutorial here, and it seems pretty good for a crash course.)
Most of what I have currently is just pipeline Bash scripts or really specific data manipulation python code. It'll be a good exercise to go through and empty out my junk drawer and see what actually useful code I have lying around. I know most of it is just adaptors and widgets, but maybe there'll be something interesting I can dust off and clean up.
I've learned so much in the past year, I'm just a little worried to look back on my code and see how awful it was/is. It'll be good to review it and move forward I think. More like mid-winter cleaning than spring cleaning, but I think that's probably for the best to get it out of the way before classes start to get too intense.
Probably going to spend the rest of the day catching up on reading literature for my thesis with the all important coffee break at 4. (Not that I haven't had enough coffee today... probably should have made a half pot instead.)
Subscribe to:
Posts (Atom)