159 karma · joined March 29, 2014
Can you expand on what mathematicians discovered and how it can be applied to coding? Or does it require a certain programming language? I'm looking at the Hyperfiddle website and trying to understand how these concepts are connected. Thanks!
Specifically, I've been working on a activity tracking app that can take plain text and create structured data from it. For example
> I played tennis with Kevin and won 6-2
would turn into
```
type: tennis
opponent: Kevin
my_score: 6
their_score: 2
outcome: win
```
As you can imagine, when it comes to natural language there are many variations of I won (outcome: win), he/she/they won (outcome: loss), I was beat, etc which means that my inputs are not nearly as structured as the examples used in the paper I'm reading. Given that I'm not trying to cover every use case in the English language, which I assume would require some form of NLP, but rather just a subset that a single user would input, do you think think it would be possible to solve this with PBE techniques?
> two pieces of fish, an onion, an egg, baked beans and biscuits
every single day is a contributing factor. I'm all about simplifying life, but think we should remember that eating a varied diet is fairly important to well-being.
(last solar event in small font) Sunset 19:17
(current date/time small) Mon 15 19:26
(relative time to next solar event in large) Dusk in 17
It tracks dawn, sunrise, solar noon, sunset, and dusk. It's pretty simple but has changed how I go about my day. I don't use an alarm to wake up, but I've learned that when it's 8 hours to dawn I should be getting in bed.
I grew up in Switzerland and the cost incentive to running the dishwasher and washer/dryer at night was significant. Many families changed their behavior as a result.
Definitely going to make the switch to the
> 100% renewable energy – for a 2 cent per kilowatt hour premium over current PG&E rates
This
> [i]s the first to admit that the Zero UI name isn't meant to be taken literally. "It's really meant to be a provocation," Goodman admits. "There are always going to be user interfaces in some form of another, but this is about getting away from thinking about everything in terms of screens."
The "productivity" designation is an inadequate one. There a few obvious productivity apps that translate well from processes that people are used to in the real world, like note-taking apps, that don't require much education for the user to understand. It's a notebook. Cool, got it.
Onboarding is such an important facet of this discussion, and you do mention it below:
> I'll need to spend just as much time making the interface discoverable
Unfortunately, developers do get so close to their product that they forget that users often don't know where to start, so I think that having to build an onboarding process is something to be expected. Education is the only way to make one UI for many people. I think the questions that need to be asked are: 1. How long is it going to take to make my users proficient at my app? 2. Can I make it fun for them?
I don't think the moral of the story is "Don't make productivity apps", I think it's "Don't make an app that's hard to explain to its users"
Unless they have an external pressure like: - In the case of B2B, complying to company policy (Slack) - In the case of B2C, it's social and everyone is already on it (Facebook)
Install to home screen removes the browser UI, so it won't be native, but it'll be close.
http://www.theverge.com/2015/4/20/8454613/push-notifications...
Hopefully iOS will support service workers in the future.
That episode mentions Gary Wolf's 2008 Wired article [Want to Remember Everything You’ll Ever Learn? Surrender to This Algorithm](http://www.wired.com/2008/04/ff-wozniak/), which I think is what inspired me to create Hibou.