LevelDB is Google's embedded key/value store that uses similar design concepts as the BigTable Tablet
package permutations | |
import java.util.* | |
interface Circular<T> : Iterable<T> { | |
fun state(): T | |
fun inc() | |
fun isZero(): Boolean // `true` in exactly one state | |
fun hasNext(): Boolean // `false` if the next state `isZero()` |
# 0 is too far from ` ;) | |
set -g base-index 1 | |
# Automatically set window title | |
set-window-option -g automatic-rename on | |
set-option -g set-titles on | |
#set -g default-terminal screen-256color | |
set -g status-keys vi | |
set -g history-limit 10000 |
/** | |
* A Gist proving that Kotlin's nullable type can be made into a monad without wrapping into another | |
* object and satisfy the Monadic laws | |
* | |
* Kotlin has comprehensive null safety built into the language enforced at compile time, using its | |
* nullable type. | |
* | |
* Its language structure makes dealing with nullable values simple and succinct. Unlike other language | |
* monadic constructs such as Option (scala), Optional(Java8+) and Maybe(Haskell), it is enforced at | |
* compile time and is compatible with existing non monad aware API (for example, |
Just migrated it from Codepen.io to markdown. Credit goes to David Conner.
Working with DOM | Working with JS | Working With Functions |
---|---|---|
Accessing Dom Elements | Add/Remove Array Item | Add Default Arguments to Function |
Grab Children/Parent Node(s) | Add/Remove Object Properties | Throttle Functions on Resize |
Create DOM Elements | Conditionals |
Once upon a time…
I once took notes (almost sentence by sentence with not much editing) about the architectural design concepts - Command and Query Responsibility Segregation (CQRS) and Event Sourcing (ES) - from a presentation of Greg Young and published it as a gist (with the times when a given sentence was heard).
I then found other summaries of the talk and the gist has since been growing up. See the revisions to know the changes and where they came from (aka the sources).
It seems inevitable to throw Domain Driven Design (DDD) in to the mix.
- By Edmond Lau
- Highly Recommended 👍
- http://www.theeffectiveengineer.com/
- They are the people who get things done. Effective Engineers produce results.
Due to the incessant swarm of complete and utter nonsense that has been forcing its way into Firefox over time, I've decided to start collecting my personal list of “must-have” about:config tweaks required to turn Firefox into a functional brower.
NOTE: Unfortunately this is somewhat out of date. The comments link to some resources that may be more up-to-date. Patches welcome.
These can be used for nefarious purposes and to bypass access restrictions.
Quite a lot of different people have been on the same trail of thought. Gary Bernhardt's formulation of a "functional core, imperative shell" seems to be the most voiced.
"Imperative shell" that wraps and uses your "functional core".. The result of this is that the shell has fewer paths, but more dependencies. The core contains no dependencies, but encapsulates the different logic paths. So we’re encapsulating dependencies on one side, and business logic on the other side. Or put another way, the way to figure out the separation is by doing as much as you can without mutation, and then encapsulating the mutation separately. Functional core — Many fast unit tests. Imperative shell — Few integration tests