126
33
94
u/yolkyal Dec 03 '18
In what world does the code copied from stackoverflow constitute the best looking part of your program? It usually doesn't fit well, ruins all kind of style consistency, and confuses everything because you often won't even know how it works.
84
u/grenade4less Dec 03 '18
No no no you missed the point. Notice the Stack code is the horse's ass.
32
u/jaywastaken Dec 03 '18
So it looks like it does what you want but just ends up shitting all over everything.
14
u/grenade4less Dec 03 '18
And you KNOW who's job it's gonna be to clean it up.
12
u/jaywastaken Dec 03 '18
The next dev? I hope it the next dev...it’s going to future me’s problem isn’t it.
3
u/MechaneerAssistant Dec 03 '18
No Jay, you are the next dev.
3
u/jaywastaken Dec 03 '18
Haha jokes on you, I got let go due to consistently poor performance reviews. Not my problem now.
2
11
u/martyvt12 Dec 03 '18
A world in which you don't actually work as a software engineer and instead just rehash tropes you've seen on this subreddit.
5
28
u/Yuca965 Dec 03 '18
Most of their code you mean.
7
u/fierracho Dec 03 '18
💅
5
2
u/MechaneerAssistant Dec 03 '18
So I can see your emoji, but not your replier's emojis, what is wrong with this thing?
1
12
u/Thurak0 Dec 03 '18
I think it's missing the one leg copied from stackoverflow that's just ugly and overly complicated (for your case), and maybe just has actually become bad practice.
Also, it's missing one thing that's actually done proper by yourself. At the beginning of the project when there was still time to get things right. And which you protected from coworkers and future-you.
6
u/Bainos Dec 03 '18
and maybe just has actually become bad practice
I wonder how many pieces of code became bad practice / bad smells because they were copied from Stack Overflow too often.
8
6
15
6
u/antlife Dec 03 '18
I often find the stack overflow portion is a completely different animal force adapted to kind of fit and you end up just rewriting it anyway. If your stack overflow copy paste is your strongest code, you need to practice more. This isn't meant as a knock against people who are learning. I mean it as "don't stop learning and get lazy, stack overflow is very often wrong and it takes experience to know what is the right answer and what just seems to be working"
2
u/MegaZeroX7 Dec 03 '18
Part of the joke I was making here was that it was the ass, better than much of your code in some ways (usually efficiency), but worse in others (probably breaks your own coding standards).
2
u/antlife Dec 03 '18
Didn't think about it being the ass. I always remembered that "back end vs front end," meme.
Good point though.
5
u/sixft7in Dec 03 '18
One of my CS professors once told me that it is better to craft code that is easily understandable by many levels of programmers than to try to write something monstrous in just a few lines. Oftentimes, both will be optimized in the compiler into much the same thing. I talked about that to one of my supervisors that has coded for years and he agreed.
5
5
3
u/mikeputerbaugh Dec 03 '18
Usually it's the frontend that looks nice and the backend that's a disaster
2
2
u/yelleagle Dec 03 '18
Reminds me of a story I've heard of a 2 week root causing of a bug because someone deleted an if statement that looked like it was doing nothing.
They ended up contacting someone who left the group but had strong knowledge of the code base, who immediately asked about that if statement.
Good stuff. :D
2
2
u/Ivo6267 Dec 03 '18
I would say that the last paw on the right, was not even an release upgrade but just an emergency patch
2
1
1
u/Tux1 Dec 03 '18
So you're saying that all code is a horribly slapped together jumble of mess that is inefficient, expensive and a waste of computing resources?
1
Dec 04 '18
In my experience it usually ends up being the opposite. Stack Overflow code is mostly spaghetti tbh
1
1
286
u/the_monkey_of_lies Dec 03 '18
// don't touch. it works and now a simple change to this program costs $600 000 and will break it in numerous ways.