Home All Groups Group Topic Archive Search About
Author
17 Jun 2009 8:59 AM
starter
Hi,

I wanted to know how to solve any problem in c#. I have 5 years of
experience in that 4 years worked on Sql server and I was able to
solve problems in Sql server using T-sql programming.

So any MVP's in C# or Experienced developers suggest me how can I get
the confidence that I can solve any problem in c#. Is it enough if I
read C# technical books like (C# in nutshell) or (Apress Pro C#) or
need to improve on algorithms techniques. Let me know what you will do
in this scenario.

Thanks & Regards,
Vital

Author
17 Jun 2009 6:02 PM
Jeff Johnson
"starter" <enligh***@gmail.com> wrote in message
news:8353de31-e037-446f-b26d-c51a655d18fc@f19g2000yqh.googlegroups.com...

> I wanted to know how to solve any problem in c#.

Me too. As soon as I can figure out how to use C# to get laid, I'll be
thrilled.
Are all your drivers up to date? click for free checkup

Author
17 Jun 2009 6:31 PM
Gregory A. Beamer
starter <enligh***@gmail.com> wrote in news:8353de31-e037-446f-b26d-
c51a655d1***@f19g2000yqh.googlegroups.com:

Show quoteHide quote
> Hi,
>
> I wanted to know how to solve any problem in c#. I have 5 years of
> experience in that 4 years worked on Sql server and I was able to
> solve problems in Sql server using T-sql programming.
>
> So any MVP's in C# or Experienced developers suggest me how can I get
> the confidence that I can solve any problem in c#. Is it enough if I
> read C# technical books like (C# in nutshell) or (Apress Pro C#) or
> need to improve on algorithms techniques. Let me know what you will do
> in this scenario.
>
> Thanks & Regards,
> Vital


Learn to google and go through the Microsoft documentation. These skills
will help you more than trying to memorize all of the rules of C#, which
will both change and get more complex over time.

You should also practice code kata (coding to increase skills) when you
have idle time. This will help you remember what you have done and are
doing.

As for solving problems, the big skill is breaking down the problem into
manageable bites. And, having tests on your code so you can refactor
without fear.

No matter how much of a rock star you might become, you will still not
get it right the first time for a variety of reasons. Some, like lack of
requirements, are out of your control.

Even today, you can probably solve any problem. The question is "how
long will it take you to solve the problem"


--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

Twitter: @gbworld
Blog: http://gregorybeamer.spaces.live.com

*******************************************
Show quoteHide quote
|      Think outside the box!             |
*******************************************
Author
17 Jun 2009 10:19 PM
Jesse Houwing
Hey!

Don't forget!

Reflector (and it's abaility to disassemble code) is your best friend to
become a master in .NET

Jesse

Show quoteHide quote
> starter <enligh***@gmail.com> wrote in news:8353de31-e037-446f-b26d-
> c51a655d1***@f19g2000yqh.googlegroups.com:
>
>> Hi,
>>
>> I wanted to know how to solve any problem in c#. I have 5 years of
>> experience in that 4 years worked on Sql server and I was able to
>> solve problems in Sql server using T-sql programming.
>>
>> So any MVP's in C# or Experienced developers suggest me how can I get
>> the confidence that I can solve any problem in c#. Is it enough if I
>> read C# technical books like (C# in nutshell) or (Apress Pro C#) or
>> need to improve on algorithms techniques. Let me know what you will
>> do in this scenario.
>>
>> Thanks & Regards,
>> Vital
> Learn to google and go through the Microsoft documentation. These
> skills will help you more than trying to memorize all of the rules of
> C#, which will both change and get more complex over time.
>
> You should also practice code kata (coding to increase skills) when
> you have idle time. This will help you remember what you have done and
> are doing.
>
> As for solving problems, the big skill is breaking down the problem
> into manageable bites. And, having tests on your code so you can
> refactor without fear.
>
> No matter how much of a rock star you might become, you will still not
> get it right the first time for a variety of reasons. Some, like lack
> of requirements, are out of your control.
>
> Even today, you can probably solve any problem. The question is "how
> long will it take you to solve the problem"
>
> Twitter: @gbworld
> Blog: http://gregorybeamer.spaces.live.com
> *******************************************
> |      Think outside the box!             |
> *******************************************
--
Jesse Houwing
jesse.houwing at sogeti.nl
Author
18 Jun 2009 12:55 PM
starter
On Jun 18, 3:19 am, Jesse Houwing <jesse.houw...@newsgroup.nospam>
wrote:
Show quoteHide quote
> Hey!
>
> Don't forget!
>
> Reflector (and it's abaility to disassemble code) is your best friend to
> become a master in .NET
>
> Jesse
>
>
>
> > starter <enligh***@gmail.com> wrote in news:8353de31-e037-446f-b26d-
> > c51a655d1***@f19g2000yqh.googlegroups.com:
>
> >> Hi,
>
> >> I wanted to know how to solve any problem in c#. I have 5 years of
> >> experience in that 4 years worked on Sql server and I was able to
> >> solve problems in Sql server using T-sql programming.
>
> >> So any MVP's in C# or Experienced developers suggest me how can I get
> >> the confidence that I can solve any problem in c#. Is it enough if I
> >> read C# technical books like (C# in nutshell) or (Apress Pro C#) or
> >> need to improve on algorithms techniques. Let me know what you will
> >> do in this scenario.
>
> >> Thanks & Regards,
> >> Vital
> > Learn to google and go through the Microsoft documentation. These
> > skills will help you more than trying to memorize all of the rules of
> > C#, which will both change and get more complex over time.
>
> > You should also practice code kata (coding to increase skills) when
> > you have idle time. This will help you remember what you have done and
> > are doing.
>
> > As for solving problems, the big skill is breaking down the problem
> > into manageable bites. And, having tests on your code so you can
> > refactor without fear.
>
> > No matter how much of a rock star you might become, you will still not
> > get it right the first time for a variety of reasons. Some, like lack
> > of requirements, are out of your control.
>
> > Even today, you can probably solve any problem. The question is "how
> > long will it take you to solve the problem"
>
> > Twitter: @gbworld
> > Blog:http://gregorybeamer.spaces.live.com
> > *******************************************
> > |      Think outside the box!             |
> > *******************************************
>
> --
> Jesse Houwing
> jesse.houwing at sogeti.nl

How can reflector help to solve problems in c#?

Thanks
Author
18 Jun 2009 5:30 PM
Jesse Houwing
Hello starter,

Show quoteHide quote
> On Jun 18, 3:19 am, Jesse Houwing <jesse.houw...@newsgroup.nospam>
> wrote:
>
>> Hey!
>>
>> Don't forget!
>>
>> Reflector (and it's abaility to disassemble code) is your best friend
>> to become a master in .NET
>>
>> Jesse
>>
>>> starter <enligh***@gmail.com> wrote in news:8353de31-e037-446f-b26d-
>>> c51a655d1***@f19g2000yqh.googlegroups.com:
>>>
>>>> Hi,
>>>>
>>>> I wanted to know how to solve any problem in c#. I have 5 years of
>>>> experience in that 4 years worked on Sql server and I was able to
>>>> solve problems in Sql server using T-sql programming.
>>>>
>>>> So any MVP's in C# or Experienced developers suggest me how can I
>>>> get the confidence that I can solve any problem in c#. Is it enough
>>>> if I read C# technical books like (C# in nutshell) or (Apress Pro
>>>> C#) or need to improve on algorithms techniques. Let me know what
>>>> you will do in this scenario.
>>>>
>>>> Thanks & Regards,
>>>> Vital
>>> Learn to google and go through the Microsoft documentation. These
>>> skills will help you more than trying to memorize all of the rules
>>> of C#, which will both change and get more complex over time.
>>>
>>> You should also practice code kata (coding to increase skills) when
>>> you have idle time. This will help you remember what you have done
>>> and are doing.
>>>
>>> As for solving problems, the big skill is breaking down the problem
>>> into manageable bites. And, having tests on your code so you can
>>> refactor without fear.
>>>
>>> No matter how much of a rock star you might become, you will still
>>> not get it right the first time for a variety of reasons. Some, like
>>> lack of requirements, are out of your control.
>>>
>>> Even today, you can probably solve any problem. The question is "how
>>> long will it take you to solve the problem"
>>>
>>> Twitter: @gbworld
>>> Blog:http://gregorybeamer.spaces.live.com
>>> *******************************************
>>> |      Think outside the box!             |
>>> *******************************************
>> --
>> Jesse Houwing
>> jesse.houwing at sogeti.nl
> How can reflector help to solve problems in c#?

It can be very helpful to actually see what's going on under the hoods of,
for example, a webcontrol. Instead of getting things to work by trial and
error, you can actually deduct how it should work and fix th eproblem you're
dealing with. It's been very hlpful in the past :).
--
Jesse Houwing
jesse.houwing at sogeti.nl
Author
29 Jun 2009 3:16 PM
Gregory A. Beamer
starter <enligh***@gmail.com> wrote in news:58b96815-105d-4207-a482-
43a86028c***@c19g2000prh.googlegroups.com:

>
> How can reflector help to solve problems in c#?


It allows you to reverse engineer compiled .NET assemblies and examine how
other people solved the problem. It will not work with properly obfuscated
assemblies, however.


--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

Twitter: @gbworld
Blog: http://gregorybeamer.spaces.live.com

*******************************************
Show quoteHide quote
|      Think outside the box!             |
*******************************************
Author
29 Jun 2009 3:15 PM
Gregory A. Beamer
Jesse Houwing <jesse.houwing@newsgroup.nospam> wrote in
news:e5317a7e7801013f8cbbdc1a1cf66f2@news.microsoft.com:

>
> Hey!
>
> Don't forget!
>
> Reflector (and it's abaility to disassemble code) is your best friend to
> become a master in .NET


One of the MUST HAVE tools for any .NET developer. ;-)


--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

Twitter: @gbworld
Blog: http://gregorybeamer.spaces.live.com

*******************************************
Show quoteHide quote
|      Think outside the box!             |
*******************************************
Author
18 Jun 2009 12:53 PM
starter
On Jun 17, 11:31 pm, "Gregory A. Beamer"
<NoSpamMgbwo...@comcast.netNoSpamM> wrote:
Show quoteHide quote
> starter <enligh***@gmail.com> wrote in news:8353de31-e037-446f-b26d-
> c51a655d1***@f19g2000yqh.googlegroups.com:
>
> > Hi,
>
> > I wanted to know how to solve any problem in c#. I have 5 years of
> > experience in that 4 years worked on Sql server and I was able to
> > solve problems in Sql server using T-sql programming.
>
> > So any MVP's in C# or Experienced developers suggest me how can I get
> > the confidence that I can solve any problem in c#. Is it enough if I
> > read C# technical books like (C# in nutshell) or (Apress Pro C#) or
> > need to improve on algorithms techniques. Let me know what you will do
> > in this scenario.
>
> > Thanks & Regards,
> > Vital
>
> Learn to google and go through the Microsoft documentation. These skills
> will help you more than trying to memorize all of the rules of C#, which
> will both change and get more complex over time.
>
> You should also practice code kata (coding to increase skills) when you
> have idle time. This will help you remember what you have done and are
> doing.
>
> As for solving problems, the big skill is breaking down the problem into
> manageable bites. And, having tests on your code so you can refactor
> without fear.
>
> No matter how much of a rock star you might become, you will still not
> get it right the first time for a variety of reasons. Some, like lack of
> requirements, are out of your control.
>
> Even today, you can probably solve any problem. The question is "how
> long will it take you to solve the problem"
>
> --
> Gregory A. Beamer
> MVP; MCP: +I, SE, SD, DBA
>
> Twitter: @gbworld
> Blog:http://gregorybeamer.spaces.live.com
>
> *******************************************
> |      Think outside the box!             |
> *******************************************

what do you mean by refactor?

Thanks
Author
18 Jun 2009 1:07 PM
Mark Rae [MVP]
"starter" <enligh***@gmail.com> wrote in message
news:bc0e21fc-c41c-4c89-a8fb-36ba77c24d38@c20g2000prh.googlegroups.com...

> What do you mean by refactor?

http://www.google.co.uk/search?aq=f&sourceid=chrome&ie=UTF-8&q="C%23"+refactor


--
Mark Rae
ASP.NET MVP
http://www.markrae.net
Author
29 Jun 2009 3:19 PM
Gregory A. Beamer
"Mark Rae [MVP]" <mark@markNOSPAMrae.net> wrote in
news:O2WqEXB8JHA.5428@TK2MSFTNGP02.phx.gbl:

> "starter" <enligh***@gmail.com> wrote in message
> news:bc0e21fc-c41c-4c89-a8fb-36ba77c24d38@c20g2000prh.googlegroups.com.
> ..
>
>> What do you mean by refactor?
>
> http://www.google.co.uk/search?aq=f&sourceid=chrome&ie=UTF-8&q="C%23"+r
> efactor
>
>

Like I said "Learn to google". ROFLMAO!

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

Twitter: @gbworld
Blog: http://gregorybeamer.spaces.live.com

*******************************************
Show quoteHide quote
|      Think outside the box!             |
*******************************************
Author
18 Jun 2009 1:16 PM
Jeff Johnson
"starter" <enligh***@gmail.com> wrote in message
news:bc0e21fc-c41c-4c89-a8fb-36ba77c24d38@c20g2000prh.googlegroups.com...

> what do you mean by refactor?

Sounds like you're trying to sprint before you can even crawl. You want to
be able to "solve any problem in C#" but you don't even know about
refactoring? You need to start small....
Author
29 Jun 2009 3:18 PM
Gregory A. Beamer
starter <enligh***@gmail.com> wrote in news:bc0e21fc-c41c-4c89-a8fb-
36ba77c24***@c20g2000prh.googlegroups.com:

> what do you mean by refactor?

Refactoring is the practice of improving code as you write it, without
changing the feature set.

The most common refactoring is getting rid of duplicates in your code base.

What it does is improve quality of code so it is less fragile and more
maintainable.

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

Twitter: @gbworld
Blog: http://gregorybeamer.spaces.live.com

*******************************************
Show quoteHide quote
|      Think outside the box!             |
*******************************************

Bookmark and Share