Ty Beard - Bumbling Fat Wargames Nerd Lolyer High On His Own Farts

  • 🐕 I am attempting to get the site runnning as fast as possible. If you are experiencing slow page load times, please report it.
Yes, but "then" doesn't exist as a keyword in C/C++/C#.
Yeah, it looks like he mashed BASIC and C together, or just wrote some pseudocode, because syntactically it does read like a proper IF statement and considering his age he might be familiar with BASIC. It might also be Pascal, but I don't know if || is a valid operator in an IF statement, but you don't need to put a semi-colon at the end of a line if it's the last line in a block.

I'm going with pseudocode though.
 
The use of underscores bugs me.

if (nickTweetsAboutCase || nickTalksAboutCase){
caseLossCount++};

But then I haven't touched a code in years so I don't fuckin know.
Underscores are only commonly used in variables or nouns that have a likelihood of being used to generate a displayed name, at least according to my dev Guild's best practice outline. So that could be future proofing for the print code or a mistake.
 
  • Informative
Reactions: Bender
The use of underscores bugs me.

if (nickTweetsAboutCase || nickTalksAboutCase){
caseLossCount++};

But then I haven't touched a code in years so I don't fuckin know.
C:
if (nickTweetsAboutCase || nickTalksAboutCase) {
  caseLossCount++;
}
You put the semicolon and the squiggly-wiggly the wrong way round you big silly, also I fixed your formatting. You're right about the underscores though, your casing is much more preferable to Ty's version. I'm kind of hoping we're going to end up with a GitHub page that has that code in every possible language that GitHub supports.

Edit: We could probably make Nick an object which would be fine since objectifying men is perfectly acceptable according to every feminist who hates vidya characters with big boobs. I'm not sure if there's any benefit to doing that though, since this is a pretty short and simple program. I might try to get in touch with a couple of guys I know who hopefully aren't too busy and are willing to entertain this silliness. The only difference in the code would be
C:
if (Nick.tweetsAboutCase || Nick.talksAboutCase) {
  caseLossCount++;
}
But we could add extra ultra-important things to Nick like Nick.favoriteDrink=("Laphroaig") and whatnot, things the world deserves to know!

Or we could just laugh at this post and not bother because it's too much effort.
 
Last edited:
C:
if (nickTweetsAboutCase || nickTalksAboutCase) {
  caseLossCount++;
}
You put the semicolon and the squiggly-wiggly the wrong way round you big silly, also I fixed your formatting. You're right about the underscores though, your casing is much more preferable to Ty's version. I'm kind of hoping we're going to end up with a GitHub page that has that code in every possible language that GitHub supports.
Fuck semicolons, man, shit always trips me up.
 
  • Feels
Reactions: INVCTS and Bender
C:
if (nickTweetsAboutCase || nickTalksAboutCase) {
  caseLossCount++;
}
You put the semicolon and the squiggly-wiggly the wrong way round you big silly, also I fixed your formatting. You're right about the underscores though, your casing is much more preferable to Ty's version. I'm kind of hoping we're going to end up with a GitHub page that has that code in every possible language that GitHub supports.

Edit: We could probably make Nick an object which would be fine since objectifying men is perfectly acceptable according to every feminist who hates vidya characters with big boobs. I'm not sure if there's any benefit to doing that though, since this is a pretty short and simple program. I might try to get in touch with a couple of guys I know who hopefully aren't too busy and are willing to entertain this silliness. The only difference in the code would be
C:
if (Nick.tweetsAboutCase || Nick.talksAboutCase) {
  caseLossCount++;
}
But we could add extra ultra-important things to Nick like Nick.favoriteDrink=("Laphroaig") and whatnot, things the world deserves to know!

Or we could just laugh at this post and not bother because it's too much effort.
Honestly, I would suggest keeping the Nick object and making the Case an object of its own. Give them Display Name values for future print methods and scalability.

Additionally, keeping the variables attached to a object would let the code be reused pretty easily for other cases and commentators. We don't want to accumulate tech debt by doing a quick and easy build.
 
  • Like
Reactions: TurboNAS and Bender
Some from yesterdays stream .

TYGetsPussy.jpgTYGetsPussy_2.jpg
 
Honestly, I would suggest keeping the Nick object and making the Case an object of its own. Give them Display Name values for future print methods and scalability.

Additionally, keeping the variables attached to a object would let the code be reused pretty easily for other cases and commentators. We don't want to accumulate tech debt by doing a quick and easy build.
I like it, keep it streamlined and relatively easy to refactor down the line, although we could just sum it up with three lines of Python, I guess.
Python:
lawsuit, timesVicLost = 1, 0
while lawsuit:
    timesVicLost += 1

Edit: Fucked up my Python.
 
Can someone help me out with this?
I'm pretty sure it should prompt twice then loop around and display caselostcount, but instead it takes the first input then immediately loops back.

edit: i'm dumb and didn't realize that the newline stayed in the input buffer. ignore me.
 
Last edited:
  • Winner
Reactions: Bender
Can someone help me out with this?
I'm pretty sure it should prompt twice then loop around and display caselostcount, but instead it takes the first input then immediately loops back.

edit: i'm dumb and didn't realize that the newline stayed in the input buffer. ignore me.
lol wtf someone actually made a fucking program hahahahaha

Oh shit, I can't breathe send hgelp

I might have a go when I wake up and sober for a few minutes, but it'll probably be in Python and I don't know how to use Git, so I'll probably just PM you.
 
Last edited:
I realy like that he makes the weebwar the culture war to end all culture wars.
 
C:
if (nickTweetsAboutCase || nickTalksAboutCase) {
  caseLossCount++;
}
You put the semicolon and the squiggly-wiggly the wrong way round you big silly, also I fixed your formatting. You're right about the underscores though, your casing is much more preferable to Ty's version. I'm kind of hoping we're going to end up with a GitHub page that has that code in every possible language that GitHub supports.

Edit: We could probably make Nick an object which would be fine since objectifying men is perfectly acceptable according to every feminist who hates vidya characters with big boobs. I'm not sure if there's any benefit to doing that though, since this is a pretty short and simple program. I might try to get in touch with a couple of guys I know who hopefully aren't too busy and are willing to entertain this silliness. The only difference in the code would be
C:
if (Nick.tweetsAboutCase || Nick.talksAboutCase) {
  caseLossCount++;
}
But we could add extra ultra-important things to Nick like Nick.favoriteDrink=("Laphroaig") and whatnot, things the world deserves to know!

Or we could just laugh at this post and not bother because it's too much effort.

And the java version:
Java:
Lawsuit vicMignognaLawsuit = vicMignogna.getLawsuit(mignognaVsFunimationLawsuitId);
Topic vicMignognaLawsuitTopic = (Topic) vicMignognaLawsuit.toTopic();
.....
If(Nick.getShowTopic() == vicMignognaLawsuitTopic || Nick.getTweetTopic() == vicMignognaLawsuitTopic) {
     vicMignognaLawsuit.loseCaseAgain();
}
 
Last edited:
It's funny, but it's bad. I'm kinda stuck, do I say "lol" or "get out" here?
As long as your comment is 82 characters or less, you’re still good by PEP-8

And the java version:
Java:
Lawsuit vicMignognaLawsuit = vicMignogna.getLawsuit(mignognaVsFunimationLawsuitId);
Topic vicMignognaLawsuitTopic = (Topic) vicMignognaLawsuit.toTopic();
.....
If(Nick.getShowTopic() == vicMignognaLawsuitTopic || Nick.getTweetTopic() == vicMignognaLawsuitTopic) {
     vicMignognaLawsuit.loseCaseAgain();
}

This is beyond baffling architecture.

Make your own best practices around getters, setters, properties, polymorphism and casting, and fucking follow them.

Edit: each “thing” you do in that snippet is done in two different ways. Each way is correct, but it’s a huge red flag when you see code snippets like that.
 
  • Informative
Reactions: Harvey Danger
This is beyond baffling architecture.

Make your own best practices around getters, setters, properties, polymorphism and casting, and fucking follow them.

Edit: each “thing” you do in that snippet is done in two different ways. Each way is correct, but it’s a huge red flag when you see code snippets like that.

The thing that bugged me the most is why the return value from the toTopic method needs to be type cast. What fucking third world hellhole did this project get off-shored to to come up with shit like that? The SEI needs negative CMM levels for shit like this.
 
Back