| /** | |
| * This code was used as a part of PoC, done for my talk at ReactKyiv meetup: | |
| * https://animationsslides.brutallo.now.sh/#/ | |
| * | |
| * | |
| * Emoji animations were inspired by this article: | |
| * https://matthewrayfield.com/articles/animating-urls-with-javascript-and-emojis/ | |
| */ | |
| /** |
| // create a bookmark and use this code as the URL, you can now toggle the css on/off | |
| // thanks+credit: https://dev.to/gajus/my-favorite-css-hack-32g3 | |
| javascript: (function() { | |
| var elements = document.body.getElementsByTagName('*'); | |
| var items = []; | |
| for (var i = 0; i < elements.length; i++) { | |
| if (elements[i].innerHTML.indexOf('* { background:#000!important;color:#0f0!important;outline:solid #f00 1px!important; background-color: rgba(255,0,0,.2) !important; }') != -1) { | |
| items.push(elements[i]); | |
| } | |
| } |
Sometimes a programming language has a "strict mode" to restrict unsafe constructs. E.g., Perl has use strict, Javascript has "use strict", and Visual Basic has Option Strict. But what about bash? Well, bash doesn't have a strict mode as such, but it does have an unofficial strict mode:
set -euo pipefail
set -e
by Tatiana Mac
Last updated 14 April 2021
As speaking comes with immense privilege, I have crafted a speaker rider to set expectations and boundaries around my engagement. I am grateful to all the conference organisers who have brilliantly hosted me. I would love to continue to exercise this privilege to speak at conferences, and use this privilege to make the landscape more accessible and beneficial to tech's most historically excluded and marginalised communities.
😫 I provide a lot of explanations for those of you who never had to consider these things. Most thoughtful conferences I've attended check most of these boxes intrinsically, particularly when conference runners are experienced speakers. They get it.
| Why do we have unadorned string literals (native strings) in our codebase? | |
| Doesn't that put us in danger of UnicodeError exceptions? | |
| (1) Your codebase should be using text by default. At the borders, you convert | |
| strings from other APIs into text and then use text throughout, only | |
| converting to bytes (or native strings) when those types are needed for | |
| another, outside API. | |
| (2) On Python2, text can be safely combined with (or compared to) text[1]_. Bytes | |
| can be combined with bytes. And ascii-only bytes can be combined with text. |
| """A pytest fixture for running an ssh mock server. | |
| Requires pytest and asyncssh: | |
| $ pip install pytest asyncssh | |
| """ | |
| from socket import AF_INET | |
| from unittest.mock import Mock | |
| from contextlib import asynccontextmanager |
| #!/bin/bash | |
| TOKEN="xxxxxxxxxxxxxxxxxxx" | |
| ZONE_ID=2222222222222222222222222 | |
| # [email protected] | |
| # KEY=11111111111111111111111111 | |
| # Replace with | |
| # -H "X-Auth-Email: ${EMAIL}" \ | |
| # -H "X-Auth-Key: ${KEY}" \ |
| def read_nonblocking(path, bufferSize=100, timeout=.100): | |
| import time | |
| """ | |
| implementation of a non-blocking read | |
| works with a named pipe or file | |
| errno 11 occurs if pipe is still written too, wait until some data | |
| is available | |
| """ | |
| grace = True |