The default fonts you can choose from when developing for Android are not very interesting. Normally they are OK for my simple purposes, but for once I wanted something a little bit prettier for my new app, Happy Moments.
I found this tutorial very useful for using custom fonts on Android:
If you want to browse the content of older revisions, there is a non-trivial way by inserting /!svn/bc/REVNO between the base URL of the repository and the path component of the target directory inside the repository, for example you can browse the contents as of revision 1234123 like this:
I put together this simple presentation about a few simple but very effective practical tips that should make you lightning fast on the command line. I use these literally every minute I spend in the shell. All the tips should work in Linux, UNIX, BSD and similar.
I created the presentation using Google Docs, but it was not really a great experience:
The dotted green line you see under headings is not intentional, it appears only after exporting to PDF. I don’t know why. I would prefer it without the line as shown correctly in Google’s viewer, but I want to use Speaker Deck as it is not blocked at my workplace and has a better WordPress plugin.
I used the Speaker Deck Embed plugin to embed the presentation here. Oh and Speaker Deck is really awesome.
A Linux Live CD that should be interesting, educational, and highly entertaining for any self-respecting programmer: a security challenge with 6 levels based on the online contest created by Stripe in early 2012.
The easiest way to use the Live CD is with a software like VirtualBox: create a virtual machine with no hard disk and 256MB memory and point the CD device to the ISO file and that’s it, start the VM! The Live CD uses US qwerty keyboard by default, you can change that by passing a boot parameter at the boot prompt, for example:
Alternatively you can use the shortcuts fr, jp or hu for French, Japanese or Hungarian keymap, respectively.
When the system starts you are logged in as user level00. You will be presented with a hint that should help you gain access to the password of user level01. Your mission, should you choose to accept it, is to find and exploit the vulnerabilities presented at each increasingly difficult level, advancing forward until you reach level06 (and celebrate!)
By completing this challenge you will become a better programmer:
You will increase your awareness of the importance of security, and probably write more secure, more robust code in the future.
You will improve your skill of finding problems and weaknesses, which is the critical first step in optimization tasks.
You will have a wonderful time, and come out enlightened!
Note that even in Windows, the correct path is actually ~/.subversion/servers when using git-svn, even though this is NOT the normal configuration directory for the native svn.exe. For example in Windows 7 svn.exe typically uses the path C:\Users\YOURUSER\AppData\Roaming\Subversion.
This was quite confusing to me at first, because after I got svn checkout working well by editing C:\Users\YOURUSER\AppData\Roaming\Subversion\servers I was surprised to find that git clone svn still had the proxy issue.
In case you were wondering, the http_proxy and https_proxy environment variables are ignored by both Git and Subversion.
Mike Heyworth created the original app, I contributed mocks and elements for the new design, which Mike incorporated in the latest version of the app released just a few days ago. If you are in IT, do try it out, challenge yourself, test your skills, and just have fun with it!
If you like this FREE app please do buy the PRO version and support us!
More usability and design improvements will be coming soon (1-2 months), so stay tuned!
I had this strange issue the other day. My account password has recently changed, and for each Subversion repository linked to that account I had to re-enter my password. Normally it is enough to re-enter once per repository: Subversion updates the corresponding authentication setting file so that I don’t need to enter it again. But for some repositories it kept asking for it…
After some digging around, I realized that my user did not have write access to the file that sores the password. That is easy to fix once you know what to look for, and if you know which file it is. However that can be tricky if like me you don’t know how Subversion organizes its settings files…
In Windows 7 (using the Git shell) you can find your Subversion setting files that you don’t have write access to like this:
find /c/Users/YOURUSER/AppData/Roaming/Subversion ! -perm -200 -type f
This can be useful to confirm your suspicion about filesystem permission issues. If you don’t care about all that, you can just add write permission to yourself on all files indiscriminately with: