So basically your code is more functional and has larger throughput, while using resources more efficiently? Great, no need for the superfluous copied part!
Requirements: Build a boat.
Add some pontoons and call it a day.
adds them to the bottom, flips immediately
Add bigger pontoons.
Move the call.
You have to build it first, so that the customer can say "Exactly! A bus! But it needs to go across water, I don't know what that's called though."
"Ah shit i forgor" *seals up the whole bus so it doesn't leak and floats" there, perfect!
I was thinking filling it with expanding foam would work too.
Very high latency, though. Great for some use cases, useless for others.
"Sleek and stylish front end with a reliable, strong and stable back end"
Perfectly describes my body.
Now throw away the copied part.
I won't touch it!
I dare you! You got version control and good unit test coverage after all, no? ;)
The front is pretty but useless
The back is functional, flexible and customizable.
But the client asked for this:
No, they didn't. They probably wanted this but described a bus with a fancy nose. Didn't mention capability of flying either.
You made it more scalable? Good work
the part I stole from stackoverflow and the part I stole from reddit:
I would genuinely love to ride that bus. Unironically sick af
Looks like a duck
Yeah, ducks are sick af too
the more fancy your code looks, the more shitty it becomes
So shitty is fancy, right?
Right?
Chef’s kiss
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
