This has been discussed earlier here

To summarize though:

BatchID, and JobID, might look nice, but if your using Camel Casing you're just as likely to run into something like:

IDAnalytics and IDValidation etc...

Which as objective as the issue may be I believe is very ugly, and can lead to legibility issues in the future.

This has been discussed earlier here

To summarize though:

BatchID, and JobID, might look nice, but if you're using Camel Casing you're just as likely to run into something like:

IDAnalytics and IDValidation etc...

Which is (subjectively) confusing

This has been discussed earlier here

To summarize though:

BatchID, and JobID, might look nice, but if your using Camel Casing you're just as likely to run into something like:

IDAnalytics and IDValidation etc...

Which as objective as the issue may be I believe is very ugly, and can lead to legibility issues in the future.

This has been discussed earlier here

To summarize though:

BatchID, and JobID, might look nice, but if your using Camel Casing you're just as likely to run into something like:

IDAnalytics and IDValidation etc...

Which as objective as the issue may be I believe is very ugly, and can lead to legibility issues in the future.