skysight-inc/HackerNews huggingface dataset:
Yes, but not efficiently (it will be very slow) and will be hard to detect because of noise (the article mentions the 'cacophony' of gravity noise).
This is similar to EM radiation, so, you do frequency modulation (or amplitude, but that seems harder with gravity - you'll need to modify mass...), so you have a base high frequency on top of which you add lower frequency. The substraction later gives you a clean signal (or, Gravity Radio).
Supreme Court Upholds Ban on Sleeping Outdoors in Homelessness Case
Complementary - https://github.com/anordal/shellharden/blob/master/how_to_do...
You don't need to differentiate between Swedish and Finnish, since the layouts are identical, but between Danish and Norwegian, because Ø and Æ swap places between those two. (So, blue for Norwegian?)
It always fascinates me when this happens. Don't the CAs understand that the browser vendors can and will kill their business if they don't comply with the rules? It's not like a fine that can be ignored.

How dysfunctional does a company have to be to let this happen?
We merge upstream from VS Code every month and we plan to keep up to date with it, so extensions will continue to work and we'll continue to inherit new features as they become available.

It's a development burden for sure -- but still an order of magnitude cheaper than trying to build a good workbench surface from scratch.
I was assuming traffic from Florida to Boston or Albany. Local traffic is local traffic and I thought about the Holland tunnel->Kenmare->Williamsburg Bridge route. Which I found too exceptional to mention and likely only used by people that live in the region and should be using public transit for such trips.
I dislike the story points. Maybe 5 people in the world who understand them how to use it correctly. Often, it's just translated to hours.

The scrum guide 2020 doesn't mention story points at all.

I don't know how to fix this. But maybe we should just go back to plan in hours..
How far away from home? And which part of town? I've heard of writers doing a cabin in the woods with a typewriter so they don't get distracted by the internet.
Yeah, you should have more concern over human error and Boeing than this. But, boy, the more I have flown and the older I am, the more I get anxious during turbulence when I fly.
> Investors are not taking too much debt.

Your analysis is cogent. I'd only add, relating to the above, that it feels that we are "back" at it qua risk.-
Probably worried that it would break something for a significant number of customers, so they took a cautious approach. That's the problem with any Internet-wide change: you don't always know who will be impacted negatively or how severely. No one wants to make a quick change only to find out some critical system is now broken.
Supreme Court overrules Chevron deference [pdf]
Rhino horn is not ivory. Its keratin. Higher value to weight ratio than ivory.
You can't aim our current grav wave detectors. In a very simplified form, it's two very long tubes with laser in it, you aren't pointing these buildings like you could do with even very large telescopes.

The detectors have different sensitivity depending on the direction of the waves, so if a wave comes from a "bad" direction (perpendicular to both arms, e.g. directly from above), a particular detector might not detect anything, even if the wave is strong.

This is why (amongst many other reasons) it's important to have multiple detectors around the world (e.g LIGO has two locations in the US, you also have Virgo in Italy, and they do collaborate), this way you can assure in theory that you can "see" every wave, no matter which direction it's coming from.

(AFAIK).
Mousetrap Mondays.. I am afraid of cancer causing mice.
To me the big winning is that you don't have to memoize transitively. Occasionally someone asks me for help to optimize some react code, and then the dependency array contains some object/callback that has a dependency which has a dependency which wasn't memoized.
Remember when Chris Christie said a modern tunnel was not worth the cost to NJ?
Ask HN: Bottom Up ML Development at FAANG?
I’ve worked as a Data Science/ML Engineer for 12 years. I’ve worked for 2 “boring” Enterprise Software companies most people haven’t heard of, and 2 non-tech commercial hardware product (e.g. HVAC systems) companies. In all my jobs, my work has been defined by the “business.” It’s a typical top-down approach, with the business or stakeholders proposing all the use cases and the business value. Our job is to explore feasibility of these use cases and build something.

I recently interviewed for an SWE-Machine Learning role at a FAANG company. I asked the interviewer how they worked with the business to come up with use cases, and they said they (the SWEs) came up with the use cases, not a business stakeholder. SWEs typically came up with ideas, wrote a proposal (design document??), and things went from there, all to way to finding the people to build it and test it. It was a very bottom-up approach. When I asked them how they worked with the business side of things to determine the value of what they were building, they seemed a bit perplexed at my question. I asked for more details on examples of projects that were done this way, but the answers were very vague. They would not specify which products they worked on either. The interview fell apart at that point.

Could somebody who has worked in this type of way at a large tech company help me understand how this works? What’s an example of a project that was done this way? How do you propose a project and get buy-in? How are people allocated to the project, how to you evaluate the success of it, etc? Is it really a completely bottom-up approach? Are there any blog posts, books, etc that talk about this process in more detail?

I’ve been thinking about the products where this type of approach could work, and I can definitely see how this could work for a social media product. You could build an ML feature and run experiments to validate if it drives time on the site by directly measuring how people are using the site. But surely FAANG has a ton of other use cases (e.g. sales pipeline) where domain experts are driving the use cases?

Any insight people can provide will be helpful. A bottom-up approach is really different from all the jobs I've had my whole life. So I'm very curious to learn more. Thanks!
> What more do you want?

That the labeling disambiguate "made in a factory that makes sesame products" and "actually contains sesame." What we now have with "may contain" could be either and everyone is worse off
The first image on the post says it's not.
Zuckerberg disses closed-source AI competitors as trying to 'create God'
> de-inlining (or whatever the proper word is)

The phrase you are looking for is "loop-invariant code motion". https://en.wikipedia.org/wiki/Loop-invariant_code_motion
Yes, but that is very much different than claiming this is an inbuilt function.

My car has the ability to be loud and annoying, but I’d have to cut the muffler off first.
> I've found that storing changelog snippets in the repository is far more scalable (one file per note in a directory).

Do you have an example repo that you can share? This sounds really ideal but wondering how this is managed and organized between releases.
You guys weren't supposed to find it
The National Museum of Computing at Bletchley Park
https://www.tnmoc.org/

The Science Museum in London has some pieces, such as Babbage’s first Difference Engine and a PDP-8.
https://collection.sciencemuseumgroup.org.uk/search/categori...
[dupe]

More discussion: https://news.ycombinator.com/item?id=40816352
Ask HN: Do retros that don't suck even exist?
If we do retros as they are, they can be a great way to bring meaningful changes to the team - but it usually doesn't.

Usually people start with a bi-weekly retro at the end of the sprint, debriefing everything including the incidents, then slowly it becomes a monthly thing, and surely enough whoever is loudest in those meetings gets to say whatever they want. It ends up being a waste of time and a huge disappointment. Also, no one really takes on the action items coming out of those meetings.

Why is it that a supposedly meaningful 60 min retro can suck so much?

Of course there's got to be some ways to ensure retros actually work. Or, is there?
Crossing the Verranzo Bridge and coninueing on the Brooklyn Queens expressway or 278.
Starting in Ft. Lee?
You seem to be down voted by level 0 thinkers. No doubt they will down vote me now too.

You are completely correct. While the statement is factually correct regarding the cost of rhino horn, it is completely meaningless information.

We may as well throw in the cost per gram of a heart transplant while we're at it.

I will say that annual demand is probably the more meaningful figure to work with, and it would be even more useful to express that in terms of "how many more years of this level of demand will lead to the extinction of rhinos."
I second this suggestion. Web components and the shadow DOM provide a fully isolated "namespace" where you can keep CSS from leaking out into other components. You can still include shared CSS in those files so you get the best of both worlds.
My first guess is that during turbulence everyone has their seatbelt on. No one is walking around the cabin. It’s only at the start of unexpected turbulence that anyone should get hurt. Once your seatbelt is on things have to get pretty bad to get hurt.
[dupe]

https://news.ycombinator.com/item?id=40812622
I'm a Midwesterner in New England who's taken maybe a dozen trips to New York. I wouldn't mess with the steam system if given the chance, just see that it gets documented I guess. There's a steam system at the college I went to, Manhattan-style steam in the Maine woods was pretty cool...

Personally I care more about bringing NYC-level transit to more of the country than further optimizing one of the few pretty good systems we have.

If I ran, I'd run on a transit ticket, with a platform of mostly cutting subsidies for private passive transportation, and increasing subsidies for public and active transportation.

Let's build out a national high-speed rail network. It's been great to see the economic development along the Downeaster tracks since reopening in 2001, and exciting that it looks like a new Black Hawk line will happen in northern Illinois near where I grew up.

Automobiles have been a disaster for the country. I didn't see a noticeable improvement in safety metrics from seatbelts in the data: the only correlation I saw was reduced crashes during periods of economic decline... Pedestrian deaths keep climbing. Emission and safety (hood height) standards are a clown show. EVs don't solve for MPs in TWPs/RWPs. One more line in New York isn't where I'd focus my energy, but I'm all for those lines and improving connections with NJ and New England.

Americans have never moved less, and more and more intense hyperlocal squabbling seems a result. Historically, if you didn't like local decisions or wanted better opportunities, you moved. That's not really the case anymore. (I previously cofounded a moving and storage startup.)

Imagine if the Chinese had spent the last twenty years keeping the 19th century alive like veritable steampunks in Shanghai [1] instead of building out the world's best high-speed rail system.

1. https://www.theatlantic.com/photo/2013/08/26-years-of-growth...
I've got to give Atom a lot of credit for laying the groundwork for VS Code, but I can't imagine ever going back to use it. I doubt this project will ever get the performance to an acceptable level, since it seems like that was never an architectural goal for Atom. VS Code proved that it was absolutely possible to have a performant editor written with web technologies, you just need to prioritize it from the start. That's true for any application, of course, but not something web developers are accustomed to (especially not a decade ago).

It made me a bit nostalgic trying it out again, though. I used Atom for about a year before switching to VS Code, and I remember the vibrant community around it. It definitely fulfilled it's goal of being hackable, since there were extensions that completely extended the UI in some pretty neat/silly ways.
He was at the library not a coffee shop. I bet they still could have got him at home: Swat kicks he door in, shit! Lock the laptop! Slams the lid. Notorious Linux suspend bug kicks in and it fails to suspend. (You can tell because the fans keep going) Shit. Open, slam, open, slam. Hang on guys, I need to like modprobe or something…
Shit those bracelets hurt.
Most of the areas or things the PS alternatives can't do, are things PS should never have done, like 3d and animation. Krita even has an AI plugin that is great. I'm a pro, and PS has tons of tools I've never needed or wanted.
The problem is network effects (everybody else is using it), anticompetitive behavior (e.g. buying out competition) and corruption (e.g. lobbying).
On Windows,

mv s:\src d:\dest

Works as you expect. Now on some unimportant directory try:

mv s:\src

I have to think hard about an equivalently-stressful typo on another interactive shell.
It's very likely the case, since heart rate measurement is a significant burner of apple watch battery.

As a comparison when using a bluetooth chest strap with my apple watch the battery life during a 90 minute workout barely drops at all. The chest strap also provides a much higher frequency of reads, making it more useful for workouts that involve lots of heart rate change such as weights training and crossfit.

The Apple watch's heart rate monitor is great for a wrist-worn device, but it's lower frequency of reads make it better suited to exercises where the heart rate doesn't change drastically such as swimming, jogging, walking, rowing, elliptical etc.
This is why I choose GNU/Linux phones (Librem 5 and Pinephone).
Security theater cycle at this is stage:

1. Develop features at any cost, over-collect data, neglect security

2. Hacker gets in, pick the entirety of the data made readily available, credit card numbers, social security numbers, prod credentials, sexual orientation predictions that the company made on their customers for some reason, all of the pay history of the company, instagram creds of the ceo's girlfriend, and takes a dump in their bathroom

3. Try to shush the story

4. It gets exposed by an independent journalist in Kazakhstan who just reads /r/leaks

5. "we recently discovered that a malicious individual got access to a few logs on a random test server. Oops! So far we didn't find proof that it was used. Rest assured that security is our utmost priority. We love security here at ACME corp. Our teams have matching 'security' shirts, and every thursday we pray to Glombo, the security god. As a gesture to our customers we offer everyone a free 2 week trial of our 'security+' package ($15.99/M after trial, don't forget to cancel). Once again, sleep well knowing your data is safe with us!".

6. 6 months later the security gap is half plugged by an intern developing a novel password management system that encrypts passwords in base64

7. Go to 1. because no-one cares
I would have to respectfully disagree. React Hooks was probably the last "big" update to React and it totally changed how you build an application. The issue with hooks is you had hooks like useEffect that has very clear footguns that most seasoned developers knew but new developers would step on over and over and you also had optimization strategies with useMemo that weren't well known unless you've been around react for a while. Thing is with both of these is they can be automated with a compiler rather than having devs optimize it manually. My code has a ton of useMemo's and those micro optimizations and I estimate I can eliminate about 10k LOC assuming the react compiler does what it's advertised to do.
If you make your point in a more verbose and personable way it will be more convincing.
I guess bakeries will now actually add a tiny bit of sesame to everything, seems easiest.
[dupe]

Actual article: https://blog.google/products/translate/google-translate-new-...

(https://news.ycombinator.com/item?id=40808584)
Any code I have ever touched.
Depends on your goals/focus:

Smaller, cleaner, and faster code while still focusing on dynamic interfaces? Svelte or SolidJS

Focus on server-side HTML rendering with little to no browser dynamism? PHP (It really is quite nice now.)

Focus on server-side HTML rendering with some browser dynamism? HTMX + server framework (PHP, Django, Go templates, etc.)

Getting a job as quickly and easily as possible, especially at larger companies? React or Angular (You're a cog in the machine, but cogs often get better paychecks to deal with multi-megabyte code blobs.)

Can't decide between code elegance/performance and finding a job, so you're willing to compromise a little on both? Vue
I wonder how much of this is because the software talent which joins TeamViewer or LastPass is of really poor quality.

I mean, is there any good engineer who actually wants to work for these companies?
Having a 1:1 with everyone on your team when you start works better. Admittedly, few teams take the time to do that. But doing so sets up a remote culture where people will talk to each other outside of scheduled calls. Because remote daily syncs often generate thoughts of, "Nah, I won't communicate now... I'll wait for the call". And that both slows down communications and bogs down the daily calls.

So I'll stand by the statement that if daily sync is your solution, you are missing part of the puzzle.
the best I've seen is just treating them as roughly day-equivalents.

the problem with pointing is that a lot of tickets are really really trivial and the main expenditure is attention, not effort. and on the other hand, the cards that are big enough to warrant measurement are often chuck full of unknown unknowns.
Sadly, we didn't end up implementing it ourselves. Release notes were a "nice to have" so it became one of those things that gets kicked down the road.

The primary advantage of the ticket-based approach is that it's much easier to involve non-dev stakeholders. I'd choose it whenever other people might want input in the process. Most ticketing systems also offer a lot of flexibility, you could incorporate the ticket name, group tickets by relation, block completion states, act on deployments, etc. The ability to edit the note without rebasing is a major bonus as well.

The git-based approach potentially leads to a more readable commit history, and strongly associates any release notes with the actual code change. On the other hand, it's a pain to edit and can distract devs while they're problem solving if not setup well.
Brimar thermionic products great British valve project
What I learned from sharing my private self with an AI journal
What is the significance of this
I bet they’re carbon fiber now.
> Pound for pound, the Sacklers probably did more damage to America than any other drug dealers in history.

That's complete horseshit. They produced a drug of known, unvarying dosage in regulated pharmaceutical manufacturing plants, overseen by pharmaceutical engineers making sure that no illegal or unsafe substances adulterated the final product.

For once, there was a drug on the street that wouldn't cause junkies to overdose. It wasn't hot with fentanyl half the time. Jackasses didn't cut it with baby formula or laxatives. Hell, it didn't even encourage druggies to reuse needles.

But if you need empirical evidence, drug overdose deaths only spike after the DEA cracks down on pill mills. They demonstrably saved lives. Any sane person who examines this at even a shallow level would concur. You've drank the kool-aid.
Java Mission Control [0] has a button to toggle for displaying the profile as thread roots or method roots for this purpose. I am not imaginative enough to come up with a visualization that shows both (maybe utilize background color or another indicator to show the leaf function's relative frequency in the other direction?). Either way, both directions have their use case when investigating.

[0] https://adoptium.net/jmc/
Even if the poachers can detect the contamination, they are probably going to kill the rhino, flee the area, and then assess the goods. So you still have a dead rhino unless the doping is well communicated and obvious to all.
I think this is a 9 year old snapshot of Bower
This court continues to make decisions that might be defensible if you were making them for the first time, but go against decades of precedent in which time many laws have been written on the assumption that things would work a certain way. For a group that claims to be holding to tradition they sure are willing to throw things into chaos.
Unless I am misunderstanding the article (or it is just not giving enough information), it isn't that Apple removed direct access to the hardware in watchos 5 but that they changed the algorithm.

It seems the previous algorithm gave more constant readings, but that is why I am curious more about why they made the change.

Given that as far as Apple is concerned, you still bought the Apple Watch. Regardless of wether the data is going to the heath app or another app, you still paid them money. Possibly even more money if that third party app is a subscription through the app store. There is no incentive for them to make this a worse situation for their users, quite the opposite actually.

So the reasoning for why Apple made this change is important.

As far as a developer having direct access to the sensors, that is a tricky situation. We can argue that for a heart monitor it is a good idea but I don't think every app needs access to every sensor for privacy reasons.
I’m not saying that’s wrong, and that discussion happens elsewhere too. My main issue (also brought up by other commenters) is that this strategy can only work when there are relative disparities in wealth. When you say "expansion in poverty" I'm assuming you mean it attracts the poor to the city (ie moves them), and not that it actually creates more poor individuals. (If that's an incorrect interpretation, please correct me). If that's true, every city cannot “divest in poverty” because it’s just moving problem rather than fixing it. It’s a shortsighted, hyper-localized, and some would say selfish strategy because it pushes the problem somewhere else to be fixed.

We’ve all probably worked on teams where a member wasn’t pulling their weight to solve problems. At the myopic individual level, that’s a great strategy because it maximizes their rewards while minimizing their cost. But that can’t be applied globally because at some point someone in the team has to actually start solving problems. We can’t all be the team free loader and a lot of social structures and game theory is about avoiding the tipping point where there are too many free loaders and not enough people solving problems.

It would be like a city having a lot of veterans returning from war and struggling to transition to civilian life. IMO, the solution shouldn't be "remove all veterans services and make it harder for veterans to live here so they take their problems elsewhere." Superficially, and locally, that "solves" the veteran problem, but globally it probably makes things worse. That's not really the type of society I would advocate for.

All I’m saying is I prefer politicians and policies that focus on actually solving root problems. There are many people who are quite fine ignoring those problems as long as it doesn’t affect them, and their policies reflect that. They’re just not the horse that I want to back with my vote, even if it would be materially better for me.
That's just not true. No turbulence is better than turbulence.

That said, experiencing light chop on a modern large airplane presents no danger to the airframe or properly secured passengers. You really should be strapped in, though, especially if you're on a small plane. Wake turbulence, for example, actually does present a significant risk to smaller aircraft.