GNU Octave is a high-level interpreted language, primarily intended for numerical computations.
(via GNU Octave)
- not equal
~=
- logical AND
&&
GNU Octave is a high-level interpreted language, primarily intended for numerical computations.
(via GNU Octave)
~=
&&
import Ember from 'ember'; | |
Ember.TextField.reopen({ | |
init: function() { | |
this._super(); | |
var self = this; | |
Object.keys(this).forEach(function(key) { | |
if (key.substr(0, 5) === 'data-') { | |
self.get('attributeBindings').pushObject(key); |
import Ember from 'ember'; | |
export default Ember.Controller.extend({ | |
appName:'Ember Twiddle' | |
}); |
(by @andrestaltz)
So you're curious in learning this new thing called Reactive Programming, particularly its variant comprising of Rx, Bacon.js, RAC, and others.
Learning it is hard, even harder by the lack of good material. When I started, I tried looking for tutorials. I found only a handful of practical guides, but they just scratched the surface and never tackled the challenge of building the whole architecture around it. Library documentations often don't help when you're trying to understand some function. I mean, honestly, look at this:
Rx.Observable.prototype.flatMapLatest(selector, [thisArg])
Projects each element of an observable sequence into a new sequence of observable sequences by incorporating the element's index and then transforms an observable sequence of observable sequences into an observable sequence producing values only from the most recent observable sequence.
Most accidents are attributed to human error, but in almost all cases human error was the direct result of poor design
When you have trouble with things — whether it’s figuring out whether to push or pull a door — it’s not your fault. Don’t blame yourself: blame the designer. When we see an object we’ve never used before, how do we know how to use it? The appearance of the device should provide the critical clues required for its proper operation — knowledge has to be both in the head and in the world.
Conceptual Model. The human mind is a wonderful organ of understanding. A good conceptual model can make the difference between successful and erroneous operation of many devices in our life. Design is an act of communication between the designer and the user, except that all the communication has to come about the the appearance of the device itself.
class Person | |
def initialize(name) | |
@name = name | |
end | |
def small_talk(other) | |
greet(other) | |
topics = methods.grep /^chat_about_/ | |
topics.shuffle! |
# Select all invoices with last_error | |
blob = Invoice.where("last_error ILIKE ?", "Invalid field%").includes(advisor: :bank_account).map do |invoice| | |
[ invoice.id, invoice.bank_account.account_number_crypted, invoice.bank_account.aba_crypted ] | |
end.to_json | |
# On blueberry | |
require_relative 'app' | |
require 'json' |
source 'http://rubygems.org' | |
gem 'arel', github: 'rails/arel' | |
gem 'rack', github: 'rack/rack' | |
gem 'i18n', github: 'svenfuchs/i18n' | |
gem 'rails', path: 'vendor/rails' | |
gem 'sqlite3' | |
gem 'pry' |
require 'bundler' | |
Bundler.setup(:default) | |
require 'active_record' | |
require 'active_record' | |
require 'minitest/autorun' | |
require 'logger' | |
require 'pry' | |
# Ensure backward compatibility with Minitest 4 |
module ActiveRecord | |
# = Active Record Autosave Association | |
# | |
# +AutosaveAssociation+ is a module that takes care of automatically saving | |
# associated records when their parent is saved. In addition to saving, it | |
# also destroys any associated records that were marked for destruction. | |
# (See +mark_for_destruction+ and <tt>marked_for_destruction?</tt>). | |
# | |
# Saving of the parent, its associations, and the destruction of marked | |
# associations, all happen inside a transaction. This should never leave the |