Well the whole point of this paper is NOT everything is a graph.
HN user
retbull
I try to be interested in big data and not make my coworkers tear their hair out with my code. I am very aware that technical writing is a skill I don't have and can't seem to develop easily.
Every 6 months? That seems like a pretty long window for tribal knowledge to get lost. Is 6 months arbitrary or is there some reasoning behind that cadence?
The original paper that is referred to in this is https://arxiv.org/abs/2209.06833
They saw raid shadow legends was making more money than them and thought they'd take a page out of their book on micro transactions.
I feel like it is pretty indistinguishable in STS if you lost because you made an incorrect decision somewhere or the run is unwinnable. Something like Zelda or Metroid you can reach a point and the game has some kind of obvious solution or key you need. STS has too many solutions to the problems of what you face and no way to go back and recheck things. The fact that it is almost impossible to find an unsolvable STS seed seems to indicate that their approach is pretty good. Player frustration in STS except for the tiny number of runs indicated in this post is entirely skill based.
Builder patterns for primitives? I think that seems super cool but then aren't you just building a new language?
As long as I can install DOOM on it IDK about the platform.
:(
Reading this is making me sick. I am working on leaving my large company for a start up for this exact reason. Something as simple as changing a tag on a server requires submitting a request -> waiting for the reply that they are working on it -> getting someone contacting you 1-3 days later -> Confirming the changes you want -> finding the changes in place the next day -> telling them the ticket is closed.
"Only direction is up"
From an entirely tongue in cheek perspective isn't all ruby idiomatic.
https://commons.wikimedia.org/wiki/File:Power_lines_through_... They cut down all the trees nearby so its basically a clear cut strip thats as wide as the poles are tall.
Did you read the article at all? They aren't talking about the pay as it is a separate issue. There literally isn't time for the managers to train and onboard people resulting in a bad experience for the new employee, the customers, and sometimes even resulting in termination for violation of policies the employee never learned about. You can't put knowledge in someones head with just money.
That story is so incredibly narrow and misleading its absurd.
Yeah volume is a terrible metric to go by. I work as a data engineer and a lot of the time if I am working between environments or when migrating between data centers will have a copy of the data locally that I can write tests against or move to somewhere I can compare it to a running output. This would be possible to do entirely remotely I guess but not nearly as easy. (note I never do this with anything that contains PII)
Statistics like the op said. If you are expecting your decay products from an interaction to be 20% X and 80% Y but after 100 billion attempts which should have averaged out to the expected outcome you instead get 21% X and 79% Y something in your calculation is wrong.
From what I read in this article they didn't prove that the force exists at all they actually showed that it wasn't present in several areas. This helps other people who are doing experiments in the area by cutting down on the range of sizes they need to look in for it but it doesn't provide evidence for its existence.
I feel like if you are working with genome levels of data maybe you shouldn't be using JS to do the work. JS is a great tool in some cases but not really a scientific one. I guess you use whatever you know.
I don't really agree with much of google any more but I was at one point fairly involved in a project there. They do have some more secure systems for government use that isn't the crazy leaky ad cesspool gmail and docs is.
Ah papyrus oh how I missed you from high school.
Hopefully this is the first time. Honestly the government needs to make more open decisions like this (hard because of tracking budgets and how contracts are awarded and defined as complete). A bit more flexibility and open decisions with easy input from their users would do our country a HUGE service and save a metric fuck ton of money.
I need me some of this invisible top hat quantum computer.
Gotta make sure it is double blind. Don't want those parrots going in with knowledge there.
Not in maintainability. It is pretty hard to follow Scala when people use the flexibility too much. You have so many options that everyone develops their own flavor of overrides/overloads and style. This makes transferring skills between jobs or even just projects much harder as the same looking code line can mean several things.
Uh it looks like there are at least holes where the tie downs can fit. The glass roof is kinda nuts for sure though. Those high walls are also annoying if you want to put tool boxes in your truck. It might be possible to still be practical by making some changes to how you might store things for easy access like on a normal truck but it probably can't use current existing solutions. :/
Yeah but the glass breaks really easily so it should help disperse the impact.
I mean AWS has driven a lot of developer practices in the last 10 years. Not a terrible bandwagon to jump on.
I live in a suburb so I have to drive to many places but I have started to notice that even if I can't walk to the store in less than 20 min it feels a ton less stressful than driving for 3 and parking for 5. I should probably get a bike as this is the perfect distance for it.
When I am in SF often I can walk faster than I can drive.
Getting more and more tempting over here. I am tired of my monthly video bills going higher and higher just to watch a couple of shows I like.