🧠 is-one-one ?

A wonderfully overengineered Python project that explores every possible way to prove, confirm, or spiritually deduce whether 1 is actually 1.

Why though?

Honestly? I'm a 6th Sem B.Tech student in Delhi and I should probably be studying. But I saw someone do this for Zero and I thought—why let Zero have all the fun?

If you think 1 == 1 is enough, you’re too sane for this repo,
but where's the fun in that?

What is this?

This repo is a growing collection of unreasonably complicated ways to check if 1 == 1.
Yes, the answer is always True. No, that won't stop us.

We’re talking:

• Using Trigonometry to find 1 (thanks, Class 12 math).
• Subtracting Unicode values like we’re hacking the Matrix.
• Using Logarithms because we forgot how to count.
• Checking System Memory just to be absolutely sure.

---

How to contribute

Wanna make this dumber? You're welcome here.

All you have to do is:

1. Fork this repo.
2. Add a new function to is_one_one.py.
3. Make sure it returns True (because 1 is 1).
4. Important: If your code is easy to understand, you're doing it wrong. We want chaos, not clean code.
5. Bonus points for using libraries that have no business being in a math script (like BeautifulSoup or Pandas).
6. Open a Pull Request.

Examples:

def is_one_using_quantum_mechanics():
    # 15 lines of matrix multiplication that 
    # always results in the identity matrix
    return True
    
def is_one_using_indian_parents_expectations():
    expected_rank = 1
    return expected_rank == 1

Please do not write smart or clean code. We don’t do that here.

Documentation

Looking for a specific way to prove 1 is 1? Check out our Methods Directory for a full list of available functions, their logic, and usage examples.

How to run it

python is_one_one.py

You'll see a bunch of checks that all (somehow) confirm that 1 is indeed 1.

Why does this exist?

My contribution to the internet (useless stuff). Efficiency is boring.
Because someone once made a repo called is_zero to prove nothing. I felt it was only fair to give the number 1 the same level of unnecessary attention.

License

MIT — Do whatever you want with this chaos.

Final thoughts

If you're reading this and thinking

“This is actually the most useless thing I’ve seen all week”
...mission accomplished. I spent way too much time on this just to prove a point that didn't need proving.

Contributors

A huge thanks to the legends who decided to waste their CPU cycles on this:

Click on any contributor's avatar above to visit their GitHub profile. New contributors are automatically added here!

The "Serious" Engineering Side

While this repo is chaotic, the infrastructure behind it is production-grade. I'm using this as a study in DevOps and Software Reliability:

• Automated CI Pipeline: Every Pull Request is automatically vetted by a GitHub Actions runner on Ubuntu.
• Regression Testing: A dedicated test_core.py suite ensures that new "chaos" doesn't accidentally break the fundamental proof of 1.
• Branch Management: Utilizing a professional Issue-to-PR workflow to manage community contributions.

---

Support the "Research"

If this project gave you brain rot:

• Star this repository (It keeps me motivated).
• Follow me for more overengineered nonsense.
• Share it with a friend who writes "too much code."

Made with ❤️ and ☕ by itsdakshjain