Seth Krasnianski sethkrasnianski

Ps: The current setup was done on 01-04-19

Project Dependency Versions at the time 👇

  "react": "^16.7.0",
  "react-dom": "^16.7.0",
  "react-scripts": "2.1.3",
  "typescript": "^3.2.2"
  "tslint": "^5.12.0",
  "tslint-config-prettier": "^1.17.0",

Do not use forEach with async-await

TLDR: Use for...of instead of forEach() in asynchronous code.

For legacy browsers, use for...i or [].reduce()

To execute the promises in parallel, use Promise.all([].map(...))

The problem

This document has moved!

It's now here, in The Programmer's Compendium. The content is the same as before, but being part of the compendium means that it's actively maintained.

There's a couple of ways, one way is

Get search results
- Do SPC / and type in your search string
- or SPC x S and search string - where x is your scope indicator (p for project, d for directory, etc..)
Once you have the occurences you want, hit C-c C-e inside the helm buffer to put all your match occurences and puts them into a special buffer called the edit buffer or something like that
in that buffer you can use any commands you'd normally use on a buffer
the C-c C-c to commit your changes.

Automatic build versions from git in Xcode (and other goodies)

Installation procedure for pre-build actions to automatically populate Xcode Info.plist with dynamic data.

1. Xcode Scheme pre-action

Edit Xcode Scheme and add a pre-action script. Copy the contents of preaction.sh into the pre-action script box.

Hi Zach :D

Modals are funny beasts, usually they are a design cop-out, but that's okay, designers have to make trade-offs too, give 'em a break.

First things first, I'm not sure there is such thing as a "simple" modal that is production ready. Certainly there have been times in my career I tossed out other people's "overly complex solutions" because I simply didn't understand the scope of the problem, and I have always loved it when people who have a branch of experience that I don't take the time

Hi Nicholas,

I saw you tweet about JSX yesterday. It seemed like the discussion devolved pretty quickly but I wanted to share our experience over the last year. I understand your concerns. I've made similar remarks about JSX. When we started using it Planning Center, I led the charge to write React without it. I don't imagine I'd have much to say that you haven't considered but, if it's helpful, here's a pattern that changed my opinion:

The idea that "React is the V in MVC" is disingenuous. It's a good pitch but, for many of us, it feels like in invitation to repeat our history of coupled views. In practice, React is the V and the C. Dan Abramov describes the division as Smart and Dumb Components. At our office, we call them stateless and container components (view-controllers if we're Flux). The idea is pretty simple: components can't

	#!/usr/bin/env sh

	# Multiple vulnerabilities have been disclosed in RubyGems:
	# https://www.ruby-lang.org/en/news/2018/02/17/multiple-vulnerabilities-in-rubygems/
	#
	# And again in March 2019:
	# https://blog.rubygems.org/2019/03/05/security-advisories-2019-03.html
	#
	# If you're an Rbenv user, here's any easy one-liner to upgrade to a
	# safe version of Rubygems (2.7.8 / 3.0.3 or later) for each installed Ruby version:

	defmodule Async do

	def run do

	task1 = Task.async(fn -> :timer.sleep(10000); :slow end)
	task2 = Task.async(fn -> :timer.sleep(2000); :fail end)
	task3 = Task.async(fn -> :timer.sleep(1000); :fail end)

	await([task1, task2, task3])
	end

	wait4eth1() {
	CNT=0
	until ip a show eth1 \| grep -q UP
	do
	[ $((CNT++)) -gt 60 ] && break \|\| sleep 1
	done
	sleep 1
	}
	wait4eth1