Advertisement
If you have a new account but are having problems posting or verifying your account, please email us on hello@boards.ie for help. Thanks :)
Hello all! Please ensure that you are posting a new thread or question in the appropriate forum. The Feedback forum is overwhelmed with questions that are having to be moved elsewhere. If you need help to verify your account contact hello@boards.ie
New job is VB.Net
Options
Comments
-
Righteo lads, almost 6 months later....
... and in that time I've worked on two code bases, both vb.net, one .net 2.0 (mostly a 1.1 conversion) and the other .net 1.1.
Can't see this going anywhere quickly, just bug fixes and feature requests on top of what is there... Time to start looking around again
D.0 -
Sounds like a bait and switch.
The silver lining is you should get a pay rise when you move.
(And don't believe them when they tell you they'll put you on more interesting projects when they get your letter of resignation)0 -
Righteo lads, almost 6 months later....
... and in that time I've worked on two code bases, both vb.net, one .net 2.0 (mostly a 1.1 conversion) and the other .net 1.1.
Can't see this going anywhere quickly, just bug fixes and feature requests on top of what is there... Time to start looking around again
D.
Where are you based?0 -
-
-
Advertisement
-
-
The silver lining is you should get a pay rise when you move.
I'm on an okay daily rate (direct), I've no complaints in that regard. I made big bucks on a (direct) Delphi contract for a few years, but gave it up in the end as the technology was so out of demand I felt that I had to move on. Disappointed to be using old technologies again - don't need to be leading edge but want to be more relevant (and interesting).
Dublin 8.Where are you based?
Tell me about it. Did i mention that not long after I started the senior guy left, who was the only guy left after the mass exodus of '08. All then landed on my shoulders. Welcome to sh(I).TDublinWriter wrote: »...welcome to I.T.
I don't really like the code base as is. While there was efforts when it was originally written in the mid-90s to layer the code base, putting all your data access classes in a class library with data somewhere in the name does not a data access layer make. Apparently there used to be shouting matches about such things in the past /sigh/. I've struggled with poor encapsulation and some weird and unexpected state management. The design then seems to push a lot of logic back into the UI layer with never ending IF THEN ENDIFs, it makes vb.net look very bloated and verbose when in reality even C# on top of these class libraries would suffer the same faith.Colonel Panic wrote: »Well yeah, but better to do bug fixes and features on top of a more up to date code base if you can help it!
Some work has been done but there are a couple of reasons we can't run with it at the moment. But that still leaves 1.1 era code and for instance a funky so called data access layer. My initial urge was to work off -radar and bring stuff back in, but I've enough of this stuff during the day to want to work on it in the evenings...Earthhorse wrote: »Could you update the code base to something more recent? Might be a nice little project for you if you're finding it easy.
D.0 -
Advertisement