HDTenEightyP/NetNews huggingface dataset:
From: rslade@fraser.sfu.ca (Robert Slade)
Subject: Questions - NOT! part 2 (H2H)
Organization: Simon Fraser University, Burnaby, B.C., Canada
Date: Fri, 25 Dec 1992 09:07:01 GMT

INTRVW8.H2H   921123
 
                      Questions - NOT! part 2
 
Hypothetical questions are not the only "no-no"s dear to the heart
of interviewers.  Here are some further "bad examples".
 
Questions you don't know the answer to - Very often used in
conjunction with hypothetical situations.  I vividly remember a
question that was asked of me many years ago.  The question had to
do with first aid, and was very technically detailed.  However, it
left a few ends open which I tried to query the questioner on. 
After my third question, I was astounded when he dismissed it with
"well, I guess you know what you're talking about" and I realized
that he had not the faintest idea of what he was asking.  He had
seen the situation proposed in a magazine.
 
Simple questions - "You have a driver's license, eh?  Which is the
brake pedal?"  Most of these questions should have been answered by
looking at the resume.  If the candidate has a driver's license, the
candidate will know which pedal is which.  If you can't obtain more
information than that, don't ask the question.
 
Transparent questions - "We are looking for someone who enjoys
working with people.  Do you enjoy working with people?"  Most
people will not see themselves in this caricature, but it happens in
about half of interviews.  If the question isn't in quite that blunt
a context, the same question might be asked of, say, a candidate for
a technical support position.  This person, if they know anything
about the job, knows that they will be spending half the day on the
phone with boring, ignorant users.  Of course they are going to
answer that they like people.  If they didn't, they wouldn't have
applied for the job in the first place.  Even if they secretly wish
they could take out contracts on all your clients, they will still
answer the same way.  (If you want to know how well they do deal
with people, note how they respond when asked to come in for the
interview.)
 
No questions - Believe it or not, I have observed interviews of
extended length where as few as two questions were asked of the
candidate.  The remaining time was taken up by the interviewer
expounding his (it's usually "he") opinions on the job, company and
industry.  Sometimes on other miscellaneous topics as well. 
Remember, you are there for a purpose.  Just because these poor
souls want something from you (a job) does not automatically make
them a "captive audience" for your "pearls of wisdom".  The idea is
to find out which one of them has the most wisdom to offer you, and
your company.
 
copyright Robert M. Slade, 1992   INTRVW8.H2H   921123
Newsgroups: can.jobs
From: liuyh@vis.toronto.edu (Yuanhui Liu)
Subject: Re: MAKE MONEY WITH PC
Organization: Department of Computer Science, University of Toronto
Date: 21 Dec 92 17:45:16 GMT

In article <1h4tnpINNskk@access.usask.ca> choy@dvinci.USask.Ca (Henry Choy) writes:
>Spencer J. Barnes (sbarnes@dragger.ifmt.nf.ca) wrote:
>: In <1992Dec9.020005.12501@credit.erin.utoronto.ca> glover@credit.erin.utoronto.ca (Mike Glover) writes:
>: 
>: >>In article <1992Dec7.205355.28329@julian.uwo.ca> britton@gaul.csd.uwo.ca (STEVEN BRITTON) writes:
>: >>>>->     1. Sell it
>: >>>>       2. Rent it out
>: >>>	3. Get people to pay for time to beat it over the monitor with
>: >>>	   a sledgehammer.
>: >	4. Sell tickets to watch MS Windows programmers pull their hair out
>: >	   trying to make a useful GUI application.
>:         5. Provide a hardcopy atmospheric motion dispersal prevention
>:            service. (Rent-a-paperweight) P->
>
>6. Write software to sell.
>7. Make money by CAD
>
8.  Offer your services to create impressive laserjet printed resumes for your
    unemployed neighbors(these days you are guarenteed lots of clints)
Newsgroups: can.jobs
Subject: (Agency) Sr. Programmer - AS400\VancouverBC\BS\CS\Communications SW
From: vwillden@coast.almanac.bc.ca (Vincent Willden)
Date: Wed, 30 Dec 92 10:47:11 PST
Organization: Coast Personnel Services Ltd. Nanaimo, B.C.

**Previously posted to misc.jobs.offered, Tuesday Dec. 29**

Reference #JO1229 (please quote this number in all correspondence)

Functional Job Title: Sr. Programmer - AS400
Location: Vancouver, BC Canada
Education: BS    Major: Computer Science
Salary Range: 60 - 70K
Interview: Company Paid
Relocation: Company Paid
Company Benefits: Full Range
Recruiting From: Across Canada and U.S.A.
Specialty Information: AS400, SNADS, APPC, DOS, Novell, LAN's, WAN's, E-mail,
                       OS/2, Windows, Communication.

Our client company wants the best AS400 Technical Programmer available and they
want them now.  The individual will be involved in the development of
Communications S/W for computer to computer, computer to FAX, E-mail, satellite
based transmissions, multi node connectivity, voice response, voice passage
communications, user to user communications across multiple platforms.

Previous products have primarily addressed IBM mid range computers (AS400/S38),
however new generations will include VAX, H.P., UNIX, PC VS/2 and the whole
gamut.  The company is ten years old and has about 35 employees but is entering
an existing rapid growth phase.  The candidate must have intimate knowledge of
AS400/S38 (ten years experience) and must have a strong understanding of data
communications and interconnectivity.  Should have worked in Development/Lab
environment.  Must have RPG III or RPG 400.

Note: We will look at exceptional candidates who want more.  The degree is not
      mandatory for Canadian candidates, but it will be very helpful for U.S.A.
      candidates in order to bring them in under Free Trade.

Also: This is not an entry level position.  Please do not apply unless you fit
      the criteria stated above.  Our client company will not pay a fee for
      candidates that do not have the skills previously stated.  We will not
      reply to underqualified applicants.

Phone, FAX or E-mail (ASCII only) your resume to:

_______________________________________________________________________________

   Coast Personnel Services Ltd., 103-65 Front Street, Nanaimo, B.C. V9R 5H9
   Professional Personnel Placement, From the Heart of Vancouver Island
   1-604-753-4465 (Voice)     Compuserve: 71754,2135     1-604-753-2278 (Fax)
   vwillden@coast.almanac.bc.ca  (InterNet)                   Vincent Willden
Newsgroups: can.jobs
From: skenny@pico.engr.mun.ca (Shawn Kenny)
Subject: Re: Fire in St. John's, Nfld.
Organization: Memorial University of Newfoundland
Distribution: can
Date: Tue, 22 Dec 1992 21:29:38 GMT

sfysh@epas.utoronto.ca (Stephanie Moskal Fysh) writes:

>Could someone in Newfoundland please post more info. about the fire in
>St. John's?  I'd like to know what block(s) have been destroyed.  They
>have a strange reluctance to report such matters as street names on
>the news!

The area in question is around the Parade Street terminal where, among
other streets, LeMerchant Rd, Long's Hill and Harvey Rd intersect.

As far as I know the fire, which started in the CLB Armoury, was
initially thought to be under control. Obviously it wasn't. The fire
flared up again and subsequently gutted the Social Services building and
Dominion store next to the CLB. Cool temperatures and high winds didn't
make the matters any easier for controlling the blaze. Embers were carried
across the street where a half-dozen or so adjoined wooden buildings caught
fire. This was enough cause for concern that residents in the area were
forced to evacuate and retire to a make-shift hostel. BTW most of the area
and downtown core of St. John's consists of adjoined structures. Initial
estimates put the damage at several million. Also the CLB Armoury had an
"historic archive" of photos and such which (as far as I know) is lost
---- quite a shame.




>-- 
>Stephanie Moskal Fysh    |   "Today an eighteenth-century scholar may well
>Dept. of English         |   be Jewish, female, or generally irreverent."
>Univ. of Toronto         |                             - Lawrence Lipking
>(sfysh@epas.utoronto.ca) |                            
--
"I'm having a lot of holiday stress. ... Deep down, I doubt my greed for 
presents can overcome my desire to misbehave." Calvin and Hobbes by
Bill Watterson.
	skenny@pico.engr.mun.ca St. John's, NF Canada
From: nneil@ersys.edmonton.ab.ca (Neil A. Armstrong)
Newsgroups: can.jobs
Subject: Power Plant Jobs
Date: Wed, 30 Dec 92 18:29:13 MST
Organization: Edmonton Remote Systems #2, Edmonton, AB, Canada

I am looking for a position in a Power Plant. My second choice would be 
at any university or similar large institution producing high pressure 
steam or emergency power. Resume available upon request. Leave mail here.

Neil A. Armstrong              nneil@ersys.edmonton.ab.ca
From: klassen@sol.UVic.CA (Melvin Klassen)
Subject: Re: registration -vs- forwarder policy
Organization: University of Victoria, Victoria, B.C. CANADA
Distribution: can
Date: Sat, 2 Jan 93 23:22:31 GMT

In article <C08yy0.3qJ@wimsey.bc.ca> sl@wimsey.bc.ca (Stuart Lynne) writes:
>
>Now nslookup -type=soa gov.coquitlam.bc.ca.
>    *** (name-server) can't find gov.coquitlam.bc.ca.: Non-existent domain

That's the "correct" answer.  When you try:

     nslookup -type=soa     coquitlam.bc.ca.
and
     nslookup -type=soa           gov.bc.ca.

you do get useful information.  

So, what's your point?
Newsgroups: can.domain
From: davecb@nexus.yorku.ca (David Collier-Brown)
Subject: registration -vs- forwarder policy
Organization: York University
Distribution: can
Date: Sat, 2 Jan 1993 18:22:10 GMT

In article <C07r77.4ut@uunet.ca> smd@uunet.ca (Sean Doran) writes:
>CA does a number of things right, notably the assurance of proper
>nameservice for anything that has a cooperative Internet forwarder,
>X.400 routing, and a listing in the UUCP maps.  All of these have been
>good political decisions.

sl@wimsey.bc.ca (Stuart Lynne) writes: 
| Well I wouldn't agree with that. There is currently (unlike the .us
| or standard NIC domains) no requirement for having an Internet Domain
| Name Server to support your domain. Down south it *is* required. You
| can't get registered in .com or .us unless someone is willing to
| support an MX for you.

  Ok, here's a factual disagreement and a policy question.  Lets put the
policy question up for debate...


  As I understand it, and organization with a discontinuous net (ie,
no internet mail forwarder) in Canada can register a domain name.  In
the United States this is untrue.  There you can have an IP network
number allocated, but you cannot have a domain name without a mail
forwarder (and someone to hold your MX records, as a practicality
issue).

  The U.S. position has been criticized because a company cannot
``reserve'' their domain name.  The Canadian position has been
criticized because the domain is unreachable.

  Is this an either-or situation?  Is there a middle ground?  Is there
a necessary relationship with the allocation of an IP address?
  Does the .ca domain registrar actually place the domain entry into a
DNS server without any A or MX records? What effect does this have on
email?

  Ok folks, lets have at it (:-))

--dave




-- 
David Collier-Brown,  | davecb@CCS.YorkU.CA | lethe!dave
72 Abitibi Ave.,      | 
Willowdale, Ontario,  | York Postmaster and
CANADA. 416-223-8968  | occasional sendfail(8) consultant.
Newsgroups: can.domain
From: sl@wimsey.bc.ca (Stuart Lynne)
Subject: Re: can.domain
Organization: Wimsey Information Services
Distribution: can
Date: Sat, 2 Jan 1993 21:20:36 GMT

In article <C08H06.6xB@uunet.ca> smd@uunet.ca (Sean Doran) writes:

}At the moment, it's difficult to tell whether to blame John Demco as
}the coordinator for CA-DOM for various gripes and problems, or the
}committee (and certain members of it) for presenting him with policy
}decisions he might not have made on his own.  Given the secretiveness
}of the process and of the membership of the committee and
}mailing-list, it is hardly surprising that people are frustrated.
}
}I have yet to understand why the historical records of the
}deliberations of the CA-DOM committee haven't been made public.  Could
}it be that some of the members of the committee might be a little
}embarassed by some of their comments in the past?  Or is such openness
}something they would welcome?
}
}Perhaps we could start off with an explanation (for the benefit of
}people who don't know) of how the CA-DOM committee makes decisions,
}the draft copy of the new CA-DOM rules, and an introduction (again for
}the benefit of people who don't know who they are, which is
}practically everyone) of the members of the committee, and the
}official observers.  

Currently this is the most often stated request I've seen from people
who are not on the committee. Regardless of which side of the fence
they sit on. 

Perhaps someone on the CA-DOM committee can comment. We know you're 
out there. (Hi Ed and John!)

-- 
Stuart Lynne <sl@wimsey.com> ......................... UNIX Facsimile Software
Wimsey Information Technologies ................... moderator biz.sco.binaries
uucp login:nuucp passwd:nuucp .................... ftp.wimsey.com:~ftp/ls-lR.Z
PD Software for SCO UNIX .................... ftp.wimsey.com:~ftp/pub/wimseypd
Newsgroups: can.domain
From: daniel@nstn.ns.ca (Daniel MacKay)
Subject: Candian Domain Information, By Gopher!
Organization: NSTN Network Operations Centre, Nova Scotia, Canada
Date: Sun, 3 Jan 1993 00:15:00 GMT

Hello!

This seems an appropriate place to remind people that Canadian Domain
information is available for your searching and browsing pleasure in the
NSTN gopher.  Point your gopher at

	nstn.ns.ca

If you're one of the unfortunate few without your own gopher client, telnet
to that address and log in as "fred" to use our experimental, nonproduction
public access gopher client.

In either case, select _White Pages_ from the main menu.  Then browse
through organizations in the _Canadian Organizations_ directory, or search
on full words (e.g. "macmillan") using the search menu item.  There are
keywords for cities, people, organizations, and a little paragraph on each
entity, so you may be able to do some creative searching.  Items in this
directory are kept in sync with the official ones by weekly updates.

In any case, enjoy.  Send bricks, send bouquets, send money, to the address
below.
--
	Daniel MacKay				daniel@nstn.ns.ca
	NOC Manager, NSTN Operations Centre	902-494-NSTN
	Dalhousie University, Halifax, Nova Scotia, Canada
Newsgroups: can.domain
From: sl@wimsey.bc.ca (Stuart Lynne)
Subject: Re: Domain naming conventions
Organization: Wimsey Information Services
Date: Sun, 3 Jan 1993 02:06:50 GMT

In article <1993Jan2.234428.886@cs.UAlberta.CA> cdshaw@cs.UAlberta.CA (Chris Shaw) writes:
>In article <C08zs2.4uG@wimsey.bc.ca> sl@wimsey.bc.ca (Stuart Lynne) writes:
>
>Oh, I see. To EMail something, I have to telephone the post office or my
>corresponent. Why don't I just ditch EMail altogether & use the phone?

Ok. Tell us all how you send email to someone if you don't already have
their email address. Pay special attention to how it will be different
between the two proposed schemes. 

>False, in this instance. Canada Post mandates one correct addressing method,
>and it works. The same can be true in this instance, although I don't think
>that the number of domain names warrants a normative scheme just yet.
>Maybe in the USA this is not the case.

>
>>Is there any technical problem with 
>>supporting some small number of different ways to select a name. I.e. you
>>get your choice of tdkcs.waterloo.on.ca OR tdkcs.n2j.ca OR some other
>>scheme that doesn't clash and is desired by some large body of users. 
>
>The only problem is to make sure everyone implements it. I'd be willing to bet
>that the place-name format (eg waterloo.on.ca) will be the method of choice
>for 98% of users, however. 

What's to implement. You have an MX record pointing n2j.ca to a forwarding
point. How is that different from having an MX record pointing to 
waterloo.on.ca. What is the problem with having both in place if they
are both being used. It takes a few extra lines in the authoritative server's
named setup.

E.g. in /etc/named.boot

	primary		v3h.ca			named.demo
	primary		port-moody.bc.ca	named.demo

In /etc/named.demo
	   IN SOA van-bc.wimsey.bc.ca. hostmaster.wimsey.comn. (
		19930101001
		900
		300
		12096
		3600
		)
	   IN A 192.48.234.1
	*  IN MX 100 mail

Note that you only need one file, both v3h.ca and port-moody.bc.ca domains
can be adequately described by it. So it boils down to adding one line
into /etc/named.boot if you already have one setup.

Assuming John Demco delagated authority to my machine for v3h.ca and
port-moody.bc.ca I would be able to act as generic forwarder for all
sites in port-moody and in the area delineated by v3h.

The US domain is using distributed servers at this level. RFC1386 lists
a number of existing zones that have been delagated in this fashion (for
forwarding to city.state.us, they do not have the concept of using the
postal code). For example TUCSON.AZ.US is delagated to leonard.arizona.edu.

-- 
Stuart Lynne <sl@wimsey.com> ......................... UNIX Facsimile Software
Wimsey Information Technologies ................... moderator biz.sco.binaries
uucp login:nuucp passwd:nuucp .................... ftp.wimsey.com:~ftp/ls-lR.Z
PD Software for SCO UNIX .................... ftp.wimsey.com:~ftp/pub/wimseypd
Newsgroups: can.domain
From: smd@uunet.ca (Sean Doran)
Subject: Re: registration -vs- forwarder policy
Organization: UUNET Canada
Date: Sun, 3 Jan 1993 07:56:22 GMT
Distribution: can

bdb@becker.GTS.ORG (Bruce Becker) writes:

>	I'm wondering whether the .CA domain people
>	do anything at all vis-a-vis the DNS, & if
>	so, what system is by default authorative
>	for new registrations when they are approved?

One of two things goes into a file maintained by John Demco (as
hostmaster@cdnnet.ca) when there is either an Internet forwarder or
nameservers for a subdomain of CA.

The first is essentially:

bar.yk.ca.	IN	MX	10	internet-forwarder.ca.
;(with other MXers as appropriate)

The second is just as simple:

foo.yk.ca.	IN	NS	nameserver.ca.
		IN	NS	nameserver.net.

This is hardly stunning; it's the proper way to run a zone in the DNS.
The system is simple: if there's a "Forwarder: Internet: foo.bar;" line
in the form, then foo.bar is listed as MXers as in the first example
above.  If the form lists "Forwarder: Internet: DNS;" and also lists
nameservers, the result will look like the second example.

John Demco does check to make sure that the nameservers are giving
sane answers, which is rather nice of him (and also probably saves him
large amounts of grey hair).  I doubt that he checks to make sure that
MXers can handle mail -- that is usually non-trivial.  However, he
probably does check to make sure that the targets of the MX records
have A RRs in the DNS, and maybe that they are routed somewhere
sane-ish.

	Sean.
Newsgroups: can.domain
From: eah@xenitec.on.ca (Ed Hew)
Subject: Re: can.domain
Organization: XeniTec Consulting, Kitchener, Ontario, CANADA
Distribution: can
Date: Mon, 04 Jan 1993 03:54:12 GMT

In article <381@unbc.edu> lyndon@unbc.edu (Lyndon Nerenberg) writes:
>Given the highly political nature of the *current* .ca old boys club,
>how could an openly elected group be any *worse* ???

Lyndon, are you aware that in addition to many experience voices in
the .ca "old boys" club, as you put it, there are quite a few newer
committee members?  I was invited to join the CA Domain Committee
just this last March, and there have been a number of newer additions
since then.  I'm aware of yet another membership invitation that went
out just this last week to ensure even better representation of all
the facets of the Canadian networking community.

Then, just to ensure that the committee doesn't miss any voices with
useful suggestions to contribute, a USENET newsgroup was just recently
created, can.domain.  For your information, various members of the
committee are actively monitoring these discussions, and a couple of
very useful can.domain comments have already made it into committee
discussions.  Being the party who's facilitated this communication,
I know this to be fact.

I think you'll be pleasantly surprised at some of the communications
that I expect will be coming the other way in the near future as well.

It's my intention that everyone with something useful to say is being
heard, and that no one will be operating in the dark.

                --ed            (Ed Hew)
--
        Canadian UUCP Map Coordinator           <path@cs.toronto.edu>
   ==>  UUCP liason to .CA Domain Registry	<registry@cs.toronto.edu>
        XeniTec Consulting Services             <edhew@xenitec.on.ca>
Newsgroups: can.domain
From: John Demco <demco@cs.ubc.ca>
Subject: CA statistics
Submit-To: candom@xenitec.on.ca
Organization: [resent by] The CANDOM gateway and Propagation Society
Date: Sat, 2 Jan 1993 05:46:00 GMT
Resent-By: registry@xenitec.on.ca
Precedence: bulk

Hi, here's a summary of the CA subdomain registrations to date.
--John

CA Registered Organizations by Scope                 as of January 1, 1993

Year    AB   BC   MB   NB   NF   NS   NT   ON   PE   QC   SK   YK   CA  Total
----    --   --   --   --   --   --   --   --   --   --   --   --   --  -----
1988     1   11    0    0    0    0    0    2    0    0    0    0   43     57
1989     3   10    0    0    0    0    0    9    0    1    0    0   15     38
1990     4    8    0    0    0    3    0    3    0    2    0    0   21     41
1991    11   12    4    0    4   12    0   22    1    3    2    0   34    105
1992    20   33    6    3    4    7    0   61    0   18    5    1   46    204
----    --   --   --   --   --   --   --   --   --   --   --   --   --  -----
Total   39   74   10    3    8   22    0   97    1   24    7    1  159    445


CA Registered Organizations by Classification

Year           Commercial  Educational   Government        Other        Total
----           ----------  -----------   ----------        -----        -----
1988                    8           42            3            4           57
1989                   18           14            5            1           38
1990                   18           14            5            4           41
1991                   52           20           17           16          105
1992                  114           40           23           27          204
----           ----------  -----------   ----------        -----        -----
Total                 210          130           53           52          445


John Demco, CA Domain Registrar       E-mail: demco@cs.ubc.ca
Department of Computer Science        Tel: +1 (604) 822 6724
University of British Columbia        Fax: +1 (604) 822 5485
Vancouver, BC, Canada  V6T 1Z2
Newsgroups: can.domain