tucq88

Learning RxJS

Intro

• Reactive programming is programming with asynchronous data streams, also deal with synchronous.
  • A stream is a sequence of ongoing events ordered in time, that can emit:
    • Value,
    • Error,
    • Completed signal
• Everything could be considered as a stream: Single value, Array, Event, etc

tucq88

Keybase proof

I hereby claim:

• I am tucq88 on github.
• I am tucq88 (https://keybase.io/tucq88) on keybase.
• I have a public key ASBh_OYPN972zWlq6HGDHS4xCfaM83ExmFm_HXZ5825Miwo

To claim this, I am signing this object:

tucq88

#!/bin/sh
# add this to your bitbar directory
# don't forget to chmod +x


# width and characters for the progress bars
# feel free to configure these
width=30
fill_char="█"
empty_char="▁"

tucq88

https://www.safaribooksonline.com/library/view/learning-react-native/9781491989135/
https://www.safaribooksonline.com/library/view/clean-architecture-a/9780134494272/
https://www.safaribooksonline.com/library/view/learning-path-jmeter/9781788473224/

tucq88

When you

• send tokens,
• interact with a contract,
• send ETH,
• or do anything else on the blockchain,

You must PAY for that computation. That payment is calculated in Gas and gas is paid in ETH.

tucq88

Tutorial: Designing a GraphQL API

This tutorial was created by Shopify for internal purposes. We've created a public version of it since we think it's useful to anyone creating a GraphQL API.

It's based on lessons learned from creating and evolving production schemas at Shopify over almost 3 years. The tutorial has evolved and will continue to change in the future so nothing is set in stone.

tucq88

1. Learn something (Reading, Watching) from 05-25 minutes before start working.
2. Prepare today TODO list a day before
3. Break work into measurable pieces and work in (multiple) 1 hour session(s)
4. Be human and healthy by getting up, go around, take a walk and talk with people
5. You don't need inspiration to start anything. Just do it.

---

Ref: https://superyesmore.com/studio-commandments-a5300cdf50b8a30ec909955b119f9174

tucq88

<?php
function dump()
{
    //
}

function dd()
{
    //
}

tucq88

{
  "exclude": [
    ".git/**",
    "node_modules/**"
  ],
  "remove-empty-rulesets": true,
  "always-semicolon": true,
  "color-case": "lower",
  "block-indent": "  ",
  "color-shorthand": false,

tucq88

As we are still a small team, so we've optimized Git-flow to be more simple and have it fits with our team size and project complexities better

We gonna have 3 primary types of branches: master branch, staging branch and features branches, which are:

• Brach master is latest version of workable product. Each increaments will be merged to master after sprint is finished. And it's always release-able.

• Branch staging is branched-off from master. When new iteration is started, it will reset to latest master's state. And dev team will use this branch to demo their work.