This gist shows how to create a GIF screencast using only free OS X tools: QuickTime, ffmpeg, and gifsicle.
To capture the video (filesize: 19MB), using the free "QuickTime Player" application:
#!/bin/bash | |
# This script finds all the mercurial repositories in the current directory | |
# and does a "hg pull -u" to get the latest changes from all the repositories. | |
# | |
# Make sure you know what you're doing before running this ;-) | |
confirm_prompt() { | |
read -p "Are you sure you want to 'hg pull -u' every repository? " -n 1 | |
echo |
# Load balancer configuration | |
upstream exampleApp { | |
# Directs to the process with least number of connections. | |
least_conn; | |
# One failed response will take a server out of circulation for 20 seconds. | |
server 127.0.0.1:10080 fail_timeout=20s; | |
#server 127.0.0.1:10081 fail_timeout=20s; | |
#server 127.0.0.1:10082 fail_timeout=20s; | |
#server 127.0.0.1:10083 fail_timeout=20s; |
Servo serv; | |
int pos = 0; | |
void setup() { | |
serv.attach(D0); | |
Spark.function("setpos", setPos); | |
Spark.variable("getpos", &pos, INT); | |
} | |
void loop() { |
Recently CSS has got a lot of negativity. But I would like to defend it and show, that with good naming convention CSS works pretty well.
My 3 developers team has just developed React.js application with 7668
lines of CSS (and just 2 !important
).
During one year of development we had 0 issues with CSS. No refactoring typos, no style leaks, no performance problems, possibly, it is the most stable part of our application.
Here are main principles we use to write CSS for modern (IE11+) browsers:
Disclaimer: This piece is written anonymously. The names of a few particular companies are mentioned, but as common examples only.
This is a short write-up on things that I wish I'd known and considered before joining a private company (aka startup, aka unicorn in some cases). I'm not trying to make the case that you should never join a private company, but the power imbalance between founder and employee is extreme, and that potential candidates would
// src/index.js | |
/* eslint-disable no-console */ | |
const logger = require('winston'); | |
const app = require('./app'); | |
const port = app.get('port'); | |
process.on('unhandledRejection', (reason, p) => { | |
logger.error('Unhandled Rejection at: Promise ', p, reason); |
*update: TBC, but this new might affect how easy it is to use this technique past August 2024: Authy is shutting down its desktop app | The 2FA app Authy will only be available on Android and iOS starting in August
This gist, based in part on a gist by Brian Hartvigsen, allows you to export from Authy your TOTP tokens you have stored there.
Those can be "standard" 6-digits / 30 secs tokens, or Authy's own version, the 7-digits / 10 secs tokens.
Recently more and more chatbots appear, the overall chatbot market grows and the platform for it grows as well. Today we are taking a close look at what benefits creating a microservice chatbot on Discord - (a communication platform mainly targeted at gamers) would provide.
The concepts and ideas explained in this whitepaper are geared towards bots with a bigger userbase where the limits of a usual bot style appear with a greater effect
(If you are already proficient with the Discord API and the way a normal bot works, you may skip ahead to The Concept)
"""Performs automatic speed edits to audio books. | |
Example usage: | |
Assuming you have an audiobook book.aax on your Desktop: | |
1. Convert it to wav: | |
ffmpeg -i ~/Desktop/book.aax ~/Desktop/book.wav | |
2. Adjust the speed: |