I am not getting this JOB for sure
-
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.
-
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:
That was to decide if you should be paid the 'developer' rate or the 'senior developer' rate (and be handed tasks accordingly too)...
-
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:
-
You 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.
-
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:
This would be a great answer if no C# user ever had to be aware of memory management issues. Too bad that's not the case. Anyone doing multithreaded programming needs to know about multithreaded contention for the heap. Anyone doing high performance programming needs to know what the costs are of various types of operation, and any time you call the allocator you are definitely going to take a 10,000 cycle nap. There's all kinds of issues around memory alloocation that an experienced C# programmer needs to know, even if none of them are how to call malloc or free.
-
I don't think knowing how does .net frame work allocate memory is going to help me writing more efficient program in C#(ya in C++ and all it's different story) because you can not control it any way. If you can i would definitely like to learn that.
CS2011 wrote:
I don't think knowing how does .net frame work allocate memory is going to help me writing more efficient program in C#
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...
-----
"The conversations he was having with himself were becoming ominous."-.. On the radio... -
This would be a great answer if no C# user ever had to be aware of memory management issues. Too bad that's not the case. Anyone doing multithreaded programming needs to know about multithreaded contention for the heap. Anyone doing high performance programming needs to know what the costs are of various types of operation, and any time you call the allocator you are definitely going to take a 10,000 cycle nap. There's all kinds of issues around memory alloocation that an experienced C# programmer needs to know, even if none of them are how to call malloc or free.