iboss-ptk

Resources

Articles / Videos

• Finematics (youtube channel about many import aspect of DeFi)
• Whiteboard Crypto (similar to finematics but includes broader aspects)
• Binanace Academy (good list of basics and jargons)
• Original Bitcoin Whitepaper (short and sweet good starting point to understand the root but more technical)
• DeFi Product Management (we are not really defi ourselves but gives good idea of where the industry is going)
• Paradigm bleeding edge stuffs
• a16z crypto playlist many good overviews of the industry

iboss-ptk

Overview

Terrain is a Terra development environment for better smart contract development experience.

Terrain will help:

• scaffold your dapp project
• ease the development and deployment process
• create custom task for blockchain and contract interaction with less boilerplate code
• using terra.js directly could be cumbersome, Terrain gives you extensions and utilities to help you

iboss-ptk

Overview

Terrain is a Terra development environment for better smart contract development experience.

Terrain will help:

• scaffold your dapp project
• ease the development and deployment process
• create custom task for blockchain and contract interaction with less boilerplate code
• using terra.js directly could be cumbersome, Terrain gives you extensions and utilities to help you

iboss-ptk

iboss-ptk

Smart Contract Learning Reresources

recommeneded

• cryptozpmbies Learn the basics, and it's interactive. Somewhat outdated but good place to start.
• etheruem developer All the fundamental knowledge about ethereum
• recommended dev setup
• best practices
• [https://ethernaut.openzeppelin.com/](security game)
• [https://capturetheether.com/](another security game)

iboss-ptk

const axios = require('axios')


const toStringParams = o => 
    Object
        .keys(o)
        .map(k => `${k}=${o[k]}`)
        .join('&')

        

iboss-ptk

App State
  App not running*
    open app -> Logged in?

  App opened
    kill app -> App not running
    close app -> App Backgrounded
    
    Login Screen
      login -> Login

iboss-ptk

Design Decision For Analytics Tracking

• Event name is following [this convention](Naming conventions: one step towards clean data) an Object-Action Framework eg.
  • Object: Account, Action: Signed Up
  • Object: Post, Action: Created
• Following that, means we can separate module (file) by object. eg. account has its own module.
• in each module, we can implement the detail about the tracking
  • params
  • transformation (if needed)
• if the tracking function seems do similar transformation before every calls, consider moving those logic into the tracking function itself. (eg. post.engaged)
• if the tracking depends on state changes, consider creating a component with hook in it to capture state changes from the context, app state, or any global-ish state (eg. ProfileUpdateTracker)

iboss-ptk

// === lib ===
type Contextualized<C, R> = (context: C) => R

const contexualize = contextConsumerGenerator => context => {
    const generator = contextConsumerGenerator()

    let contextConsumerIter = generator.next()
    let consume: any = contextConsumerIter.value

    while (!contextConsumerIter.done) {

iboss-ptk

First attempt!

Number of user that reads at least P posts weekly for within at least W consecutive weeks

• P determined by looking at weekly post reading per user distribution, we want al least
• W determined by retention rate
  • same user for n weeks, where is the critical line where we can say this user stick with us

What does this says?

• Read more posts means product is good???
  • what if they just can’t find what they want?