skysight-inc/HackerNews huggingface dataset:
The end of the dollar’s exorbitant privilege
Any time you print something at FedEx they make you accept an agreement stating that you are not printing or copying copyrighted material. I'm guessing those other places have the same type of thing. Even if it's a piece of paper posted next to the printer at a public library stating "By using this printer you acknowledge that you are not printing or copying any material for which you do not have the right to copy."

To be sure, it's a pretty loose contract and you could probably get away with printing a small amount of copyrighted material. But it at least shifts the liability onto the customer so the retailer can always point to the agreement and say "hey, they said they weren't printing anything illegally; that's on them for lying."
It is not producing a macroscopic current, it is producing something like Johnson noise https://en.wikipedia.org/wiki/Johnson%E2%80%93Nyquist_noise (The interesting part seams to be that it has another frequency distribution, but I don't understand the details.)

A real engine transform heat into electric energy that can be used to dissipate heat inside a container at any temperature. In particular at a higher temperature that the graphene and the support and the circuit. In the PR they claim that it produce "something useful" that I interpret as "work" or "electrical energy", but in that case it breaks the Second Law even if in their setup the resistor is at the same temperature.

After reading the paragraph again, I'm not sure if your interpretation is right and they are claiming that the device is transferring energy from the graphene to the resistor, but that breaks the second law, in spite in the PR they claim it doesn't.

I think they never claim a 100% conversion anyway. They just don't have a temperature difference to operate the engine.
> Would you destroy $10 billion of value/resources in the economy to save 1 person?

You can spin any arguments by framing them in such ridiculous scenarios. My comment is obviously in the context of people able to pay money to get rid of their personal responsibilities.
They've tried that already.

When I was in school (early 2000's) our GCSE computing lessons were, more or less, "Here's Microsoft Word, today we will learn how to format a letter!" or "Here's Microsoft Excel, today we will learn how to create a chart!".

The only upside to taking the class was that our school managed to identify the kids who were obviously computer literate and we got to go on a tour of Microsoft's UK headquarters...
There's nothing wrong with CSV, especially if you don't have arbitrary-text data (if you do, just don't do CSV). Excel though adds an addition layer of services, which turns it into a nightmare if used as something it explicitly wasn't made to be - a database.
Thanks cpach. I'm still holding on to some hope on more answers pouring in.I realized that the focus has shifted massively to mobile or web apps. But I still feel there are a lot of cool stuff you can and should build as desktop apps.
Why do other people use illuminated IR cameras then? Aren't they looking for decent gaze direction detection, etc.?

Isn't it unsafe to drive with a ton of light from the giant LCD, etc.? I would have though they would dim that and/or have a night mode with inverted UI colors.
Amazing comment, sorry to see you're getting downvoted. ALTER TABLE upvotes ADD COLUMN threatripper_24691123_upvote DEFAULT 1 NOT NULL;
Retention packages from the acquiring party get pretty insane to keep key employees on board.
As a daily cyclist who has experienced many close calls over the years at the hands of inattentive, impatient, or unaware drivers, I would love to believe that this world is coming. But unless insurance companies can actually go to work on predicting how accident-prone a person is based on this kind of data, and raising premiums accordingly, I don't know if it will make much difference in terms of actually changing behaviour.

Like, there should already be a lot of this kind of data out there to nail drivers to the wall post-crash, and you just don't really see it happening. Even when someone is killed, everyone involved basically shrugs, says it was a fluke, and tells the family they should get over it and move on (watch for the phrase "came out of nowhere" as a sign that everyone involved has checked out of a particular case).

And how much will consumers accept a car that tattles on them about their bad behaviour? People already lose their minds over provably-effective external automated enforcement measures which rely on plate reading like red light cams and average speed cams.
An easy way to do this is to perform a 'mixed reset' from the tip of your branch back to the mainline commit where you started work. (Use a new branch, so that your original branch "backs up" the work.)

This will leave all of the final changes in the index, "squashing" any churn. From there, individually stage lines/chunks into a small handful of atomic commits for the PR.
PowerPoint is anything but simple.

If PowerPoint works for you, that's great! I have no problem with it. But it doesn't work for me. There is a true need in this area for better diagramming tools. Plantuml and graphviz were good ideas, for which we still lack a killer execution/implementation.
I watched the video demo and I like the idea that I might easily get a PDF with nicer formatting than the default print styles. I would use that sometimes.

However, I question whether this will work consistently, since in my experience it takes a lot of developer attention to cover all the design anti-patterns out there.

It's a classic problem of course but I don't see why this is better than using something like Pocket, which has enough traction to get parsing right most of the time even if its print style might be less nice. It also has good integration with my e-reader.

For the intended physical-book version, I think you're setting yourself up for serious copyright problems. You're going to republish the Wall Street Journal because one of its readers asked you to?

Anyway it looks like a fun project and I wish you luck with it!

Regarding the video I'd like to point out:

1. It makes the service look really slow! Probably not what you want!

2. The video ends with an ad for the video hosting company, which I found confusing at first.

[edit: less speculation]
I took alot of interest in various small ARM devices.

Only to realise that lack of software support makes them almost all pretty much completely useless.

I wouldn't use any randomly bought ARM device now for hobby projects, except the Raspberry Pi.
https://www.youtube.com/watch?v=3QAXDMOVamI

I saw that scene and it reminded me of coffee drinkers with their $40 per pound beans, hand grinders, and Chemexes. Junkies like their rituals.
As an aside, this is a very clear explanation of the bug in non-technical language, much better than you normally see on general news sites. Excellent reporting!
I mean, whatever people might pretend is true when they're lazy, you don't have to maintain anything you don't want to. If you just want to make the source public once and tell anyone who asks for bugfixes where they can stick it, that's your right.
More like Heavenly serial killer if it is just over some insults.
Any chance you could provide a summary of how OOP was originally much more similar to cell biology? :)
> You shouldn't be driving. Period.

what a stunningly pretentious and ignorant thing to say.

reasons to be tired and drive: rotating shiftwork, working multiple jobs, caring for a newborn, caring for the sick. that covers millions of people, off the top of my head, without doing any research. and those are only the most black-and-white examples. more ambiguous cases include: driving from physical activity like OP mentioned, long drives to visit friends/family, events like weddings.

if you want to make the argument that sleepy driving is more dangerous than we give it credit for, then we can talk - but thats not what you said. "You should never get behind the wheel if there's a chance you'll fall asleep!" is an absurd thing to say.
> We are too busy focusing on delivering value to the business

there are a lot more linux users out there than business users
General Butt Naked is a contemporary figure. The featured article is about the founding of the Liberian state, which began almost 200 years ago. If your comment had connected the unusual General Butt Naked to that, it would have been interesting, but just linking to some crazy guy's Wikipedia article because he's from the same country isn't, really.
I'll bite. I'm 37, a tech startup founder. I'm wary of ageism and I've long believed that not being ageist would allow us to hire smarter than competitors.

However:

- The amount of programmers grows exponentially. I've seen stats claiming it doubles every 5 years.

- This means that at any time, 50% of the available workforce has <5y experience. Often this overlaps with young ages.

- It also means there are simply way more programmers under 40 than over. If you randomly hire 9 programmers there's a fair chance they're all under 30.

- Anecdotally, less than 5% of the job applicants we got was over 40.

- Young programmers haven't had time yet to make the mistake to "repeat the same year of experience 10 years in a row". If you hire a young, junior programmer, you know they're junior - what you see is what you get. If you hire an older programmer they might be great or they might be that same junior programmer but more stubborn and with higher salary expectations.

As an avid anti-ageist, in fact I'm rather disappointed about that last point. I've met many programmers at around or above my age that have gotten completely stuck into a tiny niche of experience and, even there, seem to not really have progressed much in terms of depth. Why do people let this happen to themselves? I mean I met people who spent the last 10 years developing just-not-the-same custom Magento webshop plugin over and over again, each time with a slightly different twist for a different customer. Not hiring someone like that isn't ageist, it's common sense. Once Magento is out of fashion these people have a pretty serious problem.

The reason I don't understand this is because with each new technology you learn, there's a diminishing effort to learning the next because there's so many similarities to a thing you already known. There's a reason most people complaining about "javascript fatigue" are young.

As an example, when React/Flux/Redux first came to the scene, old farts like me could recognize that its "unidirectional data flow" wasn't fundamentally different from the good old desktop MVC UI pattern (before Rails hijacked the name and gave it a different meaning). I imagine that this made learning React and architecting decent apps on it easier for me than for people who'd never seen data "flow" in circles before.

Age definitely can be an advantage. But it isn't by definition. Keep learning new stuff folks! And if that ever stops being fun, you can always become a manager.
IMO your statement is the truism that isn't adding anything. Obviously people that might fall asleep shouldn't drive. But this is a matter of degree. Everyone might fall asleep and it's a risk everyone will eventually take even in a small degree.

Some people are always somewhat tired (eg sleep apnea or CFS), some people aren't tired when they start driving but become impaired at some point. Some people might have an undiagnosed condition that contributes.

There's no reason to not celebrate a simple advancement that might save people from a disaster.
I would hope that any decent data engineer would know not to do this. Are there avenues for fully-employed engineers to help governments build these systems properly? I'd honestly be happy to just donate some of my free time to help these efforts.
> For example, Einstein was able to work through the sound of his crying baby [1].

OMG, as someone who is very irritable and has trouble focusing through any kind of noise, this sounds like a superpower. I'm guessing it's largely genetic.
HN probably expects a somewhat technical explanation, not a rant about Big Banking being overlords.

Even if it might be correct..
As kids in elementary school, each day before we accessed the education system, we pledged allegiance to the flag of the United States of America, and to the republic for which it stands...
The reason the React.js team started using Canny was because before Canny I worked on the React team at Facebook.

I didn't plan it this way. My ex-colleague, @vjeux, messaged me and asked about my new startup. I told him it was a user feedback tool, for tracking feature requests. He said React Native had that problem, and they just started using it.

So I think working at FB on React is what exposed me to getting lucky here. I think a lot of luck in startups is about increasing your exposure to getting lucky.
Somehow I missed the lede. You are correct, he is doing exactly that.

So my conclusion is bunk, although the decision tree I loosely mapped out might still be useful for others so I'll leave it as is.
There is nothing wrong with CSV or text base formats. You can even use AWS Athena to query CSV feels stored in S3. It's a good format for data import/export, that many systems can natively understand or have tools to parse, given it's known how to interpret data.

It was a data pipeline issue. Software has little to do with it. If they received data in json and tried to interpret it as CSV, the same could have happened. I believe Excel even warns when you open file that has too many rows.
> for the simple reason that you need the same compiler version to build Linux kernel modules.

Which kernel modules wouldn't come as precompiled packages in Ubuntu ? (real question - as an Arch user for instance I haven't had the need for DKMS for years)
https://www.youtube.com/watch?v=3B9Rqr_3EcY&feature=youtu.be...

https://www.reddit.com/r/MushroomSupplements/comments/9o26my...
There's a Dunkin just built in Sunnyvale on El Camino, not open yet but they're moving in the furniture. First one I've seen outside of an airport here.
I thought the same, even Visio is more complex then PowerPoint- PowerPoint has highest productivity level for me personally in this regards. Funny to say that.
There's also another dimension to that uncertainty. Dates are typically attributes of events involving one or more people in various roles, and these events are (hopefully) attached to one or more sources. The type of sources you use affects the confidence of various attributes of the event (like dates or participants).

In my area of research death records are typically a bad predictor for date and location of birth. When the records were managed by the churches (until after WWII pretty much), priests did not want to pester grieving family for the exact date of birth, so they relied on approximate age. Naturally the subject of the death record would not typically point out errors. On the other hand marriage records required looking at the actual birth records (sometimes mailed across the country), as these contained notes on all marriages of the individual (this was done to ensure monogamy).

Is it on the genealogist to consider this confidence when specifying the date of the event, or should the software intervene? Due to complexity, the former is the industry standard. But maybe there are some brave (or stupid) people who will try to take it into account in the future.
> There's nothing wrong with CSVs/TSVs

I can see the theoretical purity of this statement, but based on my experience working with CSV files generated by actual non-technical users I have to disagree here.

There are a number of footguns here that are really subtle and the average non-technical user has no hope of spotting them.

Problems that I've seen in the wild, off the top of my head:

* Windows vs. Linux line terminators breaks some CSV libraries.

* Encoding can change depending on what program emitted the CSV file, and auto-detecting encoding is not perfect. For example, Excel for Mac uses Linux encoding by default, IIRC.

* Excel does wacky things when you export a "CSV" in the wrong format; real users use Excel to generate their CSVs, not Python. For example if you import the string "0123456789" in an Excel sheet, it infers "number" and strips the leading "0" when you export. Now your bank account/routing numbers are invalid!

* "What's a TSV?" -- if users use CSV, how do you handle commas in the data? It's nontrivial to train users to do their CSV upload as a TSV.

Etc.

In practice we needed to build a fairly beefy helpdesk article with accumulated wisdom on how to not break your CSV exports, and most users don't read/remember these steps until they experience the trauma first-hand.

I'd say the CSV format is deceptively simple -- it's quite easy to do the right thing as a developer where the source and sink are both code you control, but in the wild it gets messy really quickly.
It's not as cut and dry as drinking and driving. A lot of times people who fall asleep on the road feel completely fine, until the moment they start falling asleep, and at this point their brain could be too asleep to tell it's falling asleep. I've dozed off on the road before and I can tell you, it's like someone just pressed the power button on my brain.
I love OCaml CGIs with a few hundred LOC, (almost) no build dependencies and zero runtime deps. Statically linked, stable forever.

e.g. https://demo.0x4c.de/geohash.cgi/u28br
When I use Excel to open a CSV with too many rows, I get an alert saying 'File not loaded completely'. I have to dismiss it by clicking 'OK' before I can interact with the spreadsheet.

So Excel isn't silently discarding data.
I'm an engineer and yogi. I've been experimenting with tons of working positions in the WFH era. I really need to take pics.
That's an interesting ethical point in CS: sure, you didn't intend the software you hacked together in an afternoon to be used in anything with life-and-death consequences. But that doesn't mean someone isn't going to come along later and use it, without ever even looking at the source, for something very critical down the line.

I wonder how many bleeding edge master branches of GitHub repos, pulled in blindly by someone cobbling something together to meet a deadline, are running in places they probably shouldn't be.
Can confirm this--we had meaningful fog along the coast near Refugio State Park until at least 3p yesterday, when it normally burns off by at least noon. Obviously, that's just one day, but it general it seems to be more common since the fires, and I've noticed some similar oddness as far down as Ventura
Some people don't have that privilege. Ever known someone that works two jobs trying to make ends meet? You don't have a choice except to drive home from work.
Q: You're a 20 or 30-something start-up founder, pulled a million different ways, trying to grow your company on a shoe string budget and decide you need to hire another team member; what do you do?

A: Spend all your energy to target potential hires from a demographic into which you have no insight or contacts, that typically wants more reward and less risk than you can possibly provide.

They can most certainly be open to having a diverse team but it's not up to every startup with a few employees to fix the system*

*the opinion of this 50ish visible minority
As the article notes, the CSV part of the pipeline was fine; it only broke after they imported the data to XLS.

One lesson I’d draw from that is to favor simple human-readable text formats like CSV, where they’re suitable for the job at hand.
Your post is so stupid that someone could make a copy-pasta of it, e.g.
"I tried to write a program in C++ but it didn't want to compile, so I spent 90 minutes poking at the code, looking for the error and never did find it. I don't know what the right solution is to this sort of problem, at least for developers.

-------------------

"I don't know how to use Excel (most popular spreadsheet program used for budgeting), thus my conclusion is that Excel is stupid, its users are stupid, while programmers are smart. Next time I will have to make a budget, instead of using Excel, I will create my own program that does the same, but better!"

"And since I will be building this from scratch, I will start with designing the universe"

-------------------

And trying to be constructive: you probably mixed your calculations with data. You could calculate things separately and then just put it into one sheet: revenues with +sign and costs with -sign.
> What should it be based on? Should academics be judged on performance? If so, how?

Thank for the question. It is, indeed, easier to criticize rather than offer constructive suggestions.

Here are my thoughts on the reward system:

- I would like to see published conclusions challenged (if conclusions are based on data observations or empirical evidence). And if the challenge is clean and results are fair, then:

(1) The challenger gets a credit (regardless if the paper they challenged withstood the challenge or not)

(2) The original authors of the paper get credit if the paper withstood the challenge(s).

- I would like to see a different credit system for papers in applied sciences, based on whether the result is accompanied by an implementation. Where implementation is either a working inference system (if this is all based on data), or a prototype. The discoveries that are accompanied by a working, publicly consumed implementations, in my view deserve higher credit score.

In other words, I would much prefer that our academic discoveries are encouraged to build consumable implementations (unlike US Patent law that does not require an implementation of an invention).

-if an published paper or a conference presentation was incorporated by the same team into a patent, I would remove any academic credits received by the team's researches.
In other words, I would prevent double-dipping, if I may call it that. If the given paper is incorporated into a utility patent by completely different people (and it withstood the USPTO scrutiny), then that's ok.

- if a specific field of study is theoretical in nature (eg mathematics, may be theoretical physics). I would specifically reward joint publications, discoveries where
the theoretical subject matter is incorporated into applied field.

- I would include into the reward system books, blogs and article posts that further public understanding of complex science topics (I would apply it for STEM subjects only).
Such that online video lectures, and other forms of free/unpaid public education are specifically encouraged.
I am not sure how exactly to measure effectiveness of this, but I am sure minds, brighter than mine, could come up with a fair, automatically-correcting model.
Thanks for sharing that and agreed, shouldn't be that hard to add to the app.

Interested about the serendipity idea, we have thought about it more from the point of view that user builds the book chapters. Would randomly selecting articles for a subscription type service (say deliver a book every month) make sense to you?
The Android Element client for Matrix has been working really well for me lately. There's a long way to go still, but I think there's reason for optimism.
> A program might depend on a fast timer resolution and fail to request it. There have been multiple claims that some games have this problem (...)

Yup, I wrote such a (small, freeware) game 15+ years ago. I wasn't aware of timeBeginPeriod at the time, but I observed that for some inexplicable reason, the game ran more smoothly when Winamp was running in the background. :-)
Scaling the Team with Infrastructure as Code
Confused about what makes this optimized for QR. Other shorteners such as https://t.ly/ have a shorter domain and they have an extension that allows you to shorten a url then easily share the qr code http://t.ly/extension. They also offer an api etc.
Did you mean Lotus position?