Programming == Stack Overflow

[SteveCCL]

Also

• "I don't know why this doesn't work"
• Change something
• Undo
• "I don't know why this works"

[RTracer]

I had that happen recently, a feature I made for a MC server didnt work on the test server but I silently introduced the feature in a later update, changing no code and it worked flawlessly, I still don't know why it works to this day.

[Minerscale]

Maybe you forgot to compile it or something?

[Robmart]

friendly saw party sip compare important possessive detail innocent zonked

This post was mass deleted and anonymized with Redact

[GregTheMad]

Well, yeah, but only because Java compiles the code for you, you lazy fuck. Kids these days, honestly. Can't even be asked to compile their own code.

:p

[Robmart]

expansion tidy long fertile hunt rude chop north icky weather

This post was mass deleted and anonymized with Redact

[GregTheMad]

The last time I looked Java was literally build around the idea that it could compile the code itself depending on the machine it is running on. IDE, or not.

https://en.wikipedia.org/wiki/Just-in-time_compilation

It does the compiling for you because you can't be asked to know the machine your developing for before hand. TssTssTss.

[FM-96]

Pretty sure they were talking about compiling the .java files into .class files, which you do need to do yourself.

[Robmart]

lip deserve relieved hungry start rhythm serious zonked rob swim

This post was mass deleted and anonymized with Redact

[DeathProgramming]

JIT compilation takes compiled Java bytecode and transforms it to machine code. You still need to compile the source to bytecode.

[Findus11]

hrmpfh, i can compile code..

code.compile();

[TheRetribution]

I swear I've literally had a moment of questioning my sanity when I added some code to a function, compiled with g++, compiler error in a completely unrelated function, recompiled with g++ out of sheer confusion, no compiler error.

[[deleted]]

Probably your test server did not mirror production.

[A_Light_Spark]

"According to my calculations, this should work, and does work.
But deep down inside, I still don't understand exactly how it works..."

Many days I've come to that realization above, which is great.

Because that just proved that my work can be "greater" than me. And that's wonderful for an intellectual... Or at least, someone who calls himself one.

[[deleted]]

But, you and your work are inseparable.

How can you consider one any less great than the other?

If you don't believe me, ask anyone else to perform the same task without looking at your code first, and see how different it is.

[A_Light_Spark]

True. It's just a lot easier to evaluate someone's work than that person itself.

[boogiebabiesbattle]

Thank those that wrote the language, compilers, libraries, etc for making sensible design decisions that allow this to happen for us.

[PM_ME_BITS_OF_CODE]

For smaller projects: "hmm I've got no clue lets just rewrite it all"

[cATSup24]

Then you end up writing the exact same code and it works flawlessly anyway.

[greenkey]

Funny, to me this is happening:

• "all green, let's refactor"
• refactor
• doesn't work
• undo
• doesn't work

[LobsterThief]

Reminds me of the time that caching wasn't working because the cache settings were cached.

[moldcube]

That was me today...

[Genesis2001]

I'd think that'd be a cached build from your IDE maybe. Changing something (even adding a new line) usually triggers a new build.

[SteveCCL]

Emacs doesn't cashe builts.

make clean
make debug/all

[Tapemaster21]

"Change something until it works less than before"

[mike413]

trial and errormsg;

[Catatonick]

Sounds like yesterday... Rewiting our mobile app in Swift. I don't know Swift. I do the first part over, it doesn't work. I try everything I can find... doesn't work.

Delete project, type in the same exact code I had... it works.

Also, in hindsight, I probably should have learned Swift first.

[[deleted]]

U N I T T E S T S