Tanvir Islam Streame tanvirstreame

## gist:7bdbe55c6be474d549097040b44b521f
class User {
    constructor(userId, userName) {
        this.userId = userId;
        this.userName = userName;
    }
}

class Post {
    constructor(userId, posts) {
        this.userId = userId;

## mongoose-cheatsheet.md

      
              1 file
            
          
              0 forks
            
          
              0 comments
            
          
              0 stars
            
          
                tanvirstreame
                / mongoose-cheatsheet.md
            
            
              Created
              January 18, 2023 09:32
                — forked from subfuzion/mongoose-cheatsheet.md
            
              
                mongoose cheatsheet
              
          
    Definitely not comprehensive. This is meant to be a basic memory aid with links to get more details. I'll add to it over time.
Install

$ npm install mongoose --save

Connect

const mongoose = require('mongoose');


## gist:edb38b575c99f6548954654d738bd893
const arr = [4,2,1,3];

class Node {
	constructor(value) {
		this.value = value;
		this.next = null;

	}
}

## code_review_guidelines.md

      
              1 file
            
          
              0 forks
            
          
              0 comments
            
          
              0 stars
            
          
                tanvirstreame
                / code_review_guidelines.md
            
            
              Created
              January 8, 2023 20:22
                — forked from mrsasha/code_review_guidelines.md
            
              
                Code review guidelines
              
          
    Some helpful guidelines for pull requests and code reviews

It's been often said that programming is part art, part science - that because lots of times there's no single, simple solution to a problem; or if there is, we might not know about it. There's also an infamous joke that if there are n developers in the room, then there are n+1 opinions on how things should be done. That being said, here are some guidelines that should prevent friction when submitting or reviewing code.
The most important thing

The code has to work. Unless you open a PR as a work in progress, the code should be built and tested on a device or emulator.
If you have touched the gradle build files and changed build setup, it's useful to test the whole build from scratch (clean build) and all of the types and flavours. If you have touched payments (logic or UI), you should test that it still works correctly, both in test and production builds. If you updated external libraries, test the pertaining features (e.g. if you

  
## code_review_guidelines.md

      
              1 file
            
          
              0 forks
            
          
              0 comments
            
          
              0 stars
            
          
                tanvirstreame
                / code_review_guidelines.md
            
            
              Created
              January 8, 2023 20:22
                — forked from mrsasha/code_review_guidelines.md
            
              
                Code review guidelines
              
          
    Some helpful guidelines for pull requests and code reviews

It's been often said that programming is part art, part science - that because lots of times there's no single, simple solution to a problem; or if there is, we might not know about it. There's also an infamous joke that if there are n developers in the room, then there are n+1 opinions on how things should be done. That being said, here are some guidelines that should prevent friction when submitting or reviewing code.
The most important thing

The code has to work. Unless you open a PR as a work in progress, the code should be built and tested on a device or emulator.
If you have touched the gradle build files and changed build setup, it's useful to test the whole build from scratch (clean build) and all of the types and flavours. If you have touched payments (logic or UI), you should test that it still works correctly, both in test and production builds. If you updated external libraries, test the pertaining features (e.g. if you

  
## gist:1b0cc9968d3de40abff2c27d699b0d10
// Help in developing package locally
// https://medium.com/@sam-king/an-alternative-to-npm-link-cf9ab9408f56
// https://betterprogramming.pub/how-to-create-and-publish-react-typescript-npm-package-with-demo-and-automated-build-80c40ec28aca

npm i yalc -g
yalc publish


yalc add example-package@0.0.1
yalc remove example-package@0.0.1

## gist:8b3f38bb08b6f02192a56f382820b96b
<html>

<head>
    <link href="https://cdn.jsdelivr.net/npm/bootstrap@5.0.2/dist/css/bootstrap.min.css" rel="stylesheet"
        integrity="sha384-EVSTQN3/azprG1Anm3QDgpJLIm9Nao0Yz1ztcQTwFspd3yD65VohhpuuCOmLASjC" crossorigin="anonymous">
    <style>
        thead {
            position: sticky;
            position: -webkit-sticky;
            top: 0;

## gist:eecfdf67760d6681e913a93fa43c6ada
screen.debug(undefined, Number.POSITIVE_INFINITY);

## rsa.js
const crypto = require("crypto")

// The `generateKeyPairSync` method accepts two arguments:
// 1. The type ok keys we want, which in this case is "rsa"
// 2. An object with the properties of the key
const { publicKey, privateKey } = crypto.generateKeyPairSync("rsa", {
	// The standard secure default length for RSA keys is 2048 bits
	modulusLength: 2048,
})

## public_enc_example.sh
#!/bin/bash
#
# Public-Key Encryption and Decryption
# * http://www.openssl.org/
# * http://barelyenough.org/blog/2008/04/fun-with-public-keys/
#
# Mac OS X 10.6.4
# OpenSSL 0.9.8l 5 Nov 2009

# Generate keys
	class User {
	constructor(userId, userName) {
	this.userId = userId;
	this.userName = userName;
	}
	}

	class Post {
	constructor(userId, posts) {
	this.userId = userId;
	const arr = [4,2,1,3];

	class Node {
	constructor(value) {
	this.value = value;
	this.next = null;

	}
	}
	// Help in developing package locally
	// https://medium.com/@sam-king/an-alternative-to-npm-link-cf9ab9408f56
	// https://betterprogramming.pub/how-to-create-and-publish-react-typescript-npm-package-with-demo-and-automated-build-80c40ec28aca

	npm i yalc -g
	yalc publish


	yalc add example-package@0.0.1
	yalc remove example-package@0.0.1
	<html>

	<head>
	<link href="https://cdn.jsdelivr.net/npm/bootstrap@5.0.2/dist/css/bootstrap.min.css" rel="stylesheet"
	integrity="sha384-EVSTQN3/azprG1Anm3QDgpJLIm9Nao0Yz1ztcQTwFspd3yD65VohhpuuCOmLASjC" crossorigin="anonymous">
	<style>
	thead {
	position: sticky;
	position: -webkit-sticky;
	top: 0;
	const crypto = require("crypto")

	// The `generateKeyPairSync` method accepts two arguments:
	// 1. The type ok keys we want, which in this case is "rsa"
	// 2. An object with the properties of the key
	const { publicKey, privateKey } = crypto.generateKeyPairSync("rsa", {
	// The standard secure default length for RSA keys is 2048 bits
	modulusLength: 2048,
	})
	#!/bin/bash
	#
	# Public-Key Encryption and Decryption
	# * http://www.openssl.org/
	# * http://barelyenough.org/blog/2008/04/fun-with-public-keys/
	#
	# Mac OS X 10.6.4
	# OpenSSL 0.9.8l 5 Nov 2009

	# Generate keys