{ | |
"Version": "2012-10-17", | |
"Statement": [ | |
{ | |
"Effect": "Allow", | |
"Action": [ | |
"rds-db:connect" | |
], | |
"Resource": [ | |
"arn:aws:rds-db:region:account-id:dbuser:dbi-resource-id/database-user-name" |
#!/usr/bin/env bash | |
# TODO: Need to figure out the settings for the following: | |
# 1) Dock: Items with order (not capturing binary data - since that is dependent on installed apps) | |
# 2) Security & Privacy Preferences: Full Disk Access, Camera, Microphone | |
# 3) Login items for my user (i.e. apps started when I login) | |
# 4) Retina displays scaling | |
# 5) Finder sidebar with order | |
## |
#!/usr/bin/env bash | |
# | |
# The bumbailiff allows the team to take up a small amount of technical debt | |
# (TODOs in the code) for a limited period. After that period the script fails. | |
# | |
# It will find // TODO in .js or .jsx files, and # TODO in .feature files. | |
# | |
# For example, if the allowed period for all the TODOs is 14 days. | |
# * It's OK to have 1 TODO that is 13 days old | |
# * It's OK to have 3 TODOs that are 4 days old |
- 13" Macbook Pro 3.3 GHz i7 (late 2016)
- Microsoft Surface Book (2016)
- Dell up3216q 32" monitor
/** | |
* Automatically populates Zendesk public-facing "new ticket" fields | |
* on page load. | |
* | |
* To use, copy and paste into your New Request Page template (wrapped | |
* in a `<script></script>` tag). | |
* | |
* For most fields, just use the field name (so if the field is | |
* `request[subject]`, use `subject` in the URL, while | |
* `request[custom_fields][123456]` becomes `123456`). You can also use |
import collections, math, random, numpy | |
import tensorflow as tf | |
from sklearn.cross_validation import train_test_split | |
sentences = """hated the movie it was stupid;\ni hated it so boring;\nawesome the movie was inspiring;\nhated it what a disaster;\nwe hated the movie they were idiotic;\nhe was stupid, hated her;\nstupid movie is boring;\ninspiring ourselves, awesome;\ninspiring me, brilliant;\nwe hated it they were rubbish;\nany inspiring movie is amazing;\nit was stupid what a disaster;\nits stupid, rubbish;\nstupid, idiotic!;\nawesome great movie;\nboring, must be hated;\nhe was boring the movie was stupid;\nboring movie was a disaster;\nboth boring and rubbish;\nso boring and idiotic;\ngreat to amazing;\ndisaster, more than hated;\nbetween disaster and stupid;\ndisaster, so boring;\nawesome movie, brilliant;\ntoo awesome she was amazing;\nhe was brilliant loved it;\ndisaster, only idiotic;\nrubbish movie hated him;\nit was rubbish, why so stupid?;\nrubbish, too boring;\nrubbish, disaster!;\nrubbish, very |
This is a play proposal for a new wrapper around go build
that would build your binary but
wrap it in code that would prepare isolation around your binary on run.
A concept of this is in https://github.com/jfrazelle/binctr, in that it takes a docker image and embeds the contents into a final binary so you have a self-contained binary.
The binctr example is unnessesarily heavy for go
binaries because all you need is a completely static
binary.
All of the below properties or methods, when requested/called in JavaScript, will trigger the browser to synchronously calculate the style and layout*. This is also called reflow or layout thrashing, and is common performance bottleneck.
Generally, all APIs that synchronously provide layout metrics will trigger forced reflow / layout. Read on for additional cases and details.
elem.offsetLeft
,elem.offsetTop
,elem.offsetWidth
,elem.offsetHeight
,elem.offsetParent
name: "GoogleNet" | |
input: "data" | |
input_dim: 10 | |
input_dim: 3 | |
input_dim: 224 | |
input_dim: 224 | |
# hierarchy 1 | |
# conv -> relu -> pool -> lrn |