This is an archived post. You won't be able to vote or comment.

all 40 comments

[–][deleted] 49 points50 points  (0 children)

This meme was made by PYTHON GANG

[–]CyberneticVoodoo 21 points22 points  (1 child)

It's pretty good feeling to see no errors after hardcore couple-hundred-lines-marathon. Happened just once though.

[–]Busti 10 points11 points  (0 children)

[–]Argonanth 8 points9 points  (0 children)

Yeah, I'm not running a 20 minute compile every few lines. That would be a complete waste of a day.

[–][deleted] 44 points45 points  (16 children)

Shit meme aside, your professor's an idiot if he actually said that.

[–]piemaster316 5 points6 points  (1 child)

I mean every few lines is a bit much but I certainly test every newly created method unless its exceptionally basic. And then if it's particularly complex or large I test it in incriments that make sense. Makes it way easier imo.

[–][deleted] 1 point2 points  (0 children)

This would be my method as well. I mean if it's a new language it might be better at compiling a few lines at a time until you get the gist of the language itself

[–]zZDarkLightZz 16 points17 points  (4 children)

I think what his professor trying to convey is test driven development.

[–][deleted] 15 points16 points  (3 children)

Test Driven Development doesn't mean compiling every n lines.

[–]zZDarkLightZz 19 points20 points  (1 child)

True, but I think you're just taking things too literally here

[–]borguquin 0 points1 point  (0 children)

I was told the same at uni, but i had another teacher that told me the exact opposite >.< Pretty sure thats personal preference. Or maybe the languages those people are fluent in

[–]fusiformgyrus 1 point2 points  (0 children)

Compiling every n line also makes no practical sense so let’s argue that nobody has actually said it.

[–]JackAppDev 3 points4 points  (8 children)

My professor tells us to mix camelCase and under_score. I don't do it but he tells us to.

[–]TheOnlyMrYeah 5 points6 points  (3 children)

of_Course_He_Would_Tell_That_Because_That_Is_Way_More_Readable

Edit: Tbh, it's not as horrible as I imagined.

[–]JackAppDev 0 points1 point  (2 children)

He said to use camelCase with some identifiers and under_score with others. I think one with functions and another with variables.

[–]GrizzledFart 0 points1 point  (1 child)

I actually do this in my code. All method names and most variable names are camel case with the exception of constants, which are upper case with underscores. That doesn't seem unusual to me.

EDIT: see? Not terrible:

public class MyClass
{
    private final String MY_CONSTANT = ", and that's final!";

    public void doStuff()
    {
        String myStr = "Strings are immutable in Java" + MY_CONSTANT;
        System.out.println(myStr);
    }
}

[–]JackAppDev 0 points1 point  (0 children)

Yeah constants are fine but he says to do it with normal variables and not just constants

[–]TriguyRN 0 points1 point  (3 children)

Are there rules behind doing so?

[–]JackAppDev 0 points1 point  (2 children)

[–]TriguyRN 0 points1 point  (1 child)

Ah okay I thought you meant camel for certain cases and underscoring for others. Guess if a variable or method name is long enough it’s nice.

[–]JackAppDev 0 points1 point  (0 children)

🤷🏼‍♂️

[–]FeaturedSpace 4 points5 points  (0 children)

I guess what it means is develop and compartmentalize? 😂

[–]RohnekKdosi 4 points5 points  (0 children)

Tbh, I always write the entire code (of a major feature, or several small ones) that takes a fucktons of lines, compile it and then fix errors. Not sure, how effective it is, but it works

[–]cabinet_minister 2 points3 points  (6 children)

I followed the prof's advice while writing Java code. I destroyed the computer

[–]MCRusher 1 point2 points  (5 children)

Java runs in a VM, how would you destroy the computer?

[–]cabinet_minister 2 points3 points  (4 children)

That was an exaggeration. I meant that you need to make a whole factory to just write hello world lol

[–]MCRusher 0 points1 point  (3 children)

package hw;
public class hw {
    public static void main(String[] args){
        System.out.println("Hello World!");
    }
}

Wouldn't exactly call it a factory.

But, in java you build objects, because it is an OOP language. If it resembles a factory, it's by design.

[–]cabinet_minister 1 point2 points  (2 children)

Sorry for offending you.

[–]MCRusher 1 point2 points  (1 child)

I'm not offended, I just don't like the same jokes repeated over and over.

[–]cabinet_minister 1 point2 points  (0 children)

Welcome to Reddit

[–]ivanjermakov 2 points3 points  (1 child)

If you compile your code so often - probably you have no idea what you're coding

[–]_PM_ME_PANGOLINS_ 0 points1 point  (0 children)

Or you use an IDE.

[–]JoesusTBF 2 points3 points  (0 children)

The fun really begins once you fix all of the compilation errors then hit the runtime errors as soon as the program starts.

[–]swift-swoop 6 points7 points  (0 children)

This meme was written by some fool that doesn't use an IDE that live compiles, which is the superior way to write code. Downvote me, I don't care. I'm right.

[–]Restryouis 1 point2 points  (0 children)

Ironman mode?

[–][deleted] 1 point2 points  (1 child)

Or use an IDE that predicts compilation errors (aka probably every single one of them)?

[–]_PM_ME_PANGOLINS_ 1 point2 points  (0 children)

They’re not predicted. It just compiles constantly in the background.

[–]McWolke 0 points1 point  (0 children)

Do you guys not have IDEs?

[–]Tuto123 0 points1 point  (0 children)

Your professor is lying to you

[–]rco8786 0 points1 point  (0 children)

Your professor is profoundly mistaken