BlueHatbRit

Toot.sh Code of Conduct

This document lays out the ground rules for participating in the Toot.sh community. It is intended to protect all members of our community from harassment and to ensure that our community is as welcoming and inclusive as possible. This is a working document, so the Toot.sh team may amend this CoC to better meet these goals in the future.

Goals

• Provide a friendly, safe, and welcoming environment for everyone interested in technology, games, and other similar interests, regardless of level of experience, gender identity or expression, sexual orientation, disability, personal appearance, body size, race, ethnicity, age, religion, nationality, political affiliation, or other similar characteristic.
• Create a supportive community, where people freely share their passions and are excited and positive about each other’s successes.
• Provide a venue for casual conversations — we may all be passionate about technology, games, etc, but that doesn’t mean that our conversations always c

BlueHatbRit

const max = 50;

function shuffle(a) {
    for (let i = a.length - 1; i > 0; i--) {
        const j = Math.floor(Math.random() * (i + 1));
        [a[i], a[j]] = [a[j], a[i]];
    }
    return a;
}

BlueHatbRit

Hello this is interesting how are you doing today?

BlueHatbRit

{
    // General
    "editor.fontFamily": "'Dank Mono', Menlo, Monaco, 'Courier New', monospace",
    "editor.fontSize": 14,
    "workbench.editor.enablePreview": false,
    "editor.tabSize": 2,
    "files.exclude": {
        "**/.git": false,
    },
    "breadcrumbs.enabled": true,

BlueHatbRit

import * as raven from 'raven';
import * as express from 'express';
import * as packageJson from './package.json';

const app: express.Express = express();

const SENTRY_DNS = 'your sentry dns setting will be here';

app.use(configureSentry(SENTRY_DNS));
app.use(sentry.errorHandler());

BlueHatbRit

Write an overview of the pull requests intentions.

Pre-merge tasks

• version number bumped
• tested (with automated and by hand)

Changes

List your changes. If several people worked on this PR mention the lead author at the end, like this: @sgmccli.

BlueHatbRit

<li class="js-stream-item stream-item stream-item
" data-item-id="937788308805038081" id="stream-item-tweet-937788308805038081" data-item-type="tweet" data-suggestion-json="{&quot;suggestion_details&quot;:{},&quot;tweet_ids&quot;:&quot;937788308805038081&quot;,&quot;scribe_component&quot;:&quot;tweet&quot;}">

    <div class="tweet js-stream-tweet js-actionable-tweet js-profile-popup-actionable dismissible-content original-tweet js-original-tweet promoted-tweet has-cards has-content presented scribed"
        data-tweet-id="937788308805038081" data-item-id="937788308805038081" data-permalink-path="/sddconf/status/937788308805038081"
        data-conversation-id="937788308805038081" data-tweet-nonce="937788308805038081-fe85042d-f426-4924-b0bc-3fc004dc0c85"
        data-tweet-stat-initialized="true" data-screen-name="sddconf" data-name="SoftwareDesign&amp;Dev" data-user-id="1342752169"
        data-you-follow="false" data-follows-you="false" data-you-block="false" data-tagged="quorralyne aahoogendoorn jbogard a

BlueHatbRit

What I Wish I'd Known About Equity Before Joining A Unicorn

Disclaimer: This piece is written anonymously. The names of a few particular companies are mentioned, but as common examples only.

This is a short write-up on things that I wish I'd known and considered before joining a private company (aka startup, aka unicorn in some cases). I'm not trying to make the case that you should never join a private company, but the power imbalance between founder and employee is extreme, and that potential candidates would

BlueHatbRit

Keybase proof

I hereby claim:

• I am bluehatbrit on github.
• I am elliotb (https://keybase.io/elliotb) on keybase.
• I have a public key ASB2dOmtkeomPvxflNbJFFvobxzGddAv_MukVri32swtHwo

To claim this, I am signing this object:

BlueHatbRit

We want to encourage all students to get involved with the development of this course. The materials here are mostly developed and curated by the staff team but we admit that we may miss things, or occationally get them wrong. We've put together some guidelines that should help you get started with making contributions.

Thanks for helping improve this course for everyone!

Questions, concerns, or issues

If you've got a question or problem that you think others may have, then please read this first.

The GitHub issue tracker is our preferred channel for dealing with these questions. It keeps questions public and allows others to pitch in with potential solutions, it also means everything is documented for the future. This should not be used for personal questions or issues unfit for public discussion, in those instances we encourage you to email the member of staff responsible for this course.