Difference between c# and VB.Net
-
Marcus_Idle wrote:
asked a fairly open question
My discussion was scheduled at 9:30 AM, and was done at 1:30 PM, till then I had to wait there, with out any satisfactory reasons from the HR dept. I was so frustrated when I went to the panel. Listening to the first question from the panel made me think otherwise.
"Never put off until run time what you can do at compile time." - David Gries, in "Compiler Construction for Digital Computers", circa 1969.
They did not show you much, did they. Not a good start. A job interview is a transaction of importance and they dropped the ball. You sometimes have to deal with humans when you go to these things....and also later, after they hire you...so I guess you will be better prepared next time. :)
-
J4amieC wrote:
I can take any job I please, they are looking for 1 individual. Therefore Im doing them the favour of offering my services, if they don't cut the mustard (and that includes shoddy interview/working practices) I hit the door and walk into the next interview.
In a strong employment market, this is the case. The reality, at the moment, is that I don't need to hire you - there are a lot of others who would be willing to take the job. It's a hirers market at the moment and if you need a job, you can't afford to be that choosy; unless you fancy flipping burgers.
"WPF has many lovers. It's a veritable porn star!" - Josh Smith
As Braveheart once said, "You can take our freedom but you'll never take our Hobnobs!" - Martin Hughes.
Flipping burgers? Have you even tried to get a burger flipping job recently? Good luck there too! ;)
-
It is very rude, though - 30 mins is ok, but 4 hours is taking the mickey! Especially if the interview is pretty early - 09:30 makes it what, the second of the day? If that is the general attitude of the company, then they don't seem to give a monkeys for the staff. I would probably walk out; it's not as if they are paying me to be there...
Did you know: That by counting the rings on a tree trunk, you can tell how many other trees it has slept with.
Not only rude, but indicative of a culture of not meeting expectations.
-
Last weekend I went for an interview in a Reputed organization. The first question from the interview panel was the difference between VB.Net and C#. I just came back!!! Can any one here spot the differences :)
"Never put off until run time what you can do at compile time." - David Gries, in "Compiler Construction for Digital Computers", circa 1969.
This is very limited info that leads to generalizations and plenty of fantasies. If you were applying to a job with customer contact, the question could be a potential customer's question easily answered: "VB is more explicit, easier to understand by non-specialists, C# ist more technical and dense. Both are very similar in function." - or something along these lines. The long waiting time might have served to test your intitiative: Will you ask at all about further proceedings or just wait for your fate to hit you? Are you able to ask it in a polite way? And so on...
-
Last weekend I went for an interview in a Reputed organization. The first question from the interview panel was the difference between VB.Net and C#. I just came back!!! Can any one here spot the differences :)
"Never put off until run time what you can do at compile time." - David Gries, in "Compiler Construction for Digital Computers", circa 1969.
If I had to answer that, I would say don't worry. Try looking at the difference between these languages and F#.
-
I agree in general. But I personally have experience, knowledge and good interview technique. Therefore its always a hiree's market. If a company is after a candidate who is willing to wait 4 hrs without ecxplaination, they're not after me.
-
VB.NETis a crap,C#is a truly advanced language. They are functionally equivalent. :rolleyes:If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler. -- Alfonso the Wise, 13th Century King of Castile.
This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong. -- Iain Clarke
[My articles] -
4 hours is nothing. This is a strategy I may encourage to my employer, to weed out people who don't actually want a job. Or who are to self important.. I waited for 2 hours on a conference call for a client .. 3 work days ago. One of the things that makes an organization respectable is that they WILL WAIT .. PATIENTLY for a client, and not get flustered or become RUDE when that client has the time to interact with the company. Your attitude would not have made it past the interviewing process of my employer.
I'd blame it on the Brain farts.. But let's be honest, it really is more like a Methane factory between my ears some days then it is anything else...
If you want a bunch of employees who have zero loyalty to you and will jump ship at the first better offer, then go for it. Otherwise I'd suggest reevaluating your decision. The funny thing is I can't pick up a business rag without coming across an article/letter/ etc. discussing the inability to keep good people on staff and how much of a problem it can be. The solution is quite simple; it's stupid stuff like this that drives good people away. Sure making someone wait around for no reason will weed out prima-donnas, but even in this economy it will also weed out most people who are competent enough to get a job elsewhere.
-
J4amieC wrote:
I can take any job I please, they are looking for 1 individual. Therefore Im doing them the favour of offering my services, if they don't cut the mustard (and that includes shoddy interview/working practices) I hit the door and walk into the next interview.
In a strong employment market, this is the case. The reality, at the moment, is that I don't need to hire you - there are a lot of others who would be willing to take the job. It's a hirers market at the moment and if you need a job, you can't afford to be that choosy; unless you fancy flipping burgers.
"WPF has many lovers. It's a veritable porn star!" - Josh Smith
As Braveheart once said, "You can take our freedom but you'll never take our Hobnobs!" - Martin Hughes.
-
It doesn't speak well for you or your organization if you think developers are interchangeable regardless of economic conditions. Organizations that have that attitude always end up with a statistically impressive set of third rate programmers. That's because the good ones get tired of not being valued, watching inferior ideas win, etc, and easily can move on, while mediocre programmers eventually realize that they've finally found a job that won't weed them out. This process accelerates until all you have is mediocre programmers that know they suck and count themselves lucky to have a job, and inferior programmers that have yet to figure that out. The only way good programmers come in is via new hires. In other words, by accident, and they leave once they wise up.
If you put the shoe on the other foot - most employees will treat their employers (or potential employers) differently based on economic conditions. If demand exceeds supply then they expect more money (regardless of their skill set) - so why can't employers do the same? This, however, does NOT make it ok to make someone sit for 4 hours - that's just rude.
-
Last weekend I went for an interview in a Reputed organization. The first question from the interview panel was the difference between VB.Net and C#. I just came back!!! Can any one here spot the differences :)
"Never put off until run time what you can do at compile time." - David Gries, in "Compiler Construction for Digital Computers", circa 1969.
I know it’s very late to post the answer... but below are some points from my old college notes.... ........... C#/VB champs validate if anything is wrong.... Advantages VB.NET • Has support for optional parameters which makes COM interoperability much easy. • With Option Strict off late binding is supported. • Legacy VB functionalities can be used by using Microsoft. VisualBasic namespace in VB.NET. • Has the WITH construct which is not in C#.NET. • The VB.NET parts of Visual Studio .NET compiles your code in the background. While this is considered an advantage for small projects, people creating very large projects have found that the IDE slows down considerably as the project gets larger. Advantages of C#.NET • XML documentation is generated from source code but this is now been incorporated in Whidbey. • Operator overloading which is not in current VB.NET but is been introduced in Whidbey. • Use of this statement makes unmanaged resource disposal simple. • Access to Unsafe code. This allows pointer arithmetic etc, and can improve performance in some situations. However, it is not to be used lightly, as a lot of the normal safety of C#.NET is lost (as the name implies).This is the major difference that you can access unmanaged code in C#.NET and not in VB.NET.
-
Agreed: If I don't get seen within 15 minutes of the agreed time I start asking questions and, without a proper reason for the delay, I leave. It's just plain bloody rude to expect someone to give up their time and then keep them waiting without even bothering to tell them why.
me, me, me "The dinosaurs became extinct because they didn't have a space program. And if we become extinct because we don't have a space program, it'll serve us right!" Larry Niven nils illegitimus carborundum
I agree also. It shows a severe lack of respect on there side. Or total incompetence. At my last job, when someone got to the gate of the parking lot, the receptionist would call me to tell me the person was there and I'd walk down to the lobby. More times than not I would be there before the person was. It's just a sign of respect. Especially if they don't even bother to tell the receptionist to tell them I'm running late. If nothing more, if you have to wait so long, unless you are a much better person than I am, you will be annoyed that they kept you waiting so long and the interview may as well not happen. Interviewing is a two way street. Does the company want the person and does the person want to work for the company? Just my two cents.... J.
