Wow, Just Wow

[Pete OHanlon]

That's somebody who doesn't like comments. He or she has bought into the idea that code should be self commenting.

[DaveAuld]

Steady on there.....should be simply;

var results = Engine.APIProxy.GetResults(...);

:rolleyes:

Dave Find Me On:Web|Facebook|Twitter|LinkedIn Folding Stats: Team CodeProject

[Rob Grainger]

That's kind of the opposite naming principle to my examples below. Nearly as bad.

"If you don't fail at least 90 percent of the time, you're not aiming high enough." Alan Kay.

[Lost User]

Nothing wrong there. It is not like you are going to type it.

[Brisingr Aerowing]

The longest one I have seen was about 1000 characters long. Abbreviated. With a Namespace of ~1300 characters (excluding the '.') and a class name of ~700 characters. I remember this as I was going to use the library this was in. I quickly decided to use a different library instead (this library had a whole host of other things that would belong here, if I could remember the name of the library [it was a weird, unpronounceable, seemingly randomly generated name] I would post a link to it.)

What do you get when you cross a joke with a rhetorical question?

[Bernhard Hiller]

What a stupid beginner! What does Engine mean? Is that a ApplicationProgrammingInterfaceProxyEngine? That's still not meaningful enough. And that APIProxy, that also needs a better name! I cannot understand that line of code because of that bad naming.

[Ravi Bhavnani]

What the developer really meant to do was:

var scheduleContacts = Engine.APIProxy.GetAllCompanyInfoScheduleContacts()
.Where (p => p.ScheduleHeaderId == schedule.Id)
.OrderBy (p => p.CompanyInfo);

/ravi

My new year resolution: 2048 x 1536 Home | Articles | My .NET bits | Freeware ravib(at)ravib(dot)com

[Super Lloyd]

Vark111 wrote:

Also, a horrible use of var.

I know what you mean! List<CompanyInfoContactScheduleContactsByCompanyInfoContactScheduleHeader> scheduleContacts = Engine.APIProxy.GetAllCompanyInfoContactScheduleContactsByCompanyInfoContactScheduleHeaderId(schedule.Id); would have been so much clearer!!! :-D

My programming get away... The Blog... DirectX for WinRT/C# since 2013! Taking over the world since 1371!

[KP Lee]

Ranjan.D wrote:

...GetAllCompanyScheduledContactInfo(schedule.Id) or...

The problem with that is that you don't get to get even for outrageously long names by making them even longer and more confusing.

[Marc Koutzarov]

Looks like someone has just read something about Domain Driven Development and was fiddling around a bit. :-D