This is a selection of software design patterns developed by core Flow developers
In a blockchain environment like Flow, programs that are stored on-chain in accounts are commonly referred to as smart contracts.
This is an opinionated list of issues that can be improved if they are found in Cadence code intended for production.
Why Use Cadence?
Security and Safety
Security Best Practices
This is an opinionated list of best practices Cadence developers should follow to write more secure Cadence code.
Contract Upgrades with Incompatible Changes
Learn how to effectively organize and manage a Cadence project
Guide for Solidity Developers
Cadence introduces a different way to approach smart contract development which may feel unfamiliar to
Accessing Time From Cadence
The Cadence testing framework provides a convenient way to write tests for Cadence programs in Cadence.