Go to benji.io for fresh bits!

When I ran Ember, Chrome, and VSCode together, horrible things happened. My CPU spiked and my computer crawled. From experience with Sublime and WebStorm, I suspected it was watching too many files. I found a setting that should have helped, but didn't help enough, and then _another setting that fixed the problem entirely_! 

The new special setting is `files.watcherExclude`. Apparently just `files.exclude` isn't a strong enough signal that VSCode should _really, truly_ ignore those files. 

I'm taking a face-to-face class at the Japan Society of California, but that's mostly just to get some experience with actual conversation with a native speaker. I'm actually mostly crafting my education myself. So, without further ado, here are some of my favorite resources:

• Start with learning hiragana. The Tofugu Guide to Learning Hiragana is the best out there. 
• RealKana is a good app and website for drilling hiragana and katakana. Unlike many other tools, it shows the characters in multiple fonts, and lets you choose which characters to drill. 
• I use the Genki textbook as my main text. The class I'm taking uses Japanese for Busy People; I like its focus on business people rather than college students, but the explanations are better in Genki. 
• WaniKani is a fantastic spaced-repetiton system for learning kanji and some vocabulary. It has a whole coherent system of mnemonics that are hilarious and fun. 
• Fluent Forever is a book with a general approach to learning languages. The author suggests that I will get much more out of a deck that I build; so far I have found that to be true.  
• Anki! Anki is a general spaced-repetition system -- aka flashcards, but better. There are many, many decks to download, but the act of making my own cards seems to help with retention. 
• Pimsleur Japanese.  These audio lessons focus on conversation and seem to be obsessed with drinking alcohol. "Now ask the woman if she'd like to have a drink with you. Suggest that you meet at the hotel, or at Miss Suzuki's place." The rest of my materials don't ever prompt me to produce speech, and in the end I want to be able to talk to people, so this is a great resource. 
• JapanesePod101.com. This is fun supplement to everything else, good for conversation and culture, but not enough to actually learn Japanese. The dialog is almost all with native speakers, and it features an american guy who lives in Japan and talks about his experiences there. 

And then, I've tried out a few resources and decided they're not for me:

• Rosetta Stone. I get access to this for free because I'm a Brown University alum -- nice perk. The problem is that Rosetta Stone is so focused on audio and way too devoted to their own method. It doesn't mix well with other resources. Once I'm in a lesson, it's very hard to skip forward. I'm usually frustrated with the pace when I'm in Rosetta Stone. 
• Rocket Japanese. My main problem with this is that half of the dialog is by the founder, who is a non-native speaker. Bah, I don't want to spend my time listening to an Englishman speak japanese.

More to come as I discover more great stuff. What do you like? What have I missed? 

$ ember serve
Could not find watchman, falling back to NodeWatcher for file system events.
Visit http://www.ember-cli.com/user-guide/#watchman for more info.

This was frustrating because I knew I had watchman installed just fine!

$ which watchman
/usr/local/bin/watchman

This issue on the watchman repo was helpful in figuring this out. Running watchman watch . gave a much more interesting error message:

$ watchman watch .
/Users/benji/Library/LaunchAgents/com.github.facebook.watchman.plist: Operation already in progress ^C ```

The solution for me was to tell launchtl to forget about watchman:

$ launchctl unload ~/Library/LaunchAgents/com.github.facebook.watchman.plist 

After that, ember-cli ran watchman just fine.

There's an issue for this; I'm going to post a fix to clarify the language of the error.

Most PRs for a front-end web application should include all of these:

• Purpose: what is this change trying to accomplish? Linking to specifications or tickets is fine, but you must include a one-sentence explanation in the PR description itself.
• Approach: how does this change accomplish its goal? Explain your approach's architecture at a high level.
• Worries: Is there anything weird here? Do you have any areas you want help?
• Before & after screenshots, if the change is visual
• How to use the feature or exercise the change. Just linking to a ticket with a bug description is not enough; tell the reviewer how they can verify for themselves that the feature is working as planned.

Larger PRs should also include:

• Did you consider alternative approaches? Why did you go with the approach you chose?
• How does this relate to other work? Link to other PRs or describe future plans.

I'm using the jQuery Color plugin to convert RGB to HSV. Tinycolor will work too, but I went with jQuery Color because it allows CSS transitions with $.anmiate.

Here's the code:

var HueService = {
  colorToHueHsv: function (color) {
    var jqc = $.Color(color);
     return {
       "hue" : Math.floor(65535 * jqc.hue() / 360),
       "sat": Math.floor(jqc.saturation() * 255),
       "bri": Math.floor(jqc.lightness() * 255)
     }
  }
}

The input to the function can be anything that jQuery Color can interpret as a color. For instance, there's a lilac color I like, #676de8.

So I can do HueService.colorToHueHsv('#676de8') and get back {hue: 43143, sat: 187, bri: 167}.

I then turn on one of my lights to that color with a PUT to http://10.0.1.3/api/myusername/lights/3/state with form data {"on":true,"hue":43143,"sat":187,"bri":167}

Assuming I've authenticated to the Hue bridge, the light turns on with pretty much that color. I don't think I have the brightness and saturation mapped quite correctly; it's tricky because the Hue 0-1 space for brightness has 0 at "the lowest brightness possible with the bulb still on". I'll keep tuning this -- check the source for updates.

I'm using this code in my Sunrise Hues project, which lets me build custom sunrises as a gentle alarm clock.

Michael Pollan criticized a caricature of the paleo diet, not the diet as it's recommended by clinicians for healing sick people. Healing sick people is what's really interesting to me about the paleo diet. 

1. Lots of meat every day is not a requirement for paleo. Most authors who talk about proportions say more like 10-30% of calories from protein, which ends up being 3-4 x 3-6 ounces of protein per meal. Giant hunks of meat are a stereotype from recreational bloggers, not clinician who are trying to fix sick people. Quality of meat is a HUGE deal in paleo; I eat pastured meat almost exclusively. If I could afford to eat wild meat more often, I would; I only eat wild fish. 
2. Fine, humans can live on bread alone, but are they *healthiest* living on bread alone? Certainly not. Getting nutrients from bread is fine if you don't have better options.  
3. Paleo strongly encourages fermented foods like kimchee, sauerkraut, and pickles -- just the fermented foods that don't rely on grains as the substrate. 
4. Paleo doesn't suggest that you eat all or even most of your food raw; the paleo authors I respect strongly endorse cooking vegetables as a way to make them easier to digest and easier to absorb the nutrients, for exactly the reasons in that article. 
5. Cook more? Paleo is all about cooking, because food like this simply can't be gotten at restaurants.  

But mostly, I'm not saying paleo is right for everyone and everyone should eat it all the time. I'm saying that paleo cures or dramatically improves some autoimmune conditions, and thus it's worth a real trial for people who are sick.

These ideas are mostly drawn from the writings of Chris Kresser and Robb Wolf. I highly recommend Chris Kresser's book, Your Personal Paleo Code, which has a procedure for figuring out what version of paleo is right for you

• It will cost more than you want to pay. Get used to it. For me, the value proposition wasn't there, so I started looking in the east bay, and fell in love with a property that was literally 4x the size of what I could get in SF. 
• Quit smoking.
• Figure out what you want, then figure out whether that sort of thing is available where you want to live, for the price you want to pay. If it's not, don't waste time looking for it; change the nature of your search. 
• If you don't know the area, talk to your friends and colleagues. Bay Area neighborhoods change block-by-block. I printed out a map of Berkeley and Oakland and had friends mark it up with different-colored markers. Then go look around at neighborhoods, before you even bother looking at craigslist postings. 
• Check your credit report as soon as you know you will move, and fix it.
• Prepare a rental resume: present and former apartments, and the one before that. Landlords, with phone numbers. Reason for leaving, dates you lived there. Personal references with phone numbers. (Lots of people will want you to fill out their unique application, but having all this info will make that easier.)
• Go to open houses early in your search. They will help you get a sense of prices in the area you're looking, so go even before you are really ready to rent. They are also much less hassle to schedule than 1:1 viewings. Just search for "open house" on craigslist.
• Apartments in this market appear on craigslist and are rented within days. Use livelovely.com or padmapper.com to set up alerts for exactly what you want, and contact the lister immediately. (If your filters aren't specific enough, you will be deluged with too many alerts.)
• Corrolary: confirm that the listing is still available before going to an open house. 

• Get a written letter that verifies your length of employment and salary, with the phone number and email of a HR department that can verify it. 
• Print out several copies of your credit report and bring it with you to open houses and viewings. Some landlords want you to provide it and others want to run their own credit report. 
• At open houses, dress like a responsible and boring person. 
• Arrive early for open houses and meetings with realtors. I mean EARLY. 15 minutes minimum. Why: 1) it looks good. 2) you can spend some time in the area. 3) You're probably going to get lost / the buses are going to be late / the traffic is going to be bad. 
• If you find something you love, try to view it before the open house. Everything nice is going to get tons of applicants. Being there first matters. 
• Have a non-trivial conversation with property owners and leasing managers. Thank them for their time. Ask them about themselves, their business, what they think about the bay area. This isn't just Dale Carnegie bullshit -- this is auditioning them for the long-term relationship you will have if you rent from them. 
• Read reviews on yelp before even going to see developments. I wouldn't have bothered driving to Park Merced if I had read reviews like this before I went. Most of the developments have extensive shitty reviews, in fact. 
• You can walk in to buildings and developments and get a tour during the week, but you'd need an appointment on the weekend. I suggest not making appointments; take a day off during the week and go see a bunch of developments. 
• If you can break free of public transit, you have a ton more options. Consider buying a little motorcycle or bicycle. I pay < $250/month for my motorcycle and insurance, and that enables me to look much farther away from bus routes than I could otherwise -- but I can park easily park it on the street, and my heart wouldn't be broken if it was stolen. 

The first cool thing that happened was that I spotted Bob Harper, said hello, then tweeted a picture of him. 

More hanging around, until the head judge realized at the last minute that he didn't have enough people. He asked for volunteers, so I walked up. My job was simple:  

• Watch each team member row 1000 meters.
• Make sure they held on to the handle for the entire 1000m.
• Hit the reset button between athletes.

So I stood around and hit one button over and over. It turned out that the team I was judging set a worldwide competition record for that event, and a picture of them ended up on the crossfit.com main site... with me standing behind the rower, ready to press buttons. 

The head judge asked for volunteers again the next day, and this time someone handed me a JUDGE t-shirt as I was running onto the field for the final team competition. I pulled it on, but then the head judge realized he had enough people after all. I got to keep the shirt, but didn't have to judge; best of both worlds, because judging the final team event looked complicated and stressful, not to mention sunburny.

I noticed that the athlete's warm-up area was a total mess: water bottles and tape everywhere, dumbbells and plates scattered, not enough equipment... so I decided to tidy it up and keep it stocked. I set up the 345-pound barbell that all the individual men used to warm up for their final event, and all the athletes chalked up in the chalk buckets that I kept full. Each athlete selected the height they wanted for the rings, and at least one of them left some blood behind. I saw all the athletes up close; the men are really big and ripped, and most of the women are pretty small and ripped, except for their thighs, which are tremendous. This also put me in position to observe the athletes as they came off the field after each event, usually covered with sweat and dust.

I didn't know what volunteering would be like; the only part of my prediction that was spot-on is that my neck got sunburnt. 

To get involved in an event, volunteer. If you're not given specific tasks, you can still contribute, with this passive/active couplet: 

a) Cultivate passive availability: stand around where things are happening and be available.

b) Cultivate active service: look for ways to contribute, then jump in.

Also, 

c) A sunburn is a reasonable price to pay to be this close to champions.

I work at Twitter. It's the best job I've ever had. I love working with all of these incredibly smart and whimsical people. I love contributing to a site with millions of visitors. I'm working with all of the technologies I want to work with, and my co-workers created some of those technologies. The perks are delicious and the commute is just long enough to stretch my legs. I'm not interested in pursuing other opportunities. Thank you for your interest. 

-ben