- Joined
- May 19, 2019
Arguing about a mistake a technological boomer made in a meme. I fucking love this place.
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
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.Yes, but "then" doesn't exist as a keyword in C/C++/C#.
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.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.
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.
if (nickTweetsAboutCase || nickTalksAboutCase) {
caseLossCount++;
}
if (Nick.tweetsAboutCase || Nick.talksAboutCase) {
caseLossCount++;
}
Fuck semicolons, man, shit always trips me up.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.C:if (nickTweetsAboutCase || nickTalksAboutCase) { caseLossCount++; }
And that there is how I know you've done programming before.Fuck semicolons, man, shit always trips me up.
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.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.C:if (nickTweetsAboutCase || nickTalksAboutCase) { caseLossCount++; }
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
But we could add extra ultra-important things to Nick like Nick.favoriteDrink=("Laphroaig") and whatnot, things the world deserves to know!C:if (Nick.tweetsAboutCase || Nick.talksAboutCase) { caseLossCount++; }
Or we could just laugh at this post and not bother because it's too much effort.
That is wholesome and a bit horrifying at the same time (o.0)
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.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.
lawsuit, timesVicLost = 1, 0
while lawsuit:
timesVicLost += 1
lol wtf someone actually made a fucking program hahahahahaCan 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.
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.
It's funny, but it's bad. I'm kinda stuck, do I say "lol" or "get out" here?Why can’t PULL code python?
They struggle with comprehension
When in doubt, just useIt's funny, but it's bad. I'm kinda stuck, do I say "lol" or "get out" here?
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.C:if (nickTweetsAboutCase || nickTalksAboutCase) { caseLossCount++; }
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
But we could add extra ultra-important things to Nick like Nick.favoriteDrink=("Laphroaig") and whatnot, things the world deserves to know!C:if (Nick.tweetsAboutCase || Nick.talksAboutCase) { caseLossCount++; }
Or we could just laugh at this post and not bother because it's too much effort.
Lawsuit vicMignognaLawsuit = vicMignogna.getLawsuit(mignognaVsFunimationLawsuitId);
Topic vicMignognaLawsuitTopic = (Topic) vicMignognaLawsuit.toTopic();
.....
If(Nick.getShowTopic() == vicMignognaLawsuitTopic || Nick.getTweetTopic() == vicMignognaLawsuitTopic) {
vicMignognaLawsuit.loseCaseAgain();
}
As long as your comment is 82 characters or less, you’re still good by PEP-8It's funny, but it's bad. I'm kinda stuck, do I say "lol" or "get out" here?
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.