skysight-inc/HackerNews huggingface dataset:
> When something survives 2x longer than expected, it might be survivorship bias. When it survives 10x, 100x, or 1000x longer than expected, you should probably look closer

You're implicitly assuming a normal distribution or something like it, but it's easy for a lognormal distribution to span multiple orders of magnitude like that, and the Weibull distribution commonly used in reliability modeling for this kind of thing can also be heavy-tailed if k > 1.

A simple physical example of how this could arise would be if the filament diameter of a batch of bulbs was normally distributed spanning a factor of 2, resulting in filament resistances spanning a factor of 4, resulting in filament powers spanning that same factor of 4, resulting in filament powers per unit area of filament surface spanning a factor of 2 (since the thickest filaments have the lowest resistance and thus the highest power at a fixed voltage; it'd be 8x instead on a constant-current source), resulting in filament Stefan-Boltzmann temperatures varying by about 19% (1.19 is the fourth root of 2), which works out to a temperature difference of about 200 K for filament temperatures of about 1000 K. That's probably (handwaving here) enough temperature difference for about an order of magnitude difference in vapor pressure, which (handwaving wildly at this point) might mean an order of magnitude difference in filament evaporation rate.

Also, typically there are hotspots in a filament where it's thinner than the rest, which evaporate more rapidly because they're hotter, which makes them get thinner faster, making them even hotter. So the dominating factor in filament lifetime (at a given voltage) might not be how thick it is but how smooth it is.

So, you might find out something interesting. Or you might just find that this bulb had an unusually thick or smooth filament.

(Carbon has 1000x higher vapor pressure than tungsten, though, which is relevant here: https://www.powerstream.com/vapor-pressure.htm.)
Take on Tesla? The driver is responsible at all times. If AP was failing to stop the driver should have been paying attention and took over.
I can't tell, is that bounce rate mentioned in the article good or bad?
significantly less

I can't take your comments seriously anymore. This isn't true by any stretch of the definition of "significantly less". Please do some basic research: https://www.glassdoor.com/research/jobs-companies-2019/
Thank you! We actively seek out customers with idiosyncratic matching because we're better at it than alternatives. We rely on user engagement, in-session model responsiveness, and in-house expertise from the marketplaces themselves.

Part of the way we solve this is NOT with machine learning, but with tools to empower internal merchandizing teams and product teams in a way that fits nicely with the automated system. If you're a on a search team and had to goof around with elastic-search scores or hack in inserts for a new market merchandizing team, you've felt this pain. The path forward is ML + human expertise, which is better than either alone.

> basically fail at it

Our goal is to figure out "why" and "how to make it better." These are $T companies and dominate all performance ad spend. It's hard to think about such big numbers. One problem is that they start with crappy inventory (people who want to advertise) and it's really hard to actually _do_ something on these platforms with promotions that you do see. On marketplaces, you don't have these problems as much, because everything is already vetted and you can convert in the marketplace. That's why you're there, so it's a great experience.

So, we start from there, media matching that people love, and work backwards.
LinkedIn's editorial team also published a story that quotes reactions from people on LinkedIn to this New York Times news story. Reading the NYT article, I was a bit shocked at some of the behaviors like "delegating upwards", or using bad faith excuses to skip work, or bringing personal political agendas into the workplace. But it seems many on LinkedIn - or at least those cherry picked examples here - are cheering on these behaviors.

https://www.linkedin.com/news/story/gen-z-workers-baffle-old...
Quickwit | Senior Rust engineer | Remote (EU, ASIA) | https://quickwit.io

Quickwit is building the next-generation open-source search engine for petabyte-scale data. We are also behind tantivy, the Rust search engine library that has rallied a great community of users since its inception.

We are looking for an engineering generalist with extensive experience writing Rust code and leading technical architecture. Working with large data sets, dealing with complex distributed systems, and developing backend services should be second nature.

More info about the position: https://quickwit.io/jobs/distributed-software-engineer
:eyeroll:

Why is it always "them" vs "us"? NSA/CIA are doing probably a better job at global surveillance of everything and everyone, simply based on resources available to them. Every powerful enough government spies on the largest scale they can, because just letting someone else to spy on you and not spy yourself (if you can) would be infinitely foolish.

Even at local scale. If citizens could find a way to hold their president on short leash, such president would be more likely to listen to the citizens. But citizens don't have such powers, only presidents do, so they only have to listen to each other.
I wonder how salmonella from onions works - it's pretty standard to always peel the onions so is the salmonella on the surface and your knife carries it through the onion or is the salmonella in the onion already?
I like the layout of the design document and I might steal this page idea myself. However I don't agree with all of the contents:

> The law of orthogonality

For better or for worse I went the other way and crammed murex full of builtins. Most builtins are single purpose too.

Rational: while it creates additional work learning murex it does make pipeline more descriptive

> The law of responsiveness

This I do agree with an murex does a lot of tasks asynchronously for exactly the same reasons too

> Configurability is the root of all evil

I actually don't disagree with their point on principle but I think a better stance should be "Defaults should not leave most users itching for configurability" because I think configurability is a good thing however a product should ship already configured so that users aren't left having to enable features they want.

The early versions of murex came with features turned off so it behaved a lot more like Bash. Then I realised nobody is going to enable spellchecking, syntax highlighting, etc because nobody is going to know it is there. So now most features are enabled by default.

> The law of user focus

The description I agree with, the examples I do not. You don't need to remove features to make something user focused. You just need to make those features usable and discoverable.

Which leads nicely onto the last item...

> The law of discoverability

This I agree with wholeheartedly.
The downvotes are because "worthless" is hyperbolic and unhelpful. Clearly, the coins have value because someone out there feels like paying money for them.

More importantly: we _HAVE_ to understand the market dynamics here. What's going on is very human and very important to realize.

Matt Levine from Bloomberg has a very simple explanation: the cryptocoin world has discovered "senior debt vs junior debt", and are using this concept to create stablecoins.

------------------

The issue is, the rest of the world _REMEMBERS_ 2008, and what happened the last time we relied upon the senior/junior debt split. The concept is simple:

Junior debt is high-risk. Senior debt is low-risk. Through the use of structuring your economy around this concept, your junior debt "supports" senior debt.

A stable-coin, is simply the senior-debt on some other cryptocoin.

-------

Lets take BTC for example. Lets say I want to "create" a stablecoin out of BTC, despite its widely varying valuation. Lets say I set up a senior set of notes: it stays at $1 as long as BTC stays above $10,000.

But what about all the "risky part" ? Well, someone out there in the world wants to bet it all on the risky part. When BTC rises from $10,000 to $50,000, they want to make $40,000 with $0 investment. Because the "senior" guy already took the risks for $10,000 and below, I can now offer the "rest of the gains" to the junior guy, who can play with all the values of BTC above $10,000 (except, without having to pay any money in the first place).

When BTC goes up to $20,000, the junior guy spent $0 and made $10,000. Senior guy still has $10,000.

When BTC goes up to $50,000, junior guy now has $40,000 and senior guy has $10,000.

This sounds hypothetical, but its in fact very similar to how the stablecoin TITAN / IRON was structured, with Titan as the "senior" stablecoin and Iron as the junior.

Now just wrap it all up in a smart contract, maybe tie the concept to Ethereum (or whatever other cryptocoin suits your fancy), and you too can reinvent senior/junior debt structures and pretend you're a genius.

------

You see? Senior is "just" the stablecoin guy. Junior is the WSB idiot who might lose all of his money.

Or in other terms: your CDO of CDOs is truly and 100% secure. You may have a pile of shit, but you can extract stable values out of it.

Or at least, so went the theory of 2008 housing crisis, CDOs, and CDSes and all that. We know where that went however.

It hasn't even been 13 years and everyone's forgotten about the underlying assumptions that broke the market in the 00s.
Why would you use a driver's license when everyone can have a digital ID card?

In Belgium the notary will always ask for your digital ID card.
TLDR; If you're looking to reduce the risk of contamination, consider purchasing whole chickens or, at least, skin-on, bone-in, cuts.

This is because the risk is substantially higher if you purchase skinless or deboned chicken - most contamination is on the surface of the chicken, and is easily killed during cooking.

However, during processing, the tooling used to debone or deskin the chicken may get contaminated, and necessarily pierces the flesh of the meat. This tooling isn't usually disinfected between chickens (cost prohibitive). As a result, if one of the birds has surface contamination, this contamination will remain on the outside of the instrument, grow, and subsequently infect the inside of all the other birds.

This is important, because direct heat is actually pretty good at killing bacteria. However, if the bacteria are able to penetrate to the inside of the chicken, there's a substantially greater likelihood that the temperature (and duration) on the inside of the chicken are insufficient to kill disease causing bacteria.

Note: The overall idea is to recognize that surface bacterial contamination can be killed with sufficient temperature over a sufficient duration of time, recognizing that the lowest overall temperature will be in the thickest part of the meat, and ensuring that there isn't a mechanical mechanism that will introduce contamination in that area.
I'm not defending the police per-se, but I assume the local PD probably doesn't know how to handle such an investigation yet.
I assume UF has a conflict of interest office for this reason and I can see UF's argument whether I agree with the outcome or not. So I would ask why these 3 professors? Are there not private Florida institutions (e.g. UMiami) or universities in other states that have voting rights experts?
Chainlink is the industry standard oracle network for connecting smart contracts to the real world. With Chainlink, developers can build hybrid smart contracts that combine on-chain code with an extensive collection of secure off-chain services powered by Decentralized Oracle Networks. Managed by a global, decentralized community of hundreds of thousands of people, Chainlink is introducing a fairer model for contracts. Its network currently secures billions of dollars in value for smart contracts across the decentralized finance (DeFi), insurance, and gaming ecosystems, among others. Chainlink is trusted by hundreds of organizations—from global enterprises to projects at the forefront of the blockchain economy—to deliver definitive truth via secure, reliable data.

Open roles:

* Release Engineer: https://jobs.lever.co/chainlink/a8dd7868-eaf7-4d97-98a9-2f5b...

* Senior Software Engineer - Golang: https://jobs.lever.co/chainlink/23bbe7b6-e956-4a42-ab6b-82d7...

* Big Data Engineer: https://jobs.lever.co/chainlink/b6657c98-d27c-4420-9d02-7695...

* Solidity Engineer: https://jobs.lever.co/chainlink/ba773e65-aef7-4346-84a8-1ceb...

* Solutions Engineer: https://jobs.lever.co/chainlink/ef4cbde4-2e2b-4896-b24b-ac0e...

* Other openings: https://chainlinklabs.com/jobs

The full vision of the Chainlink Network can be found in the Chainlink 2.0 whitepaper: https://research.chain.link/whitepaper-v2.pdf

These roles are location agnostic anywhere in the world, but we ask that you overlap some working hours with Eastern Standard Time (EST).

We are a fully distributed team and have the tools and benefits to support you in your remote work environment.
Even less than people want to hear that gold is just shiny dirt, people don't want to hear that almost all perceptions of value are inherently subjective and meaningless.

That social credit, and money, and everything we hold dear and true is just narrative we've crafted around ourselves to cope with the uncaring void that is the cosmos.

So -- my guess -- people are probably going to keep thinking that things are valuable so long as everyone else around them does. And technically everything can be reduced to nothing more than a set worthless human brain farts.

Edit: except for your values of course. Whoever you are, your values are certainly meaningful, and your life is a story that really matters.
Location: Berlin, Germany

Remote: Preferred

Willing to relocate: No

Technologies: Typescript, React, Nextjs, Elm, Nodejs, Python, Django,Express, AWS, SQL

Résumé/CV: on request

Email: j (at) mejuto.co

Website: https://mejuto.co/

I have worked with international software companies, universities and institutions in software engineering, marketing tech and consulting.

My specialty is Full-stack software development. Happy to work in Frontend and backend.
The outer packaging is often contaminated, and can contaminate the beef packaging. Bacteria survive in the freezer.

Beef, except for pre-ground beef, is generally much safer than poultry.
I hadn't noticed until you pointed that out but yes I have!
Historically, we've had major bubbles and crashes in all kinds of financial markets, from stocks and bonds, to property and dotcom stocks. Is there any reason to believe that cryptocurrency is more stable and we won't have a catastrophic crash?
It's not actually that much different than a negligent driver. The driver was negligent with the OTA update and the driver was negligent enough to trust autopilot in traffic.

Tesla should of course improve its autopilot technology but I don't see how they're responsible for the crash.
well, just for the record, I do, and I've also worked for the body that calculates our CPI. just before I left we were studying how to get what we call "administrative item data" from the retailer's themselves rather than relying on surveys, household interviews, internet scrapes or staff research. To be fair, CPI was never my specific methodology speciality, but I can talk your ear off about household incomes, relative welfare measures and theoretical probabilistic data linking and entity resolution :) (I've also had a finger in the pie of a lot of other measures even though I wouldn't call them my speciality, but I'll wager I've got more experience than 99.9% of hacker news in this regard).

honestly, as someone who's had to put together official stats, I'm almost always disappointed to hear the conspiracy theories and methodology misunderstandings in the general and tech community. back in my day when the government wanted to do actual conspiracy they just cut the funding for measuring/recording something. but instead we get "CPI is rigged", "do you know what the REAL unemployment rate is" government-manipulation ignorant memes.
strongDM | All Roles! Go / Golang | FULL REMOTE (core hours ~North American timezones) | Full-time | https://www.strongdm.com

strongDM is an identity-aware proxy for managing and auditing access to infrastructure: Kubernetes, databases, generic SSH destinations, internal web applications, Windows (RDP), cloud providers, and more. We build secure, high-throughput networking systems in Go.

We've been fully remote for years, building software to help people work remotely. We have high standards and high levels of respect for each other and our customers.

Recent financial news: September 2021 - $54M series B https://prn.to/3ipnEVw

Current roles:

* Senior Software Engineer (Golang, secure distributed systems)

* Senior Front End Engineer (React, TypeScript, GraphQL, Electron)

* Director, Infrastructure

* Product Management, All levels

* Sales Engineering & Solutions Architecture

* Sales, Marketing - All roles / All levels

* More roles here: https://www.strongdm.com/careers

If this sounds like the type of work and the type of environment that would suit you, send me (Justin, co-founder & CTO) a note at justin@strongdm.com
The problem with all of this is that it's complicated, people misstate things, and everybody is eager to prove that "their side" is right.

So then you get excessive claims like "no state purges voter rolls" which is just easily falsifiable, and then it gets falsified and leads one side to believe that to be the end of it.

Whereas what really happens is that a state goes to purge its voter rolls, they have a list of 100,000 "dead people" and the list is erroneous and contains hundreds of live people, because government databases are full of dung. So then they get sued, often right before the election, to prevent any of the names from being purged, including any of the 99,000+ who were actually dead.

Another thing that happens is that someone dies between the last purge and the election. Then either they submitted their ballot before they died (but were ineligible to vote because they weren't alive on election day), or they were sent a ballot after they died and a member of their family submitted it. So there are always a few dead people in every election who voted after they died, and some of these are actually fraud (in the second case), and others aren't "fraud" but they're still invalid votes that shouldn't be counted. Rarely if ever does this, alone, change the outcome; but the ballots are there.

Which results in the over-claim on the other side. "There are zero dead people voting." Also easily falsifiable.

Then each side gets to declare the other side wrong and biased and hidebound and irrational.
Why do you think she was telling the truth? People’s instincts in such situations are for self-preservation, and shifting blame elsewhere is common.
To present more of the picture here:

"Paige Stanley, a researcher at the University of California, Berkeley, says many of these studies have prioritized efficiency — high-energy feed, smaller land footprint — as a way of reducing greenhouse gas emissions. The larger the animal and the shorter its life, the lower its footprint. But she adds, "We're learning that there are other dimensions: soil health, carbon and landscape health. Separating them is doing us a disservice." She and other researchers are trying to figure out how to incorporate those factors into an LCA analysis.

Stanley co-authored a recent LCA study, led by Jason Rowntree of Michigan State University, that found carbon-trapping benefits of the grass-fed approach. Another recent LCA study, of Georgia's holistically managed White Oak Pastures, found that the 3,200-acre farm stored enough carbon in its grasses to offset not only all of the methane emissions from its grass-fed cattle, but also much of the farm's total emissions. (The latter study was funded by General Mills.)"

That's from your first link (npr dot org). Seems like the jury's still out on this one.
Note though you have Aurora PostgreSQL as well as CockroachDB and Yugabyte which speak PostgreSQL and may be able to support MangoDB
The full text is in the the description of the video:

More info: https://www.chatcontrol.eu
Boy This Is a Long Truck
> Having gone through the purchase and sale of houses I'm honestly confused at how this happens. It involves a ton of paperwork, phone calls and in-person appointments, generally.

It seems that this was sophisticated identity theft.

If someone managed to get a DL with your name on it, but their picture, and your SSN, then it's pretty much carte blanche at that point.

Go into a bank and say "I need to close my accounts". "What are the account numbers?" "Oh, golly, I forget -- here's my DL, my BDay is XX-YY-ZZZZ and my Social is 123-45-6789. I recently moved from 1234 Main St. to 4567 First Ave." "Of course sir, one moment." Next thing you know you're walking out with a check.

And..that's it, it all comes from that. Buy a house, sell a house, request some documentation. Especially, since they're SELLING the house, they don't have to go through the rigors of a background check for the loan. The BUYERS are placed under a microscope. The sellers? "So, you got the key?" "Yea." "We're good, sign here."

And it's noone's fault except the original perpetrator. Everyone else did "due diligence". If the questions were answered properly, showed appropriate ID, what more can they do?
Huh, so if we are trotting out experience credentials, I have also worked with thousands of developers (I guess?) over the last ~20 years as well. My first programming language was Apple BASIC on an Apple II, and I haven't stopped learning since!

I think we use this term differently, perhaps? This term is not intended to be an attack, but rather just an acknowledgment of a common type of technical debt that results from people getting influenced by marketing teams and choosing tech based on how "trendy" it seems. Sometimes this might be done explicitly since they are intending to jump ship anyway... I've had conversations at the bar out of earshot of "the suits" where this exact topic was discussed! Most of the time it's not intentional or explicit, but just novice engineers directed by poor management to greenfield apps, and then falling for marketing claims and choosing based on how "trendy" the marketing claims it is vs real, observed needs. MongoDB is still getting taught at many bootcamps and coding curriculums as an "SQL, but better for beginners since you don't need that annoying schema thing!"
I think Zuck has lost the plot. Anyone know the best way to take a bet on it?
Tesla launches a new home charger that works with all electric cars
Containers may not be a security boundary yet, but they do promise a level of security and even though the kernel and various runtimes may not be there yet, one day they will be.

Every time there's a container escape or privilege escalation, it's treated as serious and patched. I look forward to the day when we can confidently say that containers are in fact a security boundary.