2013-05-02

Not talking about Hacking

Funny, the original poster "talks" about "not talking about hacking". But he does. Hilarious, in a way:
Welcome to Hacking. The first rule of Hacking is: you do not talk about Hacking. The second rule of Hacking is: you DO NOT talk about Hacking! Third rule of Hacking: if someone yells "stop!", goes limp, or gets arrested, the hack is NOT over. Fourth rule: only two guys to a hack. Fifth rule: one hack at a time, fellas. Sixth rule: the hacks are bare Windows PC's. No Linux, no Unix, no Macs. Seventh rule: hacks will go on as long as they have to. And the eighth and final rule: if this is your first time at hacking, you have to hack.

http://www.dailytech.com/Australian+Federal+Police+Mock+Hackers+Only+to+be+Hacked+in+Return/article16023.htm

2013-04-27

Structuring Unit Tests

A very fine idea for naming and nesting unit tests:

To have a nested class for each method being tested.

Sources:

This little trick, this one simple sentence, is like a missing piece in the jigsaw. I liked it from the very start. It fits very well alongside guides for naming of testing methods, like expressed in this article:

http://blog.stevensanderson.com/2009/08/24/writing-great-unit-tests-best-and-worst-practises/

I just wonder how this practice could fit into JUnit. Will have to try.

Also on the same page:

2012-11-30

2012-11-24

Securing files in Google Drive

Just a quick round-up of methods of securing files in otherwise almost perfect Google Drive:

This also made me wonder: with Windows 8 Microsoft gave users their SkyDrive - what about securing this little beast?