SQLite3 Cheat Sheet
Download from: http://www.sqlite.org/download.html
Getting Started: http://www.sqlite.org/sqlite.html
# Replace <sentry_key>, <sentry-url> and <project-id> to formulate your CURL request. Don't forget to add a trailing slash to URL otherwise you'll get wierd CSRF errors! | |
curl -X POST --data '{ "exception": [{ "type": "$ErrorMessage"}] }' -H 'Content-Type: application/json' -H "X-Sentry-Auth: Sentry sentry_version=7, sentry_key=<sentry_key>, sentry_client=raven-bash/0.1" https://<sentry-url>/api/<project-id>/store/ |
# Set the gaudy prompt. | |
# ^O puts terminal back into default text mode for every prompt, | |
# preventing random glyphs. | |
resetterm="\[\017\]" | |
# \[ and \] prevent the shell from counting these characters | |
# against the line length. |
SQLite3 Cheat Sheet
Download from: http://www.sqlite.org/download.html
Getting Started: http://www.sqlite.org/sqlite.html
Feel free to contact me at [email protected] or tweet at me @statisticsftw
This is a rough outline of how we utilize next.js and S3/Cloudfront. Hope it helps!
It assumes some knowledge of AWS.
ASCI art characters for creating diagrams
clj -m cljs.main -re nashorn
(def thread (.type js/Java "java.lang.Thread"))
(let [global-atom-lock
(let [ctor (.type js/Java "java.util.concurrent.locks.ReentrantLock")]
(new ctor))]
// Copyright 2015 The Chromium Authors. All rights reserved. | |
// Use of this source code is governed by a BSD-style license that can be | |
// found in the LICENSE file. | |
import 'dart:async'; | |
import 'package:flutter/foundation.dart'; | |
import 'package:flutter/material.dart'; | |
import 'package:flutter/widgets.dart'; |
\usepackage{tkz-euclide} % checked for version 3.02c
CertSimple just wrote a blog post arguing ES2017's async/await was the best thing to happen with JavaScript. I wholeheartedly agree.
In short, one of the (few?) good things about JavaScript used to be how well it handled asynchronous requests. This was mostly thanks to its Scheme-inherited implementation of functions and closures. That, though, was also one of its worst faults, because it led to the "callback hell", an seemingly unavoidable pattern that made highly asynchronous JS code almost unreadable. Many solutions attempted to solve that, but most failed. Promises almost did it, but failed too. Finally, async/await is here and, combined with Promises, it solves the problem for good. On this post, I'll explain why that is the case and trace a link between promises, async/await, the do-notation and monads.
First, let's illustrate the 3 styles by implementing