L
luke
http://www.angrycoder.com/article.aspx?cid=1&y=2003&m=7&d=17
I was actually dragged onto the Microsoft technology treadmill in 1992
when they bought out Fox in Perrysburg, Ohio. Yep, I'm one of those
XBase guys who was suddenly jerked out of the '80s (dBase, Clipper,
FoxBase/FoxPro) into the Client/Server gold rush. Kidnapped from the
nether worlds of Unix and Novell I kicked and screamed and finally
learned to like my captors.
....................
Then the announcements from Redmond started coming about the time I
got my first gig in .NET: "Forget what you knew in COM." and "COM is
dead" and other such statements. So all that hype about the n-tier
approach to design was also dead? I thought this approach was
agnostic; You could as easily apply the principles to Java and it
still made sense! Apparently not...at least according to the experts
at Microsoft.
Since that time, I've had a few more .NET opportunities. And in spite
of Microsoft I've kept things along the n-tier theory. And now, before
the paint has dried on the first release of .NET, a brand new .NET is
released and some noise about how they're hacking up a really good DB
product (SQL Server) so it can do .NET ala Oracle/Java. Well now. I
had to learn Oracle along my travels (at least PL/SQL and stored
procedures), as well as SQL Server stored procedures. So now are all
my abilities in Transact-SQL in peril too? Why do I want to write
stored procedures in C# anyway?
All this change-the-tools stuff is getting under my skin. While I
don't want the stability of COBOL (learn a tool at the beginning of
your career and still be using it on the day of your retirement
party), neither do I want to spend my life chasing the dream. I don't
know how most coders do it, but when I decide to invest in a
technology, I make a serious investment: I spend all of my extra time
and money buying endless streams of $50 books, reading $5 magazines,
researching stuff online and yes, even taking classes. I've given some
very good years to Microsoft's vision and made a decent living in the
process. Is it time for a change?
I was actually dragged onto the Microsoft technology treadmill in 1992
when they bought out Fox in Perrysburg, Ohio. Yep, I'm one of those
XBase guys who was suddenly jerked out of the '80s (dBase, Clipper,
FoxBase/FoxPro) into the Client/Server gold rush. Kidnapped from the
nether worlds of Unix and Novell I kicked and screamed and finally
learned to like my captors.
....................
Then the announcements from Redmond started coming about the time I
got my first gig in .NET: "Forget what you knew in COM." and "COM is
dead" and other such statements. So all that hype about the n-tier
approach to design was also dead? I thought this approach was
agnostic; You could as easily apply the principles to Java and it
still made sense! Apparently not...at least according to the experts
at Microsoft.
Since that time, I've had a few more .NET opportunities. And in spite
of Microsoft I've kept things along the n-tier theory. And now, before
the paint has dried on the first release of .NET, a brand new .NET is
released and some noise about how they're hacking up a really good DB
product (SQL Server) so it can do .NET ala Oracle/Java. Well now. I
had to learn Oracle along my travels (at least PL/SQL and stored
procedures), as well as SQL Server stored procedures. So now are all
my abilities in Transact-SQL in peril too? Why do I want to write
stored procedures in C# anyway?
All this change-the-tools stuff is getting under my skin. While I
don't want the stability of COBOL (learn a tool at the beginning of
your career and still be using it on the day of your retirement
party), neither do I want to spend my life chasing the dream. I don't
know how most coders do it, but when I decide to invest in a
technology, I make a serious investment: I spend all of my extra time
and money buying endless streams of $50 books, reading $5 magazines,
researching stuff online and yes, even taking classes. I've given some
very good years to Microsoft's vision and made a decent living in the
process. Is it time for a change?