atwalsh

import picar_4wd as fc
from picar_4wd import Ultrasonic, Pin
import time
import collections
import random

us = Ultrasonic(Pin('D8'), Pin('D9'))
power_val = 25

atwalsh

#!/bin/bash
# Credit: https://fitzcarraldoblog.wordpress.com/2018/08/06/how-to-move-a-mouse-pointer-automatically-in-linux-to-simulate-user-activity/
# Script to keep mouse pointer moving so that, for example, Suspend to RAM timeout does not occur.
#
# The mouse pointer will move around its current position on the screen, i.e. around any position
# on the screen where you place the pointer. However, if you prefer it to move around the centre
# of the screen then change mousemove_relative to mousemove in the xdotool command below.
#
# Set LENGTH to 0 if you do not want the mouse pointer to actually move.
# Set LENGTH to 1 if you want the mouse pointer to move just a tiny fraction.

atwalsh

import stripe

stripe.api_key = ''
file_path = ''
connected_account_id = ''

with open(file_path, "rb") as fp:
    # Upload file to the platform account
    file = stripe.File.create(
        purpose="business_icon",

atwalsh

Story Points vs. Time-based Estimates

Story points...

Abstract Complexity, Not Time:

Story points measure the relative complexity of a task or user story rather than the absolute time it takes to complete. This abstraction allows teams to focus on the effort required to deliver a feature rather than getting bogged down in estimating hours or days, which can be highly variable and affected by external factors. Time is also heavily based on WHO is going to do the work. This can add another level of variable which can throw off the expectation for a sprint. If the individual who was “SUPPOSED” to work on the story is now no longer available, you MAY NOT have another individual as skilled to complete the work which risks a delay, or the work being deferred to another sprint.

Promote Relative Sizing: