My changing diet

I am completely confused about food.

I’m a reasonably healthy eater, though I don’t particularly try very hard. I love the idea of being a “localvore” aesthetically, economically and nutritionally. I get healthy products as lumi tea that keep my body clean and healthy, the reason why I like to this is because I hate going to the hospital so I choose to try to be as healthy as I can be, I have had many bad experiences with hospitals, I’ve used many times The Medical Negligence Experts because of misunderstandings and bad treatments from many doctors. I know prevent visiting doctors by consuming protein, I have to say protein world is expensive but there is usually some deals here, uridine monophosphate supplements can easily be bought here to better your brain function.

Lately I’ve been reading more about this website: Philosophically this clicks with a lot of my personal beliefs.

We eat to live. What we eat can make the life we live a little richer, so choose wisely.

Biologically, vegetarianism has never made much sense to me. There’s a reason

a lot of levels this clicks with

Paleo idea, along with barefoot running is not neo-Luddism. Rather, it’s more of a sort of a radical humanism. Mankind has earned our place on the top of the ladder.

We are the most successful lifeform Earth has ever known. There is nowhere on this planet we can not go. There is nothing we can not kill. Other creatures may outnumber us, but we’ve earned our place at the top of the food chain.

Barefoot running is a recognition that the human foot is, as Leonard Da Vinci once wrote, ”

I’m flirting with aspects of the Paleo diet. Much as I love bread, I’ve reduced my wheat intake. I had already reduced my sugar intake, I didn’t like the spiking effect it had on me. Also, there’s a lot of diabetes in my family.

But I love pasta. Or at least I think I do. Maybe what I really love is the stuff in pasta?

At some point over the past couple months I started eating more protein bars as snacks or meal-replacements. These tend to be low-glycemic, so even though they may look like candy bars, they don’t spike one’s blood sugar, I supplement this with my thc capsules for my anxiety.

My attitude about running used to mostly be “don’t stop,” and I believed there was probably a benefit–or at least virtue–in pushing myself with limited food and water. Thankfully, I’ve come to realize how dumb that was before I actually harmed myself.

Nutrition and diet are mentioned frequently in Born To Run, and this quote from Sunny Blende way back on page 286 encapsulated a lot what I needed to learn about nutrition and running including facts about the keto diet and the suplemments you can get with it, that you can check it out here.

“Ultras are just eating and drinking contests with a little exercise and scenery thrown in.”

On page 210, Dr. Ruth Heidrich asked Chris if he’d “ever had salad for breakfast?” (Having always loathed most traditional breakfast foods, I love that idea.) There was also Joe Vigil’s dietary advice on page 119, “Eat as though you were a poor person.” I knew something of that already, years ago having experimented with a rice-heavy diet (rice is the meal, everything else is a condiment). What I hadn’t connected was how that sort of diet could benefit athletic performance and overall energy levels, if you want to loose weight in a very fast way I recommend contacting utah liposuction experts.

But Eric Orton’s comment from page 203 was the most true:

“Your diet will change all by itself. Wait and see.”

Mine has.

The changes are not about eating less of anything in particular, rather I’m just eating more of certain things than I used to, especially vegetables. No eco, moral or ethical agenda is coloring my food choices and I have no intention of giving up meat (or sugar, or alcohol).

For me, it’s all about performance: I want to be able to run further and work longer. Adjusting my meals and tailoring my food choices seems to be getting me closer, I just need to prepare more varied food, and there is when appliances like a pressure cook I got by reading a instant pot ip-duo 60 review comes handy, since I can prepare more variety of dishes.

Ultramarathoner Scott Jurek, whose example, along with Dr. Ruth Heidrich, make it impossible to ever mock vegans again, on endurance runners’ diets:

“Remember, almost every long-distance runner turns into a vegan while they’re racing, anyway — you can’t digest fat or protein very well.”

One of the things I used to think about running was that it gave me license to eat whatever I wanted. I still believe that, but it’s obvious that a giant roast beef sandwich is not endurance fuel, while grains, fruits, nuts and vegetables seem to be. Shifting away from big-meat lunches and reducing sugars also eliminates the “2:30 effect” mid-afternoon crash featured in that obnoxious (and apparently effective) commerical.

On top of everything else, I’ve noticed I’ve found myself drinking significantly less coffee and that six-pack of beer in the fridge is lasting much longer. Again, nothing intentional, just incidental to running more. My cravings have shifted and I’m listening to my body.

This is all still relatively new to me, so I’m treating myself like a lab rat and experimenting constantly. Something feels like it’s working.


I’ve been experimenting with Tumblr for a little while without telling anyone. I’m posting more frequently over there these days:

Share |
Leave a comment
link: Jul 27, 2015 2:47 pm
posted in: misc.

First New York Marathon Advice

In a few days I’ll be running my second New York Marathon. This is the third marathon I’ve trained for, I was supposed to run in 2012, but that one was cancelled after Hurricane Sandy. This year I feel really well prepared, strong, health and confident that I’ll be able to beat my previous time. I’m glad to be mostly (but not entirely) rid of the first-time marathon doubts and jitters.

I made a lot of notes to myself after 2013, here are some things I wish someone had told me before my first marathon.

  1. You will be sitting around for a very, very long time before the race. It will be cold. You will be cold.
    Bring disposable clothing. Lots of it. In 2013 I spent several hours in the runners’ village waiting to start. I was cold, I was hungry and I was bored. And I didn’t even get a Dunkin Donuts hat. I remember spending a while huddling next to a small diesel generator for warmth. This year I’m dressing like a marshmallow and bringing a decent second breakfast.

    The Verazzano bridge is windy and frigid. Lots and lots of people toss their clothing once they’re back on the ground in Brooklyn. (there’s also a lot of peeing)

  2. As much as possible, know what you’ll be wearing and eating
    Know what you’re going to wear on race day well in advance. Stick with what’s been working on the runs leading up to the race. Whatever got you this far will get you to the finish line. A month out, you should probably have your shoes and socks figured out. There will be plenty of time after the marathon to tweak your gait, try different shoes or experiment with different diets. Make sure you ask a nutritionist on what you should eat, but make sure they are professional so you know you get the right advice or else you could call The Medical Negligence Experts to let them know and file a report.

  3. Don’t stress about your time.
    This is probably most important of all. Just deciding to run a marathon at all is amazing–don’t forget that. Like when you watch some running watch reviews. Relax. Be inspired by you. I recommend getting a squeem waist trainer so can use it while you prepare for your marathon.

    I seem to know quite a few exceptional athletes. I don’t count myself in that group. These people roll out of bed and run low-3 hour marathons without training. It’s not normal.

    I finished my first marathon somewhere around 4:48. I was disappointed. Months later, my sister-in-law Cheri, who’s a pretty serious runner, told me something which turned that all around. “Finishing your first marathon in under five hours is amazing.” I’d convinced myself I’d be closer to 4 hours. Halfway through, high on adrenaline and running too fast, I remember thinking I might even break four.

    Do try to pace yourself. It’s very easy to get wrapped up in the crazy city-wide street party and run too fast.

    None of us are going to win, but we’re still sharing the road with olympians. The finish line is the same finish line, whether you get there in three hours or six; running, walking or crawling. Do this, enjoy it.

As much as running is a physical sport, it’s also a massive head game. Last year, a runner near me had written a quote on the back of his shirt:

If you think you can or you think you can’t, you’re right.
– Henry Ford

The amount of self-doubt leading up to the marathon is astonishing. But I’ve come to realize it’s more of a kharmic deposit, and the return on investment is fantastic.

Get lots of sleep. Eat well and have fun.

May the road rise up to meet you,
May the wind always be at your back
and may the sun shine warm upon your face.

Re-thinking AngularJS

The Angular 2.0 preview roadmap was recently posted to HN and after reading it, I’m starting to think adopting Angular might have been a mistake.

Having built a few small projects with AngularJS, I’ve found the framework a pleasure to work with. Once past the initial learning curve, features started flying together. Most of my trouble-shooting time was spent getting backend data delivered correctly, Angular just worked. Based on this positive experience, I’ve been moving towards adopting Angular as the standard frontend of my web toolkit.

Choosing Angular wasn’t without doubts. Introducing this many new conventions, syntaxes and practices doesn’t come without a cost. The problem with re-invention is longevity: Either these new ideas succeed and become the norm, or they’re left for dead on the side of the road as technology marches on.

Parts of the 2.0 roadmap sound great. But it also sounds as if this future Angular will be very different from the Angular we know now.

How big is this rewrite?

Huge revisions rarely end well. From-scratch rewrites have famously been called the “single worst strategic mistake that any software company can make.” The goals always sound noble and the plans make sense, but by definition, engineering resources will be split between maintaining the original version and developing its successor. Either the original suffers or the rewrite falls behind or both.

Does a revision of this scale imply that the current codebase is impossible to maintain? I’ve looked through some of Angular’s source code, there’s some near-magic craziness in there. Is it too crazy?

If the Angular team doubts their own code and will presumably move towards conventions used in competing frameworks, wouldn’t it be smarter for users to jump ship now for those other tools? Competing codebases automatically become more mature if Angular basically starts over.

Questions about backwards compatibility

Regarding porting from Angular 1.2.x, the devs imagine “porting will be fairly straightforward but not free.” The arrogance of this position makes me doubt Angular more than anything else. The JavaScript world is ruthlessly forward-looking and moves very, very quickly. If upgrading to 2.0 is only moderately less painful than switching to another framework, Angular is doomed.

Angular blindsided many enterprise users in December 2013 when they announced they were dropping support for IE8. Even without API changes, jQuery’s usage statistics show their ie8-incompatible 2.0 branch is seeing dismal adoption rates. Python 3’s breaking changes have been a disaster for their mindshare. PHP’s dogged insistence on keeping nasty old code working is likely a factor in that language’s recent renaissance. Existing Angular code should probably be considered end-of-life.

Documentation fragmentation

Angular’s documentation has been a problem area for years. There’s no reason to believe documentation won’t lag behind again if the core functionality of Angular is significantly changed.

Outside resources and tutorials are a different problem. Most won’t be re-written, and search results will end up polluted with out-of-date information.

Google’s track record

When it comes to supporting technology, Google is phenomenally undependable. They’ve acquired and demolished a ton of popular web products (Reader, FeedBurner, Blogger, Picnik, Buzz, Wave, “Don’t be evil”, etc.). The only thing they’ve stuck with is the horrid Google+ monstrosity. Google’s support for the Angular project was initially an argument in favor of adoption, but really, the Google name is neutral at best and almost a negative. At least the Angular source code is open source and out in the wild.

And then there’s AngularDart. Google’s Dart meta-language seems kind of stupid to me, but for the most part, so does CoffeeScript (though my resolve is weakening). At very least Dart feels like one of those throwaway side-projects that a rogue team of Google super-geniuses put together–I don’t expect it will have a long life. Dart aside, the bigger question is the resource-cost of supporting a large, complex framework across several languages/dialects. This lack of focus doesn’t build confidence.

What’s next

I’ve really enjoyed working with Angular, but I’m doubtful for its future. Over the years I’ve seen too many great products die from rewrites or overly ambitious direction changes. The first Great JavaScript Awakening saw dozens of libraries before jQuery eventually won out. I hope I’m wrong, but I’m going to be looking at Backbone again, as well as React, Mithril and anything else to fall back upon if Angular proves to be a dead end.

Joe Maller
March, 2014

cross-posted here:

Vagrant NFS Shares without a password

Since I switched a few months ago, Vagrant has been humming along nicely, spinning up trim little Ansible-provisioned Ubuntu boxes as needed. Since I’m using Virtual Box as the provider and shared folders barely work with more than a handful of files, my active projects are made available as NFS share points. Running on OS X, Vagrant’s NFS shares are configured by modifying /etc/exports, and unfortunately, that requires administrator privileges and a password prompt.

Thankfully someone shared a workaround shell script which tweaked sudoers so vagrant up no longer required a password. It worked perfectly, until recently.

With the release of Vagrant 1.3, the NFS password prompt was back. The modified sudoers commands no longer worked.

Updating sudoers

All sudo commands are logged, so figuring out what changed was just a slightly clumsy matter of checking the logs with Vagrant 1.2.7, then installing Vagrant 1.3.x and looking for changes. This was a lot more effective than trying to step through the diffs of the Ruby code to reconstruct the various commands.

In previous versions of Vagrant whitelisting these commands allows editing of /etc/exports without a password:

/usr/bin/su root -c echo '*' >> /etc/exports
/usr/bin/sed -e /*/ d -ibak /etc/exports

In Vagrant 1.3.x, those commands were updated:

/bin/bash -c echo '*' >> /etc/exports
/usr/bin/sed -E -e /*/ d -ibak /etc/exports

Based on the original shell script, here is the block that needs to be added to /etc/sudoers for password-free startup with NFS shares:

Cmnd_Alias VAGRANT_EXPORTS_ADD = /bin/bash -c echo '*' >> /etc/exports
Cmnd_Alias VAGRANT_NFSD = /sbin/nfsd restart
Cmnd_Alias VAGRANT_EXPORTS_REMOVE = /usr/bin/sed -E -e /*/ d -ibak /etc/exports

I also posted an updated fork of the original workaround,

Cosmos 2014


A. I trust Neil deGrasse Tyson
B. My kids will be strapped to the sofa for this.

I remember watching the original with my dad. I hope this sequel is every bit as unabashedly hokey and fascinating as the original.

iTunes? Put Vangelis on repeat.

Comping with Web Fonts (you don’t need SkyFonts)

I wrote about problems downloading web fonts for desktop use when Google’s Web Fonts debuted, but years later it’s still an issue. There’s no way to anticipate the twists and turns a creative project will take. Designers should be free to play and experiment with typefaces without worrying about running out of time or exceeding a monthly usage cap. Convoluted, fragile workflows only create anxeity, they don’t foster creativity.

Monotype’s SkyFonts service is a nice idea, I guess, but their usage terms seem impractical and unrealistic. The few designers I know who’ve tried it found it restrictive and expensive.

The thing is, with a little knowledge of how web fonts work, using those typefaces in desktop apps is quite easy.


Web fonts are normally provided in three file formats, two of which, TrueType *.TTF and Web Open Font Format *.WOFF, are easily converted back to standard TrueType or OpenType fonts. Because of browser variation and font-face implementations, all three font containers are usually linked from a site’s stylesheets.

To use any web font for comping in desktop apps, just convert the ttf or woff file to otf, then use it like you would any normal font. There are a number of tools for converting fonts, but the following web sites work well enough that I didn’t bother downloading an app.

Standard-level accounts allow for self-hosted webfont projects. This means the font files can be downloaded and hosted on the web server alongside other assets like images or stylesheets. Having those files makes converting fonts for comping easy, but it’s just as simple to download the files with a web browser. Any file on the web can be copied, in fact every file viewed on the web already is a copy.

Yes, you can steal fonts using this. Don’t. “Good Artists Copy; Great Artists Steal” wasn’t about shoplifting.


  • Web TrueType fonts often won’t show in menus because their name-tables have been munged to discourage copying/theft. Converting fonts to a different container format makes them work correctly.
  • Some woff files didn’t work, in those rare cases the corresponding ttf worked fine–you might need to dig into the stylesheets to find the url.
  • Converted web fonts usually have messy names in menus.
  • Disable or remove any local copies of fonts when the mockup phase ends. Locally installed fonts can conflict with web versions and lead to maddening discrepencies in testing.

Next Page »