skysight-inc/HackerNews huggingface dataset:
"if you are worrying about the amount of protein in your diet, then you are almost certainly eating more than enough."

This is not strictly true for every diet. If you consume a plant based diet and don't eat meat substitutes, you can quite easily come in below the recommended protein level.

In my case, eating a calorie restricted vegan diet to lose weight, consuming sufficient proteins to meet the 0.8g/kg baseline while maintaining a caloric deficit requires daily planning. It's by no means impossible, but you do have to think about it.

Also seitan is your friend.
Yes. Blaze is the name of the binary inside Google. 90% of the code is in common. Differences are 1. integration with Google-internal tools, and 2. legacy misfeatures we plan to remove.

(I work on Bazel)
What's the trusted setup with zcash?
That seems to be more a function of a robust Constitution and institutions than democracy...
German politicians’ personal data leaked online
Except that Blaze/Bazel share code, are very similar and converging over time. The plan is for Google to use Bazel+extensions at some point in the future. Borg and Kubernetes don't share code (they are written in different languages: C++ and Go), look similar only from a very high level perspective and are diverging over time.
The full title is "Nowcasting of Population Alcohol-Related Harms Using Novel Bayesian Timeseries Methods and Synthetic Controls" which is a bit of a mouthful and too long for the HN title.
Not surprising from Brad. Every once in a while one of his articles show up on hacker news. He's good at creating debate, mostly because what he writes is always a bunch of BS wrapped in this kind of comments that make people want to comment.

I yet have to find an article from him about engineering that makes any sense. He's able to write a few lines of jQuery this seems to make him feel like he knows so much about things he has no experience on.
It actually does - having only 100 users means it's impossible to implement an effective canary system. It also means that your entire system being down affects way less people than an issue on the canary system at Google.

You have way more important things to worry about in a startup than optimising uptime.
Desktop and web development also got to ignore responsive design for a long time, and that revolution added serious complexity to HTML/CSS/JS and browser engines. You could slap a minimum desktop resolution on your product and call it a day.
Git is actually pretty good at automatically resolving conflicts within files; unless you edit the same lines, it’s easy. If you do edit the same lines, merging is pretty straightforward.

This whole conversation the last day or two on HN has been kind of nuts. Like everybody agrees you shouldn’t put all your code in a single file, right? Why not? It would let everyone see all of the source code in one place! But it would be huge and hard to avoid conflicts. So we split things into files. Then “trees”, etc...

Basically it sounds like googles monorepo is really a bunch of repos glued together with changes in one triggering changes in others. The difference, it seems, is that google does not get to benefit from the things OS developers like about git. It’s like google developed custom versions of GitHub, circleci, and other tools and are marketing that as a better solution (just build several billion dollar solutions to manage your monorepo!).

And even after all that, google has a bunch of separate repos for important open source or secret work.
Device Location from Mobile Network: Cell ID
I tend to see it used like this: a tactical game is about the movement of the pieces/units and about winning this match without particular consideration for the next one, or considerations of logistics or use of resources. A strategic game is concerned with the overall campaign (did I win in such a way it favors the next match? Was it even a good idea to play this match? Did I use too many resources?)

Indeed it's about high level vs zoomed-in detail.
That is trivially untrue just from cats - as obligate carnivores they have "overclocked" kidneys such that they can drink sea water and gain hydration. This serves them regardless of fresh water availability due to their need to break down so much protein for calories and will quickly suffer ammonia poisoning if given they lack sufficient argine while digesting a meal. And yet the kidneys are still a common thing to start failing in old age and call for a lower protein diet to counteract. Again in an obligate carnivore with less intestinal length.

It is true that we aren't obligate carnivores but the underlying mechanism for damage exists regardless of how well it is countered.
How do black holes fit into this picture? Are they anti-de Sitter locally?

I mean if our universe maps to 2d boundary, you could find it out if you try to pack 3d volume of space full of information/matter. The volume must become full earlier than if the the information is limited by the surrounding area and not by the volume.
> This wasn't written for a technical audience (or they wouldn't have had to explain what each band was), "everyone" knows what AM and FM radio are, and few know (or care) that they are modulation modes.

I think it's worth pointing out that the difference between AM and FM being modulation is right in their respective names: Amplitude or Frequency Modulation. It's very descriptive - not exactly rocket science.
Location: Wrocław, Poland

Remote: yes

Willing to relocate: no

Technologies: C (embedded, avr, stm32), Python, Linux, ansible, aws, some frontend (vue), planned: go, elixir; electronic prototyping and debugging; manual workshop skills
CV: on request

email: zdzichucb at gmail dot com

github: https://github.com/d21d3q/

I like to work as close to bare metal as possible with deep understanding of domain. Working with electronics, oscilloscope is pure fun for me.
Recently I am experimenting with web technologies with directions to backend, but I don't mind touching frontend.
I would like to join some team working with (creating) telemetry system.
Review 2018: Offering Solutions Software
Brexit: The really worrying thing about the Irish backstop
Thanks for the response and for writing the books. Seriously considering buying both as a present to myself for the Orthodox Christmas.
I think the satiating element is the fat rather than the protein, no?
"if you are worrying about the amount of protein in your diet, then you are almost certainly eating more than enough."

I wonder where that author got that from... last I checked whenever I don't eat enough protein my hair and nails get brittle and fall, my skin gets dry, and I get random muscle pain...

I had those issues for years and years of my life, and tried everything, only after I went to a almost zero carb diet (that at the time I didn't even knew it had a name, it was just something random I tried after trying everything else) that those issues went away... and as soon I eat "recommended" level of protein instead of eatingn "too much", the problems return.
Unable to unlock an Android phone?  Skype   application allows code bypass
Treehouse, Pluralsight and Udemy all have advanced React courses. HOC, Redux, Auth, and pretty much everything else is covered. You get a free trial at Pluralsight which is more than enough time to do one or two courses.
Is there an inflation in the number of authors per paper?
satiating, what a silly way of saying satisfying..
On the other hand, if I facilitate people arguing for fascism I will also eventually lose freedoms if they win. And in the meantime make a number of other people just that little bit more miserable.
HTML/CSS were engineered to be device-independent and to separate styling from the underlying semantics, from day one. Properly understood, "responsive design" is a triviality; all good design is responsive design.
Maybe ... but that still does not mean that science proofed a high protein diet is bad for the kidneys of healthy humans.
For a different definition of zero though. While webpack now does something useful with no configuration (which is great), you will most likely end up adding lots of configuration for any application. Whereas with jetpack there's a chance that you won't (at least in my experience).

The challenge of course is the diversity of the ecosystem. Different projects are trying to address it differently, e.g.

* CRA is opinionated and unconfigurable

* Neutrino/pwa-cli propose a higher level plugin approach (i.e. install a plugin, without needing to configure it, in webpack plugins take many lines of configuration to configure)

* Next/Gatsby use a plugin system as well but are also specialised tools which means a lot of decisions can be abstracted

* jetpack tries to be application/use case/framework agnostic and provide you with the most commonly used/useful foundation, you can optionally add extra (e.g. sass), but you don't have to recreate the foundation (i.e. es6, jsx, modern css, css modules, hot reloading, serving, producing html, etc)

It's also about the DX, jetpack lets you run a dev server with a single command, it lets you analyse the bundle with a sigle command, it builds an optimised, split chunk bundle with a single command.

Just pointing out some motivations behind the project, I'm a fan of webpack, been using it for many years.
I think the objections to rewriting code are sometimes justified, rather than just blindly following rules. As you said, refactoring code helps you understand it. This means that you can end up feeling like your code is objectively clearer than before you started, but sometimes it's just an illusion caused by the fact that you just (re)wrote it. If there are other people in the company that already understand that functionality, you're disrupting the effort they put into understanding the old version of the code. Combine this with the risk of introducing bugs or missing some obscure bits of functionality, and there is valid reason to object.

I find this is particularly common mistake by junior programmers (not saying this applies to you), presumably because they aren't used to reading other people's code. Frustratingly, this is often coupled with an attitude that missing out large chunks of existing user functionality is acceptable if it makes the code a bit simpler.

Of course, sometimes rewrites/refactors really are an improvement. Sometimes code really is fragile and confusing, either because of who wrote it or because it has had many small changes tacked on in the easiest places. Or perhaps the last person that understood that code has left the company, so it's OK that you find the code clearer only because you just wrote it! But in any case, it is fair to ask for real justification for a rewrite.
Federal law prohibits them on the driver's side in the US[0].

[0] https://wheels.blogs.nytimes.com/2010/12/30/in-defense-of-co...
I think you mistunderstood that link is arguing for. It's basically github flow with tagging on what you release, only goes into a bit more details and discussed alternatives and suffers a "bit from too much information"

https://guides.github.com/introduction/flow/

Is a cleaner and more obvious guide.

The idea is you have a constantly usable master, and your branches should be short lived so you don't hit a brick wall trying to get reviews and merge on your massive change sets.

Ultimately it means you want to test and review your change before it goes into master as opposed to creating "production", "staging" and "develop" branches, which largely just kick the can down the road and is a different way to solve that "what's deployed where" issue.
Enhancing Touchscreen Experience by Proximity Detection and Haptics Feedback [pdf]
Famous last words ;)

While leveraginvg serverless gives a lot of benefits in terms of hardening and infrastructure setup, all the traditional application security issues (e.g. OWASP TOP 10) like SQL injection can still apply.
This is awesome, congrats! I will definitely try this for my next project
Right, that's why large swathes of Europe face 40% youth unemployment, higher than where I live in Africa, right?
Very recently there was an article in the NYT about the benefits of eating protein, and more so than the recommended amount, if you're trying to increase strength (something that's != body building). It benefits everyone, esp at older age.

A review of studies showed a clear advantage of high protein diet.
I don’t know about burnout, but lose interest seems real. I graduated from MIT having dropped perhaps 2 or 3 courses. I’ve “dropped” at least 10x that number on EdX and Udacity.

I think it’s mostly a matter of engagement and commitment (no real penalty to dropping a MOOC and it didn’t cost much, if anything) and not that burnout is any worse. IOW, the rate of loss of interest might be no higher, but the initial level of interest might be lower, putting you closer to the threshold of dropping out.

Full time university is also the last time I had no other life obligations...
This is fantastic! As a prominent backend developer and someone who loves working on side projects, but hasn't got a design side for frontend development I can see myself using this for all of my own projects going forward!
I think the point being made was:

"Logic programming is considered superior to HTML/CSS even though it isn't. Just like one gender thinks that they are superior to others even though they aren't."
I respect your anecdote, but there are many other factors that could be in play here (for example vitamins that you get along with whatever protein source you use).

If you'd like to suggest that everyone is eating too little protein, you should setup a double-blind study with a few hundred participants.
I think it's different. I can be highly satisfied with a bannana split ice cream, but hungry again far sooner than after eating steak.
Because there are people who think things work at Google must work magically for their company. There are many patterns that seem perfect in theory but fail miserably in the real world. Always think different and take nothing for granted.
So, perhaps people should be able to vote for their dictator? :)
Not really, since Python can nest functions:

def something(x):
def myfunc(y, z):
...
return result
reduce(myfunc, x)

So the difference is like having to write

x = some_very_complex_expression_that_can_get_quite_long
some_function(x)

instead of

some_function(some_very_complex_expression_that_can_get_quite_long)

In many cases this may make code even more readable.

I'm not saying that Python's lambdas are perfect as they are or that multi-line lambdas would be a bad thing. I'm just saying it's not as bad as you paint it.
How long did it take to port?
With acoustic modems on both sides. Can you hear the old-style modem connect screech now?
Well said. And humans definitely need healthy intestinal tracts - and need complex carbs to last long enough to feed beneficial microbiota.
"Fascism" has never won by arguing, though. It isn't even a well-defined ideology! Fascism means using political violence (i.e. beating people up, or worse) to seize power in something very much like a coup d'etat; it really is as simple as that. That's not free speech, and it's not even something that our government protects. Threats are illegal. Purported "speech" that poses a clear and present danger is illegal.
Google Moved $23B to Bermuda Tax Haven in 2017
A coaster in Roller Coaster Tycoon 2 that takes 12 real time years to complete
Facebookincubator/fbt: A JavaScript Internationalization Framework
I've performed that experiment repeatedly ad nauseum. For me the protein makes me push the plate away faster than the fat and leaves me not hungry for longer.
In other words, tactics are about how to win the fight. Strategy is about which fights to engage in to accomplish an overall goal.
If monorepos enable monopolicies (even if monorepos are compatible with usage that doesn’t involve monopolicies), that’s perfectly good reason to avoid them regardless of whether they cause monopolicies.

In “The Beginning of Infinity,” physicist David Deutsch makes a point like this about styles of government. Deutsch suggests the defining characteristic of a good governmental system should not be whether it consistently produces good policies, but instead that there is an extremely low-cost barrier to removing bad policies once it becomes clear they are bad.

Thinking this way, if monorepos permit a situation where there are monopolicies about allowed languages, allowed deployment tooling, etc., and those policies cannot be quickly discarded when it becomes clear they are bad for a certain business goal, then this is perfectly good reason to disfavor monorepos regardless of whether they cause the bad policies.

I think your responses continue to miss the point because you’re talking about correlation and causation as if it matters in a situation like this: but it precisely doesn’t matter.

If a tool doesn’t actively prevent certain policy failure modes (even if it does not cause anyone to choose a bad policy), that is a relative failure of the tool.

Contrasting with polyrepos where it is quite harder to enforce failed monopolicy ideas is one area where polyrepos are a better tool: to misuse polyrepos policy-wise you have to go way out of your way and add a lot of draconian policy enforcement tooling that often can still be circumvented. Those inherent barriers are a good thing that monorepos don’t have.

Separately, I’d also say that the political failure mode where central IT wants to enforce draconian policies is extremely common, and those types of organizations specifically see a monorepo as a tool of (their desired) oppression and control.

Since the base rate of occurrence of horrible companies is super high among all companies, it probably does mean that P(bad | monorepo) is pretty high conditional evidence of a bad workplace culture.
What suffering? Did they fight in the front-line or plough fields old day long? The handful of males at the top didn't make ALL men not suffer, neither did make ALL women suffer. Royalty women had better lives than the 99% of men throughout history. That's revisionist history at it's finest and the same BS reasoning the writer of this blogpost has.
You are pretty out of touch with reality then
I mean your cell phone's location from which you would otherwise tether the connection would be close enough. I guess no one has written an app to convey that information. The other use case of gps could be a good source of time if you have no network connectivity.
Protein is considered to be the most satiating. This review article calls it "fairly well established"

https://www.sciencedirect.com/science/article/pii/S092422441...
I love seitan, but I’m not sure it’s necessarily healthy. A lot has to be removed from wheat gluten. Probably soy/tempeh are better for being Whole Foods
More efficient might mean less CO2 consumed to simply produce an identical plant. Would have to trial it. Assume this genetic manipulation might even stunt growth in some species. Again would need trials.

I cannot find the particular article I was looking for regarding withered leaves that plagued a long-term (10+ years) genetic manipulation project in sugar cane, but here is a list of problems I found:
http://natureinstitute.org/nontarget/browse_titles.htm

From my observation of friends who were doing genetic manipulation of plants, it is not easy.
Register-based VMs means your bytecode compiler needs to do register allocation.
Well, if you exceed expectations, doesn't that mean you didn't set your goals high enough?
Even their free services have great support, I had some non-standard DNS setup that wasn't possible through their web interface and it was up and running within a few hours.
This is, quite simply, horrible advice.

If you are strength training regularly and slowly increasing the weights you are using, mild muscle soreness should be expected. If the soreness is bothering them, there are several options that are known to help - stretching, additional warmup or cool down exercises, ice, heat, or massage.

The signs that could suggest a protein deficiency are decreasing muscle mass, weakness, and/or swelling, but even then you would suggest a trip to the doctor, not simply to increase protein intake.
You can organize using a class hierarchy, which make it possible to have separate rules for .foo button and .bar button. To over-rule something you make it more specific like .foo form button, .bar form button
My understanding is that OKRs at Google are visible throughout the org, and coleagues are able to (and do) provide feedback on them.

Most orgs that adopt OKRs only make them visible to the person's manager, and without transparency and good feedback, the other problems mentioned here proliferate.
Can't have any good news about Tesla on hacker news no no no
(Genuine question.) Do you think "small changes" shouldn't be "tacked on in the easiest places"?

I'll try to give an example I hope is realistic:

One of the heaviest things an application can get is a complete theme system. Suppose you don't have one. It's not a requirement.

Adding a theme system when there is none is months of work and might impact basically every line of code that displays anything.

So you're not doing it. Now for some exceptional system there is just one case where somewhere you are displaying something under an external widget that doesn't meet its size constraints or whatever - long story short your text is invisible, you want to inverse the font to get it working. You don't have any code like that.

Do you think it is OK to add it to the easiest possible place: in this case perhaps you add an optional argument called "need_to_invert_color" (this awkward phrasing tells you it's a hack) to a single function, default it as false, comment it as: //invert the color of the font. This is needed where an external graphing widget with a black background leaks onto our canvas due to not respecting our pixel boundaries, so that our text displays over it.

And then where you call comment the same thing, that //currently a bug in the widget code makes the widget leak xyz pixels below its bottom border. As a temporary fix we introduce an argument need_to_invert_color into our display function. As of this writing 3 Jan 2019 we are just using it from here. The correct fix would be for the widget to stop leaking instead, and when that is done white text is unnecessary - and we might not notice. So we start by testing whether the area we will be overlaid over is indeed the wrong color.

ETC. In other words a quick hack for a corner case, that doesn't fix the underlying bug (workaround) and even as a hack makes use of something that doesn't exist (a theme system), instead adding and documenting a half-assed thing tacked on.
Ask HN: Going from Developer to Manager. What should I know or learn?
After reading (and resonating quite a bit with) "Developer Hegemony" by Erik Dietrich, which was one of the recommended books in the "what did you read in 2018" posts, I think about steering my career to a manager instead of a developer position.

For all those of you who've done the same or planning to do the same: What are the most important skills or what's the most needed knowledge in such a position? Where can I learn it? What should I read?