Legend:
- ✏️ method changes
this
. - 🔒 method does not change
this
.
Array<T>.prototype.*
:
concat(...items: Array: T[]
🔒 ES3
rebase
vs merge
).rebase
vs merge
)reset
vs checkout
vs revert
)git rev-parse
)pull
vs fetch
)stash
vs branch
)reset
vs checkout
vs revert
)Here are my goals that I would like to accomplish over the next year.
#!/usr/bin/env ruby | |
require 'yaml' | |
require 'json' | |
input_dirname = ARGV[0] | |
output_filename = "parsed_interviews.json" | |
class Categorizer | |
HW_CATEGORIES = [[/.*dell.*/, ["pc","system"]], |
Blog typography
Pets and Yoga at work isn't culture
Being a Senior Developer
Technology of Future -interesting blog post
General Interview Questions and stuff
Arduino for beginners
MonoRails - young vs mature Rails app - words of wisdom
Programming Jokes
Blueprint - Reverse Engineer Instances
Random Name generator
Senior programmers won't have a problem with these, while junior programmers will usually give only half-answers.
A text-book answer: classes are a blue-print for constructing computer models for real or virtual objects... boring.
In reality: classes hold data, have methods that interact with that data, and are used to instantiate objects.
Classes are a blue-print, they may hold data, likely they hold methods; classes are directly connected with an idea of objects, because object is an instance of a class. As objects are first-class citizens in Ruby, there is a main, root class Object, and all classes are inherited from this root entity. Modules, generally, are a tool for mix-ins and they provide something we call a namespace. Modules cannot be initialised the way we can do this with classes, but they provide a multiple inheritance.