2 replies
by lisabates88 Accepted solution
by tony hopkinson Accepted solution
recognised that Delphi was dying in that it was getting harder and harder to get competent Delphi devlopers. So they decided to start switching to C#. I've been involved in this effort, so I'm amassing C# experience to back up the course I went on.
Eevry skill you have in Delphi will carry over into C#, even explicit memory management. ASP.Net is slightly different at the upfront level, but as soon as you get under the covers, in the middle and backend, there's no real difference.
Don't buy into the idea that your Delphi skills have no value, that's bollocks. I've never had a skill that didn't have some value as I accumulated experience in different environments.
To me the shift to C# was hardly any more difficult than from Delphi 5 to 6. Anyone who tell's you different is some HR BS merchant trying to give you a salary cut.
If you can't get your employer to move on, new projects in .NET etc. or say doing .NET components and then calling them through COM from Delphi, look for a new employer, they are damaging your career.
Delphi to C# jobs are quite popular in the UK, very few are sticking with Borland even less are moving to that code gear drivel.
This discussion is closed to new replies.
Trending Web Development posts
Sort by Trending