|
![](/i/fill.gif) |
On 06/10/09 15:05, Orchid XP v8 wrote:
Probably all of these are good enough for the resume. Some may need
rephrasing or more details.
> - Built a recursive Turtle-style fractal plotter.
What the heck is this? You mean similar to Logo? You may want to add a
line beneath it (indented a bit) that has a one line explanation of what
this is (but don't change the above description if it's accurate).
> - Built a Lambda calculus interpretter.
Put this in. Specify what language you used, though (and spell it
properly!)
> - Built a mini-Mathematica engine.
Give more details - perhaps as bullets beneath it. What were its
capabilities and in which language?
> - Built a modular software sound synthesizer.
Good. Again, perhaps some bullets describing features.
> - Built a collection of data compression modules.
What language and which data compression formats (you could just put
the latter in parentheses).
> - Built a Mandelbrot generator with multiple colouring options.
Good enough. Language?
> - Built a mini-Prolog interpretter.
Good enough. Language? You could give more details as above (what
features did you implement, etc).
> - Built a simple ray tracer.
Language? Remove "simple" and put something like "prototype". Maybe
list some basic features.
> ...should I continue?
Sure.
There's a danger of your resume becoming too long. In which case you'll
want a short version (2 pages) which have only the ones that you think
are really prominent or interesting to the job. Then, separately, you
can have a CV that has all of the above, with details on most as bullets.
> Every single one of these has been a small one-man project totalling
> less than 1,000 lines of code, I would estimate.
Doesn't matter. Most of these are non-trivial.
> Alternatively, I could say something about stuff I did at work.
> "Prepairing for audits" generally just consists of checking I've signed
> everything I'm supposed to sign, and hoping that the auditors don't find
> any problems. I could perhaps mention the Disaster Recovery Plan I wrote
> completely from scratch (and which client and government auditors love,
> by the way). But not massively relevant to this specific application.
> (Or maybe it is? Maybe I'll end up writing technical documentation for
> these guys? Who knows...)
Definitely put the recovery plan in there. If you're not too impressed
with audit preparations, then just put it as a bulleted entry under your
current occupation (along with the other entries under that - system
admin, recovery plan, etc).
--
"Hex Dump" - Where Witches put used Curses?
/\ /\ /\ /
/ \/ \ u e e n / \/ a w a z
>>>>>>mue### [at] nawaz org<<<<<<
anl
Post a reply to this message
|
![](/i/fill.gif) |