skysight-inc/HackerNews huggingface dataset:
But then "When announcing in layer2 mode, one node in your cluster will attract traffic for the service IP."

This bottlenecking seems undesirable. At the very least, if you have one "main" traffic heavy service whichever node ends up servicing that IP address could have elevated cpu usage from processing all the network traffic via kube-proxy.

The obvious solution would be to allocate say 2 or more so ip addresses for the service with dns round robin set up. Then as long as all three are being handled by different nodes you are not bottlenecking nearly as badly. But perhaps I am missing it, but I'm not seeing a feature where you can force those two or more ip addresses to be claimed by different nodes. (If the feature is strict, then you would want more data plane nodes than IPs, so that having one node down will result in having part of the Round robin DNS unclaimed by any node).
There's also the DJ-3 Universal Drilling Jig from Bridge City Toolworks:

https://bridgecitytools.com/products/dj-3-universal-drilling...

(that coupled w/ a Mafell drill and jigsaw, a Jointmaker Pro v2, and a shooting plane and board are my last hand tool purchases until I have a dedicate shop and a nice bandsaw for resawing)
Oh really? Now you invite researchers instead of shutting down legitimate projects to investigate your algorithms?
The best way I've found to introduce junior developers to code reviews is to pair on it. Just go side-by-side down the diff and hop into an editor when necessary. It also helps teach a developer how to review code and what to look for--which has knock-on benefits of its own.
I'm sure the creditors will happily accept payment in Bitcoin in lieu of cash. it's dIgItAL gOlD except the digital gold can be copied and pasted to make a new kind of digital gold that is identical to the other gold, completely unlike actual physical gold.
We're already closer to idiocracy than I thought possible before the last decade, so I'm good without an OwMyBallsCoin
You have a solid point, but I wasn't talking abut summarizing or excerpt from a press release (those are anyway handed as press-kits before with all NDA agreements and so on).

Real human journalists have a delay of about 1m before making a short tweet. Funny (or not), something similar was in the "live update" article page in less than 10s. Including photo(s). I was on quite a lot of tech-conferences/live events and earned a decent living then as an independent tech journalist (but then I got bored and really it was a 1-man-show).

Another personal observation (from field), that was not happening prior to 2010-2012, the years we all got Siri, Cortana..

You can make the dots and dashes.
>>that's accelerant but not the fuel.

Yes, indeed! Which is why I'm having so much trouble with ppl proposing technological solutions - technically it might solve the problem in some situations, but the bigger problem is indeed some combination of general confusion, highly adversarial information environment laden with disinformation, and people's all-too-frequent love of confirmation bias and willingly believing BS and overlooking warning signs.

I hope we can sort it...
My suggestion would be typical: concise, professional, and when straight-forward, specific. The key is to remember that the nature of a code review is first to improve product, and perhaps secondarily to improve process (ops or procedure) and perhaps thirdly, people improvement in the form of collective learning.

Thus, if we're talking about refactoring a line-of-code then just writing the refactored line-of-code is probably the most clear and concise. If it's more involved than that, then it may be worth taking offline. In the example you've provided here, I'd suggest the best language is likely: Refactoring this block as a separate function provides the following benefits: 1. blah, 2. blah blah, and 3. blah blah blah and no side effects. The only additional clarity that's helpful is to say whether it's optional, required, or some other directive.
I think the issue could be volume (and also that the vast majority of humans aren't actively exercising their ability to write fake news at present). Also that language models might be far more convincing.
Show HN:  [NSFW] Diffusion models for porn generation
Apple has monopoly power, and engages in anticompetitive behavior.

Being a monopoly in the US is not illegal. Abusing your market power and being anti-competitive in a way that harms consumers is illegal.

Apple is one of the world's largest companies. They shouldn't get a pass to be anti-consumer just because they don't own 51% of a certain market.

I would argue that "iphone users" instead of broadly "cellphone users" is its own market, but that is really besides the point. A monopoly in the academic sense is not needed for monopoly power to exist.
I worry about these sorts of conditions being applied to computer programmers
Atari Turns 50
I agree in general, though I find the second on clinging to code difficult when people counter with timelines. It can be difficult to express to juniors how to reason about taking a bit more time to do it "right".
There is a recent movie called Dream Horse based on true story: "Twenty years ago, one woman convinced her neighbours to buy, rear and train a thoroughbred racehorse, Dream Alliance. Now their unlikely story is relived in a feelgood film"

https://www.theguardian.com/film/2021/may/30/against-all-odd...
Making an application where you have full control over what's going on is never going to be simple.

But at least when doing desktop/mobile dev you typically have a framework that leverages a lot of stuff for you. This framework is totally absent when doing SPA today.
I dunno, we seem to issue fines a lot nowadays and the behavior doesn't change.

What even would the the expected value for a fine in this situation? It seems overly complex to calculate as I don't think even the FTC tried to put a value of the damages from the sale of the person information.
Looks like the author has settled that issue once and for all.
There's a lot of tension between an economic environment that rewards high levels of mobility, and desire to live near/in a strong local web of friends and relatives who can help support you.
> But requiring 2FA tokens is not a universal practice.

It is not universal practice, but it is industry-standard, so I don't particularly understand why it is surprising that the FTC is recommending that CafePress adhere to industry standards.
Best case scenario, they get some good word of mouth... which doesn't matter as FAANGs have more applicants than roles anyway. Worst case scenario they have an angry rejected candidate attempting to dispute the feedback. I doubt any large tech company would consider doing this.
So I went away for the week-end, and my bot decided to watch porn for 48 hours.

Here are the results.

The models have been kept small for the time being, but it's based on diffusion models, the same technology that Dall-E and image-gen use,
so the current low-quality of pictures is mostly a scale issue.

I have generated ~1500 images and ~500 "videos", so server costs are minimal.
Further work will aim to allow user to generate videos from a text prompt, or from a picture.

Feel free to share the pictures on various social networks if you'd like to tickle their nude-content classifiers.
I though the bottom part of your page was an image, but it's live demo. Perhaps add some text explaining that I can try it.
It's interesting that the pendulum has swung, and yet it's still mainly impacting the same group of people.
>you are not entitled to a high-earning FAANG job. It's really that simple.

He's not talking about FAANG jobs. He's talking about Joe Blow companies that pays "market rates," and "great benefits!" to code really boring stuff with no highlights on the resume.

He said these companies are too lazy to research any references and are just copy/pasta leetcode tests to their interviewees; tests the hiring people probably can't even validate as correct without an answer key.
I think one of many issues with the car windshield observation is we don't have a good baseline. So we notice that in 1990 there were more bugs on our windshields compared to 2020 after a drive through Kansas. But maybe 2020's insect levels are actually a return to normal, preindustrial levels after an anomalous century of high bug populations? We don't have a bug windshield strike stats from 1890.

Honestly it's such a dirty metric with so many compounding variables I'm shocked that anybody is seriously considering it as a meaningful data point beyond the most basic, surface-level understanding of the issue. To be honest the whole thing reeks of the usual hacker-news crowd issue where people want to pretend they know about a topic (e.g. systemic issues in pollinator/agricultural pest population management in high-intensity modern industrial agriculture) but are underestimating the complexity of the issues by a huge magnitude.
Its one of the biggest features of GitHub, exposure.
When doing fancy things with typescript types, be really careful - it's possible to accidentally construct typescript types that will increase your tsc compile times by multiple seconds and the tooling for troubleshooting this is nonexistent. A tiny change to one codebase I work on made compile times go from 300ms to something like 7 seconds and it took me something like 14 hours of grepping and manually bisecting source code to find the cause - tsc was O(N * N * N) trying all possible types for a string literal to determine whether any of them were valid matches, and someone had defined a very fancy string literal type.

When this happens, typescript language integration (like in vs code or sublime text) will suddenly fall over and stop working correctly, and it'll be near impossible to figure that out too.

Our build uses rollup to invoke tsc and as it happens their profiling system doesn't actually measure how long tsc takes to run - the time is unaccounted :) So in general, be aware that 'typescript is taking a long time to compile' is a blind spot for this whole ecosystem and if you hit it you're going to have to work hard to fix it.
Most of the tech world is 2 though. Our entire category lives because management is too dumb or power hungry to realise that.

Sure, you probably shouldn't outsource to the cheapest places who barely speak English (eg. India, South East Asia, Russia, Eastern Europe), you'll have tons of communication problems.

If you outsource from the States to the UK or Western Europe (and test the language knowledge in advance) you'll save tons of money and get engineers who can communicate with you.

If the language is not a problem (eg. your staff speaks the language of the subcontractor) I've seen amazing deals work out without a hitch; eg. Russian founders hiring engineers for hundreds per month in Russia, Indian founders hiring cheap resources in India.

Outsourcing didn't work out 20 years ago because we didn't have tools to work remotely effectively (zoom scalable video codec and better broadband have been a game changer) and because people went to the cheapest countries.

There is a middle ground of productive engineers living far away, happy to earn less and who don't want to live among the homeless in an expensive SF flat.
I'd love an economic system that championed efficiency over growth.
We discussing safety, or track laid?
Sorry, I'm not following what you're hinting at. Can you explain?

If I had to speculate why Apple wouldn't bundle a unencumbered and popular codec, my first guess would be concerns over power efficiency. But I don't know codecs, and your comment reads like you have more specific insight.
I am not really comfortable doing that. Others may have a different experience than me. You never know which team / hr person you are going to interact with.
>I think it's also a major waste of time to complain about it.

Why's that? People are obviously taking time out of their day to read the complaint, and a non-zero amount of those people may be in a position to enact some small changes.

>Let me put it this way - you are not entitled to a high-earning FAANG job.

Not once reading this entire thing did I feel like the author felt entitled to a high-earning FAANG job. They actually make it pretty explicitly clear that they are talking about non-FAANG companies employing FAANG-style (or, what those non-FAANG companies think is FAANG-style) interviews. And it's still pretty clear, to me at least, that the author doesn't feel entitled to those jobs either.

>You feel like it's a waste of time to learn Leetcode questions? Then don't do it. Case closed.

That's... That's what they did. And they wrote about it.
This fascinating article [1] on the history of SMB hacking in Japan gives some more details on Minus World-like worlds and how they could be manipulated by "hot swapping" Famicom cartridges.

"Players quickly figured out that it was possible to access levels beyond 8-4 by hot-swapping cartridges.

What is positively known is that in 1986 a magazine called “FC Bug Boy Special: Super Mario 256W ” was released by JICC Publishing Office in Japan.3 This magazine detailed how to access worlds beyond 8-4 with the hot-swap method.4 It also included data tables and information about these mysterious levels.5 This publication most likely helped information about “256-World” spread through the budding player/hacking community."

This ultimately led to the release of the Tonkachi Editor, sort of like a primitive Game Genie where you could laboriously modify memory to more precisely hack together your own levels.

"It was a binary editor, but far from the sophisticated software available on today’s computers, it was light and simple at best, and could only patch data displayed in hexadecimal or ASCII code, not move or copy data. Since there was no environment, of course, no printout was possible. Moreover, due to the nature of quick disks, subsequent files could easily be destroyed if they were rewritten on a different drive or other device, and recovering them required a great deal of effort. In fact, even now that I am accustomed to using a Tonkachi, a task that can be done in a few minutes on a PC can take up to an hour or two on the NES if you use a Tonkachi."

This ultimately resulted in a ROM Hack version of SMB called Tonkachi Mario released all the way back in 1987, at least a decade before I'd have assumed such hacks were being released.

[1] https://glitchcat7.com/the-complete-history-of-kaizo-mario/
Hill Climbing is a fantastically old competition. The heritage extends well beyond the vehicles. The culture of everyone from The Scrutineers to the burger vans is well worth looking into, if you can.

An example, continuously running since pre-quake SF:

https://en.wikipedia.org/wiki/Shelsley_Walsh_Speed_Hill_Clim...
It's definitely possible, and can make a lot of sense -- MyRocks/RocksDB for MySQL seems like an interesting and well designed system to me. It is fairly natural to compare MyRocks to InnoDB, since they're both MySQL storage engines. That kind of comparison is usually far more useful than an abstract comparison that ignores the practicalities of concurrency control and recovery.

The fact that MyRocks doesn't use B+Trees seems like half the story. Less than half, even. The really important difference between MyRocks and InnoDB is that MyRocks uses log-structured storage (one LSM tree for everything), while InnoDB uses a traditional write-ahead log with checkpoints, and with logical UNDO. There are multiple dimensions to optimize here, not just a single dimension. Focusing only on time/speed is much too reductive. In fact, Facebook themselves have said that they didn't set out to improve performance as such by adopting MyRocks. The actual goal was price/performance, particularly better write amplification and space amplification.
Evolved as in the true meaning of the term - Darwinian evolution. Homo Sapiens have live and grow and die in extended kinship groups, this has been the case for 99.9% of the time we have been around - and if we go further back to pre-human times, we likely lived in those kinship groups too. We only collapsed this structure since industrialisation / urbanisation - last hundred, maybe two hundred years
Kind of an extension of this is that Facebook isn't looking for qualified developers. They're looking for qualified developers who will bend over backward to make a pile of money.

And many non-Facebook employers are looking for qualified developers who will bend over backward to make a much smaller pile of money. They might be making a bad decision, but it's their bad decision to make.
Here is the original ending (movie spoilers):

https://en.wikipedia.org/wiki/All_You_Need_Is_Kill
I keep hearing people say this, but it's not my experience at all. I have no idea what kind of web sites they're visiting.
$150 does seem very steep… given these numbers, I would feel a lot better simply buying films to donate to my library.
What are you talking about? Every web server will both compress and encrypt responses when using HTTPS.
>benefit of the doubt

Ah, he was making a joke about a typo you made. Not an attack.
dahfizz is comparing Apple’s (allegedly) anti-competitive behavior to Microsoft’s anti-trust violations, drawing a false equivalency between to two (possibly by misunderstanding the difference). I’m clarifying the difference. Being anti-competitive is not a crime unless one is doing it as a monopoly.

It doesn’t matter if Apple is a “rich market leader”. 57% does not make them a monopoly, and therefor the legal level of criminal anti-competitive behavior doesn’t apply.
There are at least two that I've seen in the bay area, so it checks out.
As gas prices surge, stations now hold up to $175 of your money when you swipe
Yeah, that was gonna be my contrarian HN hot-take too. Basically if it becomes really obvious some day that basically all online news publication is noise written by computers, maybe people will stop actually trusting it so much?
Alternative hypothesis for which I have at least as much evidence:

Because of large language models, detecting Fake News becomes trivial and cheap. Building and doing inference on language models is too expensive for most attackers, so they give up. Only well financed state actors are capable of disseminating fake news, and they are no better at it than they are today because content generation is not a bottleneck.
Fake news.

Reptiles do not need another reptile's blood
> "Why did you do it this way?"

While the question is literally (and without any other thought) what I have sometimes in mind, usually I ask something like:

I feel I might be missing some insight or context, could you walk me through your rationale?

Because if I don't get some code change I may very well be missing something. And in any case by talking we're only going to improve our mutual understanding, both of the codebase and of each other's thought process.
https://archive.ph/OC2Tl
> No, I do not know why every single ICELAKE processor is commented as Sunny Cove.

Wikipedia can clarify that for you:

> Ice Lake is Intel's codename for the 10th generation Intel Core mobile and 3rd generation Xeon Scalable server processors based on the Sunny Cove microarchitecture

https://en.wikipedia.org/wiki/Ice_Lake_(microprocessor)
> I think the central idea ... is a pretty useful thing.

What's the best use case that you care to name?

> It also happens to be rife with scams, mania, wildly non-useful projects, and all the rest. Just because it has terrible parts

This is the argument that "sure, 98% of it is crap, but there's good too".

Or put differently: "I've seen 98 scams in a row, so this increases the odds that the next ones that I see won't be a scam!" It's a conclusion in search of a justification.
> There are plenty of ad blockers for Safari

And none of them work as well as uBlock Origin on Chrome.

Trust me, I tried. I even paid money to try a few extensions out on Safari in the hopes I would get a better experience, but even that doesn't work.
You seem to be saying that all originalism must be fake, a cover for political bias. You fell into the GP's third paragraph. Without ever even attempting to refute it, you just restated the position.

GP had a point. You didn't answer it at all.

Both GP and I assert that a principled originalism is possible, one that is not just a cover for political bias, and that such is superior to a super-legislature. Do you have any answer for our position? "These guys are using originalism as a cover for their bias" isn't an answer. (Unless you're asserting that a principled originalism is impossible - which you haven't stated, let alone supported.)
Of course interviewers are entitled to or able to do these kinds of interviews. That doesn't mean one can't complain about it, and thereby hope to shift attitudes to where they change what they do. There'd be little to talk about or do if we could never describe ways in which we want things to change. This person is themself entitled to complain, and yet here you are complaining about them complaining (which you are entitled to as well).
I view Google’s dominance in WC3 discussions and standards settings to be a far greater threat to innovation than Apple limiting browsers on its mobile platform.
Why would you assume people in a remote country will write worse software than you?

There is plenty of foreign talent.

Sure, companies are not great at picking outsourcing firms, I think corruption and/or picking your mate's consultancy firms plays a role in that.
As is WebP. But it did notably take a while.
Same... and I got scolded by an recruiter after she asked me more questions about my experience.

She basically told me I am underselling some of the experience, and I should put some of it more, and perk it up a bit. It was very helpful.

Engineers have that. You have to take example a bit from real estate agents, on how they describe a place. Always highlight the positives.
Here’s one update:

The horror is already starting. A nurse sent this message to a nurse on TikTok who has a large platform:

I don't have a platform so I can't reach people like you can, but please share this! I work in ** on a small niku/l&d floor. Our trigger laws went into effect immediately after the decision. ofc we had a woman walk in with an ectopic at 11:30pm last night. We had to basically sit on her until the doc could speak with a lawyer. Her ectopic RUPTURED. She then did not get her procedure done for another 9 hours because the doc was working with the lawyer for so long trying to work around the laws and not lose his license. By the time she had her procedure she had over 600cc of blood in her abdomen and she almost died. I am so scared of how often we as nurses are going to see things like this now and not be able to do a damn thing about it. We're all livid at huddle tonight, several of my coworkers were in tears.
I agree with the tone of your suggestions, but your suggestions still take quite some time to read. They can easily be shortened without losing any information. For example, no need to to apologize for being the process person (being overly apologetic decreases the value of apologies anyway).

Also for me it feels like you're seeing code reviews as a senior/junior thing. It's more than that, no?
Imagine playing sim city, except you don't get terrain shaping, bulldozer, or rezoning.