The concepts you have repeated throughout your posts, like reflection, generics,
and threading, are not new concepts. They are, however, programming 'buzzwords'
for examinations and managers due to being brought to the forefront with
newer language implementations such as Rails, C#, and Java. In time, these
words will become as 'boring' as class, interface, and inheritance.
The .NET framework is not the first to support these concepts and will not
be the last. Yeah, that's right, something will replace what we're doing
today (heck, there are days that it feels that new methodologies are coming
up before I even get a chance to wrap my arms around the current stuff!--that's
why I like this job!). But in the end, the underlying concepts remain the
same--only implementation changes--whether you're jumpering ad on/off bit
with a wire or doing it using code in some high level programming language;
the logic persists.
Part of being a programmer/developer/architect/whatever is having the understanding
of core computing concepts and design principals and how they apply to a
particular situation--and then apply it. The IDE, syntax, and even the model
can change without consequence at that point. The MSFT tests test functionality
in a certain programming modal--which, agree or disagree, is not what makes
a programmer at the end of the day. Anyone (maybe) can string together syntactical
goo.
If you're really concerned about not falling behind, my suggestion is to
focus on concepts of OOP, design practices, and such--and move forward without
worrying about what environment you're targeting. As Mike suggested a few
posts ago--if you're interested in MSFT, grab the free Express products and
spend some time with them. Create a console app, and then figure out what
it takes to make it into a web application, or a Smartphone application.
If you're more into Open Source, grab VMWare, a Linux distro and load up
Rails. Use your current knowledge as a grounding and go from there.
This is probably both the most difficult concept of learning modern development--figuring
out where to start!
Good luck.
-dl
--
David R. Longnecker
http://blog.tiredstudent.com
a> me too....
a>
a> I thought Microsoft is going to take care of all the technologies and
a> people should concentrate more on their business logics...to me (as a
a> developer / designer) this looks more work...Learning lots of new
a> things and spending so many hours which one will be the best solution
a> for longer run. Our products still good with older technologies and
a> customers are very happy we dont see any desire to move to .NET. I
a> bet there might be many such companies who are happy with older
a> investments. I can still expedia.com site still good on classic ASP
a> (thats what I can see in browser that its still pointing to .asp).
a>
a> I even dont have working expereince with Reflection, Generics, App
a> Domain, Threading, Code Access Security, Delegates. If I dont learn
a> these things asap then it will not take time to become obsolete in
a> the market. My 13 yrs expereince will go in vain within no time.
a>
a> When I will learn these things the job I will get will not use these
a> things so again skills will be wasted and by the time new things will
a> come up and I will start leaning those. etc etc
a>
a> Nowadays, I have a gut feeling that software development by
a> introducing new technologies is just another money making business.
a> You come up with new things...people buy books, expensive training
a> materials..all these things are connected...but ultimately customer
a> suffers and again big IT budget...
a>
a> Masudur wrote:
a>
Hi,
abcd wrote:
I am working on Vistual Studio since last 10 yrs. Working from VC++
1.x and VB 3.x. Currently I am working in VS 6.0, classic ASP, COM,
ADO. Today its called as old technologies. I have very novice++
expereince with .NET. Recently I appeared for one intvw and that
guy just blasted me and FAILED me . He asked CAS, threading, App
domains, concurrency ADO.NET, and lots of advanced .NET questions
even I have not encountered reading those. I know I am working on
Visual C++, MFC, ATL, VB 6.0 since many years. I can handle dot net
too once the responsbiliities come. My currently products are in
old technologies and thats what I sped most of my day working in
those technologies and not getting enough practical exposure to new
.NET things...
How should I handle this issue.
[if this is not the correct group to discuss this topic then kindly
excuse me]
thanks
Actually, you're in quite a nice position, because it has never been
so easy to learn technology independently, without going to follow
an
expensive course. The web has so many resources allowing you to
learn at home.
Choose wisely which technologies you learn, though. Learning Windows
Forms (.NET Windows Applications) is not recommended, since this
technology will eventually disappear and be replaced by WPF. My
recommendations for learning are:
- WPF
- WCF
- ASP.NET
- Silverlight
- LINQ
- ADO.NET
That's a lot already, so take it one step at a time.
Courage,
Laurent
--
Laurent Bugnion [MVP ASP.NET]
Software engineering, Blog:
http://www.galasoft.ch
PhotoAlbum:
http://www.galasoft.ch/pictures
Support children in Calcutta:
http://www.calcutta-espoir.ch
boy...
i am getting afraid now... of all these stuff...
i have to learn lot of things
new and new things are coming...
