Christ Centered Gamer

Cigar? Never had one of those, haha. Hear they are kind of hard to get a hold of.

Cuban food? No. I had Puerto Rican and it's really good.

The sammich. 'Tis a most glorious concoction.

Drills?

I have a power drill, albeit not a very great one. I'll invest in a good one some time in the future, probably when I end up buying a house.

ArchAngel wrote:I have a power drill, albeit not a very great one. I'll invest in a good one some time in the future, probably when I end up buying a house.

Be sure to get a good set of drill bits. I love my masonry bits... probably more than I should. I look for excuses to drill things....

Duly noted. I have a cheap set of bits, too. I've already snapped a couple of them.

Self help programs?

What exactly do you mean by a self-help program?
Technically, me regularly reading articles online is a self-help program for getting me more informed.
Or regularly exercising is a self-help program for becoming more fit.

But if you're talking on a more specific Tony-Robbins-If-You-Believe-You-Can-Achieve sense, then no.

Please complete the following sentence:

"If you have a class file that's almost 5,000 lines of code long, it's..."

"...too big; it should be broken down into multiple classes."

I could be convinced to keep it at the size if it's a utility class, but it'd still be best served as broken up.

The worst, imo, is giant functions/methods. It's easy to collapse the functions with a modern ide and make the whole thing readable, but a giant function is just unnavigably sloppy. It's hard to read, hard to debug, inelegant, and usually inefficient. I mean, how hard is it to put some of that logic into appropriate private functions? You're going to thank yourself later.

But man, I've seen asp files over 10k lines long. Talk about unmanageable. I've also seen functions close in on 1000 lines. Just horrendous.

Yah... I'm rehabilitating a co-worker who doesn't understand why a 5,000 line class, which handles its own FTP, Web Services and database CRUD ops, is a bad thing...

For utility classes: static?

Mostly. I'd generally choose which to apply depending on what the function will do and what is needed for it, but an object architecture is better suited, it starts to leave the realm of a "utility class."

Heh want a job?

Haha, thanks, but my current one keeps me busy.

Bummer. I wasn't entirely kidding.

What kind of brain rot do I have now that I understand what you guys are talking about?

-_-