I am not getting this JOB for sure
-
Went for a job interview today after the basic question on .net Framework he asked some question on memory management. I answered the question like GC and others…Then he went on to ask “How does .net framework allocate memory” and my answer was… If I wanted to know that I would have learned C or C++ and not C# and If I remember correctly I am here for C# interview and .NET framework does the memory management for me(Well most of the time). :laugh:
I had an interview at Sony in Wales years ago which was worse. A bit into the interview the interviewer aked is I could document someone else's code (alarm bell at 3) and then told me I'd got a bit of C code to copy a string wrong and when I did the
forloop expansion it became clear he didn't write any code and why the previous worker had quit and the code was unfinished. The alarm bell was at 11 and I got my running shoes on.Join the cool kids - Come fold with us[^]
-
So, in your opinion, a .NET developer is not supposed to know that ? I can accept that one does not need to know the internals in detail but they should at least have some basic knowledge of how it works. For that matter why even a C++ or a C developer need to know that. He can say that all I do is to call new or malloc and memory gets allocated for me.
[EDIT]
Rama Krishna Vavilala wrote:
have some basic knowledge of how it works
I don't think that "How does framework allocate memory" falls under basic category and to put it in nutshell you must know the metadata to understand and explain this. For example how does framework decide that it will allocate the memory on heap or stack is based on the metadata which is again based on the type you have declared while writing the program(infarct it's the compiler who generates the instruction and little tweak here will change a lot of things but again...) but when it comes to dependency properties the funda is totally different then normal. and again you need to know many things here eg. why does not framework allocate memory for different instance of class until the default value is changed or how it is doing that. But i really don't think its a falls under basic category at all. [/EDIT} Well i never said a thing about knowing it or not (in facet i know how does frame work allocate memory)only thing i was asking was the question relevant after i have answered all most all the questions on Dispose and GC and other framework related questions
modified on Saturday, March 5, 2011 1:21 PM
-
I had an interview at Sony in Wales years ago which was worse. A bit into the interview the interviewer aked is I could document someone else's code (alarm bell at 3) and then told me I'd got a bit of C code to copy a string wrong and when I did the
forloop expansion it became clear he didn't write any code and why the previous worker had quit and the code was unfinished. The alarm bell was at 11 and I got my running shoes on.Join the cool kids - Come fold with us[^]
-
yep...they do ask stupid question some time knowingly to test you and some time they just don't know what the heck they are talking about :thumbsup:
-
Went for a job interview today after the basic question on .net Framework he asked some question on memory management. I answered the question like GC and others…Then he went on to ask “How does .net framework allocate memory” and my answer was… If I wanted to know that I would have learned C or C++ and not C# and If I remember correctly I am here for C# interview and .NET framework does the memory management for me(Well most of the time). :laugh:
CS2011 wrote:
“How does .net framework allocate memory”
Response: One byte at a time... like when you're eating a bacon sandwich.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997 -
CS2011 wrote:
“How does .net framework allocate memory”
Response: One byte at a time... like when you're eating a bacon sandwich.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997 -
Went for a job interview today after the basic question on .net Framework he asked some question on memory management. I answered the question like GC and others…Then he went on to ask “How does .net framework allocate memory” and my answer was… If I wanted to know that I would have learned C or C++ and not C# and If I remember correctly I am here for C# interview and .NET framework does the memory management for me(Well most of the time). :laugh:
Well, for a StringBuilder it generally starts at sixteen characters and then doubles if it needs more.
-
Went for a job interview today after the basic question on .net Framework he asked some question on memory management. I answered the question like GC and others…Then he went on to ask “How does .net framework allocate memory” and my answer was… If I wanted to know that I would have learned C or C++ and not C# and If I remember correctly I am here for C# interview and .NET framework does the memory management for me(Well most of the time). :laugh:
CS2011 wrote:
If I wanted to know that I would have learned C or C++ and not C# and If I remember correctly I am here for C# interview and .NET framework does the memory management for me(Well most of the time)
Well, most of the time.
-
CPallini wrote:
Q: “How does .net framework allocate memory?”
A: "I don't need to know that in most cases, so .NET has executed Garbage Collection on that piece of allocated information."
I wasn't, now I am, then I won't be anymore.
-
Went for a job interview today after the basic question on .net Framework he asked some question on memory management. I answered the question like GC and others…Then he went on to ask “How does .net framework allocate memory” and my answer was… If I wanted to know that I would have learned C or C++ and not C# and If I remember correctly I am here for C# interview and .NET framework does the memory management for me(Well most of the time). :laugh:
I see from your other posts that you were offered the job, but you are not accepting the offer. Please don't tell me that's just because of this question.
-
Mark Wallace wrote:
They probably only asked the question to weed out candidates who invent stuff to fill gaps in their knowledge, and to help spot bad team players
Yes that might be true but don't you think when the JOB Title say "C# win forms Developer" there should be at least about 10% of question based on C# language my interview lasted for more then one hour and only Question related to c# was "How C# is different from Java". Well i have just received the mail from them and they have offered me the position on senior developer and i really do not understand why...i guess life is unexpected. :) [Edit] and i have decided not to join the organization[/Edit]
modified on Saturday, March 5, 2011 11:13 AM
-
I see from your other posts that you were offered the job, but you are not accepting the offer. Please don't tell me that's just because of this question.
-
Nop...not 'coz of the question but their attitude...i didn't felt like working for those guys
Yeah, I had that feeling when I interviewed at MySpace. Everybody interviewing me had zero sense of humor. I don't think I saw a single smile while I was there.
-
CS2011 wrote:
“How does .net framework allocate memory”
Response: One byte at a time... like when you're eating a bacon sandwich.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997You know, there are something that just can't be translated to French, and your answer is one of them. just a literal and phonetically (mostly) translation results in not too kid sister friendly!! "une bite à la fois, comme manger un sandwich au jambon" I have a dirty mind.
Watched code never compiles.
-
While I give your response a 5 and it is accurate for most .net developers (I hope) I'm reminded of the person that was hired at a place I worked at didn't know why a DVD wouldn't read in a CD drive. :sigh:
People are more violently opposed to fur than leather because it's safer to harass rich women than motorcycle gangs
That reminds me of once when I called support because my CD drive wasn't working. I had a DVD in it. I know why that wouldn't work though, I just failed to check whether said disk was CD or DVD.
-
Good answer, could you give me, please, any reference?
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]Well, someone here will surely pointer you in the right direction.
-
Went for a job interview today after the basic question on .net Framework he asked some question on memory management. I answered the question like GC and others…Then he went on to ask “How does .net framework allocate memory” and my answer was… If I wanted to know that I would have learned C or C++ and not C# and If I remember correctly I am here for C# interview and .NET framework does the memory management for me(Well most of the time). :laugh:
For every 137 C# developers there should be one who knows how the CLR allocates memory or does GC. The number 137 is determined in the same way all the interview questions are created: scientifically ;). Now, if they wanted you to be that 138th developer and the pay/rank was accordingly you have to know memory allocation in .Net. The other developers do not need to know and if they ran into a snag they either go to the 138th developer or they use Google or read a book and find out relatively easy how it is done. We tend to forget that the frameworks are created to make the life easier for most of us and concentrate on the business side of the app and not the memory allocation and similarly deep aspects. When I want to reuse stuff I don't want to learn how stuff does it internally. Today there is no more time for all of us to know everything. Anyway, memory allocation in .Net is an interesting subject and I've read about it in depth 4 years ago. I can't remember much about it and I needed it only once since then. I would be curious of examples when knowledge about internals of .Net memory allocation comes handy in the day to day programming. Cheers, -------------------------------------------------------------- It's an object reference not the kind you mention in a resume.
giuchici
-
Went for a job interview today after the basic question on .net Framework he asked some question on memory management. I answered the question like GC and others…Then he went on to ask “How does .net framework allocate memory” and my answer was… If I wanted to know that I would have learned C or C++ and not C# and If I remember correctly I am here for C# interview and .NET framework does the memory management for me(Well most of the time). :laugh:
They either wanted to know if you knew the difference between the stack and the heap, and when to use one over the other, or were refering to the fact that the GC is good but not perfect, and there are still times when it is necessary to write your Dispose methods.
-
Went for a job interview today after the basic question on .net Framework he asked some question on memory management. I answered the question like GC and others…Then he went on to ask “How does .net framework allocate memory” and my answer was… If I wanted to know that I would have learned C or C++ and not C# and If I remember correctly I am here for C# interview and .NET framework does the memory management for me(Well most of the time). :laugh:
I believe that you answered very well, right up to the point where you told us, but presumably not the interviewer.."most of the time"..and that is the spot in the interview where you could have both A) stomped on the interviewers toes a little, for a reason that surely escapes me, and B) covered those "most of the time" cases and thereby really differentiated yourself from the herd. I think that a slight pause and a calming deep breath would have served your employment search better in this case. The person asking an applicant silly questions may actually be attempting to find wheat amongst the chaff.