Skip to content

Instantly share code, notes, and snippets.

@swalke16
swalke16 / workday_request.py
Created July 11, 2022 15:32
Workday credential verification
import requests
import json
from xmltodict import parse
# Populate these with your Workday info!
tenant_name = ""
username = f"ISU_USERNAME@{tenant_name}"
password = ""
# Exact URL may vary
url = f"https://services1.myworkday.com/ccx/service/{tenant_name}/Human_Resources/v38.2"
<!DOCTYPE html>
<html>
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width">
<title>IKE Custom Application Example</title>
</head>
<body style="background-color: white; font-size: 32px;">
<input type='text' id="txtBox" />
</body>
<!DOCTYPE html>
<html>
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width">
<title>IKE Custom Application Example</title>
</head>
<body style="background-color: white; font-size: 32px;">
<input type='text' id="txtBox" />
</body>
<!DOCTYPE html>
<html>
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width">
<title>IKE Custom Application Example</title>
<script>
// For security reasons the external application should only receive or
// send events from the IKE application. The origin below is the correct origin
// for the application to run on production. For the IKE Test environment you
@swalke16
swalke16 / test.ics
Last active October 4, 2019 14:43
test cal
BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:PUBLISH
X-WR-CALNAME:October 2019 Events
X-WR-TIMEZONE:America/Chicago
BEGIN:VEVENT
DTSTART:20191003T000000Z
DTEND:20191003T020000Z
@swalke16
swalke16 / sna.ical
Created July 22, 2019 20:52
sna ical test
BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:PUBLISH
X-WR-CALNAME:City Events
X-WR-TIMEZONE:America/Chicago
BEGIN:VEVENT
DTSTART:20190725T180000Z
DTEND:20190725T200000Z
@swalke16
swalke16 / sync-places-for-categories.rb
Created February 13, 2019 15:31
Sync Places For New Categories
# this script given that new categories have been created and attached to the relevant apps
# will for the specified account_names and category_names sync all the relevant google places
account_names = ["Baltimore", "Denver", "Los Angeles",
"Short North", "SMRT Columbus"]
category_names = ["Antiques & Vintage", "Beer, Wine, & Spirits", "Juice & Natural Foods"]
accounts = Account.where(name: account_names)
accounts.each do |account|
category_ids = account.categories.where(name: category_names).pluck(:id)
@swalke16
swalke16 / sna.rb
Last active December 6, 2018 18:08
Add SNA Website Places to featured list
# Note this process is bad and currently broken. During this import I discovered that something like 92 records with google IDS matched during the populate step did not exist in our data pulled in by google. Furthermore we had dropped 19 other places that couldn't be matched to google.
#SCRAPE --> IMPORT —> POPULATE —>
web_list = PlaceList.find(51)
goog_list = PlaceList.find(45)
featured_list = FeaturedList.find(12)
PopulateGoogleIdsJob.perform_later(web_list)
=== RUNNING COMMAND IN /Users/swalker/Documents/dev/lendinghome-monolith/client/src/components-core ===
yarn install
yarn install v0.16.1
info No lockfile found.
success Nothing to install.
Done in 0.06s.
=== RUNNING COMMAND IN /Users/swalker/Documents/dev/lendinghome-monolith/client/src/components-core ===
yarn link
@swalke16
swalke16 / coding_assignment.md
Last active March 8, 2016 20:13
Coding Assignment

##Assignment We would like you to create an application that plays the game farkle against a human competitor, and we’d like you to implement it in ruby.

####Guidelines:

  1. Use any resources (books, videos, web sites, etc...) that you need to create your solution. This is a test about how well and fast you can learn.
  2. Use the standard rules for farkle from the wikipedia page.
  3. You don't need to make the interface look pretty. A terminal based interface that shows the state of the game and allows the human to play is fine.
  4. Use git / github as source control and to share the project with us. Remember to try and take small steps, commit frequently, and use meaningful commit messages.
  5. Don't attempt any bonus item(s) (except perhaps unit tests) until you have a working simple solution.