A quick google shows 'blackmail' definition can either be restrictive to secrets as you say or can encompass 'extortion' depending on the definition you use.
1,044 karma · joined February 24, 2013
First ten minutes experience: I've got a little weirdness with the differences in generated code from x-code vs new designer (an outlet name went from upper case to lower for instance).
iOS designer is giving prominent error "Custom components are not being rendered because problems were detected".. Though everything seems fine and log doesn't particularly help.
But it still feels like this is wrong even though we know the above. The reason it feels wrong comes back, as it always does, to Apple's walled garden. If we could 'use it at our own risk' as we might with an unpublished Android API or an unpublished Windows API, everyone would be fine with it.
But when 'unpublished API' means 'if you go near it your app is dead' that is a much less reasonable thing.
So the psychological programming is getting used to not expecting that spike (and possibly that 'full' feeling), and still feeling you sated your self.
Pyramid set a bench press to your 3 or 4 rep max, or widowmaker some squats. If you aren't sore you have some sort of mutant super abilities.
Of course, it is still calorie in, calorie out, but we need to understand what effects metabolic changes in our body if we want to understand what calories are going out. Furthermore, quality of life generally indicates most people don't want to shut their metabolism down even if it did mean weight loss -- we want to be energy using machines that are motivated to "get up and do stuff", so just blindly reducing calories is not the path to that.
Calorie counting is an important part, but knowing what macro-nutrients ratio is just as important. More protein, more fat, more fiber, less carbs will help that a lot. Why is calorie tracking still so important? because fat takes forever to metabolize and is denser than carbs, so (a) You will need to break the psychological programming of expecting food to provide instant fuel, fat will take an hour(ish) to energize you; if you just are "still hungry" and eat more in 30 minutes you're losing the battle. (b) Most of us are used to eating a volume of food that equates to the calories we want from carbs. Eating that much in fat will obviously not help weight loss goals, so when eating fat dense foods we must eat much smaller portions.
There are really two separate feedback loops we use to feel sated. Fat is good
The main points being (1) brain needs glucose, can't fuel any other way (2) glucose is needed for maximum muscle response so if you are fit/athletic in any way you can be short-changing your performance if you have no glycogen stores to tap for "burst fuel"
1) A lot of discussion of being sore. Sure one of the first things mentioned is "I've been sore before", but then we move on to more complaining about it. That is a natural part of doing any new movements, no matter how in shape you are overall.
2) No appreciation of the value of high rep movements. True, they are not good for hypertrophy (probably, even there the research is shakey whether low and high should be mixed), but they are good for building connective tissue strength, for burning calories, for increasing range of motion in a movement, for bone density...
3) Author links a balanced WebMD article but the link text implies it fully agrees with the negativity.
4) Article doesn't talk much about joint issues which are probably the biggest concern a lot people have with crossfit movements. The violence of many of the movement can lead to muscle and connective tissue problems, but those heal and are obvious.
So, what are my issues with Crossfit?
1) Quality control. The excuse of crossfitters to "just find a better gym, they aren't all like that" is inadequate. Its a single program and a single franchise making money off each gym-goer, not an abstract concept like say HIIT. Ask Krispy Kreme or Quiznos how the no-quality control franchise theory works.
2) They rely on joint stability and momentum as much or more than on muscle. You are simply getting no benefit from that.
3) The movements are violent unnecessarily, this I agree with the author on. The joint reliance, the tugging at muscles and tendons, are all high risk for injury. While there are things that type of work can build that regular weight training cannot, the risk/reward is only worth it for people with specific training needs and doing specifically valuable movements. Kettle bells and kipping pull ups are pretty much never as valuable as good mornings, dead lifts, assisted pullups, and lat pulldowns. Clean and jerk has valuable movements taken separately, but combines them with high joint risk moves in between.
One of the key differences I think, is that you think as a professional manager of people. The author thinks like a "do-er", a contributor, and is looking for people who work like her. She may be an unusual woman that tends more toward the male pattern of behavior, but that is just happenstance.
One thing you both agree on, is that (whether she hates it or not) there are common differences between men and women that extend beyond appearance. Where I differ with her: Whether chromosomes or upbringing or micro-biota I don't care, those differences exist, they are useful diversification and should be accepted, even though they each need to be managed in their own way.
It is the difference between supporting a mission (even one that many may disagree with), and simply being an organization that exists to continue itself.
I would draw the comparison to someone holding a hostage at gunpoint. You don't put that person on trial before final judgment comes down.
I also find Shanley's demeanor extremely rude, off-putting and counterproductive to a discussion on any topic.
Based on what other people are saying here, my guess is, that's what we've got going on here. My common sense says there is probably a measurable, but insignificant effect by the enzyme in the yeast.
Edit: also, the theory is just that the stomach is a mixing bowl, so the poor man's field test is here is pretty trivial, maybe I'll have some fun tonight with a blender, some yeast, and a bottle of cheap hooch.
Rather than 'fencing' regions then, if it could be done to just sort proximity that way, it would be incredibly useful even while sparsely populated.
NoSQL / Document databases got so cool so fast, and were usable with little to no actual know-how that people just lost their minds and used them by default. That was always the wrong decision.
RDBMS are the swiss army knives. They do "all the things". But power, responsibility, etc.
I use various types of NoSQL models for various special purposes, they are great, and should be used, for those purposes. You almost always need an RDBMS. If it's not your gold record (because you need quick writes and can lock a whole document at a time), then you need to replicate to RDMBS for better ad hoc reporting. OTH, if RDBMS is your gold, you may want to replicate to NoSQL for fast lookups.
I'm currently working through a situation where the latter is required. I have hundreds of thousands of records and the need to solve a classic backpack problem (with hundreds of thousands of potential items to go in the pack, each of which can have n instances)... so I've replicated a few billion pre-solved solutions to Azure Table Storage. It solves a particular problem, but its not my WHOLE application's data store.
So I adapted, and I really do like ST. Got the features I want, and a clean interface.
"Dev 2": Mostly works independently, knows when to ask for help
Senior Dev: Provides more help / guidance