yehudamakarov

#Heading 1 ##Heading 2 ###Heading 3 ####Heading 4 #####Heading 5 ######Heading 6

---

Paragraph

yehudamakarov

import mongoose, { Document, Model } from "mongoose";
import { IRashiDocument, IRashiObject, RashiSchema } from "./Rashi";

export interface IChumashObject {
    learnOnDate: Date;
    dayOfTheWeek: string;
    hebrewPesukim: Pesukim;
    englishPesukim: Pesukim;
    amountOfPesukim: number | null;
    rashiDocument: IRashiObject;

yehudamakarov

#To create a new symlink (will fail if symlink exists already):

ln -s /path/to/file /path/to/symlink

#To create or update a symlink:

ln -sf /path/to/file /path/to/symlink

yehudamakarov

{
    "ignore": ["**/*.test.ts", "**/*.spec.ts", ".git", "node_modules"],
    "watch": ["src"],
    "exec": "npm start",
    // probably just extension...
    "ext": "ts"
}

// and in package.json:

yehudamakarov

import React from 'react';
import { TouchableWithoutFeedback } from 'react-native';

export default class DoubleTap extends React.Component {
  static defaultProps = {
    delay: 300,
    onDoubleTap: () => null,
  };

yehudamakarov

The problem is that it's risky, because your local changes are seen by git as diffs relative to the current branch tip, but those diffs may not be applicable to the other branch. For instance if you added a line after an existing line, and that line doesn't exist on the other branch, git won't know what to do From the command line you can do git checkout -m branch which attempts a "merge" algorithm, which may work, or else give you a mess of merge conflict markers Otherwise you can stash your changes, and pop them back later git stash (...later...) git stash pop (git stash pop can result in merge conflicts if you aren't in the same state your were when you stashed it. If so you get the merge conflicts to resolve, and the stash remains on the stack too.) The third option is to erase your changes. You can do that from the command line with git checkout. git checkout -p will prompt you before reverting each change, so you can be sure you're not throwing away anything important.

I think (not sure) `g

yehudamakarov

Without any extra options, mklink creates a symbolic link to a file. The below command creates a symbolic, or “soft”, link at Link pointing to the file Target :

mklink Link Target

Use /D when you want to create a soft link pointing to a directory. like so:

mklink /D Link Target

Use /H when you want to create a hard link pointing to a file:

yehudamakarov

import * as React from 'react'
import * as Redux from 'redux'

import { MyReduxState } from './my-root-reducer.ts'

export interface OwnProps {
  propFromParent: number
}

interface StateProps {

yehudamakarov

    public class AuthenticationBL : IAuthenticationBL
    {
        private readonly IAuthenticationRepository _authenticationRepository;
        private readonly IConfiguration _configuration;

        public AuthenticationBL(IAuthenticationRepository authenticationRepository, IConfiguration configuration)
        {
            _authenticationRepository = authenticationRepository;
            _configuration = configuration;

yehudamakarov

System Design Cheatsheet

Picking the right architecture = Picking the right battles + Managing trade-offs

Basic Steps

1. Clarify and agree on the scope of the system

• User cases (description of sequences of events that, taken together, lead to a system doing something useful)
  • Who is going to use it?
  • How are they going to use it?