by BoogieM » 12 Jan 2015 10:53
Behold, YOLO Driven Development!
# Do not refactor, it is a bad practice. YOLO
# Not understanding why or how something works is always good. YOLO
# Do not ever test your code yourself, just ask. YOLO
# No one is going to read your code, at any point don’t comment. YOLO
# Why do it the easy way when you can reinvent the wheel? Future-proofing is for pussies. YOLO
# Do not read the documentation. YOLO
# Do not waste time with gists. YOLO
# Do not write specs. YOLO also matches to YDD (YOLO DRIVEN DEVELOPMENT)
# Do not use naming conventions. YOLO
# Paying for online tutorials is always better than just searching and reading. YOLO
# You always use production as an environment. YOLO
# Don’t describe what you’re trying to do, just ask random questions on how to do it. YOLO
# Don’t indent. YOLO
# Version control systems are for wussies. YOLO
# Developing on a system similar to the deployment system is for wussies! YOLO
# I don’t always test my code, but when I do, I do it in production. YOLO
# Real men deploy with ftp. YOLO
Forget those old pagan traditions of test-driven development and behavior-driven development. A new methodology every day keeps the IT consultants away! Ruby.zigzo summarizes this YDD manifesto as follows: “this is a joke, don’t do any of this stuff… or do it! YOLO!”
However, a simple GitHub search for “because YOLO” delivers over 600 hits, proving that numerous developers have already begun adopting the YOLO approach:
1 (map(lambda __suchwoow:\
2 map(lambda __because___yolo__:\
3 __lololol_.__setitem__(( (__because___yolo__)) , (0)),
4 range(2*(__suchwoow), ((very_math)), __suchwoow ) ),