skysight-inc/HackerNews huggingface dataset:
Ok so its just overcomplicated for woke reasons.

Having a lingua franca for computing is a good thing. All these efforts to localize computing are nothing but a giant waste of time.
The question is more like is it possible to get a job at a Maccas in Chicago after being fired from one in NYC.

But I think a good question to ask is - is it possible to get short order cook work anywhere in the US after being fired from McDonalds. Might depend on the reason but, most likely ... yes.
The main problem wasn't the duplication, it's modifying someone else's code without letting them review the change.
Dessa geografiska områden definieras inte av "80% nånting", utan är belagda begrepp som använts under längre tid, inkl inom statistik.

https://sv.wikipedia.org/wiki/S%C3%B6dra_Sverige

https://sv.wikipedia.org/wiki/Sydsverige

Ingen av dessa geografiska områden inkluderar Stockholm. Sluta använda ChatGPT som källa, det får dig bara att framstå som korkad.
There's like five trilogies in the same world, well worth reading the whole thing. The first is probably the worst in terms of what the characters go through, but the really nice part is how later books build on what happened here.
There are systems like MIT's Alpenhorn and Vuvuzela that protect metadata like push notifications by using encryption and deliberately adding noise to foil traffic analysis. Notably both sender and receiver are kept private and you do not need an out-of-band key exchange mechanism to initiate communications for the first time.
Ask HN: How to stick one project only so you can finish it
Tell me your hack to do it.
Chromatic Integration for Cypress
First peek at the Chromatic visual testing plugin for Cypress! Setup only takes 2 small changes, and it gives you snapshots with the full DOM + styling and assets for every test. You can try it now in early access.
DevOps/Agile always has a serious set of sustainability trade-offs, but in the beginning tends to show relatively quick progress. A great model for service companies billing by the hour for a limited scope product-iteration lifecycle, but a poor choice for building reusable infrastructure assets. =)

If you are good... than you will automatically leave a trail of commented stubs, design pattern templates, and working examples.... that set a project trajectory implicitly. Thus, avoiding having to explain choices to people that can't or won't understand (good frameworks can help in extreme cases of stupid).

People often entrench themselves in bad ideas/habits. Training peers can be challenging, as sometimes one must subtly repeat the same evidenced concept everyday in a different way for a month till a core simple concept registers (Neurodivergent managers can communicate in this manner even over trivial choices.) Being a good communicator is important when a problem domain shifts into the theoretical (i.e. 0 search results for the Jr.), and learning not to sound disrespectful/irritating takes practice.

At some point, a team needs to cut their losses, and confine the weak/obstinate members to an area that matches their skill/will level. This is often the first step in getting laggards to quit on their own, or making due with HR biases.

Good luck, =)
> Use a phone as a phone, not as your universal computing interface

Sounds limiting. Nowadays there are plenty of phones that can handle reasonable workloads at a reasonable price. Especially if you don't care about the camera.
I'm sorry? I also disagree with the authors conclusion but the article is definitely giving me less "jerk vibes" than this reply.

The lesson learned in the article should be "talk to your co-worker on why they solved a problem a different way". It should be about communication, which this reply does not shine in either.
>The fact is, most security teams, even the very large ones, are not especially concerned about operational security for inbound vulnerability reports.

This never made sense to me, can anyone explain?
This blog provides a fantastic overview of Tidb's impressive zero-downtime approach to Kubernetes node upgrades, showcasing a seamless transition with minimal disruption. Consider combining Tidb's zero-downtime upgrades with Incident Management platform to fortify your infrastructure for a responsive future.
LibrePGP – Fork of OpenPGP
The pushing services must be running in the background constantly to provide the push notification services. This is how apps can receive notifications without even running it.

If every app uses its own push notification services, an average consumer may end up with half dozens of those notification agents running consuming more RAM and battery life. For Android devices this might be OK (8-16GB RAM nowadays) but for Apple, this may not even be possible for its RAM size (<=8GB).
For me it is a combination of the search results being of equal or slightly better quality combined with all the nice little touches (Lens, auto redirect, etc). I am trying to banish ads in general and Google specifically from my life so I am also a little biased.

Last 2 months I used around 500 searches each month. So, the unlimited pricing is good for me.
The average human is not trained to be smart. They are trained to earn money, provide for family and navigate social situations.
Perhaps this is not meant for me. I use gpt-4-turbo frequently, which costs only $5 per month. For the same price, if I were to purchase from Kagi, I would need to limit my quota, like using a different search engine for unit conversion or obtaining a simple Raspi pinout. Why design a product that encourages users to use it less? In my opinion, a $5 with limited searches doesn't justify the cost.
Which solves about zero problems and creates many. Let's stop this woke nonsense and instead focus on improving english speaking ability of the world. Having a common language everyone understands only has benefits.
One commit per day minimum. That's basically it. Stick to it, and get back into it quickly if you break a streak. Six years and counting here.
Since there are a lot of "replies to the author" in here: The article is from 2020.
> I am an African. And I live in a country where such laws targeting LGBTQ has been enacted. FYI, Most people here have no idea what LGBTQ means and those who do don't give a damn.

Counterpoint (quotes from Wikipedia about Tanzania, where the conference was held):

> 95 percent of Tanzanian residents believed that homosexuality is a way of life that society should not accept [2007 survey]

> same-sex sexual acts (even in private and consensual) are criminal offences, punishable with life imprisonment

> On June 19, [2013] Human Rights Watch and the Wake Up and Step Forward Coalition released a report including several detailed allegations of torture and abuse of lesbian, gay, bisexual, and transgender (LGBT) individuals while in police custody.

> In 2018, a so-called "witch hunt" was declared against gay people in Dar es Salaam, where gay men were forced to endure anal examinations and torture.
> Morgan Stanley even released an investor note, valuing the Dojo business at 500B $ (it's not a joke, yes, 500B $).

... What on earth was that analyst on? Like, that's just nonsensical; did they give any _reasoning_ for this? One wonders what their valuation for EuroHPC or the US National Laboratory system would be; presumably trillions.
Chromecast with Google TV (1080P) Secure-Boot Bypass
>When I've found security vulnerabilities in somebody's code, I can't think of a time I ever thought about GPG-signing my notice to them.

It's not authenticity that matters here, it's confidentiality.
Exactly, it reminds me of this:

"Drift to low performance is a gradual process. If the system state plunged quickly, there would be an agitated corrective process. But if it drifts down slowly enough to erase the memory of (or belief in) how much better things used to be, everyone is lulled into lower and lower expectations, lower effort, lower performance."

-- From the book "Thinking in Systems".
It depends solely on company/team culture.

If people are churning after like 1-2 years, they never get to experience the long term pain themselves, and new hires will lobby for rewrites anyways. Since individual apps are rather small, rewrites service-by-service should be straightforward and manageable.

Ancient knowledge would be helpful here, but most teams simply don’t have „real“ seniors around. Therefore simple advice from my end:

1. keep the database stupid and sane. Postgres usually has everything needed for nearly every usecase in a good enough and battleground way. Don’t overdo complex join queries in hot code paths.

2. use a mature, slow-changing (as in: no breaking changes yearly) tech stack, that is powerful out of the box. When you need to use several infrastructure crudges, the tech isn’t powerful enough. I recommend Elixir, Go or even JVM-flavors, these will carry you far.

3. Monolith it is, fullstack. Every service/frontend you split apart might become easier in isolation, but you pile up significant overhead and complexity in terms of global monitoring/orchestration/dependencies/testability/debugging. Elixir/Phoenix, PHP/Laravel, … are fine choices that also have straightforward scaling options and cover everything you need probably.

4. minimize/eliminate usage of JS wherever possible. Aside from infrastructure providers/external APIs, this is the biggest source of maintenance issues. Also SPAs are rarely worth it, there still is a boring way of progressive enhancement that just works.
Just remove notifications entirely, they're just noise.
Space is at a premium on mobile and water ingress is a problem, there's no licensing fees to use such a jack and the part itself is absolute peanuts to buy. The real estate they gained by getting rid of the part eventually got filled by something that's almost certainly more expensive.

You don't have to overthink, you just need to think. Why permanently graft a part to a highly space optimized device when it isn't even being used most of the time?

I got over it, you should too. It helps to try to put off the onset of grumpy old man syndrome as long as possible.
The only clear citation of this definition of "sympathy strikes" is... the current Tesla issue :)
I doubt Microsoft would give such a project the passion it deserves in terms of optimization and support of new and future formats. I think this is better left for a third party like ImageSharp, Magick.NET, or libvips with the .NET bindings.
I've seen a few of these online, this seems to be the most comprehensive out there.

A couple of questions:
- How did you build the model to ensure accurate summaries?
- How did you build the audio version?
- What's your tech stack?
Yep, it is. Super happy with it. I added some custom themes and links to my second brain, but other than that, all mdBook. I also have more notes about writing a book with Markdown and self-publish at https://www.ssp.sh/brain/create-a-book-on-markdown/.
I'm also not sure I quite get the love. I got the free trial, and I've set it as my browser's default search engine for now to get used to using it. The problem for me is that it's at best equivalent to, and at worst a lot poorer than the same search in Google. Which is a shame, because I've been finding Google less and less useful recently.

Maybe I need to fiddle around with the settings more, get some better filters in there. But part of the advantage of Google is not needing to fiddle - it knows that I probably want programming results if I search for "rust" and things like that. I'll stick Kagi out a bit longer, because I really like the idea of it, but I've been fairly disappointed so far.

EDIT: one specific criticism is that I speak English but live in Germany, so I typically want English-language results except around German-specific things where I want local results more. Setting my location to Germany results in a lot of German results for unrelated searches (e.g. documentation for some library, or information about an actor), but setting it to "international" makes it harder to find the local results I'm often looking for (e.g. libraries in my local area). Google isn't great at this either, but it gets it right a lot more often.
Damn thats smart!
This IS the actual lesson they want to convey. "Use <tool> but don't overdo it and attempt to use <tool> everywhere."

It's just a bad mix with the clickbait title, a story that has a different root cause and a somewhat obscurely written conclusion.
The real problem here was the overall software architecture and development workflow that apparently wasn't geared towards building 2.0-alpha versions of a component while still keeping the 1.0 version untouched.
How very odd. The events of recent years, IMHO, make this _more_ plausible not less.

I think you are referring to LLM bots, the so-called "AI" tools that are everywhere now? Because ISTM that these are manifestly _not_ intelligent, and their main function has been to illustrate, both literally and metaphorically, that most humans lack the critical facilities needed to discern superficially-plausible nonsense from actual intelligent output from intelligent beings.
'How I Bankrupted Twitter' – Elon Musk [video]
Does anyone know where a civilian (me) could access a pdf?
>We have far superior communication channels that are secure, easy and private today (Signal, Matrix, WhatsApp, iMessage)

These are valuable tools, but they aren't usable on the command line the way gpg is. Signal doesn't help me sign an update to my software package.

Also I think the web of trust is a pretty cool concept, in theory at least. I don't know if anything outside GPG supports it.
> To reduce banding, the idea is that for each pixel, you choose between the rounded up or rounded down value semi-randomly, with a probability depending on how close you are to each value.

This oversimplifies it a bit. Most dithering algorithms are deterministic. They are based on choosing a value for a pixel, remembering the difference between the ideal and the chosen value and then spreading out that difference to surrounding pixels.

Random dithering is more commonly used in audio signals, AFAIK, not much in image processing.
Diet doesn't do much if you have bad genetics, I eat and brush the same as my gf, we don't smoke/drink, exercise the same, we basically have the same exact lifestyle. She has teeth issues multiple times a year, I never had a single problem
Invoice Buddy – One API to send bills
Found something helpful to send invoices from the backend. Give them a vote on product hunt so I can stop manually making bill.com invoices. https://www.producthunt.com/posts/invoice-buddy
Kubectl Powered by GPT
ooh this is cool. Is there any support for gradients of these? I guess maybe you could do some mask thing for opacity. But it would be cool if we could vary the fractal noise frequency
Advanced languages can compile quickly - it depends on the feature set chosen. For example, do-notation is an advanced feature not found in most languages, but it compiles quickly as it is syntactic sugar. Operator overload, on the other hand, might require a solver and thus compile slower. It's not a particularly advanced feature, however. Binary optimization passes do not make the language any more advanced (on the user side), but will slow down compilation. Advanced design and compile-times are pretty orthogonal.

As for maintainability, it's not clear to me that reams of imperative code is easier to maintain than something terse and declarative. In fact, probably the opposite.
I don't see how that's a fair characterization of a book that has this quote in the first chapter:

> Many of the recommendations in this book are controversial. You will probably not agree with all of them. You might violently disagree with some of them. That’s fine. We can’t claim final authority. On the other hand, the recommendations in this book are things that we have thought long and hard about. We have learned them through decades of experience and repeated trial and error. So whether you agree or disagree, it would be a shame if you did not see, and respect, our point of view.

It's been a while since I've read Clean Code, but I seem to recall it stated many times that blindly applying the rules of Clean Code without good justification would lead to bad code. The author even provides examples of this. People in this thread are criticising Clean Code principles as if they are meant to be a rigidly enforced dogma. They aren't, and the author never intended them to be so.
You can't finish it. Did Google finish? Did Facebook finish?

But you can set a goal. "Get feature X done this quarter".

Doing so let's you switch projects a bit more guilt free - since you are working more of a kanban size.
That's not the question. It's about what is included in the geographic area referred to as "Southern Sweden".
There's a theory that "maintaining a streak" is highly effective as a motivational tool.
Extending that idea to the web, or at least to the blogosphere and information / knowledge web-sites, seems useful.
I wonder if there is a web service which has calculated vector embeddings for some of the web, and supports vector search, e.g. given a URL, find URLs with similar embeddings.
Inverting that, web-sites could annotate their web pages with embeddings via json-ld; which search engines could utilise. Both these ideas might be impractical, e.g. the cost of http GET of the vector might be similar to the cost of calculating the embedding; and the embedding would be only comparable with embeddings from the same model (which would be recorded in the json-ld) so it would age quickly. It would also be subject to SEO gaming, like meta tags.

A quick search didn't find either of these; the closest was this paper which used json-ld to record a vector reduced to 2 dimensions using tSNE :
https://hajirajabeen.github.io/publications/Metadata_for_Eme...
Metadata standards for the FAIR sharing of vector embeddings in Biomedicine
S¸ enay Kafkas et al.
Thank you for sharing something so personal. <3
If that's indeed true, there is no point to compress an image that is larger than a target viewport---any larger image can be scaled down on encoding and upscaled on decoding. But all formats mentioned easily support much larger images.
I believe the higher the mean seniority (as in time in the same workplace) gets the more a programming workplace resembles a cult.
That's actually something I dislike, I don't want my results to be different based on where I am.
Transfection by heat shock is also a possibility. Anything that creates transient pores on the cell membrane should work, at least in theory.
Not just no proof; proof positive that the initial claim, at least, was bullshit, for one very simple reason. The restaurant in question _does not have a basement_. (This feels like laziness on the part of the person who made it up; it should be very easy to determine.)
>That doesn’t make any sense though, assuming a couple of thousand people lived there initially with all the ample land a population of ~2000 would have increased to over 100k at a somewhat conservative growth rate of ~2%...

>So overall I don’t think we can really apply real world demographics to middle earth. There certainly must have been some force/factor not directly described by Tolkien that kept growth rates very low.

Perhaps women in Tolkein's world are far less fertile than in our world (except for Samwise's wife). Or maybe they developed some effective contraception.
Wow, started reading this now.

There's a lot of surprises in there for sure. The people crafting the spec seem to have had some peculiar goals that I don't quite understand. Especially all the implicit stuff in path data is surprising to me.

Also, a relative value of stroke-with is "relative to the diagonal length of the current viewbox". This was surprising, but makes a lot of sense when I think about it. And the default unit is %, which also makes sense after some thinking.

Seems like frustrating work, I'm glad the author can channel it into writing :)

Thanks for sharing.
So the high priest / philosophical originator (guardian.com) of the cult should not "be taken as a representative of the average EA," and nobody saw fit to mention his...unusual views (due to his naive utilitarian philosophy) later on in that EA forum thread, the first thread he's posted in 9 years, the thread who's topic is closely related to the topic of the Twitter thread I linked?

Is EA distancing itself from Singer (who's views are, by all accounts, extremely influential in the EA community), as they did with SBF (whose hedge fund's initial $170m seed capital was raised from EA devotees)? When multiple high-profile people associated with EA are proven to be....problematic, should we pretend the common factor linking them is insignificant?

Inflammatory? I thought I was quite restrained compared to some of the commenters on that Twitter thread.
This irked me recently. I think it’s very reasonable for networkd to delegate everything after the interface meets an “online criteria” to later services. However I was disappointed that you couldn’t then tell networkd an interface was “active” (vs. online) later down the line.

Would be interested to hear how you & others approach this. Perhaps I’m not thinking systemd-y enough hah.
Another aside: I only recently made the connection between the ancient Philistines (https://en.wikipedia.org/wiki/Philistines) and Palestine when a speech by Erdogan supporting Palestine was shown on the news and it had a slogan with "something something Filistin" in the background...
You could just use whatever romanized version of your name is the standard for your language and writing system without any real down side except EEWWWWW ANGLOCENTRISM NOOOOO. That way people from other cultures around the world (who generally don't have trouble learning the latin alphabet in addition to their own) will be able to do something with your name rather than seing random symbols they can't even attempt to pronounce, won't remember and certainly won't be able to re-type.
There was some discussion on techniques to get around that in this HN post about a messenger type product: https://news.ycombinator.com/item?id=37105477
Right, the reason to do it is obvious and the development work is straightforward, it's a step forward but it isn't something to get all breathless about.
I read about the WoT and I found the idea fascinating, but I've never used it myself. Would love to hear anything you have to share about using it in practice.
Most agree that we shouldn't actively do it, but we definitely do it consciously and subconsciously. It's a very human trait, even if we don't like it. The brain just doesn't have the capacity to evaluate everyone from scratch every time, so it takes shortcuts, and 'accepts' people based on the way they present themselves. The kinds of clothes they wear, shoes they're wearing, and accreditation from mutually trusted institutions. I agree the shortcuts that cause harm should be curbed to the best of our abilities but we can at best notice it and correct after the fact - but it'll still happen.
Zero, one, and carry, you mean?
> You don't need AI

No one thinks this. People that are worried are worried __because__ you don't need AI. AI is just more powerful tools.
One of the best features of MX that you can run it easily as persistent image on USB, especially if you get yourself a small relatively good NVMe SSD with enclosure (DIY USB stick)
What is in it for early starters working at a start up? Lower pay, more demands, more stress, probably get shafted on options terms, and they have to be the kinds of people who can probably be the founders of their own thing?
The difference is in the magnitude, not kind.
The changing part is not time consuming, is having to fix the same bug over and over because you didn’t realize this same function was copy-pasted in 7 different files. It really gets worse when you realize this a year after the first bugfix, still dealing with a stupid bug you fixed a year prior, if it wasn’t for copy-pasted code.

I’m also against DRYing up unnecessarily, but if the code is a 100% match in intention and/ord behavior, then it’s going to be deleted.