in reply to Conditioned Response (or lack thereof)

I find everything these days to be leaning towards the "any time, anywhere" coding philosophy.
All my best profanity was learned in CS courses where you spend the entire length of the course in front of a computer but your final exam is something complex on a piece of paper.
I recently went job hunting, and all the positions I interviewed for tested me formally in some fashion or another. In fact, the only place I can think of that is still safe from "immediate coding" is the cubicle. I have found that despite the changes I have witnessed, my friends and I still have the ability to say "Let me get back to you", and actually come up with a decent design.
But, I will bet you a nickel that won't last long. As visual programming becomes more popular I think the focus will turn to cutting down design time by creating more advanced design wizards.
  • Comment on RE: Conditioned Response (or lack thereof)

Replies are listed 'Best First'.
RE: RE: Conditioned Response (or lack thereof)
by cwest (Friar) on Oct 15, 2000 at 02:42 UTC
    I went job hunting some time ago and was not tested anywhere, although I expected to be.

    Where I work, I keep a 'lab.pl' on every server/workstation that I come in contact with. It's basic make up is: 

    #!/usr/bin/perl -w
use diagnostics;
use strict;
$|++;

use Data::Dumper;

__END__

    [download]
    With that in a file with 700 permissions, I can almost work up to the "any time, anywhere" level.

    If a co-worker asks me a coding question, I can mock up a demonstration at a terminal and teach them what I'm doing as I code. This is very handy.

    And if there are errors, I just talk through them till I have a working model, then I can mail them my file and they have an example to keep. 

    --
Casey
   I am a superhero.
[reply]
[d/l]

In Section Meditations