More on this book
Community
Kindle Notes & Highlights
by
Ken Kocienda
Read between
September 15 - October 4, 2018
he closed the loop on my demo.
When software behavior is mysterious, get more organized.
psychological hurdle
on the Purple project. We rarely had brainstorming sessions.
If brainstorms run longer than an hour or so, or if there are more than a handful of people in attendance, or if they’re a common occurrence, they can devolve into a form of sneaky procrastination.
when it comes to making products, philosophical discourse is the wrong tool for the job when practical decisions are needed.
finding the self-confidence to form opinions with your gut you can also justify with your head.
until
His deft touch always made everything better.
switching your typing to the word that seemed most likely given your taps—what you might have meant—or keeping the exact succession of letters you tapped and saw pop up in the user interface—what you actually did.
it didn’t take too long to see that letter-by-letter grading didn’t produce better results than just looking at the usage frequency values.
autocorrection became a process of building a pattern from the user’s taps and searching the dictionary for the closest-matching pattern from the ideal set.
I handled it by keeping reasonable and regular work hours.
when I walked into the Moscone Center on keynote day, I still didn’t know what Purple would be called.
a company eventually runs out of reasons for design decisions
Remove all subjectivity and just look at the data.

