Content pfp
Content
@
0 reply
0 recast
2 reactions

horsefacts pfp
horsefacts
@horsefacts.eth
- Keep all strings under 32 bytes - Replace modifiers with internal functions - Linked libraries 😈 (cc @maks) https://warpcast.com/maks/0xb0fda8ff
7 replies
3 recasts
23 reactions

Tayyab - d/acc pfp
Tayyab - d/acc
@tayyab
What was your journey for mastering Solidity?
1 reply
0 recast
2 reactions

androidsixteen pfp
androidsixteen
@androidsixteen.eth
Would also love to know your answer to this @horsefacts.eth!
1 reply
0 recast
1 reaction

horsefacts pfp
horsefacts
@horsefacts.eth
(cc @tayyab) I wouldn't claim mastery, but some influential steps along my path so far: 1) Several years of experience writing non smart contract software. Nothing too hardcore, mostly Ruby/Python/Clojure. Learned about testing, design, and not to fear weird languages and paradigms.
1 reply
0 recast
3 reactions

horsefacts pfp
horsefacts
@horsefacts.eth
2) Working on an EVM indexer. This exposed me to different abstraction layers of the EVM stack and how data crosses each boundary: execution client internals, EVM, Solidity, dapp architecture. I didn't know at the time, but I learned a lot that was later useful to understand Solidity.
1 reply
0 recast
2 reactions

horsefacts pfp
horsefacts
@horsefacts.eth
3) NFTs. Although I thought smart contracts were interesting, I was hesitant to write my own for a long time. The teams I'd worked with had a very high bar for safety and I didn't feel ready to program other people's (fake internet) money. Suddenly there was a domain that wasn't quite as high stakes as DeFi.
1 reply
0 recast
0 reaction