[#4766] Wiki — "Glen Stampoultzis" <trinexus@...>

21 messages 2000/09/04
[#4768] RE: Wiki — "NAKAMURA, Hiroshi" <nahi@...> 2000/09/04

Hi, Glen,

[#4783] Re: Wiki — Masatoshi SEKI <m_seki@...> 2000/09/04

[#4785] Re: Wiki — "NAKAMURA, Hiroshi" <nakahiro@...> 2000/09/05

Howdy,

[#4883] Re-binding a block — Dave Thomas <Dave@...>

16 messages 2000/09/12

[#4930] Perl 6 rumblings -- RFC 225 (v1) Data: Superpositions — Conrad Schneiker <schneik@...>

Hi,

11 messages 2000/09/15

[#4936] Ruby Book Eng. translation editor's questions — Jon Babcock <jon@...>

20 messages 2000/09/16

[#5045] Proposal: Add constants to Math — Robert Feldt <feldt@...>

15 messages 2000/09/21

[#5077] Crazy idea? infix method calls — hal9000@...

This is a generalization of the "in" operator idea which I

17 messages 2000/09/22

[#5157] Compile Problem with 1.6.1 — Scott Billings <aerogems@...>

When I try to compile Ruby 1.6.1, I get the following error:

15 messages 2000/09/27

[ruby-talk:4995] Re: Ruby Book Ch 2 English -- arguments/parameters/options?

From: schneik@...
Date: 2000-09-18 18:57:24 UTC
List: ruby-talk #4995


Jon Babcock wrote:

> Should the explanation read, "Output the parameters sequentially." or
> "Output the arguments sequentially."  Or does it matter?

Not to most people, but somewhere it does, but I don't recall where.

Here is an interesting reference I chanced across a week or so ago,
involving the Professor of Perl OO (among other things :-).

Damian Conway Talks Shop
by Joe Johnston
Aug. 21, 2000
http://www.perl.com/pub/2000/08/conway.html

> Whatever software your trying to build, you need people who are
> inspired by the idea of that software.  Even if they aren't virtuoso
> hackers: you can always teach a person to code better, or tidy their
> code after it's written; you can never teach a person to love your
> project. And without that emotional engagement, you'll never get the
> superhuman effort that's required to produce quality software.
>
> It often seems to me that recruiters ask the wrong questions when
> interviewing programmers. Sure you have to find out if they know the
                            ==========================================
> difference between an argument and a parameter, but it's vastly more
  ==============================================
> important to discover what kind of enthusiasm and energy they're going
> to bring to your project, why they'll put in 18-hour days on it, why
> they'd pay you to work on it. Find those people and you'll get quality
> accounting software.

--
Conrad Schneiker
(This note is unofficial and subject to improvement without notice.)



In This Thread

Prev Next