Skip to content

Instantly share code, notes, and snippets.

View jesse-spevack's full-sized avatar

Jesse Spevack jesse-spevack

View GitHub Profile
@jesse-spevack
jesse-spevack / auth.gs
Created January 18, 2024 18:58
Delete Your Tweets
const API_KEY = PropertiesService.getScriptProperties().getProperty('apiKey')
const API_SECRET = PropertiesService.getScriptProperties().getProperty('apiKeySecret')
const ACCESS_TOKEN = PropertiesService.getScriptProperties().getProperty('accessToken')
const ACCESS_TOKEN_SECRET = PropertiesService.getScriptProperties().getProperty('accessTokenSecret')
const CLIENT_ID = PropertiesService.getScriptProperties().getProperty('clientId')
const CLIENT_SECRET = PropertiesService.getScriptProperties().getProperty('clientSecret')
/**
* Authorizes and makes a request to the Twitter API v2
* OAuth 2.0 Making requests on behalf of users
<div
data-controller="multiselect"
data-multiselect-selected-items-value=[]
>
...
</div>

The Minaswan::Interview

Session Format: Talk

Abstract

White-boarding is not nice. An unpaid take home project is not nice. We decided to apply the Ruby community motto "Matz is nice and so we are nice," to our enterprise technical interview process. Come learn what changes we made, how we enlisted support of other rubyists and non-rubyists alike, and how you can too.

Details

The current state of interviewing is not nice

About Turing Shadow Day

On-Site Job Shadowing

Schedule

Time Event
12:30 Welcome and overview of the day
1:00 Pair with Engineer
3:00 Q & A with Engineering Manager
3:30 Q & A with HR
@jesse-spevack
jesse-spevack / cfp_railsconf19_panic.md
Last active January 22, 2019 19:43
I am not panicking. You're panicking.

Title

Publicly viewable title. Ideally catchy, interesting, essence of the talk. Limited to 60 characters.

I am not panicking. You're panicking.

Format

  • Regular Session
  • Workshop

Track

```javascript
import {Component} from 'react'
class Counter extends Component {
state = {
count: 0
};
render() {
import React, { Component, PropTypes } from 'react';
const TOGGLE_BUTTON_SELECTOR = "toggle-button"
const TOGGLE_LABEL_SELECTOR = "toggle-label"
const DEFAULT_LABEL_TEXT = "Label Text"
const DEFAULT_BUTTON_LEFT_TEXT = "Button Left"
const DEFAULT_BUTTON_RIGHT_TEXT = "Button Right"
class ToggleButton extends Component {
constructor(props) {

Contributing to shoulda matchers

  • Why: I use shoulda matchers.
  • What: I found a feature request at thoughtbot/shoulda-matchers#927 that sounds approachable. It asks for some clarification in the docs / code about using the enum matcher.
  • I Need: to dig into shoulda matchers and get the dev setup running locally.
  • When I'm Done: In the original GitHub issue it sounds like the developers are in favor of the feature, so I think I can get this accepted for the next version of the library.

Contributing to factory girl

  • Why: I use factory girl.
@jesse-spevack
jesse-spevack / census_dtr.md
Last active November 28, 2016 18:30
Census DTR

DTR Memo

Project: Rails Engine

Group Member Names:

  • Jasmin Hudacsek
  • Calaway
  • Brian Goss
  • Jesse Spevack

Project Expectations:

What does each group member hope to get out of this project? Goals and expectations:

@jesse-spevack
jesse-spevack / exercism.md
Last active November 21, 2016 17:56
Jesse Spevack JavaScript Exercism Reflections

##Leap My code: here

  • Responder #1 (here) - This responder used a multi-line if / else statement and did not extract out the 3 modulo operations into a separate function.

  • Responder #2 (here) - This responder used a ternary statement, but unnecessarily included a true / false return.

  • Responder #3 (here) - This user decided to build the logic out with a nested conditional, nesting the %100 and %400 checks within the %4 conditional. It appears cleaner at first glance and the nested structure does mirror the logic of the problem, though I know in a more complex situation a nested conditional could prove to be a real can of worms.

  • Responder #4 (here - This responder used thr