And yet many blog dbs fall over under what is ostensibly read-only loads. It could be inefficient connection reuse, shitty disks or it could be something as stupid as writing visitor data on each visit. But it's irrelevant to the main point which is that it's a blog.
This comes up every time a blog falls over that discusses or criticizes a database on HN and it's just as shallow as it ever was. Do we really expect anyone to spend significant time optimizing their blogs for load that may not ever come? We talk about "pre-optimization" and "core competency" routinely on here and then shoot the messenger when a wordpress blog using MySQL falls over that's criticizing something like MongoDB. It's irrelevant to the point of silliness.
A word of advice to those attempting a Ketogenic diet: get your blood work done on a regular basis.
If possible, get heart scans done once a year.
It's easy to slip into a sloppy version of the Ketogenic diet, at which point you're consuming lots of unhealthy fats and carbs, you triglycerides and cholesterol could shoot up and put you in shit street.
What is an unhealthy fat? Also, by definition, if you are eating more than very minimal carbs, you aren't on a ketogenic diet.
Honestly, and with no sarcasm intended, I think your advice would be similarly correct for anyone considering eating bread, or white noodles/rice - get your blood work done on a regular basis, and heart scans done once a year, your triglycerides and cholesterol could shoot up and put you in shit street.
I'm willing to wager that significantly more people have cholesterol problems with rice/bread, than they do with eating meat and fat.
Not everyone has the capacity to be strict with their diet, habits, or health in general. These people might still attempt the Keto diet.
The Ketogenic diet gets approached by lots of people with mental health issues (bipolar for one), and people who have issues being strict with their diet.
Advising them to get their blood work done, and heart checked is normal, and sensible. Getting your blood and heart checked regularly is a healthy habit, and provides vital feedback to understand exactly how your diet is impacting your health.
I like the premise of the article. This is now a black & white issue; it's not about how the onus is entirely on the user, or entirely on the machine. Instead it's about both assisting each other, but humans ultimately remaining at the wheel.
Please help me understand why DuckDuckGo decided for the query to go in the URL, as opposed to being encrypted on the client before being sent to the server as a get or a post.
Most users probably have their browsing history switched on, and synced with their friendly browsing software provider anyway, totally reversing any privacy advantage a user might potentialy gain by using DuckDuckGo.
> Another way to prevent search leakage is by using something called a POST request, which has the effect of not showing your search in your browser, and, as a consequence, does not send it to other sites. You can turn on POST requests on our settings page, but it has its own issues. POST requests usually break browser back buttons, and they make it impossible for you to easily share your search by copying and pasting it out of your Web browser's address bar.
I've saved up a long list of them into a big project that I will definitely tackle one day. Definitely.
I just need to sort out the definitions and overlapping boundaries with habits, tasks and projects and what I should be documenting and not documenting, and how I should keep a record in terms of time-stamps and how to structure my information.
Why on earth haven't I come across this information before? I spent a crazy amount of time researching frameworks before settling for Meteor, and never came across this.
> my understanding was that ultimately whatever macromolecules you are consuming, lipids, proteins, or carbohydrates all only get absorbed into the blood stream as glucose
Amino acids, glucose and fatty acids are all ancient molecular structures known to all cellular life and thus can and do circulate in our blood at all times. If everything got converted into glucose during digestion, that would mean we could live entirely off candy fortified with vitamins and minerals, and produce all essential fatty acids and all essential amino acids from the glucose. Not so.
PROTEINS provide amino acids, basic building blocks for near everything organic about our body (or all cellular life-forms really), not just muscles but hormones neurons etc etc. The body may convert protein into glucose but this laborious process occurs to any significant degree mostly under a prolonged lo-fat-lo-carb-hi-protein regimen or plain starvation conditions (ie post-fasting, not just normal fasting with plenty of fat reserves left, which is simply ketosis, hence protein-sparing and fat+ketone-burning). If so, this doesn't occur in the digestive tract, since glucose production (or provision from glycogen) is the job of the liver.
LIPIDS aren't and cannot be converted to glucose in the digestive tract, or we wouldn't store body fat to begin with and also have essential fatty acids circulating at all times now, would we? BUT 2 triglycerides CAN donate their glycerol backbones for the production of 1 glucose molecule, and I believe this is constantly happening in ketosis when glycogen is depleted. Again, glucose production/provisioning is a liver job, not a digestive tract job.
CARBohydrates of most any kind ARE converted to glucose in the digestive tract. Exceptions: fiber travels on to the colon for excretion or to be fermented by bacterial action (into I believe short-chain fatty acids and B/K vitamins) and fructose is "metabolized" into triglycerides by the liver. Since the blood needs a certain glucose level at all times (around 5g-ish), circulating glucose in excess is immediately shuttled into first: any cells that are receptive to the concurrent insulin signaling, second: glycogen storage (liver and muscles), third as a last resort converted into body fat.
When I had to learn Python to do my job, I read a few pages on python.org, and one of the things it mentioned was that 'a python developer can do in a month what a C++ developer can do in a year".
Expressive, concise code is always a good thing.
Meteor is excellent for MVPs and POCs; there are a lot of people out there with big ideas, but limited budgets to test out those ideas.
In Meteor, you can access your collections from the client and the server; and the vast number of packages on atmosphere makes writing a webapp in Meteor feel more like assembling lego than anything.
The speed at which we can write software is tightly correlated with our ability to innovate quickly; test things out, keep what works and throw away what doesn't.
I've developed things for clients in Meteor, in a matter of weeks what others have failed to deliver in year
90% or so startups fail, not because your front and backend were too tightly coupled, but because of a whole variety of other reasons. Given that most of that code will end up in the bin anyway, might as well focus on quantity, and switch to something more robust when need be.
Seems like a high price to pay.