Recently, I've come across a bunch of discussions about "modularization" and the "DA layer." Developers are talking as if they're throwing a party, while I, as someone just doing tasks, am left completely confused... But honestly, don't be intimidated by the terminology. Just focus on one main thread: don't lose data, keep the sorting organized, and avoid messing up in the end.



DA is like "submitting homework to the teacher and still being able to check it," meaning everyone can access what you send and review it; sorting is like lining up to buy bubble tea—there needs to be a recognized queue for who goes first and who goes after; finality is like "once stamped, don’t change it," otherwise, you celebrate after crossing the threshold with a screenshot, only to see the chain roll back in the next second, and I’d just laugh out loud. Anyway, my approach is still the same as with web scraping or travel guides: understand the interaction thresholds, don’t chase overly complicated narratives, finish what you start, and then move on. That’s all for now.
View Original
This page may contain third-party content, which is provided for information purposes only (not representations/warranties) and should not be considered as an endorsement of its views by Gate, nor as financial or professional advice. See Disclaimer for details.
  • Reward
  • Comment
  • Repost
  • Share
Comment
Add a comment
Add a comment
No comments
  • Pin