In the last decade the roadrunner heavily invested in himself to get familiar with Java (J2EE) development.
Now the roadrunner could call himself a specialist, but that sounds rather arrogant.
Now another development platform is really booming: .net.
And wher there is a choice, a choice will be made.
Check this link:
http://www.computerworld.com/developmenttopics/development/story/0,10801,71221,00.html
Quotes:
Corporations will find it tough to settle on a single development architecture such as .Net or Java 2 Enterprise Edition (J2EE), "unless they are the size of a dentist's office," says Yefim Natis, an analyst at Gartner Inc. in Stamford, Conn.
Take stock of your existing developer skills and infrastructure.Training developers and ripping out existing infrastructure can be costly, so an IT shop may favor sticking with the development environment that best fits its current situation.
Investigate outside vendor support. Murphy says that users who buy major packaged applications will probably be driven to gain some Java skills, since enterprise software vendors such as SAP AG and Oracle Corp. lean toward Java.
The question the roadrunner is struggling with is this:
I did not learn Java in 21 days.
How much time and effort would it take to master .net?
Sorry, but the roadrunner does not trust this promise.
Getting used to a new IDE (http://en.wikipedia.org/wiki/Integrated_development_environment) , is one.
Now I am very pleased with Eclipse!
Really understanding, feeling and smelling the code is yet another challenge and will definitely take much more then 21 days.
Even if you spend 24 hours per day, which is not feasible.
See the content (http://www.informit.com/library/library.aspx?b=Net_2003_21days):
- Week 1: At a Glance
- Day 1. Introduction to the Microsoft .NET Framework
- Day 2. Introduction to Visual Studio .NET
- Day 3. Writing Windows Forms Applications
- Day 4. Deploying Windows Forms Applications
- Day 5. Writing ASP.NET Applications
- Day 6. Deploying ASP.NET Applications
- Day 7. Exceptions, Debugging, and Tracing
- Week 1. In Review
- Week 2: At a Glance
- Day 8. Core Language Concepts in Visual Basic .NET and C#
- Day 9. Using Namespaces in .NET
- Day 10. Accessing Data with ADO.NET
- Day 11. Understanding Visual Database Tools
- Day 12. Accessing XML in .NET
- Day 13. XML Web Services in .NET
- Day 14. Components and .NET
- Week 2. In Review
- Week 3: At a Glance
- Day 15. Writing International Applications
- Day 16. Using Macros in Visual Studio .NET
- Day 17. Automating Visual Studio .NET
- Day 18. Using Crystal Reports
- Day 19. Understanding Microsoft Application Center Test
- Day 20. Using Visual SourceSafe
- Day 21. Object Role Modeling with Visio
- Week 3. In Review
I am eager how easy (or not) it is to make this move ...
No comments:
Post a Comment