| class UserCreator | |
| def initialize(listener) | |
| @listener = listener | |
| end | |
| def create(attributes) | |
| user = User.new(attributes) | |
| if user.save | |
| # send email |
These are my notes basically. At first i created this gist just as a reminder for myself. But feel free to use this for your project as a starting point. If you have questions you can find me on twitter @thomasf https://twitter.com/thomasf This is how i used it on a Debian Wheezy testing (https://www.debian.org/releases/testing/)
Discuss, ask questions, etc. here https://news.ycombinator.com/item?id=7445545
List some crypto libraries for JavaScript out there. Might be a bit out dated. Scroll to the bottom.
http://www.w3.org/TR/WebCryptoAPI/
This specification describes a JavaScript API for performing basic cryptographic operations in web applications, such as hashing, signature generation and verification, and encryption and decryption. Additionally, it describes an API for applications to generate and/or manage the keying material necessary to perform these operations. Uses for this API range from user or service authentication, document or code signing, and the confidentiality and integrity of communications.
| module PubSub | |
| class << self | |
| def create type, channel, object | |
| channel = channel.to_sym | |
| case type | |
| when :listener | |
| listeners[channel] ||= Array.new | |
| listeners[channel] << object | |
| channels[channel] ||= Array.new |
The difference between those are that unit tests one object and one object only. Typically mocking anything else outside the SUT (System under test).
Integration tests a system of collaborators, or multiple objects that work in concert. Functional tests a system from the outside into the centre as a full stack test. User stories test interactions and outcomes.
The difference between functional and user stories is that a functional test exercises a system with a focus of "given this kind of input, I expect this output back" and user story is more focused on "When I perform this kind of thing, given the system is in this kind of state or has this data, I expect to see this kind of thing as a result."
Functional can also test the side-effects rather than just the input and output.
| #!/usr/bin/env zsh | |
| # | |
| # Works best with blinking text; the last heart will blink | |
| # when you have less than 25% of your battery life remaining. | |
| BATTERY="$(pmset -g ps | awk 'NR==2' | perl -pe 's/.*?(\d+)%.*/\1/')" | |
| if [[ $BATTERY -lt 25 ]]; then | |
| echo "\e[5;31m♥\e[0;31m♡♡\e[0m" | |
| elif [[ $BATTERY -lt 50 ]]; then |
| $ curl https://api.github.com/zen | octocatsay | |
| MMM. .MMM | |
| MMMMMMMMMMMMMMMMMMM | |
| MMMMMMMMMMMMMMMMMMM ____________________________ | |
| MMMMMMMMMMMMMMMMMMMMM | | | |
| MMMMMMMMMMMMMMMMMMMMMMM | Practicality beats purity. | | |
| MMMMMMMMMMMMMMMMMMMMMMMM |_ ________________________| | |
| MMMM::- -:::::::- -::MMMM |/ | |
| MM~:~ ~:::::~ ~:~MM |
| $VERBOSE = nil | |
| require File.expand_path('../rooby', __FILE__) | |
| Person = Rooby::Class.new 'Person' do | |
| define :initialize do |name| | |
| @name = name | |
| end | |
| define :name do |
| # Do not refactor, it is a bad practice. YOLO | |
| # Not understanding why or how something works is always good. YOLO | |
| # Do not ever test your code yourself, just ask. YOLO | |
| # No one is going to read your code, at any point don't comment. YOLO | |
| # Why do it the easy way when you can reinvent the wheel? Future-proofing is for pussies. YOLO |
| ### | |
| # Scheme code is translated to YARV byte code, then evaluated in the | |
| # Ruby Virtual Machine | |
| require 'rbconfig' | |
| require 'dl' | |
| require 'fiddle' | |
| require 'strscan' | |
| class RubyVM |
