Skip to content

Instantly share code, notes, and snippets.

Gabriel Staples ElectricRCAircraftGuy

Block or report user

Report or block ElectricRCAircraftGuy

Hide content and notifications from this user.

Learn more about blocking users

Contact Support about this user’s behavior.

Learn more about reporting abuse

Report abuse
View GitHub Profile
@ElectricRCAircraftGuy
ElectricRCAircraftGuy / docusign_vs_digisign.md
Last active Nov 2, 2019
Why you should use DocuSign over SkySlope's DigiSign for digitally signing documents
View docusign_vs_digisign.md

Why you should use DocuSign over SkySlope's DigiSign for digitally signing documents

After signing digital documents over the last 2 years using both, I have to say I really hate DigiSign and really love DocuSign, for the following reasons:

Comparison:

  1. PDFs: I can't (meaning: I refuse to) sign a document without at least skimming it and understanding it. I need to mark it up as I go. I use Foxit Reader in Linux Ubuntu (it is a cross-platform program thankfully, and runs in Windows, Mac, and Linux) to digitally highlight, underline, and take notes inside PDFs. This means I need a PDF of the exact document I'm about to sign, in the exact same page order, before signing. Here's the differences between DocuSign and DigiSign:
    1. DocuSign: I click the "Download PDF" button at the top of the page, download and take notes on the PDF, then go back online and sign. I don't have to bother anyone at all to ask for a PDF copy.
    2. SkySlope's DigiSign: no option whatsoever to download a PDF unt
View count_total_project_code_lines_in_sublime
// Go to menue:
// find->find in files
// Switch on reg_ex button
// Find:
^(.*)$
// Where:
c:\your_folder\,*.php,*.phtml,*.js,*.inc,*.html, -*/folder_to_exclude/*
// Then click on the find button
// Be careful to not click on Replace!!!
View switch-local-git-repo-to-fork.md

If you are like me you find yourself cloning a repo, making some proposed changes and then deciding to later contributing back using the GitHub Flow convention. Below is a set of instructions I've developed for myself on how to deal with this scenario and an explanation of why it matters based on jagregory's gist.

To follow GitHub flow you should really have created a fork initially as a public representation of the forked repository and the clone that instead. My understanding is that the typical setup would have your local repository pointing to your fork as origin and the original forked repository as upstream so that you can use these keywords in other git commands.

  1. Clone some repo (you've probably already done this step).

    git clone git@github...some-repo.git
@ElectricRCAircraftGuy
ElectricRCAircraftGuy / GS_timing.py
Last active Oct 23, 2016
UPDATE: LATEST VERSION FOUND HERE NOW (https://github.com/ElectricRCAircraftGuy/PyTiming/); A Windows and Linux-compatible Python module for ultra-great resolution timestamps (sub-microsecond), even in older versions of Python 3 which don't natively support (in the time module, for instance) high resolutions like this. Website: http://www.electr…
View GS_timing.py
"""
timing.py
-create some low-level Arduino-like millis() (milliseconds) and micros()
(microseconds) timing functions for Python
By Gabriel Staples
http://www.ElectricRCAircraftGuy.com
-click "Contact me" at the top of my website to find my email address
Started: 11 July 2016
Updated: 7 Sept 2016
You can’t perform that action at this time.