H
Hazz
If in an interview next week I was told to Design and Develop Extensible Web
Application Frameworks using Microsoft .NET technologies.
How do I break that question down?
My first temptation would be, "Isn't the existing .NET framework
sufficient?"
My first suspicion that I don't have the experience is that I don't know the
difference between a handlers and a module.
My first attempt to salvage my ego (and watch them cringe silently) would be
to say something like, "I can derive to my hearts content from existing .NET
classes and interfaces." I mean isn't that extensibility?
My clever attempt to hide my slightly less than top tier offering might be
"What are your company's four main use-case scenarios that I would decompose
into objects, accessible through interfaces, to supplement what .NET already
offers.?"
Doesn't Framework mean some prettty serious stuff? Like a whole new
enhancement to something that is already a bit complicated? (Do I have to
tweak http.sys or dream about ISAPI at night?)
With .NET 2.0 asp.net 2.0, c# 2.0, visual studio 2005 coming out in a pretty
complete form by summer, how can I avoid having to say something like, "I
have good general .NET experience and have MCAD certification in VS .NET "
but hang on for a few months while I figure out how I would develop this
..NET extensible Framework you would like based on what I find out about
VS05, Indigo, Windows Activation Service, etc? -----------hazz
Application Frameworks using Microsoft .NET technologies.
How do I break that question down?
My first temptation would be, "Isn't the existing .NET framework
sufficient?"
My first suspicion that I don't have the experience is that I don't know the
difference between a handlers and a module.
My first attempt to salvage my ego (and watch them cringe silently) would be
to say something like, "I can derive to my hearts content from existing .NET
classes and interfaces." I mean isn't that extensibility?
My clever attempt to hide my slightly less than top tier offering might be
"What are your company's four main use-case scenarios that I would decompose
into objects, accessible through interfaces, to supplement what .NET already
offers.?"
Doesn't Framework mean some prettty serious stuff? Like a whole new
enhancement to something that is already a bit complicated? (Do I have to
tweak http.sys or dream about ISAPI at night?)
With .NET 2.0 asp.net 2.0, c# 2.0, visual studio 2005 coming out in a pretty
complete form by summer, how can I avoid having to say something like, "I
have good general .NET experience and have MCAD certification in VS .NET "
but hang on for a few months while I figure out how I would develop this
..NET extensible Framework you would like based on what I find out about
VS05, Indigo, Windows Activation Service, etc? -----------hazz