What is the bare minimum you should know as a .NET developer ?
-
And yet I do need it time and time again - as mentioned in other replies. Let's say you're at a friend's house (without your laptop, it's a social evening and your spouse won't let you take it), the subject of conversation turns to palindromes, and the hostess expresses a desire for a simple method of determining whether or not a particular sentence is one; she'd be very appreciative. She has a computer, but has no need for development tools. Installing an IDE and potentially messing up the computer (or at least being blamed for it) is not a good option. Do you write a simple console app (as I would) or would you say you'll write it when you get home and get back to her next week?
PIEBALDconsult wrote:
Do you write a simple console app (as I would)
Nope.
PIEBALDconsult wrote:
would you say you'll write it when you get home
Nope. I'd say "More wine, love?".
-
Rumour has it that before your are proficient at anything you have to be doing it for about 10 years. The language isn't all that important since it is just a way to make the computer dance. What is more important is software design.
You and I have heard similar rumours: 5 years to be useful 10 years to be good 15 years to be excellent
062142174041062102
-
10!
PIEBALDconsult wrote:
10!
Thanks! :-D But seriously, I'm speaking from experience. I had a résumé full of tools, and from that got a phone interview. I was excited until the guy on the phone absolutely lambasted me with question after question that I couldn't answer. He was actually really nice about it, and told me one piece of advice before hanging up: Learn Design Patterns. I wish today I could shake that guy's hand, because that one phone interview changed me. All this time later, I still mark that one day as the day I finally started to become a 'real' programmer. You can have all the 'tools' in the world on your résumé, and it may get you interviews, but you're not going to get past the interviews without real knowledge about programming. The language/tool is almost irrelevant. Once I had that basic foundation, even learning new languages became a breeze. Just some friendly advice. :cool:
-
Master C#. Learn how to develop without an IDE.
-
I am thinking what is the minimum should I know before I can call myself a "good" .NET developer ? This is what I am comfortable with so far : C# ASP.NET Javascript AJAX Control toolkit Telerik Rad Controls , iTextSharp library (Third party .NET controls) Some basic LINQ (I started using this in my current project).
virang_21 wrote:
what is the minimum should I know before I can call myself a "good" .NET developer ?
I'd like to extend your question, if you don´t mind. To be a good developer (no matter the language) you have to understand your customer. You have to be able to "see" what the user wants and how he wants it. The real value of a programmer lies in is his ability to understand what they expect and want from him.
-
Mycroft Holmes wrote:
recommending the OP not to use the IDE
No, I don't say "don't use it", I say "learn not to rely on it". Having the flexibility to use it or not use are is very beneficial. Like being able to walk to the gas station when you run out of gas, use candles when the power goes out, etc. There are craftsmen who use only hand tools, not because they have to, but because they choose to.
I understand your sentiment, I just disagree with it, nor do I agree with the analogies, there is too much tech required to support even the most basic tools required for programming. I do agree that there is great value in understanding the underlying structure and concepts just not the abandonment of the IDE as a training exercise.
Never underestimate the power of human stupidity RAH
-
PIEBALDconsult wrote:
10!
Thanks! :-D But seriously, I'm speaking from experience. I had a résumé full of tools, and from that got a phone interview. I was excited until the guy on the phone absolutely lambasted me with question after question that I couldn't answer. He was actually really nice about it, and told me one piece of advice before hanging up: Learn Design Patterns. I wish today I could shake that guy's hand, because that one phone interview changed me. All this time later, I still mark that one day as the day I finally started to become a 'real' programmer. You can have all the 'tools' in the world on your résumé, and it may get you interviews, but you're not going to get past the interviews without real knowledge about programming. The language/tool is almost irrelevant. Once I had that basic foundation, even learning new languages became a breeze. Just some friendly advice. :cool:
10^2! There are things you can learn from books There are things you can learn from experimentation. And there are things you can only learn by interacting with battle-scarred veterans.
-
I understand your sentiment, I just disagree with it, nor do I agree with the analogies, there is too much tech required to support even the most basic tools required for programming. I do agree that there is great value in understanding the underlying structure and concepts just not the abandonment of the IDE as a training exercise.
Never underestimate the power of human stupidity RAH
Mycroft Holmes wrote:
there is too much tech required to support even the most basic tools required for programming
No there isn't. Q.E.D.
Mycroft Holmes wrote:
there is too much tech required to support even the most basic tools required for programming
Then why make it worse? Edit:
Mycroft Holmes wrote:
abandonment of the IDE
That's not what I said. Just learn how to make do in a pinch. Remember Swordfish. No, not that part, the other part.
modified on Friday, August 13, 2010 10:40 PM
-
LOL Dude, can you remove a screw without a screwdriver? I am sure we all can!
PIEBALDconsult wrote:
Master C#. Learn how to develop without an IDE.
Sounds like "Use the force, Luke...." ;)
I prefer a margarita.
-
I am thinking what is the minimum should I know before I can call myself a "good" .NET developer ? This is what I am comfortable with so far : C# ASP.NET Javascript AJAX Control toolkit Telerik Rad Controls , iTextSharp library (Third party .NET controls) Some basic LINQ (I started using this in my current project).
Can you articulate the differences between DataSets; “typed” DataSets; Linq to SQL; and Entity Framework? … Why and where would you or would you not use them? WCF? WF? What’s the difference between Web Forms and MVC 2? What are their respective advantages? Are you familiar with Microsoft’s “Patterns and Practices”? The Enterprise Library?