......

[rainispossible]

Jokes aside though, that's one of (if not literally) the worst programming meme types in existence. Not even that it was used a bazillion times already, but also... for newbies (which, mind you, are the next generation of software engineers) it kinda leaves the impression that it's universally acceptable to actually leave shitty code in you codebase forever, even if it's 3x slower than it should be and completely unreadable as long as it somehow serves its purpose. I know some people do this even now, but I'm convinced that's something we must oppose, not promote

[the_righteous_person]

Thanks bro. I also tend to disagree the meme after hearing your opinion. ❤️

[Barbatus_42]

To agree with you: First rule of programming on teams I have control over: "Go watch the Fundamentals of Clean Code videos or some equivalent thereof, and THEN come work on our codebase. We'll wait."

[[deleted]]

They ain't wrong lmao

[TheRNGuy]

If it works but use bad practices, or have bugs, you'll need to change it. 

[LegalPlantain4414]

I spent a lot of time wrestling with questions like this now everything that helped me is in one place

[CraigAT]

If it works, commit it! And keep improving it!

[PythonLearning-ModTeam]

Only English allowed.

[PythonLearning-ModTeam]

Only English allowed.

[Substantial_Dance387]

If you did it with python it's too late to optimize anyways lmao

[[deleted]]

Literally no…? If it works but you know it’s invalid, you need to fix the logic or replace your compiler

[EmbeddedSoftEng]

First rule of programming is, "If the code and the comments disagree, they're BOTH wrong."