Nerd homework

[stanleychief]

I just hope this kid renames the variables before turning in the code. If I were grading the assignment, I'd be raising an eyebrow if the variables were French.

I once worked on some client's code, which was apparently written by a guy named Eric. Every variable in his code was prefixed with 'eric'. So the SQL DB connection was 'ericDbConn', and the result set was 'ericDbResult', the datarow object was 'ericDbRow', etc.

I thought that was pretty damned hilarious!

[ptlyon]

Originally Posted by stanleychief

I just hope this kid renames the variables before turning in the code. If I were grading the assignment, I'd be raising an eyebrow if the variables were French.

I once worked on some client's code, which was apparently written by a guy named Eric. Every variable in his code was prefixed with 'eric'. So the SQL DB connection was 'ericDbConn', and the result set was 'ericDbResult', the datarow object was 'ericDbRow', etc.

I thought that was pretty damned hilarious!

What was this piece of code written for, if I may ask?

[stanleychief]

Originally Posted by ptlyon

What was this piece of code written for, if I may ask?

It was a long time ago, but I believe that particular code was embedded in a classic ASP page. He was fetching options from the database to populate a select tag on a form.

I recall that the guy left a lot of comments too, which is usually a good thing, but his comments were unnecessary, as they didn't explain anything helpful. Example:

// This is the database connection
Dim ericDbConn = Server.CreateObject("ADODB.Connection")

Pretty obvious, given the naming, and straight-forward variable assignment. Struck me as if they were written by someone just out of school. The client was a large regional grocery store chain.

[ptlyon]

Originally Posted by stanleychief

It was a long time ago, but I believe that particular code was embedded in a classic ASP page. He was fetching options from the database to populate a select tag on a form.

I recall that the guy left a lot of comments too, which is usually a good thing, but his comments were unnecessary, as they didn't explain anything helpful. Example:

// This is the database connection
Dim ericDbConn = Server.CreateObject("ADODB.Connection")

Pretty obvious, given the naming, and straight-forward variable assignment. Struck me as if they were written by someone just out of school. The client was a large regional grocery store chain.

That was my first thought as well. Naming conventions have always been my downfall. I've learned some, but still sometimes go back to what makes sense to me at the time.

[stanleychief]

Originally Posted by ptlyon

That was my first thought as well. Naming conventions have always been my downfall. I've learned some, but still sometimes go back to what makes sense to me at the time.

There are only two hard things in Computer Science: cache invalidation and naming things.
-- Phil Karlton

https://martinfowler.com/bliki/TwoHardThings.html

[Monticore]

Originally Posted by stanleychief

There are only two hard things in Computer Science: cache invalidation and naming things.
-- Phil Karlton

https://martinfowler.com/bliki/TwoHardThings.html

Well he managed to figure it out , he says it worked like it was supposed to but he said he didn't code it like the teacher did , he said the tips in here were helpful.

thanks fellas .