awesome/falsehood
1
0
Fork 0
mirror of https://github.com/kdeldycke/awesome-falsehood.git synced 2024-11-20 11:35:56 -05:00
Code Activity

Update readme.md

Browse source
This commit is contained in:
Kevin Deldycke 2023-06-10 16:40:51 +04:00 committed by GitHub
parent 4eb8c5e237
commit 88e6d9544f
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
readme.md
View file

@ -14,16 +14,12 @@
______________________________________________________________________ ______________________________________________________________________
<p align="center">
<strong>A curated <a href="https://github.com/sindresorhus/awesome"><img src="https://awesome.re/badge-flat.svg" alt="Awesome"/></a> list of falsehoods programmers believe in.</strong>
</p>
<p align="center"> <p align="center">
<i>The logic of the world is prior to all truth and falsehood.</i><br> <i>The logic of the world is prior to all truth and falsehood.</i><br>
— Ludwig Wittgenstein<sup id="intro-quote-ref"><a href="#intro-quote-def">[1]</a></sup> — Ludwig Wittgenstein<sup id="intro-quote-ref"><a href="#intro-quote-def">[1]</a></sup>
</p> </p>
A *falsehood* is an ***idea* that you initially believed was true**, but in reality, it is **proven to be false**. A curated [![Awesome](https://awesome.re/badge-flat.svg)](https://github.com/sindresorhus/awesome) list of falsehoods programmers believe in. A *falsehood* is an ***idea* that you initially believed was true**, but in reality, it is **proven to be false**.
E.g. of an *idea*: valid email address exactly has one `@` character. So, you will use this rule to implement your email-field validation logic. Right? Wrong! The *reality* is: emails can have multiple `@` chars. Therefore your implementation should allow this. The initial *idea* is a falsehood you believed in. E.g. of an *idea*: valid email address exactly has one `@` character. So, you will use this rule to implement your email-field validation logic. Right? Wrong! The *reality* is: emails can have multiple `@` chars. Therefore your implementation should allow this. The initial *idea* is a falsehood you believed in.