Is there anything you feel you DON'T know about C#?

[RayLopez99]

After about 2 years of C# programming, I feel like a master of the
universe. Why, there are days when I feel there's nothing new under
the sun--I have mastered each and every detail there is to know.

Sure, occasionally you'll find me looking online for the proper way to
set up a class (syntax is always a problem), and I do Google online
for solutions (why reinvent the wheel?) and just the other day I did
for the first time a creation and consumption of a web service, but
those are just details.

I have learned everything there is to know about C#. Last year I was
at 90% after a year of study, this year I'm at 99%. Next year, 99.9%.

Anybody else feel this way? Arne? Peter?

RL

 

[Arne Vajhøj]

After about 2 years of C# programming, I feel like a master of the
universe. Why, there are days when I feel there's nothing new under
the sun--I have mastered each and every detail there is to know.

Sure, occasionally you'll find me looking online for the proper way to
set up a class (syntax is always a problem), and I do Google online
for solutions (why reinvent the wheel?) and just the other day I did
for the first time a creation and consumption of a web service, but
those are just details.

I have learned everything there is to know about C#. Last year I was
at 90% after a year of study, this year I'm at 99%. Next year, 99.9%.

Anybody else feel this way? Arne? Peter?

Not me.

I feel like I am at 10%.

Arne

 

[Andy O'Neill]

On 02-03-2010 06:30, RayLopez99 wrote:

Not me.

I feel like I am at 10%.

Arne

It's not c# that takes the time.
In fact I would say that c# is a minor detail of implementation.
Architecting the application, database stuff, patterns, frameworks and all
that take up much more of my time.

You can be a brilliant c# developer and write awful applications if you
don't understand all the rest.

 

[Arne Vajhøj]

It's not c# that takes the time.
In fact I would say that c# is a minor detail of implementation.
Architecting the application, database stuff, patterns, frameworks and
all that take up much more of my time.

You can be a brilliant c# developer and write awful applications if you
don't understand all the rest.

I completely agree with that.

Arne

 

[RayLopez99]

I completely agree with that.

Arne

Well I don't. You guys sound like the Roman architect Vitruvius
( en.wikipedia.org/wiki/Vitruvius) who spelled out such a long list of
necessary qualifications to become an architect that it would have
taken several lifetimes to achieve.

Obviously the more experienced you are, the better, but it doesn't
mean you can't write kwality kode with a yeoman's understanding (1 < x
< 2 years) of C# coding.

RL

 

[Dylan Parry]

After about 2 years of C# programming, I feel like a master of the
universe. Why, there are days when I feel there's nothing new under
the sun--I have mastered each and every detail there is to know.

Five years here, and I still know nothing compared to what there is that
I could and probably should know. Not a day goes by where I don’t learn
something new about C# or the framework in general. I’m currently
learning about MVC and even though I started using it ~6 months ago I’m
finding that there are better ways to do the stuff that I thought I had
cracked!

 

[Arne Vajhøj]

Well I don't. You guys sound like the Roman architect Vitruvius
( en.wikipedia.org/wiki/Vitruvius) who spelled out such a long list of
necessary qualifications to become an architect that it would have
taken several lifetimes to achieve.
http://norvig.com/21-days.html

Obviously the more experienced you are, the better, but it doesn't
mean you can't write kwality kode with a yeoman's understanding (1< x
< 2 years) of C# coding.

Not all tasks require 10 years of experience.

Arne

 

[Andy O'Neill]

Obviously the more experienced you are, the better, but it doesn't
mean you can't write kwality kode with a yeoman's understanding (1 < x
< 2 years) of C# coding.

It's possible to write quality code with 1 week's experience in c#.
That's how long it took me to pick up the basics.
Mind you., I'd been using vb.Net for like 5 years.

Bloke I worked with was brilliant at what I'd call dotNet theory.
When I started at the client he described his methodology to me and I
thought
"This bloke knows his stuff, that sounds dead clever".
He left.
His application went live about the day he left.
This was a single user intranet app which did batch data processing in
objects on the web server.
Each day a user was supposed to click a button and it did it's processing.
It took 3 days to do 1 days processing.
Nobody could work out how all the zillions of classes worked.
They junked the system.

He wrote it like that because he didn't understand databases or batch
processing on databases.
The thing should have been a 1 minute overnight batch process and the user
just looked at the results in a web page.

I think c# is a mere detail of implementation.

 

[RayLopez99]

He wrote it like that because he didn't understand databases or batch
processing on databases.
The thing should have been a 1 minute overnight batch process and the user
just looked at the results in a web page.

I think c# is a mere detail of implementation.

LOL that is a classic war story that sounds authentic.

RL