skysight-inc/HackerNews huggingface dataset:
Pinboard [0] has this feature with additional price. Just bookmark and you are done. Later you can text search in their content.

[0] https://www.pinboard.in/
Yep. I have a teensy+codec for the express purpose of experimenting with audio DSP filters.
Does it support bubbling event handling? In the form of: $(".outer").on("click", ".inner", function(){ ... } )

Without bubbling event handling, it's a no go for handling event on dynamically generated inner content.
It has to do with the thread going in generic ideological directions [1]. Generic discussion is predictable [2] and, in the case of divisive topics like ideology, gets increasingly nasty as well, as the partisans of each side show up to fight each other in the same ways that they always fight each other. All this is the enemy of curious conversation, which is what this site is for [3], and which has to be unpredictable in order to be interesting. If it helps at all, we moderate the opposite side the same way (an example I've used sometimes is [4]).

If you look at the links below and still have a question that isn't answered there, I'd be interested to know what it is. I'm afraid it's a bit of a slog to scroll back to the interesting explanations, though, since there's a lot of routine moderation mixed in there as well—but then it can sometimes be helpful to see past cases also.

[1] https://hn.algolia.com/?dateRange=all&page=0&prefix=true&que...

[2] https://hn.algolia.com/?dateRange=all&page=0&prefix=true&que...

[3] https://news.ycombinator.com/newsguidelines.html

[4] https://hn.algolia.com/?dateRange=all&page=0&prefix=true&que...
A minimal serverless IAP Terraform Recipe
We have lots of availability still!
Money Markets never look good, but they are 1) better than a savings account at the bank 2) less likely stolen by a relative when hidden under the mattress.

Money markets typically pay just better than inflation. Not so much a place to get rich, as a safe place for the money over the next year or two.
Yay, autocorrect!
Tesla has already started making cars again at its California factory
VS Code Debug Visualizer
Autocorrect comes for us all in the end.
Introducing Filecoin Discover
Hopefully it got a little less „dependency-heavy“ than before. Using eslint and babel tends to add 200mb of dev dependencies to a project...
> There also isn't any evidence that it would extend reproductive lifespan either.

FWIW, it doesn't need to do this. It just need to result in more surviving children and grandchildren. Looking 5-10 years younger when you're a female between the ages of 25 and 40 could A) get you access to a higher status mate who can better provide for your children, and/or B) keep your mate more interested in you, reducing the likelihood that they will continue to provide for the children you have with them.
They stranded me in London for 3 days after a thunderstrike took out some service vehicle. I spent 8 hours standing in a line. After 3 days the replacement flight was cancelled too.

I ended up having to take a bus from London to Berlin. Naturally they refused to pay for any of that and the emergency hotel.

Never. Again.
I’m shocked you leaked our proprietary internal architecture details and have forwarded this memo to management.
Eh - I find those people are often the same ones who write weirdly dense pythonic one-liners (cause less lines == good), don't write documentation for their code (cause all code they write == self-documenting), and assume that their interpretation of the English language is standard (even though it's often enough not their native language).
This is pretty up to date: https://github.com/ryyppy/nextjs-default
I wouldn't see it as an Arduino competitor as they're different beasts mostly aimed at different use cases.

The Teensy also has a DSP on board which can be useful in many applications, from music to signal processing.
Here's a SDR radio built around a Teensy some years back.
http://theradioboard.com/rb/viewtopic.php?f=4&t=6641
Does anyone know of any kits like that around?
I've used it a fair bit, though not for a couple of years. Few points, some of which may be out of date:

* I've seen customers fall into the trap of thinking they don't need expensive developers because you can drag and drop, just people who can use a mouse can crack on with NiFi.

* It persisted its config to an XML file, including the positions of boxes on the UI. Trying to keep this config in source control with multiple devs working on it was impossible.

* Some people take the view that you should use 'native' NiFi processors and not custom code. This results in huge graphs of processors with 1000s of boxes with lines between you have to follow. Made both better and worse by being able to descend and ascend levels in the graph. The complexity that way quickly becomes insane.

* You're essentially programming with it. I've no doubt you could use it to write, say, an XMPP server if so inclined. Which means you can do a great many things of huge complexity. Programming tools have developed models for inheritance and composition, abstraction, static analysis, etc. which NiFi just didn't have. The amount of repeated logic I've seen it's configuration accumulate is beyond anything I've seen from any novice programmer.

I ended up feeling like it could be an OK choice in a very small number of places, but I never got to work on one of those. The NSA linking together multiple systems with a light touch is possibly one such use case. For most everyone else, I couldn't recommend it.
Well, you know, the way you wrote the comment, it kind of invited us to take it as personal - as applying to ourselves.
Not only the websites, but art within them as well is starting to become more and more similar.

In particular I have the style with disfigured colorful human figures displayed in various weird poses. I am not sure what is the name of this drawing style and how it got popular, for some reason it repulses me, but here is one example I remember:

https://todoist.com/
Hard to say. At least in the case of humans, high generational turnover might have been beneficial in our evolution from aquatic apes or whatever our ancestors were to modern humans. And so longevity genes were selected against. It might be the case that most species' environments are too dynamic for super longevity genes to be beneficial rather than faster population adaptation.
Great Examples for Companion Planting and Permaculture Guilds
If I don't need anything fancy (not even SSR), Parcel does it for me out of the box:

parcel build *.html --public-url https://domain/

It's great to use my dev/build tool for static site generation.
The modern way to call APIs in Python
About your junior dev it might also be the way he was taught React.

I'm also a junior and the way I was introduced to React was by teaching me enough JS that I could theoretically write React (with a bunch of research).

One of the things I've noticed among other junior engineers (including myself) is tutorial driven development. Through a mixture of inexperience, laziness, and self doubt it can be easier to find someone else who's implemented something and just use theirs. Rather then thinking about a complex problem and naively coding up a solution finding someone else's hopefully battle tested code.

An example of this is how I used to make JS based games. I essentially used an array to toggle classes on a grid of divs divs in the style of an LCD screen. I hadn't heard of html's canvas element. My solution worked but I don't think anyone would think it's a particularly good one. If I had found someone's snake game and saw they used canvas I could have saved myself some headache.
> Some people have good writing skills, some have good technical skills. The ones who are good at both are rare.

Anecdotal, but in my limited experience those with poor writing skills are also poor at writing software.

Typically those who have put in the effort to design and understand their solution are also pretty good at communicating their changes.

The people who rush to get things done quickly and have trouble communicating their changes tend to (in my experience) not really understand what they are doing themselves. More often than not in my experience this group of developers mostly implement ad-hoc solutions that eventually have to be fixed up by the "good at communicating" group later.
Barely done this for a month now so the process is still young, but my plan is to keep around only the relevant snippets and update them in case anything changes. As to how often I review them, or the backlog, basically whenever I have time or I feel like doing it (trying not to put more pressure on me schedule than necessary).

The only things that I do "urgently" would be to add elements to the backlog, and to fix errors in the published snippets. For everything else, I put a reminder in my calendar for the weekend, or after work in case I feel energetic enough.
Used to work at a PaaS, which had a 17 year old codebase. It did something that none of our competitors could do, which was really important to our client base.

We were a second-tier player in the space, where the 1st-tier player would be exponentially more expensive to implement and of little benefit to any but the largest clients (think, SAP vs Mysql, for analogy's sake).

When courting new customers, we often encountered the question, "When are you going to re-write your product and get off [language platform]?"

We wrote a white paper to explain where we were, where we were going, and how [language platform] wasn't impeding our 1) security, 2) performance, 3) extensibility.

But we got that question every time. CEO asked tech team how long it would take to re-write the entire 17 year old code base, without losing any client facing features, in [any_new_platform].

They ended up selling to a big financial concern (for analogy's sake, think CA -- Computer Associates).

Was probably the right move.
Yes! The million dollar question is how much of that expressivity is actually required.

In many papers, the "baseline" logistic regression model is very stripped down: y~logit(.) but the neural network has had its expressiveness optimized in various ways. People aren't comparing against a 3 layer feedfoward network; there's augmentation and pre-training, architecture search and special learning schemes.

My claim is that if you want to claim that a problem needs the expressivity that (only) a neural network provides, you ought to be devoting a great deal of effort to the logistic regression model too. Make it a steelman, rather than a strawman, if you will.
This, to me, defines the heart of a true DevOps mindset. It's not easy to find this role defined as such, though, and you'll often find yourself fighting to carve it out of a more simplistic definition (i.e. automate stuff) at most organizations if you choose to pursue the path.
Apple HomePod Releasing in India
“Bad part is, all of their friends and colleagues are dead by now. They can only meet their kids' generation.“

My mum says it gets weird when people your own age you know start dying in numbers but even weirder when people much younger start dying.
> Its inscrutable nature is definitely problematic for some use-cases, and not so problematic for others.

It's a problem whereever reliable operation is required, or analytic tractability (explanation) is required, or where resources available for data labeling are limited.

Its niche appears quite small, unless and until solid mathematical foundations are developed for it.
If only we could subject enough people to cannonballs we might find one of the super humans I postulate exist.

But train wrecks would allow for significantly higher populations per experiment.

I must ponder this.

They call me Mr...
Depends which parts gets prolonged - if you are at 80 deteriorated +-same as somebody who dies at 80, and they just keep fixing the next thing that is going to kill ya, then yes, that's a pure physical misery and spiral down progressive dementia (almost all old folks suffer from some form of it).

Now if we would be 40-like in our 60s and so on, that's another story. But first thing that would probably change is retirement age.
Primary care needs a new operating system
Interview with the Rock and Roll Band “Little King”
As someone who lives in Boise, I'm angry:

1. People had to buy this test. It wasn't free.

That means

2. whoever bought the test were guinea pigs in this study.

And

3. That fact wasn't being made clear in Crush the Curve.

LabCorp should refund all the tests in Boise immediately.
I like the zipped-HTML version of this : https://addons.mozilla.org/fr/firefox/addon/singlefilez/
How could you expect someone to be able to find a problem in your live environment if they're completely unfamiliar with its architecture and what functions it was designed to perform?

It might be better to ask a behavioral question like: "Tell me about a problem you once fixed that was difficult to reproduce. How did you think through the possible causes, what tools did you use to gather information, etc.". Then ask followup questions to get more details, e.g., ask more about how they used their tools. If they're bullshitting (for example, they only had only a minor role in fixing the incident), it will be hard for them to provide plausible details as you dig deeper.

If they answer this question to your satisfaction, you could then ask them to show how they'd use certain tools, but they might have been using proprietary tools at their previous jobs (e.g., if they worked for a huge company like Google) and may be unfamiliar with the tools you're using. You wouldn't want to turn down a good candidate just because they're unfamiliar with the specific tools that you're using.
I think that's part of the typescript plugin, not part of eslint core - https://github.com/typescript-eslint/typescript-eslint/blob/... (I assume that means it only works on TypeScript.)

But, I agree with your point, that rule can catch a lot of bugs.
luv.
Just did that one, didn't find the actual coding hard at all. But, just understanding what it wanted took a lot of time which would make me nervous, which would make me look stupid under the gun.

I don't think I could do it confidently with someone looking over my shoulder, clock ticking, and $200k in sitting in a suitcase.
Also, stop making the text box slide in and out. This adds nothing and is distracting. Just make it appear and disappear.
Is there any evidence of a panspermia?
That's a bug of $HYPED_TECHNOLOGY. It's been known for years, but they're too busy evangelizing at conferences to fix it.
The problem with E4X is that it's only data; you can't define a new tag that reduces to new primitives. This kind of composability is why XHP (in PHP) and JSX are so useful.
https://www.eater.com/2020/3/31/21201374/why-are-free-online...
I recently returned to a workplace I left 15 years ago. There are a substantial number of staff still there who are around my age - early middle aged. Many look very similar, but what took me by surprise - as I've never studied a large group of aging people over a decade plus - is their skin. Superficially features, hair, body weight, etc., hadn't changed but to a man (ie across everyone) they all have "aged" skin.

So, if you want to tell if someone is 25 or 40, maybe their skin will give it away?
Whoever is willing and able to create, maintain and defend facilities there.
Marginally. The STM32H7 series offers Cortex-M7 cores at up to 480 MHz, with a Cortex-M4 coprocessor on some parts at 240 MHz. It's not quite as fast as the i.MXRT1052, but it's damn close.
allow me to acquaint you with Element.matches():

https://developer.mozilla.org/en-US/docs/Web/API/Element/mat...

https://jsfiddle.net/dg3rL81z/
My personal experience led to that assumption; I've never guessed anyone's age wrong by 15 years, hence the example. Sorry it hit you the way it did; wasn't my intent.
Airshare – Cross-Platform content transfer in a local network using MDNS
Cool info.
This is a great resource! I hope I can convince my team to implement something similar.

I see that the handbook is mostly focused on company level procedures and "What we do". Doe GitLab folow similar principles for documenting code? E.g. Update the documentation for the design before writing code?
"Weird cold" in February checking in. I did not have any temperature variations or fevers, but I got struck with a fatigue like no other. For the first time since I was 3 years old, I took afternoon naps three days in a row because I was just completely wiped out. It's rare for me to take a nap at all (happens maybe once a year)! It took two weeks to get out of this fatigued state. My other symptoms were "chills-like" sensations throughout the day, post-nasal drip and burning feeling in my chest/lungs but very minimal cough. My child did have COVID-19 symptoms back around Feb/March (can't remember exact time-frame) and I even wrote about that here on HN. Maybe I should take this test.

I still think there's a possibility this virus was already in the US before 2020. I don't think they ever found a cause to the "mystery respiratory virus" in Virginia from July 2019:

https://www.nbcwashington.com/news/local/health-officials-to...

> Three people have also died, but Dr. Benjamin Schwartz of the Fairfax County Health Department said Wednesday afternoon that those who died were "older" and had complex health problems. Officials don't yet know the extent to which the respiratory illness contributed to their deaths, he said.
Sigh, it looks like the title got a bit mangled…oh well. As most of the commenters have gathered, this was mostly tongue-in-cheek; I kept a window with a few of these kinds of posts open as I wrote so I could refer back to them so if you might be able to make out some familiar companies or technologies in there. That being said, I love hearing about your employer's technical decision making process, so I don't want to discourage anyone from writing blog posts like these. Just try to keep in mind that your decisions not be the right ones for everyone else. On the flip side, if you're looking to make technical decisions yourself, sometimes what $FAMOUS_COMPANY did is not the right choice for you :)
JSX was a direct port of XHP to Javascript.
Farewell, TensorFlow
Example project: https://luftdaten.info/laermsensor-bauen/ (only German and French translation ATM)
Awesome! Making Spark more approachable is good news for the wave of new data engineers.

Do you have any record demo you can share where we can see how a user would set up and integrate with the other tools? that would be neat
Firefox can screenshot the whole page - it's built in. I believe it can be done in headless as well.

https://support.mozilla.org/en-US/kb/firefox-screenshots
It's because the internet has given control of software to companies. Pre 2005 the only control game companies had over software was a few PC RPG's that had been rebranded mmo. In an internet enabled world, every game can be made client-server and have in game stores.

The internet is what ruined gaming because it gave corporations and developers too much power and control of the software and the ability to deny ownership, dedicated servers to their customers.
You seem misinformed.

https://www.gosh.nhs.uk/news/coronavirus-covid-19-informatio...

Please stop with all the FUD and actually read up on what we know.
It seems to be an approach to study quantum gravity.

(Drive-by plug for Stochastic electrodynamics.)
It's actually kind of funny, because that's exactly how the 2004 Doom 3 turned out - defining the game-play based upon lighting (and monster closets) to build tension.
About 7 years ago it was the most affordable USB controller that identify them self as a HID device that I could find to brute force the EFI lock on a MacBook Pro https://orvtech.com/atacar-efi-pin-macbook-pro-en.html

It was really easy to setup and start pushing code to it
TIBCO is an "Enterprise Message Bus." Think of RabbitMQ or 0MQ but supported by a giant enterprise grade vendor.

My last experience with TIBCO was them telling us the product didn't support anything but running on bare metal because "virtualization does not guarantee the order of writes to disk" (their words not mine)
You want to log an integer to the console 100,000 times? Not sure why you would, but you can do that in a React event handler or lifecycle method.
Why I use typed functional programming
Yes I keep appending and rewriting. The doc keeps growing, but smaller thoughts that form part of a bigger idea get coalesced and rewritten. This is a constant process.

Rewriting is a process of refining. Most ideas get rewritten and iterated on several times before anything coalesces. Also, it's common to have duplicate ideas at different times so coalescing them simultaneously consolidates them.

For instance, when re-reading my doc, when I see multiple ideas related to say topic A, I put all topic A items together (just copy-and-paste into adjacent paragraphs -- nothing more), try to see the bigger picture and then try to rephrase them more succinctly. I constant rewrite and synthesize the disparate ideas into something more cohesive, kind of like snowballs clumping with some getting bigger over time. Some ideas do die in the process (you can copy-and-paste these into another Docs document), while others grow bigger and become more precise in their expression.

The one idea behind the Fieldstone approach, often not considered in other methods, is engagement of the emotions. Of 100 ideas, I may only feel passionate about 5 at any given time because they resonate in my situation. For instance, some ideas/arguments/metanarratives which were meh to me pre-COVID now feel urgent, and with my current perspective, I've an emotional investment in pursuing and expanding them.

You can have 100 ideas but you really on need to work on the few that you really care about, ie. those whose time has come. Only pursuing ideas that you're emotional about helps you focus and not be overwhelmed by the myriad ideas that are in the document.

Inspiration is lumpy, but with a store of constantly refining/evolving potential ideas in the greenhouse -- which you cultivate over time -- you are better positioned to take advantage of those on the verge of blooming.

It reminds me of what Richard Feynman said about convincing others that you're a genius: "always have 6 important problems percolating in your head; when you come across a new idea, test it against the 6. Once in a while you will hit jackpot and find a good match between problem and solution. Everybody will then think you're a genius for seeing the connection so quickly, when in reality you may have been thinking about the problem for years." (paraphrased)
I would also expect Instagram to be on Facebook's infrastructure these days ;)
Is this an open source self hosted equivalent to https://aws.amazon.com/datapipeline/?
I agree. To me, it sounds like random matrix spectra.

Just because it has the shape of the Planck distribution, it does mean it comes from it.
> I think one thing that's needed to establish a culture of written communication is getting rid of any cultural elements that allow people to use the avoidance of reading and writing as an expression of power. You can frequently determine the balance of power between any two people in an organization by seeing which one has to read and prepare organized documents and presentations, and which one can simply speak and be spoken to.

This is perverse and contemptible in the 21st century. It reminds me of the line from the Simpsons movie: “I was elected to lead, not to read”. But it goes to show that any cultural change needs to come from the top in order to be effective.
USA used to support local independent media. Every little paper that got passed certain threshold was funded by state, as they provided essential service to local community.

But its much easier to control narrative if there are only few outlets. And now in post-truth world average Joe doesn't read anything but facebook, or some rage broadcast.

Read Manufacturing Consent: The Political Economy of the Mass Media, to see why the funding has stopped.
I do care. More must be done to protect consumers. I have spoken.
Yo dawg, heard you like comments