Skip to content

Instantly share code, notes, and snippets.

View jendiamond's full-sized avatar
🏠
Working from home

JenDiamond jendiamond

🏠
Working from home
View GitHub Profile
@jendiamond
jendiamond / mob_manual.md
Last active October 26, 2020 20:58
The Mob Manual

The Manual of Mob

A guide to mob programming

The Manual of Mob provides guidelines for mob programming. Mobbing is similar to pair programming but with a roomful of people. The RGSoC group The Standard Librarians, who created this guideline, found this guide an incredibly effective tool to refer back to while mobbing. Mob programming keeps everyone on the same page while they are working and the project keeps moving forward through aggregated knowledge. Mobbing allows for an incredible learning environment where a group of people with varied experience levels, including a beginner or a new comer, can help make progress on a project from the very first day. This guide is meant to be a flexible tool for you to use and change to suit your needs. It is a great way to start and a good thing to come back to after you work together for a while.

==================

Values

RailsGirlsLA & vivaLAvue

October 16, 17, 24th, 2020

Sponsor Prospectus

Rails Girls / vivaLAvue is a three-day free event targeted at women to give them a great first experience in software craftmanship. We aim to impart inspiration to get started, tools to understand technology, and an open, supportive community. Rails Girls is not just about programming, it’s about building things. During the workshop, attendees will build their first Ruby on Rails application and a Vue app on the subsequent Saturday with help and guidance from their coach. We will also have inspiring lightning talks and exercises throughout. We provide guidance, encouragement and commraderie in a safe space to learn and ask questions.

Rails Girls worldwide

Mailers with your saw to the participants, students & coaches Printed material - stickers

The Agile Librarian


1 Introduction

Hi my name is Jen Diamond I am a developer at UCLA where my Team and I are working on a digital repository for the library.

I came to UCLA Library from the world of startups where Agile was a daily practice.

I was very fortunate to be mentored by Pivotal Labs who are top of the game consultants.

The Agile Librarian

At UCLA we are building our digital library using Agile methodologies. We use quick iterative sprints, work towards a minimum viable product and continuously deploy as we build. This is a switch from the waterfall building techniques that resulted in many unfinished projects and long waits for simple changes.

I will discuss the Agile tools and methods our teams uses, including

  • SPRINT PLANNING
  • RETROSPECTIVES
  • PAIR / MOB PROGRAMMING

Cookies Sessions and Encryption

chrome://settings/siteData

  • We send a token in a post request triggered by the button to EMEL
  • Then EMEL authenticates the User
  • Then EMEL sends back a GET request which returns the token in a redirect which follows the callback URL back to our SinaiPOC
  • Then WE verify the token by checking to see if it is stored in the database

NEXT

  • Set a cookie with the domain: sinai2.library.ucla.edu
Prefix / *_path Verb URI Pattern Controller#Action
importer_documentation_guide_path GET /importer_documentation/guide(.:format) importer_documentation#guide
importer_documentation_csv_path GET /importer_documentation/csv(.:format) importer_documentation#csv
csv_imports_path GET /csv_imports(.:format) csv_imports#index
- POST /csv_imports(.:format) csv_imports#create
new_csv_import_path GET /csv_imports/new(.:format) csv_imports#new
csv_import_path GET /csv_imports/:id(.:format) csv_imports#show
preview_csv_import_path POST /csv_imports/preview(.:format) csv_imports#preview
csv_imports_previe

Don't lose faith in the reliability of your test suite

https://engineering.gusto.com/eliminating-flaky-ruby-tests/ It is human nature to ignore alarms when there is a history of false signals coming from a system.

Flaky Tests have a destructive effect on developer productivity

  • builds were needlessly retried,
  • trust in our test suite was eroded, and
  • frustration with our CI system grew among the team.
  • Non-deterministic tests led to slower iteration velocity because we couldn’t rely on our build results, and