Board index » delphi » Re: Masters in C.S., worth it?

2003-08-06 10:01:14 PM
delphi173
 

Lauchlan M writes:
to reach the .NET galaxy, but you get to use your Delphi language skills
in a .NET environment. It is because of this I am thinking of going with
JBuilder. At least Java is a different galaxy. In DFW, Java jobs still
out number C#/.NET jobs according to Dice.
 

the other half of the time?
(BTW, my first impressions were also that I liked C# better for the syntax,
but I have come around to the point where I don't see such big differences).
Lauchlan M
 

"Brian Moelk" <XXXX@XXXXX.COM>writes
supposed to mean?
--
Clay Shannon, author of "the Wacky Misadventures of Warble McGorkle"
Download it at tinyurl.com/cent
 

"Sierra Spartacus" <XXXX@XXXXX.COM>
writes news:XXXX@XXXXX.COM...
Chris Burrows
CFB Software
www.cfbsoftware.com
 

"Chris Burrows" <XXXX@XXXXX.COM>writes
have to do with declaring a variable? A variable is not a dimension, nor
does it look, sound, smell, or taste like one. "Dim" as a keyword seems
nonsensical and nonsequiterial. it is as if someone were to begin every
paragraph with the word "Kumquat" (or perhaps more accurately, every place
where the word "yesterday" is to appear, you replace it with the word
"pickle").
I think Edsger was right about BASIC (see DavidI's latest "Sip From the
Firehose" for his exact quote).
--
Clay Shannon, author of "the Wacky Misadventures of Warble McGorkle"
Download it at tinyurl.com/cent
 

"Sierra Spartacus" writes:
-Luk-
 

"Dan Barclay" <XXXX@XXXXX.COM>writes
something, after all.
I'm not crazy about "=" as an assignment operator, as that would make more
sense as the equality operator. IOW, if logic prevailed, C#'s assignment and
equality operators would be reversed. I also see nothing wrong with
"{}"--it's a lot faster than typing begin and end (albeit a little less
clear).
--
Clay Shannon, author of "the Wacky Misadventures of Warble McGorkle"
Download it at tinyurl.com/cent
 

Sierra Spartacus writes:
Misadventures of Warble McGorkle".
Get outta here...
-- Hairy <dumbfounded but not whacky>
 

"Sierra Spartacus" <XXXX@XXXXX.COM>
writes news:3f3392fc$XXXX@XXXXX.COM...
You give up some flexibility in what you can do with experession evaluation
but not a great deal. Of course ".EQ.", as God intended it, would solve all
those concerns<g>. While we're at it, .NOT., .AND. and .OR. are not given
near enough credit.
of lines work fine for end of statements as well (x ";").
Dan
 

name. Later it was used to declare any variable, especially after people
started using Option Explicit all the time (a principle taken from Pascal,
I'm sure).
Oliver Townshend
 

"Dan Barclay" <XXXX@XXXXX.COM>writes
cases IF no distinction is made between single-statements and
compound-statements. 'End' involves typing only one additional character
than {}and is much easier to see. I have a lot of difficulty distinguishing
between '{' and '('.
e.g.
for i := 1 to 10 do
singlestatement;
end;
for i := 1 to 10 do
statementOne;
statementTwo;
end;
Chris Burrows
CFB Software
www.cfbsoftware.com
 

"Chris Burrows" <XXXX@XXXXX.COM>writes
1, and so you end up with the same number of lines with or without "begin"
provided you write example 1 like this:
for i := 1 to 10 do
singlestatement;
--
Clay Shannon, author of "the Wacky Misadventures of Warble McGorkle"
Download it at tinyurl.com/cent
 

Scott Metzger writes:
newsgroups, join no user groups or professional organisations, don't
go to conferences, etc., etc.
interview.
another 12 months. Gaps in experience you need like a third armpit!
*can* retire. I still do some software development (Delphi, Access
and Word VBA) - keeps me in beer and skittles. I don't advertise or
even really 'network'. My work comes from referrals from other
clients and some other consultants who know I won't let their
clients down. I have been offered full and part time work from some of
these clients, because I genuinely *understand* their problems and
customise solutions that really work. Many have been previously
burnt by cowboys - there's lots of those around.
As I got older, I wondered how to stay ahead of the kids. The truth
of the matter is that if you have only the same effective experience
of a kid, you will lose against them, so you have to play it smart.
You have to understand people and business as well as the technical
issues and if you haven't been working on this for 20 years, it's
probably too late to start. In any case, you start by working out
what your boss needs to know, and his boss, so you can be of more
value to them.
Almost all kids are wet behind the ears when it comes to almost
anything except design, code and test. To get a job, you need to
have these skills plus the advantages of maturity. Certain skills,
like systems engineering in general, requirements engineering,
configuration management, quality management, risk management,
people management, and so forth *need* to mature, and it is rare
finding anyone under 30 who really understands them. So take a
'total' approach to your job, lift your eyes, and learn what the
world of software engineering's all about. I am not saying you have
to become a manager or even a team leader (I never was), but you
need to understand the ins and outs of these roles.
You also need to keep up technically, which involves a lot of work,
typically 10-20% on top of your 40-60 hours a week. Find out what's
new and likely to persist and learn about it. Volunteer for work
that's new and exciting and where you can learn on work time (yes,
it sometimes happens). Go to conferences and trade shows. You'll
never keep totally up with the kids in this regard, but you can
still know much more than most of em do. This group and others are
good, so are some magazines (I used to read them on planes). Also
learn how organisations work.
Work on doing things more efficiently than anyone else. This takes
time and knowledge to achieve, but its the key to being a valuable
employee.
In interviews, avoid bullshit slime pitches - there'll be enough
other candidates trying this on - and concentrate on your proven
ability to solve problems, even where the problems extend beyond the
code (and most of them do). Don't *push* your maturity and
experience at the expense of the technical task - you still need to
be able to do the job.
Finally, expect to lose a few. Remember that the interviewers may
not value what you offer, whether they need it or not. that is OK -
you don't want to work for them anyway.
There are plenty of gray-hairs out there making good money, believe
me. But most of them are very, very good at what they do, and they
love their work.
Andrew
--
Andrew Gabb
email: XXXX@XXXXX.COM Adelaide, South Australia
phone: +61 8 8342-1021, fax: +61 8 8269-3280
-----
 

On 09-Aug-03, Sierra Spartacus said:
--
Bill
--------
In a free society, government has the responsibility of protecting us from others, but not from ourselves. -- Walter Williams