stenuto

#!/bin/bash

# Function to display usage information
usage() {
    echo "Usage: $0 /path/to/input.mp4 [ /path/to/output_directory ]"
    exit 1
}

# Check if at least one argument (input file) is provided
if [ $# -lt 1 ]; then

trvswgnr

#!/bin/sh

print_usage() {
    echo "usage: compress_video <input_file>"
    echo "supported formats: mp4, webm, mkv, mov, avi, flv"
}

get_extension() {
    f="${1##*/}"
    case "$f" in

tokejepsen

import subprocess
import sys
import os
import json
import shutil

import requests
import opentimelineio as otio

haranjackson

REGION=eu-west-1
VER=1.7.3
RUNTIME=python3.7

docker run -v $(pwd):/out -it lambci/lambda:build-$RUNTIME \
    pip install scrapy==$VER -t /out/build/scrapy/python

cd build/scrapy
zip -r ../../scrapy.zip python/
cd ../..

1st1

import asyncio
import random
import time


async def worker(name, queue):
    while True:
        # Get a "work item" out of the queue.
        sleep_for = await queue.get()

wojteklu

Code is clean if it can be understood easily – by everyone on the team. Clean code can be read and enhanced by a developer other than its original author. With understandability comes readability, changeability, extensibility and maintainability.

---

General rules

1. Follow standard conventions.
2. Keep it simple stupid. Simpler is always better. Reduce complexity as much as possible.
3. Boy scout rule. Leave the campground cleaner than you found it.
4. Always find root cause. Always look for the root cause of a problem.

Design rules

n00neimp0rtant

## within current branch, squashes all commits that are ahead of master down into one
## useful if you merged with upstream in the middle of your commits (rebase could get very ugly if this is the case)
 
## commit any working changes on branch "mybranchname", then...
git checkout master
git checkout -b mybranchname_temp
git merge --squash mybranchname
git commit -am "Message describing all squashed commits"
git branch -m mybranchname mybranchname_unsquashed
git branch -m mybranchname