Skip to content

Instantly share code, notes, and snippets.

View reshleman's full-sized avatar

Robert Eshleman reshleman

9 followers · 0 following
View GitHub Profile
@ram-nadella
ram-nadella / Dockerfile
Last active May 22, 2020 20:32
tl;dr download this gist as a zip, unpack and run `docker-compose up` (need to have docker installed)
FROM ruby:2.7
RUN gem install sinatra redis
WORKDIR /app
COPY . .
CMD ["ruby", "web.rb", "-o", "0.0.0.0"]
@ryantuck
ryantuck / sre_checklist.md
Last active March 17, 2021 15:24

Regular Tasks

Regular Tasks include how normal, non-emergency, operational duties are handled—that is, how work is received, queued, distributed, processed, and verified, plus how periodic tasks are scheduled and performed. All services have some kind of normal, scheduled or unscheduled work that needs to be done. Often web operations teams do not perform direct customer support but there are interteam requests, requests from stakeholders, and escalations from direct customer support teams. These topics are covered in Chapters 12 and 14.

Sample Assessment Questions

@claudiosanches
claudiosanches / test.php
Last active February 22, 2024 19:39
Regex for test credit card brand
<?php
// Test cards
$cards = array(
'378282246310005', // American Express
'371449635398431', // American Express
'5078601870000127985', // Aura
'5078601800003247449', // Aura
'30569309025904', // Diners Club
'38520000023237', // Diners Club
@CGenie
CGenie / console.html
Created August 12, 2014 10:23
Selenium Firefox console log
<html>
<head>
<script type="text/javascript">
console.log('TEST TEST');
window.dump('DUMP DUMP');
console.error('ERROR ERROR');
</script>
</head>
<body>
@gabebw
gabebw / how_to_pr.md
Created July 24, 2014 20:28
How to Read a Pull Request

How to Read a Pull Request

  1. Go to the main pull request URL. It should end in /pull/NUMBER. Look at the 3 tabs right under the PR title. You should be in the "Conversation" view.

  2. Read the PR title and the PR description. The description should tell you what the developer is trying to accomplish in this PR. This gives you some mental structure so you know what you're looking at. It can also tell you what doesn't belong in this PR.

@hrs
hrs / say_repl.rb
Created July 21, 2014 01:25
REPL for Say
#!/usr/bin/env ruby
class SayRepl
attr_reader :voice
def initialize(voice)
@voice = voice
end
def go
@gabebw
gabebw / routes_and_objects.md
Last active August 29, 2015 14:02
Routes as objects

Routes and their Objects

Note that show paths and index paths are not arrays.

The object to use is what you'd pass to form_for, link_to, or redirect_to.

Name at /rails/info/routes object to use path
root_path no object-oriented way. Need to use root_path /
@wojtha
wojtha / Locales.yaml
Created January 15, 2014 10:13 — forked from s-andringa/Locales.yml
config.exceptions_app and ExceptionController
# config/locales/en.yml
en:
exception:
show:
not_found:
title: "Not Found"
description: "The page you were looking for does not exists."
internal_server_error:
title: "Internal Server Error"
@adamwiggins
adamwiggins / adams-heroku-values.md
Last active April 4, 2024 14:53
My Heroku values

Make it real

Ideas are cheap. Make a prototype, sketch a CLI session, draw a wireframe. Discuss around concrete examples, not hand-waving abstractions. Don't say you did something, provide a URL that proves it.

Ship it

Nothing is real until it's being used by a real user. This doesn't mean you make a prototype in the morning and blog about it in the evening. It means you find one person you believe your product will help and try to get them to use it.

Do it with style

@steveclarke
steveclarke / capybara.md
Created April 10, 2012 17:32
RSpec Matchers

Capybara

save_and_open_page

Matchers

have_button(locator)