anthonygore

<template>
  <div>
    <input v-model="input" type="number" />
    <h1>{{ output }}</h1>
  </div>
</template>

<script>
import { ref, watch, onUnmounted } from 'vue';
import { timer, Subject } from 'rxjs';

ClickerMonkey

// when T is any|unknown, Y is returned, otherwise N
type IsAnyUnknown<T, Y, N> = unknown extends T ? Y : N;
  
// when T is never, Y is returned, otherwise N
type IsNever<T, Y = true, N = false> = [T] extends [never] ? Y : N;

// when T is a tuple, Y is returned, otherwise N
// valid tuples = [string], [string, boolean], 
// invalid tuples = [], string[], (string | number)[]

onlurking

Design Systems 101 Syllabus

A 10-week course about design systems from SuperFriendly

Week 1: Introduction to Design Systems

Discussion

• Introductions

onlurking

The Five Orders of Ignorance

By Phillip G. Armour
Communications of the ACM, October 2000, Vol. 43 No. 10, Pages 17-20
10.1145/352183.352194

In my first column (Aug. 2000, p. 19), I argued that software is not a product, but rather a medium for the storage of knowledge. In fact, it is the fifth such medium that has existed since the beginning of time. The other knowledge storage media being, in historical order: DNA, brains, hardware, and books. The reason software has become the storage medium of choice is that knowledge in software has been made active. It has escaped the confinement and volatility of knowledge in brains; it avoids the passivity of knowledge in books; it has the flexibility and speed of change missing from knowledge in DNA or hardware.

If software is not a product, then what is the product of our efforts to produce software? It is the knowledge contained in the software. It's rather easy to produce software. It's much more difficult to produce software that works, because we ha

hakobyansen

#!/bin/bash

# Assigning parameters to variables for better readability
host="$1"
by="$2"
for="$3"
project="$4"

# Getting current timestamp to use it in the session name
timestamp=$(date '+%s');

onlurking

Programming as Theory Building

Peter Naur

Peter Naur's classic 1985 essay "Programming as Theory Building" argues that a program is not its source code. A program is a shared mental construct (he uses the word theory) that lives in the minds of the people who work on it. If you lose the people, you lose the program. The code is merely a written representation of the program, and it's lossy, so you can't reconstruct

u-ndefine

float decel(float x) { // as an easing function
  return 1-(x-1)*(x-1);
}

void setup() {
  background(255);
  size(750,750,P2D);
  PImage img = loadImage("image.png");
  strokeWeight(2);
  noFill();

kiennq

# Logs
logs
*.log
npm-debug.log*
yarn-debug.log*
yarn-error.log*
lerna-debug.log*

# Diagnostic reports (https://nodejs.org/api/report.html)
report.[0-9]*.[0-9]*.[0-9]*.[0-9]*.json

alexcasalboni

# config
BUCKET_NAME=your-bucket-name
STACK_NAME=lambda-power-tuning-demo

# package
sam package --s3-bucket $BUCKET_NAME --template-file template.yml --output-template-file packaged.yml

# deploy
sam deploy --template-file packaged.yml --stack-name $STACK_NAME --capabilities CAPABILITY_AUTO_EXPAND CAPABILITY_IAM

matthewsuan

import axios from 'axios'

const MAX_REQUESTS_COUNT = 5
const INTERVAL_MS = 10
let PENDING_REQUESTS = 0

// create new axios instance
const api = axios.create({})

/**