mga226

I didn't realize the comment I was responding to was from the OP. I really am sorry if I came off as harsh, but I stand by my comment.

I hope you're trolling.

If not: I think you'll find find the HN community doesn't react well to either stealing content or complaining about the (quite reasonable, in this case) cost of people's products.

Anyone else just skim the title and then get disappointed when it didn't actually relate to homemade booze?

> More proof all religions are crap.

I don't see how that follows.

- An atheist.

Genuinely interested in people's opinions:

1. Is this (a) an ad hominem attack on paleo's scientific legitimacy, or (b) an attempt to save the paleo community from the damaging effects of association with misogyny and racism?

2. Is the author claiming that a paleo lifestyle is intrinsically bigoted, or that some paleos are bigots?

Separately, I'm not sure I understand the "cultural appropriation" aspect that constitutes the entirety of the racism charge, can anyone clarify this for me?

Tiny note, I see a typo: 'dasboard' !== 'dashboard'

Fair point, but I'll just point out that sunglasses are cross-platform and work on your TV, iPhone, iPad etc in addition to your laptop.

Congratulations, by the way, on your great results!

Not to belabour the point, but I disagree. People who "have this mindset" probably appreciate this distinction better than most. It's just a domain-specific shorthand use of the word "carb."

"Carbs" in this context is referring to foods that have a high carbohydrate content, like potatoes, yams, bread, pasta, and to a lesser extent things like carrots, beets, parsnips etc. Foods to avoid if trying to keep carbohydrate intake below 20-50, as these diets typically require.

It doesn't refer to cruciferous/fibrous veggies, as well as things summer squash, even though they are almost entire carbs, because the carb content per serving in these foods is quite low - low enough that you can probably eat as much of them as you like and still be within the prescribed range.

This cuts both ways.

> Looking back, I can’t believe I jumped in knowing so little.

I also have this feeling about my first few client projects, and it was to my detriment. The fact that I was technically able to deliver something to spec convinced me that I knew what I was doing. There have been times when I've wished someone had told me back then: stop just making things, and learn how to code.

Fair enough, but I feel I should clarify my comment.

I'm suggesting that if you feel the interview process is flawed even from the company's standpoint (i.e. not screening for the appropriate skills) your best approach might be to reverse engineer the interview (i.e. get better at answering the questions, instead of actually developing the [perhaps irrelevant] skills being screened for).

The Tardos book that I think you're referring to is a $100+, 850 page CS textbook with the goal of making you an expert on algorithm design. The book I suggested costs $30 at is focused on a specific goal of getting through the interview.

I'll grant, however, that there may be better resources for this (and I'd be very curious to hear what others think those are).