- Scientific method of analysis - ideally, unbiased (but in practice this is impossible). Basic steps:
- Observe relative to the question or problem
- Hypothesize based on observations
- Test hypothesis
[ | |
{ | |
"name": "Issues by product", | |
"key_col": "Product", | |
"val_col": "Issue" | |
}, | |
{ | |
"name": "Products by issue", | |
"key_col": "Issue", | |
"val_col": "Product" |
#!/usr/bin/env python | |
# Copyright (C) 2006 by Johannes Zellner, <[email protected]> | |
# modified by [email protected] to fit my output needs | |
# modified by [email protected] to fit my output needs | |
# modified by [email protected] (2014) | |
# - use if __name__ == "__main__" to run script stand-alone | |
# - organize and define more reusable functions (could be more idiomatic) | |
import sys |
--[[ | |
Add a table like this to the script, near the beginning of the file. | |
The numbers on the left are the max temps for the strings on the right; | |
i.e. if the temperature is between 0 and 20 degrees then the phrase is | |
"You need a big coat". These numbers are just examples and are for | |
Fahrenheit temperatures; they should be changed for your preferences and | |
to reasonable Celsius values if you use Celsius temps | |
]] | |
local Main_String_Options = { | |
100 = "You need a bathing suit", |
Little things that bother me when using OS X
Don't get me wrong, there are a lot of things to like about OS X (there's a section with just a few of my favorite things at the bottom), but I've become acutely disillusioned with OS X's veneer of perfection. It seems to me that one of the main things that Apple accomplished with OS X was to create and maintain a thriving ecosystem of third-party applications specifically designed to fix the shortcomings of the operating system.
Mind, I'm also an OS X newbie. I'm sure that there are apps or console commands or buried settings that fix a lot of these gripes. But that also sort of proves my point - because many of these are things that ought to be incredibly simple, or easy to tweak, or have a better default; but they aren't, or don't. These have been the pain points for me as a relatively experienced Windows and Linux desktop user trying to get used to OS X.
/* | |
It won't work, b/c doing the JSON parsing will be a unbelievable pain! | |
The "snazziness" of this solution isn't worth that pain and the time it takes to implement, | |
considering how much we would use it. | |
*/ | |
// MARK: Session type protocols | |
protocol Session { | |
// session id, unique to the user |
import Foundation | |
// helper protocols for adding things to the index | |
protocol Identifiable { | |
var id: Int { get } | |
} | |
protocol Tagged { | |
var tags: Set<Tag> { get } |
import Foundation | |
/* | |
Demonstrates creating and avoiding retention cycles in callbacks | |
*/ | |
/* UTILITIES */ | |
/// Wraps a something in a class | |
class Box<T> { |
: Connected!!! | |
: Found 31 buckets | |
: Bucket: 2015-10-13 00:00 - 2015-10-14 00:00 | |
: Data Sets: | |
: Data returned for Data type: com.google.step_count.delta | |
: Bucket: 2015-10-14 00:00 - 2015-10-15 00:00 | |
: Data Sets: | |
: Data returned for Data type: com.google.step_count.delta | |
: Bucket: 2015-10-15 00:00 - 2015-10-16 00:00 | |
: Data Sets: |
module Spiral where | |
import System.Environment | |
import qualified Data.List as List | |
import qualified Data.Set as Set | |
{- Process outline: | |
- 1. Create infinite sequence of points on the spiral | |
- 2. Take a finite subsequence | |
- 3. Shift all the points so the origin is in the top left |