Re: struggling with Design -Paradigms
- From: "Nick Malik [Microsoft]" <nickmalik@xxxxxxxxxxxxxxxxxx>
- Date: Mon, 19 Feb 2007 01:27:47 -0800
"arnuld" <geek.arnuld@xxxxxxxxx> wrote in message
news:1171206968.805646.45650@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
hai all,
1st of all, thanks for the replies, to my earlier post, and now with
your help (the comp.object folks :-) the confusion has gone, i am
very clear on my goals but still i have some difficulties. i will be
brief:
i do understand the meaning of variables,objects,function as i have
done some Lisp, so i can say i am not a complete newbie.
Lisp is not exactly the most common starting place. It is not procedural,
and most of the 'problems' that can be solved with OO 'solutions' are
problems that are most typically seen in procedural approaches to problems:
to whit: functional decomposition. Therefore, to move to an OO solution,
you are going to have to learn something procedural. It is a prerequisite.
yes, i have
written some trivial programes too and i can understand books written
for programmers (like Programming Ruby) but cannot understand books
written for for much experienced programmers (like Stroustrup's TC++PL
3/e). since i have never done any professional coding at some company
so i consider myself a beginner.i want to go directly to OOD (without
learning any anything else like procedural paradigm or algorithms).
Is this right way?
Don't think it is possible. It's like jumping to physician without a firm
understanding of biology and organic chemistry. You'd make a pretty weak OO
programmer if you couldn't see the solution in the procedural paradigm as
well as the OO paradigm. Honestly, there are times (frequently) when
encapsulation = overkill. If you don't have firm chops in procedural
development, you can't see your alternatives.
i will be looking for a job using C++ but searching the archives of
this newsgroup tells me that is not a good idea. hence, is it OK to
go to through path:
OOA-D -> OOP using Eiffel/Ruby -> C++
?
I'm a little biased on this point. I think you dump C++ completely. Go to
C# (oh, OK, you could go to Java too ;-). I'm sure there are a lot of jobs
in other languages, but the last time I checked, the most common languages
for hiring new developers into the field were in established places like C#
and Java. (Learning either will help with the other... double your
chances... learn both).
Once you are in the field and working for a few years, find your 'up and
coming' language and move. I think Ruby on Rails is pretty cool, as is
Python. Your career won't be defined by a programming language. In fact,
I'd be surprised if you wrote code in the same language for more than a few
years before switching to another one. It happens all the time.
--
--- Nick Malik [Microsoft]
MCSD, CFPS, Certified Scrummaster
http://blogs.msdn.com/nickmalik
Disclaimer: Opinions expressed in this forum are my own, and not
representative of my employer.
I do not answer questions on behalf of my employer. I'm just a
programmer helping programmers.
--
.
- Follow-Ups:
- Re: struggling with Design -Paradigms
- From: arnuld
- Re: struggling with Design -Paradigms
- References:
- struggling with Design -Paradigms
- From: arnuld
- struggling with Design -Paradigms
- Prev by Date: Re: Relational-to-OOP Tax
- Next by Date: Re: The reality of Topmind (Was: Topic-Organized Object-Oriented Programming)
- Previous by thread: Re: struggling with Design -Paradigms
- Next by thread: Re: struggling with Design -Paradigms
- Index(es):
Relevant Pages
|