omer alpi omeralpi

Git Commit Best Practices

Basic Rules

Commit Related Changes

A commit should be a wrapper for related changes. For example, fixing two different bugs should produce two separate commits. Small commits make it easier for other developers to understand the changes and roll them back if something went wrong. With tools like the staging area and the ability to stage only parts of a file, Git makes it easy to create very granular commits.

Commit Often

Committing often keeps your commits small and, again, helps you commit only related changes. Moreover, it allows you to share your code more frequently with others. That way it‘s easier for everyone to integrate changes regularly and avoid having merge conflicts. Having large commits and sharing them infrequently, in contrast, makes it hard to solve conflicts.

Answers to Deep Questions about Solidity

The following list of questions was taken from https://www.reddit.com/r/ethereum/comments/72reba/do_you_have_deep_questions_about_solidity_or_the/

An updated summary on the different ways one could have two contracts interact (DELEGATECALL, STATICCALL, libraries, all that stuff) with clear pros/cons for each (gas cost, whether it requires EVM assembly directives, etc)

Question by /u/drcode

I won't talk about low-level opcodes here because of the brevity of the answer. In general, there are four ways functions can be called in Solidity:

	{
	"explorer.fileNesting.enabled": true,
	"explorer.fileNesting.patterns": {
	"package.json": ".eslint, prettier, tsconfig, vite, pnpm-lock, bun.lockb, nest",
	"tailwind.config.js": "tailwind.config, postcss.config",
	".env.local": ".env*",
	".env": ".env*"
	}
	}

	# Generate a new pgp key: (better to use gpg2 instead of gpg in all below commands)
	gpg --gen-key
	# maybe you need some random work in your OS to generate a key. so run this command: `find ./* /home/username -type d \| xargs grep some_random_string > /dev/null`

	# check current keys:
	gpg --list-secret-keys --keyid-format LONG

	# See your gpg public key:
	gpg --armor --export YOUR_KEY_ID
	# YOUR_KEY_ID is the hash in front of `sec` in previous command. (for example sec 4096R/234FAA343232333 => key id is: 234FAA343232333)