Patent / Copyright madness
Automated copyright enforcement really seems to work well… NOT!
And Apple is up to no good as usual…
Oh, and if you were thinking of setting up a service which required a login, and you thought you’d protect people’s accounts well, then that might be patented…
And this weekend, while doing the weekly write-up, I re-read the post, and started thinking, because I kindof feel that my own hobby projects very easily fall victim to this. They get shot down because I start thinking of how much stuff I would have to rewrite (things I’ve already solved in previous projects, but never put down the time to make generic enough to reuse) or figure out, and it just takes my edge off wanting to sit down and do it.
But then it struck me, what help me get reinvigorated, what helps me come over at least that hurdle: A moderately quiet place, time enough for a conversation, a good (programmer) friend, and optionally a beer.
Broken gets fixed. Shoddy lasts forever — I wonder, does this mean that, if something is shoddy and you want it fixed, the correct action is to break it?
I found myself wanting a way to have a central repository react to pushes based on what branch was pushed (I am working on a script at work, which some of my colleagues are beta-testing for me).
Whilst I develop a new feature I need a way to push that potentially buggy version of the script to a path where the testers can find it, while using a completely different path for the stable version which everyone else could use without any big risk of it messing anything up.
What I ended up with was this:
#!/bin/sh read _from _to _branchPath _branch=`basename $_branchPath` if [ "$_branch" == "develop" ]; then cd /path/to/local/repository/on/server unset GIT_DIR git pull git checkout develop cp -f ./scriptname /path/to/beta/test/directory/ fi
And since I agree with this post (namely that vimdiff would be a great diff viewer for git) I went ahead and followed the instructions of that post
Using vimwiki to track time sounds brilliant. It’s almost enticing enough for me to look into vimscripting to help out. Yet another project I’d like to spend time on :S
Being that paranoid soul I am, and now that I can also call myself a tester, I realize I’ve become even more aware of how many different entry points there are which needs to secured, such as vim’s modelines (protip: use secure modelines
From this post I learnt about license-loader, which I need to look into.
I found this post to be an excellent intro to awk, I am going to spread this around whenever I need to show anyone the basics
This post about 52Hz made me kindof sad :/
On the other hand, this post filled me with some hope.
I think it could be beneficial if this site was more widely distributed, so here’s me doing my part.
Finally, this post was pretty cool, and I immediately thought of at least two people I know who would get a kick out of reading this.