akrish4 / learn-by-write

This is a open source contribution repository , Anyone can fork , and make changes and make a PR , Happy Learning.

Hi I'm Ananthakrishnan Nair RS

A student developer😃 from India 🇮🇳

Me 👨‍💻

A web developer & Open Source Enthusiast, currently pursuing B.Tech in CSE discipline. My field of interest is DL/ML, App/Web Development. Looking for an organization where I can utilize whatever knowledge I have gathered or acquired till now and further enhance my skill-sets in the IT field. I am the type of guy who always learns by implementing, always having a strong desire to learn. I spend most of my time contributing to Open-Source Projects and software.

• 🔭 I’m currently working on ....ml
• 🌱 I’m currently learning .... python
• 👯 I’m looking to collaborate on .... open source projects
• 🤔 I’m looking for help with .... ml & js
• 💬 Ask me about .... SQL,python, cpp
• 📫 How to reach me: Email

Hello World

GitHub Statistics 📊

Tech Skills 💻

Projects

Connect With Me 📥

Show ❤️ By Starring My

learn-by-write's Issues

min() and max() features

Fun fact about min() and max() is that these functions can help you to sort in alphabetical order! If a string is passed as an argument, min() will return the first letter (alphabetically) and max() the last one (somewhat zetabetically). And if you specify more than one value, min() will return the first string in alphabetical order and max(), in contrast, the last one. For example, min("alpha", "omega") gives you "alpha", while max("alpha", "omega") returns "omega".

For Example:
max("gloomy", "grey", "green")-"grey"
min("gloomy", "grey", "green")- "gloomy"

The “fatal: refusing to merge unrelated histories” Git error

The “fatal: refusing to merge unrelated histories” Git error occurs when two unrelated projects are merged (i.e., projects that are not aware of each other’s existence and have mismatching commit histories).

Consider the following two cases that throw this error:

1. You have cloned a project and, somehow, the .git directory got deleted or corrupted. This leads Git to be unaware of your local history and will, therefore, cause it to throw this error when you try to push to or pull from the remote repository.

2. You have created a new repository, added a few commits to it, and now you are trying to pull from a remote repository that already has some commits of its own. Git will also throw the error in this case, since it has no idea how the two projects are related.

Solution
The error is resolved by toggling the allow-unrelated-histories switch. After a git pull or git merge command, add the following tag:

git pull origin master --allow-unrelated-histories

Learn-By-Write | Python | Cpp | Java | DSA | ML | DL | CV

Contribute in any , learn by doing , happy learning..

Relative units - em and rem

1em = 16px

1rem = 16px

Delete Readme files

Some folders have empty README.md file. If you don't need the README.md files in those folders, you may want to delete those files.

Immutable vs mutable

Lists	Tuple	Dictionaries	String
mutable	-	-	Immutable