There’s also the new bling bling oh look shiny (squirrel) approach, versus the existing and established client base and app approach. Pumping out new apps using the latest buts just shows you’re good at playing with new toys. Improving, expanding, and working with real user bases, develops problem solving and people skills. I’ve worked on apps where we’ve moved existing clients to web based solutions and had to deal with client expectations to have the same keyboard shortcuts, wanting similar screens to their old vt100 emulation screens (well nit that bad, but not far from it). Some do view that as a pain, but clients who have to pay for the changes are the ones who find it most painful if the change is just for change sake.
Learning how to work effectively with existing clients and codebase will develop real skills you can’t get elsewhere. If you want to code with the latest bits pushing out only new stuff, you can do that with the internet and your spare time 😏 Btw: reporting services custom code... just sating😉 From: David Burstin Sent: Tuesday, 13 October 2015 2:19 PM To: ozDotNet Subject: Re: vb.net I think the real message here is - forget the language, just don't work for Nelson's senior. Stubborn a**h**** are not confined to any particular language. :) On 13 October 2015 at 14:14, Nelson <nelson.honey...@gmail.com> wrote: My concern here (regarding the job offer) is not about the language use. i cannot stress enough how a pain in the a** it can be when working with seniors who are reluctant to change and adopt newer better technology. And as a Junior in the team you are basically screwed, especially you started your training with all the modern tech and tools. I had a hard time convincing my senior to switch to ASP.NET MVC from WebForms. although that turn out may not be the best idea - he still code like WebForms way in MVC anyway he still thinks WebForms is superior and can do stuff MVC cant do till this date.... unfortunately you can also imagine how your ideas got banned just because you are the junior and he play the experience game with you. even though that experience translate to sticking to 10-20 years old libraries when there are modern, much more popular alternatives (the best example i think of right now is that he is still using his copy of a 1997 alpha version of date.js library - probably thats the time he started learning js?) I'm not saying VB.NET people are all stubborn and old. but the probability of having to work with a**h*** is just much higher than i like. After all, it won't be a cultural fit for me personally as i'm a state-of-the-art person and would love to work with new technology On 13 October 2015 at 13:53, Bill McCarthy <bill.mccarthy.li...@live.com.au> wrote: Although there’s lots of c ‘style’ languages, the devil is always in the details/differences. I find it hard to switch between c# and js and not forget/mess up. With vb.net and js not so much a problem. The same use to be said for vb and vbscript in days of asp From: David Burstin Sent: Tuesday, 13 October 2015 1:41 PM To: ozDotNet Subject: Re: vb.net I started my .net journey with vb.net, but these days I code C# unless I have to use vb for working with a legacy system. I agree with Bill - there really isn't much difference between using the languages in .net. In fact, knowing my way around the .net framework (from having used it with vb) made the transition to c# much easier. BUT, outside the .net world, I have found my knowledge of C# has helped me in reading (and learning) other languages - eg java, js, ruby. These all have a syntax which is far more like c# than vb. So, if you can only use one language, for me it would be C# - but there is no reason at all that you should be confined to one language. If you are interested in the job, than go for it. Whatever happens, you will learn. Any job provides an opportunity to practice our craft and become better programmers. Plus, you can do projects after hours in whatever language you want :) Cheers Dave On 13 October 2015 at 13:33, Bill McCarthy <bill.mccarthy.li...@live.com.au> wrote: This usually a great rant starter for a Friday conversation. Realistically though Vb.net is much a muchness with c# on .net. Definitely the best language if doing integrated xml. With late binding stuff it has some advantages with better conversions, but also disadvantages such as wider scope. Realistically the biggest disadvantage of vb.net is if you want to integrate some large source code from open licence stuff... usually more is available in c#. From: Tom P Sent: Tuesday, 13 October 2015 12:48 PM To: ozDotNet Subject: vb.net Guys I've been offered a junior dev job but they insist on vb.net only. Does anyone know what is happening with vb.net going forward? I would hate to get stuck into the vb.net world and have it killed off within a few years. Thanks Tom
