1,600 karma · joined July 19, 2009
I think it's easy to fall into "this comment is a value judgement on my skill/person, and not my code" if code review feedback is targeted at the person and not the code.
Hence the discouraged "why did you do this" form vs the more helpful "this might be better because" format.
I find line by line reviews useful for small PRs of limited scope (bug fixes, etc), but find it a difficult space to talk about things like approach, architecture, etc.
For the latter, I've found round tables where the dev in question have the time and space to explain their reasoning in a synchronous real-time manner to be valuable.
(But as you side, that goes both ways, to both the reviewers and reviewed)
2. Relies on a "web standard" that Google is pushing and is implementing in Chrome (and so far, I think, only confirmed to be in Chrome)
I'd take most arguments in this with a grain of salt, as it predates much of the progress that CSS (and things like Sass/Less/PostCSS) have made over the past decade.
Fun fact: Antirez worked on Redis solely on a MacBook Air 11"
http://oldblog.antirez.com/post/apple-mba11-my-sole-computer...
Caps lock pressed AND released in isolation within 250ms is escape.
Caps lock pressed in conjunction with another key is control.
The way it seems to do it is to trigger key events on key_up rather than key_down, meaning "escape" is triggered when you release caps lock, not when you press it. This can feel a little strange in some edge cases, but in normal usage, I don't notice it at all.
This has essentially saved my MacBook Pro touchbar as a dev machine, since I absolutely loathe the touchbar escape key, but didn't want to lose caps lock as control.
If the second part is more accurate, why did you even bother mentioning the first? If it's correlation you don't even 100% believe in, leave it out.
If someone, in your place of business, says "what you just said was hurtful and offensive", then yes, I think maybe you shouldn't say it. Or at least take pause and consider why what you said may be hurtful.
None of that prevents your ability to say what you want outside the office.
I'd caution against using a single situational anecdote and drawing conclusions about an entire culture. For one, it's highly likely that many maids in the U.S. (especially at a dedicated guesthouse or bathhouse) would also have a more minimized reaction to guest nudity and privacy. The experienced ones have seen some shit.
Not everyone is going to agree on the best way to foster diversity and inclusiveness, and that's fine.
> You need read-only, airgapped backups before you can consider yourself safe.
Ahem:
> Carb restriction is key. You can literally eat until your stomach hurts all day long and lose weight.
But too often, in the swing towards "think about more than just calories!" I see folks completely ignore calories. It's much, much harder to over eat on some foods than others, true, but IMO I find people espousing "you can eat as much as you want all the time!" to be equally damaging.
Set a target caloric amount. Eat towards that. Fat/protein heavy foods make that easier to maintain.
Certain foods help satiate better than others at lesser calories -- which is why some people find that eating 1500 calories of high fat and protein foods to be much easier to live with than eating 1500 carb heavy calories.
IMO, that's one of the big draw of keto. It's not that you can magically eat 5000 calories of cheese and meat and lose weight. It's that you can eat a caloric amount at a deficit and still feel energetic and full and like you didn't miss out on anything.
While I agree that for many people, restricting carbs is a far easier method of eating healthy while still feeling fully sated, stating that you can "literally eat until your stomach hurts" is false, misleading, and potentially destructive.
5000 calories of cream cheese or other caloric dense foods is, still, at the end of the day, 5000 calories. Caloric restriction isn't the only way to diet or eat healthy, but ignoring overall caloric intake (even rough estimates) while only focusing on "what" you eat is one of the biggest pitfalls I see.
1. This essay is part of a series, where guest authors are explicitly asked to "uninvent" something. So there's a level of built-in hot take to this.
2. The author is Ted Chiang, writer of Story of Your Life (and the work that the movie Arrival was based on). He's explored how language affects how we think before (Story of Your Life/Arrival is explicitly about this). So this kind of falls in line with that.
Anyway, I think this is a fascinating thought experiment to work through. What would China be like with a phonetic system? What would change? How much of the culture is derived from the method of language and how much from other factors?
FWIW, I think Ted Chiang (author of Story of Your Life that Arrival was based on) knows a decent amount on linguistics.
At this point, Chinese characters aren't going to go anyhere. But I think it's an interesting thought experiment to puzzle through.
The full tweet is: "Uber names/blames me for account deletes, and has a different law firm -not Holders - investigating me. I have hired"
"Uber names/blames me for account deletes" is a pretty bold claim, and doesn't feel like a routine investigation.
It's not a 7 word tweet. Full text of linked tweet:
"Uber names/blames me for account deletes, and has a different law firm -not Holders - investigating me. I have hired"
The "names/blames for account deletes" is kinda weird. In either case, the title of this submission is a strict paraphrasing (despite being in quotes) of an already short tweet, which is pretty meh.
Typically the answer is: hard work and iteration, and many times not by himself. I think you're partially falling for the fallacy of the singular author completing a perfect work with unflinching vision. IMO this is incredibly rare.
Take, for example, Harper Lee and To Kill a Mockingbird. It's an amazing book. It's a novel that might at once feel effortless and also an unaltered vision of the author. But it's actually the result of years of editing (https://en.wikipedia.org/wiki/Harper_Lee):
> Ms. Hohoff was impressed. "[T]he spark of the true writer flashed in every line", she would later recount in a corporate history of Lippincott.[16] But as Ms. Hohoff saw it, the manuscript was by no means fit for publication. It was, as she described it, "more a series of anecdotes than a fully conceived novel".[16] During the next couple of years, she led Lee from one draft to the next until the book finally achieved its finished form and was retitled To Kill a Mockingbird.
Everything from the narrative structure to the title to characterization is refined, over and over again.
The goal with feedback and subsequent editing isn't the dilution of an author's vision, it's the opposite. It concentrates and clarifies the vision with each successive pass.
Obviously, you can take responding to feedback too far, but the idea of the artist-in-a-tower-birthing-a-fully-grown-work-whole is an inaccurate idea at best, and a damaging assumption at worst.
Like King says, ignore the outliers. But if no one understands a plot twist, or everyone dislikes something you really like, maybe take another swing at it. Iterate a little more. Creative output is the art of refinement as much as anything else.
(Good editors can also often help substitute for peer feedback)