Sure thing, but the "okay, I give you the password, but don't tell my gf about all the porn on there"-story is way more believable than the "some guy put an encrypted 200gb file on my laptop without me noticing".
what you want is plausible deniability and that is not easy to achieve, as some states have started to have laws allowing to hold you hostage if you do not provide an decryption key to an encrypted container (which, with your method, would be corrupted). Have a look as TrueCrypts technical details behind their plausible deniability feature: http://www.truecrypt.org/docs/?s=plausible-deniability
Already stated, but my 2 cents:
- use a good IDE with fast referencing possibility (e.g. right-click on a function call => "follow")
- use a profiler to see a flowchart or UML for a high level overview
- start commenting the classes and refactor their names if unclear. There are nice tools out there (depending on the language), which create DocBlocks for everything first and then you can use DoxyGen to generate a nice overview over everything.
And about the question of how bad you are: one of my IT lecturers had worked at BMW and they had made a test on the efficiency of their programmers on new code and on code written by other developers.
When the same developer had to extend or change code of other developers, he was a hundred times slower than when he would code on his own himself. That was around 2001, if I'm not mistaken.
Slashdot Mirror
There's a hellotamore on the revision3-page - unfortunatly without the illustrator-source-files.
Sure thing, but the "okay, I give you the password, but don't tell my gf about all the porn on there"-story is way more believable than the "some guy put an encrypted 200gb file on my laptop without me noticing".
what you want is plausible deniability and that is not easy to achieve, as some states have started to have laws allowing to hold you hostage if you do not provide an decryption key to an encrypted container (which, with your method, would be corrupted). Have a look as TrueCrypts technical details behind their plausible deniability feature: http://www.truecrypt.org/docs/?s=plausible-deniability
Already stated, but my 2 cents: - use a good IDE with fast referencing possibility (e.g. right-click on a function call => "follow") - use a profiler to see a flowchart or UML for a high level overview - start commenting the classes and refactor their names if unclear. There are nice tools out there (depending on the language), which create DocBlocks for everything first and then you can use DoxyGen to generate a nice overview over everything. And about the question of how bad you are: one of my IT lecturers had worked at BMW and they had made a test on the efficiency of their programmers on new code and on code written by other developers. When the same developer had to extend or change code of other developers, he was a hundred times slower than when he would code on his own himself. That was around 2001, if I'm not mistaken.