the more fancy your code looks, the more shitty it becomes
So shitty is fancy, right?
Right?
“Sleek and stylish front end with a reliable, strong and stable back end”
Perfectly describes my body.
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.
“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.
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.”
Add some pontoons and call it a day.
adds them to the bottom, flips immediately
Move the call.
Add bigger pontoons.
You made it more scalable? Good work
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.
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
Chef’s kiss
