Read twice as fast, one word at a time | Jesse Liberty:
"Based on significant research, Flash Reading appears to be able to instantly increase your reading speed by 50% to 100% or more, while maintaining or increasing comprehension.
The general idea is to flash each word on the screen sequentially, pausing a bit for punctuation. Some more sophisticated incarnations slow down slightly for larger words."
5 Text Reader Apps That Really Help You Speed Read
Free online speed reading software | Spreeder.com
Wednesday, March 19, 2014
Datum - Data
Making Sense of Data - - Unit 1 - Introducing the Data Process:
"A datum is a single fact or piece of information.
The plural, data, is a collection of information. "
Data (/ˈdeɪtə/ day-tə or /ˈdætə/ da-tə, also /ˈdɑːtə/ dah-tə)
is a set of values of qualitative or quantitative variables;
restated, data are individual pieces of information.
"A datum is a single fact or piece of information.
The plural, data, is a collection of information. "
Data (/ˈdeɪtə/ day-tə or /ˈdætə/ da-tə, also /ˈdɑːtə/ dah-tə)
is a set of values of qualitative or quantitative variables;
restated, data are individual pieces of information.
Google: Making Sense of Data: Fusion Tables
Making Sense of Data - - Welcome to Making Sense of Data:
Google using data to change learning patterns
(and advertise new Fusion Tables tool)
Google using data to change learning patterns
(and advertise new Fusion Tables tool)
Activities Before Lessons
Although most courses present lessons before they present activities, our research has shown that activities are more beneficial for learning than watching videos and reading text. | |
In this class, activities are presented before lessons. This way, you get a chance to experience concepts before reading about them in the lessons. |
Event Sourcing
Event Sourcing: @ Martin Fowler
"Event Sourcing ensures that all changes to application state are stored as a sequence of events. Not just can we query these events, we can also use the event log to reconstruct past states, and as a foundation to automatically adjust the state to cope with retroactive changes"
Reference 3: Introducing Event Sourcing @ MSDN Patterns & Practices
Event Sourcing Basics · EventStore/EventStore Wiki @ GitHub
All events should be represented as verbs in the past tense such as CustomerRelocated, CargoShipped, or InventoryLossageRecorded.
A common question that arises is how to delete information.
It is not possible as previously jump into the time machine and say that an event never happened (eg: delete a previous event). As such it is necessary to model a delete explicitly as a new transaction...(that is un-doing effects of one that needs to be removed)
"Event Sourcing ensures that all changes to application state are stored as a sequence of events. Not just can we query these events, we can also use the event log to reconstruct past states, and as a foundation to automatically adjust the state to cope with retroactive changes"
Reference 3: Introducing Event Sourcing @ MSDN Patterns & Practices
- Events happen in the past. For example, "the speaker was booked," "the seat was reserved," "the cash was dispensed." Notice how we describe these events using the past tense.
- Events are immutable. Because events happen in the past, they cannot be changed or undone. However, subsequent events may alter or negate the effects of earlier events. For example, "the reservation was cancelled" is an event that changes the result of an earlier reservation event.
- Events are one-way messages. Events have a single source (publisher) that publishes the event. One or more recipients (subscribers) may receive events.
- Typically, events include parameters that provide additional information about the event. For example, "Seat E23 was booked by Alice."
- In the context of event sourcing, events should describe business intent. For example, "Seat E23 was booked by Alice" describes in business terms what has happened and is more descriptive than, "In the bookings table, the row with key E23 had the name field updated with the value Alice."
Event Sourcing Basics · EventStore/EventStore Wiki @ GitHub
All events should be represented as verbs in the past tense such as CustomerRelocated, CargoShipped, or InventoryLossageRecorded.
It is not possible as previously jump into the time machine and say that an event never happened (eg: delete a previous event). As such it is necessary to model a delete explicitly as a new transaction...(that is un-doing effects of one that needs to be removed)
Hottest 'event-sourcing' Answers - Stack Overflow
CQRS Info Command Query Responsibility Segregation
CQRS Info Command Query Responsibility Segregation
Subscribe to:
Posts (Atom)