I don't get this stuff

[Byron In Exile]

In the Java routine, the counters are being incremented twice each iteration: once in the body of the loop, and also by the for() statement itself. If you want to dickHard and pussyWet true more quickly, you can just lower the if() test from 10 to 5, and hoursFucking is dependent on herOrgasm, anyway.

Otherwise, a good implementation of a classic algorithm.

 

[CelestialBody]

 

[The Heretic]

Why am I supposed to write an algorithm for something that's already almost completely written?

When you get out into the real world and run into legacy code where someone just went ahead and wrote code, you will be glad your prof beat this into your head. Every new programmer should be made to refactor code where some self-taught programmer wrote functions 5000 lines long. BTDT.

 

[KillerMuffin]

BiE, as it so happens, I meant to do that not. Really.

Heretic, stop it, you're ruining my whiny session with facts. How can I go blustering through fantasy if you keep raining on my bitchy parade?

 

[curious2c]

I want to see that part where..."KillerMuffin_eats the egg_."


heh...I Know...don't give up my day job.

 

[Byron In Exile]

Re: Re: I don't get this stuff

Every new programmer should be made to refactor code where some self-taught programmer wrote functions 5000 lines long. BTDT.

*rofl, but feeling your pain*

Although I'd suggest that the fact that one might be self-taught doesn't preclude good programming practices. Conversely, a lot of software engineers with many letters after their names often demonstrate that they're just as capable of creating unservicable code as anyone.

I inherited a project once that another programmer had written and for several months hadn't been able to make work right. He just kept adding more and more code, but he'd fix a bug and create another one. Sometimes, he'd fix a bug and not create another one, but then other times he'd fix one bug and create two. Finally, the project was taken away from him and I was asked if I could take it over. I was reluctant, since I'd been hearing about the disaster during the whole time it was ongoing, but I was bribed into accepting it. After about a week of studying the labyrinthine product of this fellow's mind, I came to the realization that the thing could never be made to work reliably. The reason was that he had obviously designed it as he was coding it, so that parts of the code that were older didn't conform to the "design" he'd eventually developed, and even that was rather nebulous, so that taken as a whole the code resembled not a program so much as a big bowl of spaghetti. At that point I threw the whole thing in the trash and started over from scratch, and was able to design and code a fully functional replacement, with half the amount of code, in not much more time (though considerably more sweat) than I had estimated it would take to fix and complete the original. As a regular employee that would have been difficult to do. Managers seem to love to hang on to software that's well overdue for rewriting, as long as it can still be patched and mucked with, as if they believe the end of the world will coincide with the end of the current quarter.

Ironically, I don't think I made as much money on the project as the guy whose work I threw away.

There's probably a moral or two in there somewhere.

 

[Byron In Exile]

BiE, as it so happens, I meant to do that not. Really.

Okay, but if you decide you don't want it in there just remember: never delete any code you've written, because then it looks like you got paid for doing nothing.

So instead of this:

hesHot++;

You would use:

hesHot++;
hesHot--;

That's one more line o' code for the ol' résumé, and a 4.2GHz CPU ain't gonna miss no three stinkin' cycles! And a proper optimizing compiler has no business generatin' any machine code from that source, anyhow!

 

[KillerMuffin]

Ain't that the truth!

I'd still like to see the Java API on the smut package. I bet they'd screw that up, too.

 

[P. B. Walker]

#!/usr/bin/perl -smut

if ($muffieStillHorny) {
find $pbwalker;
while($pbwalker =~ erect) {
throw_on_bed;
lick_balls;
suck_precum;
say("mmm");
bend_over;
get_it_from_behind;
say("slap","my","ass","call","me","Kinky!");
grab_his_hand;
masturbate_with_it;
orgasm;
}
}

I just gave myself a "perl necklace". Damn, KM!!! Sweeeet.

But next time I want to do you from behind with a regular expression <winks>.

PBW

 

[The Heretic]

Re: Re: Re: I don't get this stuff

*rofl, but feeling your pain*

Although I'd suggest that the fact that one might be self-taught doesn't preclude good programming practices.

True - bear in mind that I am basically self-taught. However, most of the worst code I have dealt with has come from people who were basically self-taught, or maybe they were just asleep in class.

I threw the whole thing in the trash and started over from scratch, and was able to design and code a fully functional replacement, with half the amount of code, in not much more time (though considerably more sweat) than I had estimated it would take to fix and complete the original.

BTDT - several times.

 

[Byron In Exile]

Re: Re: Re: Re: I don't get this stuff

True - bear in mind that I am basically self-taught. However, most of the worst code I have dealt with has come from people who were basically self-taught, or maybe they were just asleep in class.

Or maybe programming just isn't their can of beans.

Originally posted by The Heretic

I threw the whole thing in the trash and started over from scratch

BTDT - several times.

Thankfully, I haven't had much to do with maintenance, having been mainly involved in new development (designing and implementing firmware for new hardware).