0xabad1dea

Risk Assessment of GitHub Copilot

0xabad1dea, July 2021

this is a rough draft and may be updated with more examples

GitHub was kind enough to grant me swift access to the Copilot test phase despite me @'ing them several hundred times about ICE. I would like to examine it not in terms of productivity, but security. How risky is it to allow an AI to write some or all of your code?

Ultimately, a human being must take responsibility for every line of code that is committed. AI should not be used for "responsibility washing." However, Copilot is a tool, and workers need their tools to be reliable. A carpenter doesn't have to

indiesquidge

/* 
 Let us re-create `Promise.all`

 `Promise.all` method returns a promise that resolves when all of the promises in the iterable argument have resolved, 
 or rejects with the reason of the first passed promise that rejects.
 
 Read more about `Promise.all` on MDN: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise/all
 
 A basic example would be something like this:
 

cscott530

NOTE: You will need to be a Slack admin, and have access to create web sites, etc., in the target Azure account.

• Go to slack, creating a new web hook.
  • Note the webhook URL (e.g. https://hooks.slack.com/services/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)
  • Set it to post the channel you'd like.
• Go here, click deploy.
  • This adds a web-hook listening site to Azure
• Log in to Azure and find the above site that just deployed
  • Open the Application Settings, find App Settings
• Add slackhookuri, set its value to the above web hook URL (hooks.slack.com...)

traviskaufman

Better Jasmine Tests With this

On the Refinery29 Mobile Web Team, codenamed "Bicycle", all of our unit tests are written using Jasmine, an awesome BDD library written by Pivotal Labs. We recently switched how we set up data for tests from declaring and assigning to closures, to assigning properties to each test case's this object, and we've seen some awesome benefits from doing such.

The old way

Up until recently, a typical unit test for us looked something like this:

describe('views.Card', function() {

octocat

# Compiled source #
###################
*.com
*.class
*.dll
*.exe
*.o
*.so

# Packages #

IcyMidnight

DELIMITER |

CREATE FUNCTION uuid_from_bin(b BINARY(16))
RETURNS CHAR(36) DETERMINISTIC
BEGIN
  DECLARE hex CHAR(32);
  SET hex = HEX(b);
  RETURN CONCAT(LEFT(hex, 8), '-', MID(hex, 9,4), '-', MID(hex, 13,4), '-', MID(hex, 17,4), '-', RIGHT(hex, 12));
END
|