~ archived since 2018 ~

I wrote some code!

BattleBoi0406 · 2018-07-30T16:59:32+00:00

if womanISthot == True: print("THOT DETECTED") else: print("if she breathes, she's a thot")...

BattleBoi0406

July 30, 2018

20 upvotes

/r/MGTOW

Download the post

Want to save the post for offline use on your device? Choose one of the download options below:

PDF TXT EPUB

Post Information

Title	I wrote some code!
Author	BattleBoi0406
Upvotes	20
Comments	15
Date	July 30, 2018 4:59 PM UTC (7 years ago)
Subreddit	Posted in /r/MGTOW
Original Link	https://old.reddit.com/r/MGTOW/comments/935tml/i_wrote_some_code/
Archive Link	https://theredarchive.com/r/MGTOW/i-wrote-some-code.516780 https://theredarchive.com/post/516780

Comments

[–]stephcurryftw23 points24 points25 points 7 years ago (0 children) | Copy Link

[–]Horsepitt224 points5 points6 points 7 years ago (0 children) | Copy Link

[–]BattleBoi0406[S] 3 points4 points5 points 7 years ago (0 children) | Copy Link

[–]m5ufo 2 points3 points4 points 7 years ago (2 children) | Copy Link

[–]DangZagnut2 points3 points4 points 7 years ago (1 child) | Copy Link

[–]m5ufo 0 points1 point2 points 7 years ago (0 children) | Copy Link

[–]TheFrenchBoi1 point2 points3 points 7 years ago (3 children) | Copy Link

[–]BattleBoi0406[S] 1 point2 points3 points 7 years ago (2 children) | Copy Link

[–]m5ufo 1 point2 points3 points 7 years ago (1 child) | Copy Link

[–]BattleBoi0406[S] 1 point2 points3 points 7 years ago (0 children) | Copy Link

The Zen of Python

Beautiful is better than ugly. Explicit is better than implicit. Simple is better than complex. Complex is better than complicated. Flat is better than nested. Sparse is better than dense. Readability counts. Special cases aren't special enough to break the rules. Although practicality beats purity. Errors should never pass silently. Unless explicitly silenced. In the face of ambiguity, refuse the temptation to guess. There should be one-- and preferably only one --obvious way to do it. Although that way may not be obvious at first unless you're Dutch. Now is better than never. Although never is often better than right now. If the implementation is hard to explain, it's a bad idea. If the implementation is easy to explain, it may be a good idea. Namespaces are one honking great idea -- let's do more of those!

When in doubt, import this!

[–]WithJoosYouLose1 point2 points3 points 7 years ago (2 children) | Copy Link

[–]BattleBoi0406[S] 0 points1 point2 points 7 years ago (1 child) | Copy Link

[–]magnetowave0 points1 point2 points 7 years ago (0 children) | Copy Link

[–]Atton_Risk0 points1 point2 points 7 years ago (1 child) | Copy Link

[–]RoadToMGTOW2 points 7 years ago [recovered] | Copy Link

func getNawalt(_ woman: Woman) -> Woman? {

if !woman.isThot { return woman }  guard let mother = woman.mother else { return nil }  return getNawalt(mother)

}

Have fun with stack overflow.

P.S. Can’t get proper formatting working