Skip to content

Instantly share code, notes, and snippets.

View scrabill's full-sized avatar
🍔
It's always a good time for a cheeseburger

Shannon Crabill scrabill

🍔
It's always a good time for a cheeseburger
View GitHub Profile
@thomasbuckle-uk
thomasbuckle-uk / free-cs-resources
Created August 21, 2020 13:43
**FREE** online resources, video lectures and courses for learning Computer Science from the Top Universities in the World.
Some resources that are really well reviewed
This is the series that I went through when I was doing my degree, helped me grasp so many concepts that I wasn't understanding. I also LOVE the lecturer, mehran sahami, in the videos. This is the CS 106A course - which is probably the best intro for CS imo. You'll have to skip to 41 minutes of first video as its just him talking about the course for his new students etc
https://www.youtube.com/watch?v=KkMDCCdjyW8&list=PL84A56BC7F4A1F852&index=2&t=187s
Here are some updated resources that I haven't done personally but might be more relevant to you and others
Video Lecutres site has many great recorded lectures and resources -http://videolectures.net/Top/Computer_Science/#q=CS
Same with class central - https://www.classcentral.com/subject/cs
@5t3ph
5t3ph / style-stage-guidelines.md
Last active July 7, 2020 16:43
[DRAFT] Style Stage Guidelines

The HTML for this page was created to be semantic, accessible, and free of nearly all other opinions. While typically extra divs are to be avoided, each sectioning element also includes a .container div as the first child for use as a styling aid since you do not have access to alter the base HTML. IDs are included where needed for nav anchors or accessibility, and a small number of additional classes are provided for key elements without IDs.

As a contributor, you agree to abide by the following guidelines and restrictions:

  • Branding is prohibited with the exception of Monthly and Weekly sponsors.
  • The HTML is not available to modify, except for attribution values that will be added from your submission metadata.
  • You may use any build setup you prefer to create your stylesheet, but the final submission should be the compiled, unminified CSS.
@taniarascia
taniarascia / auth.md
Last active March 23, 2025 14:27
JavaScript Authentication & Authorization Book/Course

Authentication in Real-World Web Apps with JavaScript

Outline of ideas, concepts to cover, potential projects to write.

Setup Idea

  • Book with a video for each chapter.

Prerequisites/Overview

I bundled these up into groups and wrote some thoughts about why I ask them!

If these helped you, I'd love to hear about it!! I'm on twitter @vcarl_ or send me an email carl.vitullo@gmail.com

Onboarding and the workplace

https://blog.vcarl.com/interview-questions-onboarding-workplace/

  • How long will it take to deploy my first change? To become productive? To understand the codebase?
  • What kind of equipment will I be provided? Will the company pay/reimburse me if I want something specific?

FWIW: I (@rondy) am not the creator of the content shared here, which is an excerpt from Edmond Lau's book. I simply copied and pasted it from another location and saved it as a personal note, before it gained popularity on news.ycombinator.com. Unfortunately, I cannot recall the exact origin of the original source, nor was I able to find the author's name, so I am can't provide the appropriate credits.


Effective Engineer - Notes

What's an Effective Engineer?

@scrabill
scrabill / putonglasses.txt
Last active August 21, 2016 02:51 — forked from cheeaun/putonglasses.txt
put on glasses unicode
(•_•)
( •_•)>⌐■-■
(⌐■_■)
@raghubetina
raghubetina / credentials.md
Last active April 23, 2021 00:48
Hiding your credentials from GitHub

Hiding your credentials from GitHub

In many cases, we need to use secret information in our Ruby; most commonly, API keys and email account passwords.

You should never paste these strings directly into your Ruby code. There are bots that can and will steal your API keys the instant you push your code to a public GitHub repository. Even if you pay for private repositories, it's a good idea to not store secrets in your repo -- you may not want all of your collaborators (interns?) to know, for example, the API keys to your payment processor.

(If you have already pushed an API key to a public repository, you should sign into your API dashboard now and invalidate that old key, and get a new one. Assume that the old one has already been stolen. Reverting your commit will do no good.)

But if our Ruby needs to use these secrets, but we can't keep them in our code, what's the solution? Environment variables. We're going to use a gem called Figaro to make this easy.

## How to hide API keys from github ##
1. If you have already pushed commits with sensitive data, follow this guide to remove the sensitive info while
retaining your commits: https://help.github.com/articles/remove-sensitive-data/
2. In the terminal, create a config.js file and open it up:
touch config.js
atom config.js