skysight-inc/HackerNews huggingface dataset:
"Frequency illusion, also known as the Baader–Meinhof phenomenon or frequency bias, is a cognitive bias in which, after noticing something for the first time, there is a tendency to notice it more often, leading someone to believe that it has a high frequency of occurrence" https://en.wikipedia.org/wiki/Frequency_illusion

I'm not saying that it's your case, but it could be :)
Of course you asked how to share links between devices without having a social account.

I just did trimete.com and I had a lot of fun.

Do you like it? A tone of things can be done here. Looking for a front end partner to team up on this.

Any thoughts and suggestions are welcome. I'm open to any technology.
Quest (YC S21) shuts down
"Doc > Test > Code" is something I can get behind :)
Mythbusters found that two cars colliding at 50mph is not equivalent to one car hitting a brick wall at 100mph. It resembles one car hitting a brick wall at 50mph.
The biggest difference is typically that unit tests don't require a test fixture of any kind, and are expected to run wherever the compiler runs. You typically expect a huge battery of unit tests to run in seconds, and they are normally expected to run before every commit, even for every build on a dev machine. A new contributor is expected to be able to do something close to "apt get langauge-toolchain && git clone $repo && make build && make unit" and see that all unit tests pass. However, they are also expected to sometimes miss obvious bugs, like "the queries we generate are not valid with the new MySQL flags we set". They often need to be changed even for refactorings, as they typically cover implementation details, not just the public API.

In contrast, integration tests typically require a test fixture of some kind and are thus expected to require more complex setup instructions, perhaps even access to shared resources (like a DB server with a large batch of test data that can't realistically be replicated, or a testing instance of a real microservice you integrate with). By virtue of often requiring IO (network operations, DB operations etc), they are often considerably slower, so that they become impractical to run at every build. The upside is that they catch errors that were not obvious from the code, and they usually give you a high degree of assurance that a user of your service will at least not encounter silly bugs. A break in the integration tests after a redactor is also often a potential sign you've broken backwards compatibility of your API.
Since we are finding that post facto, I really doubt it. It means their customers did not care about compliance.
Comparing my microscopic Keycloak installation to Okta, I'd rather be a needle than a haystack.
> In my book that counts as "obscurity". "We are not an attractive target, hence we won't be targeted". You will be targeted, as long as your defence is weak.

I find this point to require more subtlety; "we are not as much of an attractive target, so we likely won't be targeted by a sophisticated, human adversary" is more apt for the situation. The attack vector is just not comparable to Okta's scale, which is true for the majority of companies and platforms out there. That doesn't mean security should be taken lightly, just that the magnitude and frequency of bad things happening will be lower.

> Things like auth are not your core domain

That's a good point, but it depends on the situation. I wouldn't recommend spending lots of time on this yourself, but there are standard libraries or OSS solutions available. If you're optimising for reliability, it might be beneficial to keep auth within your own systems. If you're optimising for privacy under GDPR, for example, it might be beneficial to not trust your users' data to an external provider. And so on.
I imagine a microvia cut by laser would work quite nicely on three of those pins.

The fourth pin, Vcap, would be frustrating, because using two vias to place a capacitor on the opposite side of the IC is labor-intensive, and using two vias to place a capacitor beside the IC is a bit of an unnecessarily long signal path for a filtering component. I'd rather gouge a hole and solder a capacitor directly onto the IC between Vcc and Vcap, but "gouge a blind hole in the dielectric and solder an 01005 capacitor to the IC" is not a commercially viable answer either.

Maybe pray your design doesn't need Vcap or that this can be tied to GND?
I largely agree with the author. Even the quickest internet search is many orders of magnitude slower than recollection from memory. The analogy with retrieving from cache vs RAM / disk / network is probably well known. But we should not go overboard in either direction. Everyone's memory is limited, and there are appropriate uses for both calculations and lookup tables.

Quoth Sherlock Holmes:

"I consider that a man's brain originally is like a little empty attic, and you have to stock it with such furniture as you choose. A fool takes in all the lumber of every sort that he comes across, so that the knowledge which might be useful to him gets crowded out, or at best is jumbled up with a lot of other things, so that he has difficulty laying his hands upon it. Now the skillful workman is very careful indeed as to what he takes into his brain-attic. He will have nothing but the tools which may help him in doing his work, but of these he has a large assortment, and all in the most perfect order. It is a mistake to think that that little room has elastic walls and can distend to any extent. Depend upon it there comes a time when for every addition of knowledge you forget something that you knew before. It is of the highest importance, therefore, not to have useless facts elbowing out the useful ones."
Free expression and dialog is how we grow. Who would be against that?
It'd be interesting to see (and likely public interest) to have some good analysis done of Microsofts telemetry. eg anything untoward in there, apart from just the forced telemetry itself
You know those fancy electronic notebooks? They're barely better than actual notebooks. They all seek to emulate the pen and paper experience, they go to great expense and make it a focus of their advertising that they feel like real pen and paper. Why wouldn't I just use pen and paper?

I believe electronic notebooks haven't yet realized their greatest potential, spaced repetition. I want to take my notes in an electronic notebook, then review my notes and extract parts of them to become spaced repetition items. This is something I would happily have a dedicated device for, and would pay $1000+ for such a device, but they don't yet exist.

After taking notes, natural hand made notes, I imagine creating spaced repetition "flashcards" would work like so:

1. Review notes and draw a square around something I would like to memorize; perhaps a fact I have written, or a hand drawn chart or diagram. This square becomes a "flashcard".

2. Optionally, I may hide (by blurring, or pixelating, etc) part of the flashcard.

When the time came for study, these flashcards would be presented to me following a spaced repetition algorithm:

3. Present the flashcard, including all blurring and pixelation.

4. When ready, the user is shown the full unobscured flashcard. The user may also toggle the surrounding page the square was originally extracted from, this gives the user context.

5. The user can then judge how well they remember the flashcard. The user presses a button indicating how well they remembered the flashcard. This feedback goes back into the spaced repetition algorithm.

The important innovation here is that users can easily combine hand-written and hand-drawn notes and a spaced repetition algorithm. In Anki, you can import pictures, but this is burdensome. You can write markdown or LaTeX, but those suck compared to just drawing something by hand. Studies have shown that hand drawn notes aid in memorization. The would has never seen hand drawn notes easily combined with spaced repetition, and I believe it would be better than any other memorizing scheme we've yet encountered.
We can't repair our cars, we have no privacy in when and where do we drive and now we don't even drive them nor are responsible for them. Essentially the car manufacturer plays a role of a transportation service provider now.

Ok, I'm not insisting this is bad. But now what's the point of buying a car into your ownership instead of just calling it like a taxi when and where you need it?
Patent Trends Foretell Chipmakers’ Fortunes
Is Russia’s Largest Tech Company Too Big to Fail?
Excellent read. I agree with a lot (after only a cursory read). One thing the author seemingly forgives R by not mentioning is how harsh and discouraging of beginners the community was at some early stage. That was my experience around 2002-2006.
> I don't think it's that big of a deal but it's clearly well done from a PR/marketing standpoint.

If this is true why don't all of companies do it?
I don't think this is a fair representation - for example it makes Estonia and Kosovo stand out in the world as the worst offenders. However they have relatively tiny populations (1.3 million and 1.9 million respectively); the actual CO2 impact of them is miniscule in the world, even if per-capita CO2 seems high.
Last year's Nobel Prize in Economics went to researchers who showed, via natural experiments, that raising minimum wage does not decrease employment.

It's counter-intuitive, to be sure, and there are vested interests who want minimum wage to stay down or be removed, but "the facts" are there and observable in the real world.
"Check Okta logs for elevated privilege account activity."
Best advice I've read about this fiasco
Market Makers are basically the financial system's buffers: they exist to make sure that you can always buy or sell a given security/commodity. They are the people who make buying or selling something _immediately_ possible, rather than having to wait for someone who needs what you're selling (or is selling what you're buying) to come along.

This makes trades move quickly, which speeds up price discovery. This is good for market health.

Market makers make their money on the difference between the buy-sell spread. Of course, this is a bet: if the market moves against them, they can lose money on this. Often a market has one or more officially designated market makers who are paid to _always_ have a certain number of both buy and sell offers on the market to ensure that there is always liquidity. The payments help cover their risk

(These payments are often also materialized in the form of a "takers fee", i.e. a surcharge you pay whenever you place an order into the market which can be immediately filled)

TL;DR: They're a warehouse which will always buy and sell some product, except when talking futures we're talking wagons full of nickel 1 month from now and so the warehouse doesn't physically exist
yes my company makes us do the 2FA every 9 hours for github (so annoying) via okta, though apparently our gsuite logins via okta are much longer lived.

though that sort of answers a followup Q, it would seem that there would be a market that punts the authentication to gsuite's saml, but automates the user creation and the like on the different services (and deactivation), but one still wouldn't have the "custom flows" as you said.

but if the custom flows aren't that important, I'd rather trust google to handle my authentication than okta, and in my pseudo-okta without authentication scenario, even access to my pseudo-okta would authenticate via google.
I don't understand this sentiment.

It is an industrial site. Nobody got hurt. The fire didn't spread to other people's property. Why are you all so upset about this?
What do you mean? OVH has hugely improved their offerings in that time.

They introduced world class DDoS protection for all clients.

They massively improved their global connectivity, and continue to do so.

They’ve drastically improved their support, hiring much much more English speaking staff than they used to have.

Not to mention generally improved tooling offered to customers.
Most work is probably getting a domain with respective TLS certs. Otherwise there are many options. If you just need it for three days you might want to check AWS ECS. A bit more expensive perhaps, but quite easy configuration and they provide domain and certs within a few minutes from my experience and the price shouldn't matter too much for a few days.
For my use case, R is absolutely terrible compared to some for profit statistical package / language. Using R feel like using an outdated, complicated and messy tool.

But guess what: it's free.
Values with an intrinsic unit scale up to many units and values. If you declare the parameters of a "calculate" function as USACurrency, Weight and Duration you can write

calculate(100cent, 2Kg, 300s)
calculate(0.1dollar,4.7lb/*approximate*/,5min)
calculate(something.price(),whatever.weight(),options.getDuration("exampleTimeout"))
calculate(USD(0.1),Kg(2),Minute(5))
Several impressive gravity hills can be found inside a pub in the UK called The Crooked House. It's so wonky you can feel a little queasy if you stay in there a while!

https://en.wikipedia.org/wiki/The_Crooked_House
Works both ways. If you keep me in the office for a few extra minutes after quitting time I'm claiming an hour of overtime.
> But as soon as it's a non-trivial DB with constraints/referential integrity/triggers/etc

Which is probably a reason not to use them? For me it clearly is. Everything is a trade-off, and "not being able to test it" such a big downside that I'd rather not use it at all. Amongst all the other downsides that tight coupling comes with, for me, it almost always balances towards the "just avoid it".

For example: I've worked on projects that were highly coupled to Oracle and MySQL databases, where large pieces of businesslogic (arbitrarily) were scattered over the database. So when Oracle went directions (and for prices) that my customer could not warrant, and when MySQL simply no-longer could handle the performance, we had to rewrite a lot (in postgres, mostly). Often pieces from scratch entirely. One downside of tight coupling is "lock-in". There are many more. So in that project we avoided the same mistake that brought us there: we avoided most fancy features and kept all business logic in the business-logic-layer and out of the DB. We tucked away fancy PG features behind simple and clean "facade patterns".
The Church-Turing thesis was born after Kleene got dosed with laughing gas
This is not "a software vendor accepting responsibility for the software's actions" this is a car, placed between human, unpredictable, drivers operating 2 tonne machines. Far from Photoshop working on your PC or an embedded system for your fridge.
Plus: I never saw a drama series about it
Perhaps a previously un-noticed reason for Brooks' Law being true...
There are so many movies I haven't had a chance to watch in a cinema, I wish more theaters would play classics on their largest screens. I just found out that one of our local cinemas now has weekly 'classic sneaks'. Lucky me.
Yeah, it's not surpising at all that someone managed to build a business selling auth for less than hundreds of thousands of dollars a year.
The datacenter is about 100ft from the German border.
And what happens when the biggest nickel producer in the world needs to buy nickel from someone (non-existent) else? That's not about short squeeze, that's about the market almost ceasing to exist because market is far from perfect. The point here is: if they don't rollback, there is no money for the winner.

It's an interesting reading and I think you should read.
https://davidcard.berkeley.edu/papers.html#6

"Minimum Wages and Employment: A Case Study of the Fast Food Industry in New Jersey and Pennsylvania." (with Alan Krueger), American Economic Review 84, September 1994.
This is the kind of comment a very boring person would make
There's a monthly "who wants to be hired" thread first business day of the month collecting the offers https://news.ycombinator.com/submitted?id=whoishiring
For C, I've yet to see better code than ReactOS. Look at how they keep even monstrous functions readable: https://github.com/reactos/reactos/blob/3fa57b8ff7fcee47b8e2...

For C++, try Chromium: https://chromium.googlesource.com/chromium/chromium/+/refs/h...
This post is useless without naming the specific provider.
Don't worry, people on HN know what filthy beasts data analysts truly are.
Everyone who digs that type of mathematics, is also doing some other naughty things for fun.

What is surprising from this shotty paper is that they conclude boring people are perceived as "less competent".

Seems counter-intuitive, considering accounting and taxes.
We really should not consider linux phones (and desktops!) secure. It’s only secure by obscurity and by not being a valuable target at all — they have no sane sandboxing, hardware kill switches are pretty much useless in that if you can’t trust the OS you are already lost, etc.

GrapheneOS is a secure option as well as ios. But security doesn’t come for free and not a binary thing.
Very helpful stuff for a QA
AeroPress – Inventing the World’s Best Coffee Maker
Young people definitely make decisions about things based on perceived social appeal. It's kind of a thing.
this comes immediately to mind http://arrgh.tim-smith.us/
I don't think circuit breakers should exist. And markets should operate 24/7. There is absolutely no good reason why they wouldn't in digital age. Players should not make bets where they can lose too much money.
Doesn't that depends on how well they separate access within the company? If they know that one of their support reps in Costa Rica was "turned", they might not have to declare anything in the EU if they can prove that the rep has zero access to EU customers.

Edit: to be clear, I don't know, it's a genuine question. Does "any breach" count?
How are they the model when France had green energy since the 90s? CO2 saved earlier is far more helpful.
“If the car crashes while Drive Pilot is operating, that's Mercedes' problem, not yours.”

As long-time grey-beard MB owner, and, honestly, it's not just them, the sheer amount of noise and distractions in modern cockpits is absurd now.

By this I mean, reversing sensors, slow-forward speed sensors, massive LCD screen (which may or may not be touchscreen) positioned at windscreen level, the right-hand "-ometer" that's configurable, a dial, a trackpad, a steering wheel with at least four buttons, and two 'joystick' things. And 3 instrument clusters on stalks. Heating buttons, fan, windscreen control, radio button, all down the bottom of the centre console where I have to take my eyes off the road.

It's a shit show.

My point? My current MB has never been so distracting to drive where I have to take my eyes off the road for a second to hit the demister button. Versus a car from the 1990s - no centre-LCD so the heater/demister buttons were in your peripheral vision. No touchscreen - regular buttons with tactile feed back that even had "braille like" raised paint so you could figure out where your hand was without taking your eye off the road. Don't even get me started on trying to use the radio or equaliser.

I hope, I really do, that autonomous driving works and reduces crashes, but I'm astonished there hasn't been a noticeable uptick in crashes based on just what I've written.

From the article, this is yet another button on the steering wheel. Probably because they've run out of dashboard space for all the other buttons. Auto-stop, car alarm off, assistance, sport mode, are at least 4 buttons I never use.

Where's the Jony Ive for car cockpits?
Have OLTP and want OLAP powered reports etc.? Just use estuary
They? I don't see OVH mentioned once at the above url. In fact, I see no provider mentioned.

Why wouldn't you mention them? Is it generic clickbait, and you don't want to get sued?
Prostitute...even I'm not sure whether this is a joke answer
I'm obviously missing some facts about the region, as per the OP's hypothesis, because a naive look at the map suggests that even without Crimea, Russia already has coastline onto the Black Sea between its borders with Ukraine and Georgia... there must be a strong reason in favour of invading another country rather than developing ports on the land they already have, if the goal is simply "control over the Black Sea and trade access to the Mediterranean Sea".
They're really not. It's a real person at Microsoft, and they don't know how to fix it.
Test-Driven Development by Example, Kent Beck.

If I could describe it in a sentence, it's for people who would procrastinate because they're not sure what to do next.

There's a lot of philosophical differences from "modern" TDD. It's not about test coverage. In fact, Kent doesn't encourage doing the obvious.

It's using the tests to reduce cognitive load. You think about how it actually works before writing code. If you get stuck, you can do something like write a constant in the code to make the test pass, then convert that constant into an expression. If you're still stuck, write some more tests, then triangulate those into an expression that passes the tests.

It turns anxiety from this anxiety inducing, 4-hour flow requirement, into this sudoku puzzle. If you like the flow sessions, by all means, go with that, but it's an extra tool for when you don't have the energy or blocks of time.
> how can such person be considered boring?

Have you met my constant companions, Dunning and Kruger?
Are there even any limited-access divided highways in California where speeds under 40 mph are safe? I'm not sure what they would have mapped.

As the default speed limit for such a highway would presumably be 65 mph (and traffic usually much faster), anywhere with such lowered speeds would presumably have special circumstances that would probably make it unsuitable.

The guaranteed 10 second handoff is impressive, however.
I lost a child 8 years ago. You will never be the same, you will never forget, you will never stop hurting. But it does become bearable. I cried my eyes out on the way to work and the way home every day for 6 months, but that let me get through the work day without crying. The thing you have to focus on is that nothing brings your child back, there is no way to fix things. You can only fix yourself and support your family and help everyone around you heal.

I took a couple of days off after the funereal and went back to work. My wife took a month off and after a couple of years she now says that was a mistake. Wallowing in your misery destroys you, and can destroy your family. I may sound harsh but you have to take care of yourself and your family first. Go back to work. The distraction of work gives you a break from the grief and you are providing for your family. It took me 6 months before I had a day I didn't cry, then another 6 to get to a day where I realized I was going to be ok.

As far as the settlement with the company, I think that is where you might be getting hung up. Get a lawyer or settle, either way the pain does not go away. Just choose a path and stay on it so you are moving forward. Make the decision to not regret whichever path you take. You cannot let this destroy your family or your life.
Starring your repo does not give you permission to spam me
Here's another relevant saying: "those with glass ceilings shouldn't throw stones"

We do exchange "freedom" (whatever vague definition of it) for security and convenience a lot. Even without realizing it.
So basically, my takeaway is:

* Freeflowing air in DCs is good for cooling(
* It’s bad when you have a fire;

* An improved DC design would allow an operator to $somehow stop the freeflowing air (although one could argue that it’s not free flowing anymore if one can control it);

* I’d like to know how much money really was saved by not allowing the UPSes to be cut off.

I’m very curious how the insurance companies respond, and whether they’ll demand e.g. UPS supplies to be able to cut off. Or maybe in general, the fire department should be more aware of these types of trade-offs being made, and give their approval accordingly.