Rory's Blog
Home
Blog
Projects
Facebook
Google+
Github
RSS

Github Streak Renewal?

11/12/14

All right, so just like the first game jam I went to, my second game jam has ended with me having a Github streak going. Having a streak that's already multiple days in makes me want to continue it. However, last time I had a Github streak going, it devolved into me creating issues on github repos everyday instead of doing actual work.

Basically, it was too easy to cheat.

On the other hand, I actually have coding projects, which I host on Github, that I want to work on consistently. A streak done properly would almost certainly help that along.

So, I've decided to attempt Github streaking again.

....

"Github streaking" sounds dirty, Stephan.

Anyways, I stopped working on the Game Jam game last Sunday. So, you may be wondering, Stephan, what have I been working on since then?

A simple budgetting tool. Right now, I used it to track my spending. Between cash, credit cards, and direct debits from my account, I spend from all sorts of sources. So for right now, I'm trying to explicitly keep receipts, or when I can't get a receipt, right down my spending, and then input it into this terminal-based tool to save the dates, types, and totals of my day-to-day spending.

I tried this before, but all I made was a tool that read the logs I wrote by hand. Now I have a tool that takes input to make the logs as well, meaning I can iterate both on analysis code and input code. Hopefully, that will mean I avoid using this much less.

I have looked at already available budget tools, especially open-source ones, but I find I don't know enough about finances to really know what tool I need. I'm working on that knowledge though, by reading tutorials on Investopedia, so maybe this tool will be short-lived, and I'll retire it after I know enough to pick a tool someone else makes. Or maybe I'll like having a tool I made myself. Who knows.

Anyways, it almost looks like I'm already falling back into the trap of pushing issues to repos on Github instead of actually working on them. Monday and Tuesday were both issue-only days. The difference is, however, that I'm actually trying to use issues as a design tool this time. I'm even regularly posting comments (which doesn't count towards the Github streak) to each issue, linking to good resources, and thinking about how to go about implementing or fixing the issue.

And this morning I closed an issue. Now log files are generated in order by date, then expense-type, and then the spending in each expense-type. Making actually reading my expenses through this tool's log files a little bit easier.

So, I'm trying Github streaks again. Hopefully, it works out for the best.