XJLI
NAXJA Forum User
- Location
- Long Island, NY
Re: THe NAC Lots-O-Post Thread
holy.
holy.
Haha... Left.Depends, which one is your cousin?
Things that annoy Anthony.....
:thumbup: (sorry, still not essing your dee)MOTHERXXXXERS I JUST SCORED A XXXXING DEAL ON A T18 SO SUCK MY DICK THATS RIGHT TAKE MY DICK WITH YOUR HAND AND BY DICK I MEAN PENIS IT'S RIGHT BETWEEN MY LEGS I'LL EVEN TAKE MY PANTS OFF FOR YOU OPEN YOUR MOUTH AND PUT MY PENIS RIGHT IN THERE I WONT PEE OR ANYTHING WHILE IT'S THERE JUST GET IT IN THERE FOR 5-6 MINUTES AND YOU CAN TAKE IT OUT AND MOVE ON WITH YOUR LIFE
Liar. This thread must not die./thread.
Right there.
That ends this /thread.
http://farm5.static.flickr.com/4052/4542924077_f039c63eae_o.jpgAnthony it bothered you enough to post about it online.
Oh, and your beard makes you look like a retarded hobo.
![]()
Naxja just go blocked by my job.
Time to find a new job.
http://farm5.static.flickr.com/4052/4542924077_f039c63eae_o.jpg
(the picture is huge, otherwise I'd embedd it)
Normally I float around the 'Full Beard' but lately it's been approaching 'Unkempt Beard'
(wait wait... is this what being trolled is? .!.)
(then how are you on?)
Oh he's one of the cool kids. I hadn't even considered that.
Ken, Chris, and maybe a few others will appreciate this. The guy whose code I'm editing right now is your typical software engineer. In life, he's all over the place. You would think his code would be nice and neat, but his code, while well commented, is an extension of his personality. Whenever I write code I make sure it's clean, neat, runs by itself, etc. He calls out a billion functions, all of which he could have just worked into the code and 2/3 of the length of the program is commented out lines that he decided not to use anymore. Any of you guys have to edit nightmarish code before? I'm sure Ken has.
It's warm and comfortable. And not on your face.Nope you've always been around the unkempt beard.
Depending on how many times he's used those functions, it might be worthwhile. I use the rule of thumb that if the code gets used more than a time or five and isn't extremely performance critical, it gets turned into a function and I call it. If it IS extremely performance critical and I find myself copy pasting it, I try to turn it into a macro and call it, since it neatens the code up and eases maintenance while still preserving performance. I HATE badly formatted or sloppy code. I'll sometimes leave old commented-out code for historical reasons but if it is getting removed, it's probably for a reason... the worst of all though is a combination of non descriptive variable names and out of date comments that describe how the code USED to work without saying it.Oh he's one of the cool kids. I hadn't even considered that.
Ken, Chris, and maybe a few others will appreciate this. The guy whose code I'm editing right now is your typical software engineer. In life, he's all over the place. You would think his code would be nice and neat, but his code, while well commented, is an extension of his personality. Whenever I write code I make sure it's clean, neat, runs by itself, etc. He calls out a billion functions, all of which he could have just worked into the code and 2/3 of the length of the program is commented out lines that he decided not to use anymore. Any of you guys have to edit nightmarish code before? I'm sure Ken has.
See, that would make sense. Each function is used once and it's not really something that needs to be optimized for speed. It seems like he did it to save space, but then left his original code and just commented it... His variable names are pretty good, at least. Took me a little bit to figure out his convention though. The whole thing made me scratch my head more than I expected to.Depending on how many times he's used those functions, it might be worthwhile. I use the rule of thumb that if the code gets used more than a time or five and isn't extremely performance critical, it gets turned into a function and I call it. If it IS extremely performance critical and I find myself copy pasting it, I try to turn it into a macro and call it, since it neatens the code up and eases maintenance while still preserving performance. I HATE badly formatted or sloppy code. I'll sometimes leave old commented-out code for historical reasons but if it is getting removed, it's probably for a reason... the worst of all though is a combination of non descriptive variable names and out of date comments that describe how the code USED to work without saying it.
fyi- I have flaring tools for just about every flare and push connect if you want to go with quick connects, plus a gm push connect flare is much easier to push a hose onto. Let me know when you want to do the plumbing, I can take a ride up and give you a hand with it. I also recommend usnig the copper-nickel tubing napa sells. great to work with, and lasts forever.I'm going to run rubber from the tank down to the frame rail, hard line (double flared, hose clamped) up the rail to the intake manifold (factory clamp on manifold) then double flared/hose clamped up to the fittings on the fuel rail.
Why that one? You can get a cheaper .22 bolt gun that will shoot the same. we use those guns at the scout camp, and they aren't that great.I'm daydreaming about guns right now. I want this one. http://www.tombstonetactical.com/catalog/savage-arms/mark-i-fvt-rifle-22-lr-20in-hb-1rd-black/
Why that one? You can get a cheaper .22 bolt gun that will shoot the same. we use those guns at the scout camp, and they aren't that great.
Besides, go big or go home http://jga.anschuetz-sport.com/index.php5?produktID=290&menu=105&sprache=1&produktShow=detail