Dhaulagiri

#!/bin/bash

# This script takes a remote repository and merges it into
# the current one as a subdirectory

set -e

# REPOS=('design-system-components' 'design-system-tokens' 'design-system-figma-scripting')
# REPOS=('flight')
REPOS=('design-system-tokens')

thetwopct

# stop git branch opening in vim/vi
git config --global pager.branch 'false'

hakilebara

// This is the main script function
function myFunction() {
  var ss = SpreadsheetApp.getActiveSpreadsheet()
  
  // target repositories
  var openedPullRequestsSpreadsheet = ss.getSheetByName('OPEN_PULL_REQUESTS');
  
  // spreadsheet that contains a list of Github repositories
  var coreRepositoriesSpreadsheet = ss.getSheetByName('CORE_REPOSITORIES');
  

augbog

Frontend Technical Interview Prep

EDIT: Well this has been linked now so just an FYI this is still TBD. Feel free to comment if you have suggestions for improvements. Also here is an unrolled Twitter thread of a lot of the tips I talk about on here.

I've been doing frontend for a while now and one thing that really gripes me is the interview. I think the breadth of knowledge of a "Frontend Engineer" has been so poorly defined that people really just expected you to know everything. Many companies have made this a hybrid role. The Web is massive and there are many MANY things to know. Some of these things are just facts that you learn and others are things you really have to understand.

Every time I interview, I go over the same stuff. I wanted to create a gist of the TL;DR things that would jog my memory and hopefully yours too.

Lots of these things are real things I've been asked that caught me off guard. It's nice to have something you ca

CyberPunkCodes

# Source Reload
alias reload.zsh="source ~/.zshrc"
alias reload.profile="source ~/.bash_profile"
alias reload.term="source ~/.bash_profile && source ~/.zshrc"

# cd
alias ..="cd .."

# ls
alias ll="ls -AlhG"

nikhita

How to update the Go version

System: Debian/Ubuntu/Fedora. Might work for others as well.

1. Uninstall the exisiting version

As mentioned here, to update a go version you will first need to uninstall the original version.

To uninstall, delete the /usr/local/go directory by:

jchandra74

HOWTO: Create Your Own Self-Signed Certificate with Subject Alternative Names Using OpenSSL in Ubuntu Bash for Window

Overview

My main development workstation is a Windows 10 machine, so we'll approach this from that viewpoint.

Recently, Google Chrome started giving me a warning when I open a site that uses https and self-signed certificate on my local development machine due to some SSL certificate issues like the one below:

ravibhure

In your local clone of your forked repository, you can add the original GitHub repository as a "remote". ("Remotes" are like nicknames for the URLs of repositories - origin is one, for example.) Then you can fetch all the branches from that upstream repository, and rebase your work to continue working on the upstream version. In terms of commands that might look like:

Add the remote, call it "upstream":

git remote add upstream https://github.com/whoever/whatever.git

Fetch all the branches of that remote into remote-tracking branches, such as upstream/master:

git fetch upstream

jamesarosen

I don't have a Grand Vision for (S)CSS, but I do have some ideas.

Cohesion & Coupling

In JavaScript (and any other "programming language"), we value cohesion and eschew coupling. To value cohesion is to say that all of the foo-related things are in the Foo component or the app/pods/foo pod or the lib/foo addon. Like things are together. To eschew coupling is to say that two unrelated things should not need to know about one another. Unlike things don't rely on one another. Further reading on Cohesion & Coupling:

• http://courses.cs.washington.edu/courses/cse403/96sp/coupling-cohesion.html (my favorite reference on the topic)
• http://enterprisecraftsmanship.com/2015/09/02/cohesion-coupling-difference/ (good visuals)
• http://c2.com/cgi/wiki?CouplingAndCohesion
• https://en.wikipedia.org/wiki/Connascence_(computer_programming) (connascense is closely related to cohesion)

vasanthk

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?