Codified PC Setup.
source <(curl -s https://gist.githubusercontent.com/AlexAtkinson/27b12f4dfda31b1b74fcab3fc9a6d192/raw/init.sh)| # Ultra lazy sourcing | |
| # ------------------- | |
| alias urc='source ~/.bashrc' | |
| # Save history immediately | |
| shopt -s histappend | |
| grep -q 'history -a' <<< "$PROMPT_COMMAND" || export PROMPT_COMMAND="history -a; $PROMPT_COMMAND" | |
| # Regex |
| [Desktop Entry] | |
| Icon=/home/<user>/.local/share/pCloud/pcloud.svg | |
| Exec=/usr/local/bin/pcloud %u | |
| Version=1.0 | |
| Type=Application | |
| Categories=Network | |
| Name=pCloud | |
| StartupWMClass=pcloud | |
| MimeType=application/x-executable | |
| X-GNOME-Autostart-enabled=true |
This GIST is here simply to demonstrate some workflows I've found helpful in guaranteeing a well-developed backlog for iteration teams. That said, workflows can be as simple or as complex as you need for your organization/project. At scale though, it's highly desirable to have a backlog as beautifully maintained as your products as their qualities are interdependent. And you'll see this point surface in retrospectives/feedback over time.
First off, DO NOT have workflows that looks like this:
| #!/usr/bin/env python | |
| # Copy into /usr/local/bin or as appropriate for your $PATH | |
| import argparse | |
| from pypdf import PdfReader | |
| from pypdf.errors import PdfReadError | |
| parser = argparse.ArgumentParser() | |
| parser.add_argument("pdf", help="The PDF to extract attachments from.", type=str) |
Character Sets/Ranges [] : Match any characters within. Required expression.
Qualifiers {} : Quantity or range of an expression. IE: {3}, {2,200}
Groups () : Group expressions. Subgroups supported.
Non-Capturing Group (?:foo) : Does not "remember" matches. Lower overhead.
Kleen Star * : May occur 0 or more times.
APIGW is NOT the AWS service, but an industry standard technology for servicing resource access while providing facilities for oversight, governance, security, and operability considerations.
Some options:
🗒️ An excerpt from my good, ol' Jira Team Runbook.
Acceptance Criteria tactices are ever evolving, but this is a good skeleton to start from.