skysight-inc/HackerNews huggingface dataset:
I know from experience that working at an outpost of a company run from another country can suck unless communication and direction are very clear.

Whatever the company may have said about assurances that their jobs are safe, making people in Australia redundant, moving production to the US and hiring more people in the US sounds as if thats the direction the company is heading in and the jobs in AU will be less interesting and eventually eliminated.

Retention bonuses and salary may help, but letting them know what the AU team role will be (why is it being kept rather than moved to the US). Will they have autonomy or ownership of something or just passed overflow work from the US?
You think the average person does less than one financial transaction per day? O_o

I mean, sure, not everyone is out getting a coffee every morning, but that strikes me as roughly an order of magnitude below reality.

Let’s say, shopping three times a week, with 5 transactions per shopping trip; that’s already an average of 2 transactions a day, but worse, since it’s clustered in small time intervals.

How do possibly get 0-1 transactions per day per person?

That’s.. a society where people don’t use money. It’s not a thing.
Why did you quote what I said that has nothing to do with it?

Do you have a better solution?
N.K. Jemisin Will Be Adapting (movie version of) 'Broken Earth' Trilogy Herself
If you essentially have one live version of your program, like you do when it runs on your servers, coupled documentation is probably a good idea.

If you have multiple active versions, like you often do with software released to run on someone else's machines, coupled documentation "works," but has a big downside. Namely, it prompts people to "refactor mercilessly"/change everything all the time, together with the documentation.

When you need to maintain multiple versions at a time, having a single version of the document explaining the differences between all the live versions can somewhat curb the enthusiasm for gratuitous changes (since whoever does the changes must also maintain the increasingly long and ugly description in the single document describing all the versions.) And someone needing to work with all those versions has these differences nicely laid out and those areas not having differences also clearly visible. Whereas with multiple versions of the document you need to "diff" these versions if you want to build a mental model of what changed.

Sadly (for those agreeing with this), I presume that the above is a minority opinion.
Maybe Windows is just following the footstep of macOS and Android. Even OSX doensn't last forever, macOS crank it up to the 11.
I'm adamant that the documentation for a project should live in the same repository as the code itself. This is crucial for a number of reasons:

1. If the docs are in the same repo, a commit that changes the code can update the relevant documentation (in addition to the tests) as part of the same unit of work

2. This means it can be enforced during code review: if a developer forgets to update the docs they can be reminded before they land their PR

3. This also provides a version history for the documentation which is synchronized with the code history. This is really useful when looking at history and trying to figure out what changed when.

4. This also works great with branches, PRs and releases. New features can have their documentation developed alongside the code in a branch, which makes it easier to understand a proposed change. If your software is deployed in multiple places as multiple versions (or even just staging vs production) you have a way to view the correct documentation for each individual deployment.

5. Added together, all of this builds trust. A common problem I've seen with internal documentation is that no-one trusts it to be up-to-date. Making it part of the regular code development lifecycle can fix this.

6. If you do this, you can write automated tests that enforce aspects of your documentation! I call these documentation unit tests, and wrote about them here: https://simonwillison.net/2018/Jul/28/documentation-unit-tes... - even something as simple as a test that fails if a new API endpoint isn't mentioned in a markdown file using simple string matching can ensure no-one forgets about the docs when they add a new feature.
If it's technical docs for developers, you'll get more bang for your buck by making executable documentation first - tests, deployment automation, build automation. Make it so that to do 1 logical action then there's only 1 step needed.

How do i build this? Run the build command.

How do i test this? Run the test command.

How do i run only the unit tests? Run the unit test command.

How do i start this locally? Run the start-local command.

How do these components interact? Run the contract-test command.

...

That fixes "reference" type docs better than any reference doc but there's still a place for technical guides around a code base but short screen recordings voiced over by an experienced dev on the project navigating their IDE will beat any written guide on any metric (time to write, usefulness etc.)

If it's customer facing docs, treat them as code and host them inside the application in some way. There's few things worse than reading the wrong version of a doc.
1) Fix public transport so gridlock is lessened
2) Fix housing regulations to increase supply
3) Fix open concept offices so that people have diversity of work environments are the office and allow people to work from home some days
None of this sounds shocking.
I'd be interested to hear more. Specifically, how did you keep the remote folks in the loop with conversations that happened onsite?
One thing I rarely see discussed anywhere is that a corporate tax is essentially a subsidy to existing companies and is anti-capitalistic.

The reason is that an existing corporation turning a profit can tax-free reinvest their profits in, for example, product development to improve their market positioning and profits in the future.

If they were to book that profit and pay it out as a dividend to their owners, who would then invest it into other companies, the money would get taxed twice before ending up in the investment target. The first time as a corporate tax and the second in the form of a capital gains tax on the owners.

Intuitively, it seems like this could have a significant effect on markets and might be one of the reasons we see so many markets dominated by big companies, even in non winner-take-all markets.
Also, the nattering nabob of negativity is important in reminding people that prioritising the thing that probably won't work or is difficult to make work has the opportunity cost of not prioritising things that will work. Sure, the negative voice might occasionally deter you from finding an incredible solution, but the positive voices about ambitious ideas are always deterring you from focusing on fixing other stuff.

I view my lack of success as the "that don't won't work" person in one role as the reason why we had a number of half finished products that didn't work or didn't sell. At least if a team agrees to try something that probably won't work because the rewards are so huge (or the implementation is easy and it's just the results that are questionable) they've thought about the resources needed, and won't either give up at the first hurdle or plough far more into it than it'll ever be worth.
Yes that's true. I had JavaScript on.

I agree that turning on JavaScript with Tor is risky from a security viewpoint. It significantly increases the risk that your real identity may be unmasked.
Risk, Ambiguity and Decision & Doomsday
> if your users are untrusted and not under your direct administrative control (e.g. students in a dorm, hotel guests, et c) then default-allow-everything jeopardizes your upstream transit connection (e.g. if they start spamming).

How is that different from an ISP? Or do you think ISPs should also block everything except TCP ports 80 and 443?
This need more upvotes lol
Poor eels.
ScanScore Sheet Music Scanner Review
I also interpreted the post as arguing PoS is more censorship resistant than PoW.

I regularily receive a silly critic, which I always take the time to debunk, and then often get told "it was joke.. come on".

We live interesting times.

Edit: Not questioning the honesty of the author, the clarification is legit.
Well he basically admitted it. But if y’all want to suck him off, fine. This place is overrated anyway.
The paper An early Miocene extinction in pelagic sharks [1]:

> We present evidence for a previously unknown major extinction event in sharks that occurred in the early Miocene, ~19 million years ago. During this interval, sharks virtually disappeared from open-ocean sediments, declining in abundance by >90% and morphological diversity by >70%, an event from which they never recovered. This abrupt extinction occurred independently from any known global climate event and ~2 million to 5 million years before diversifications in the highly migratory, large-bodied predators that dominate pelagic ecosystems today, indicating that the early Miocene was a period of rapid, transformative change for open-ocean ecosystems.

[1] https://science.sciencemag.org/content/372/6546/1105
Citation very much Needed.

Magnets only lose their magnetic powers very slowly. For example, samarium cobalt magnets might decrease their magnetic strength about 1 percent over a decade, which contradicts your claim.
Bitcoin: El Salvador plans to make crypto-currency legal tender
They didn't bother to set up an HMRC approved scheme?

Where these US companies? employee share holders in the USA really get screwed
Is there an equivalent for inland cables.
> the very expensive Pt-Ru coated cathode

The Pt-Ru is just a catalyst, no? Maybe it gets contaminated but it would hopefully be recycled. Might even go up in value over time rather than be consumed.
I like the general purpose GC languages like Java JS c# python lisp for most tasks though, and then go with something a bit wilder or low level like Go Haskell Rust Erlang c++ c when needed. Or R/apl for a mathy problem.

Since I enjoy high level programming and the natural experience chicken/egg I never do the low level stuff. Not since Acorn Electron assembler! But I know of it.
It seems to me there might be some conflating between 2 points going on in a lot of places:

Whether or not something will work in absolute technical terms.

Whether or not something is a good idea within the current business context.

Quickly distinguishing between which conversation you are having can moderate the discussion. I am prone to assume we are having the first conversation, which can occasionally cause friction with the business stakeholders.
Australia had similar with https://www.myhealthrecord.gov.au/ a few years ago. At the time you had to opt out iirc. At least apparently you can opt out at any time and your records will be permanently deleted.
How can you even know or assume any of this? What evidence do you have?

Snapshots aren't special magic from NetApp. Windows, HP-UX, LVM, and VMware have snapshots.

I think you're stuck in religious reverence for all things NetApp. Good luck with that.
Holden's Lightning Flight
I don't think people are used to following the rules anymore. Not when they themselves have to check. People like automatic control systems. In this case, something that bricks the drone if it goes across the fence :) (But that's just my tongue-in-cheek solution).
Cloning DARPA
Can you elaborate on the ground cable? I mean as shielding it should work regardless of what you described here, right?

And regarding voltage between these two points, why would it be so high? And wouldn't it go down to 0 quickly after connecting the cable?
If you plug yourself to nearby nuclear plant, I guess it's possible to make electricity much cheaper, as long as you can plan your energy consumption.
That won't help prevention.
That wasn't the comment I was responding to was it. my comment was about Spanish and Latin Americans in denial about racism and their colonial past
Science in flux: Is a revolution brewing in evolutionary theory?
Programming is like the universe. There are parts of of expanding faster than I can ever learn so are unreachable even with unlimited time.
Were you not aware that the Indian government threatened social media platforms that allowed users to identify a variant as the 'Indian variant'?
> Nvidia GPUs are still the number one problem. Buying anything with Nvidia in it is a waste of money. Closed source binary drivers that only work sometimes is acceptable for gamers but not if you want a reliable, controlled machine.

No it's not a hardware problem, it's a pure software / platform problem. The experience is phantastic on Windows. The reason why I went with Windows 10 base and Linux VM & WSL2 (which is pretty seamless) instead of vv is that I did not want to spend time caring about Optimus, PRIME and having to consider the dGPU/iGPU mux topology in order to get my hardware to work correctly.
What do you mean by "baking"? Google is unhelpfully showing me results about crypto currencies and how to literally bake coins into a cake.
It also appears to render footpaths in parks etc, which makes it look a bit weird in places - the monochrome rendering made it hard for me to find locations and the landmarks I am used to seeing (i.e. major parks and green space) were hard to find as they had "roads" criss-crossing them (when they don't in real life)
> Based on moral axioms, abortion is human right

Based on the moral axioms you’ve chosen. Axioms are, by definition, unsupported and unsupportable.

> Unless your moral axioms are fundamentally flawed, which is what I’ve described above.

No, what you described above was belief that was “religiously motivated, or based on non- religious logical fallacy.” Axioms are the roots from which logic works, they aren't based on logic, fallacious or otherwise. And there's no reason moral axioms that conflict with abortion need to be religiously motivated, either.

Sure, you might view any moral axioms thst disagree with yours as “fundamentally flawed”, but that doesn’t salvage your earlier description.
I believe this to be one of the success stories of my programming language, MethodScript[0]. Early on I made the strange decision (in the sense that I’ve never seen it elsewhere) to make the documentation for each api element be part of the code itself. The documentation generator is part of the code as well, so every single build of the software is capable of generating bespoke documentation for that exact version. The website simply hosts the newest version, but you can always generate your own locally.

Of course I also enforce that contributors must add/modify documentation at the same time as the code, but that’s easy, because if you modify most of the code, the documentation is also right next to it.

[0] https://methodscript.com
People died in police bombing of activists' house (1985)
Dahomey Amazons
Cats are living things which we have a special relationship with, drones are not.
Some culture value life more than things, so unsurprisingly it'll be easier to propose a ban things than the eradication of cats.
I wonder, what's the cost of lithium in battery making?

I've seen a video of how smartphone batteries are made, it's pretty advanced...
>force that on a laptop

They said: "personal computer", which could easily have 2x GPUs and 16+ cores. Heck, laptops nowadays can have a pretty good discrete GPU.

Using password grade hash with a =nonce= is absolutely no way to be accomplished per each request. The nonce would have to be the same for multiple uses - hence NOT a 'nonce'. The sharing of the said non-nonce would require a form a replicated Map (or IP-sticky processing with a local map). It's rather convoluted solution for absolutely no benefit as it's still not hard to brute force.

Storing it in such a way - slow hash + salt yields no benefits for debugging either, so I wonder why would you do so? Password hashes are useful for proving a match with an unknown plain text (while making it expensive to brute force) - so what would be the exact purpose of having non-nonce+IP?
She gave a great talk recently: https://www.youtube.com/watch?v=4lx9Wtd2P48
If I had an interviewer try that on me id hang up.
Doesn't make it any less effective for the good guys.

Some software include so much freedom that it actually hurts users. Now the idea isn't to take away any freedom but rather somehow steer users into using the software correctly.

I like to think about this advice in terms of "expert mode"--if you are regular user I am steering you into safe behavior that you probably expected, but if you are an expert I give you the freedom to do whatever you want to do.
An example of how to do this is the documentation for the PHP framework Symfony. Code examples from the documentation are run in the CI server. If a pull request breaks a code example, then that example must also be fixed as part of the pull request.

That's a fantastic feature for a popular open-source framework, as it means the documentation remains up to date.

I'm not sure at what point it's worth the effort for an internal project, though. If you have a cultural problem with incorrect, out-of-date or missing documentation this could make things worse. I'd look for the root cause of that first (training, motivation?), before trying to enforce it with technology.
As the article mentioned the meaning of OOP changed over time. Alan Kay has a description of OOP that sounds like the actor model used in erlang/elixir or mq and consuming services elsewhere.
How ‘One Hundred and One Dalmatians’ Saved Disney
I'm a fan of having code samples in the documentation, and making sure (at e.g. build/test time) that those samples actually work. Given the headline, I thought the article would talk about this, but it's more of a general "why and how you should keep your documentation up to date".
Extracting from the sea might be more ecological than mining.
If they truly are lists (i.e. not random access) then nothing will give you that. If you have the head elements of the lists and you want the median then you have to traverse (m+n)/2 elements just to get to the median. There is no way around that. If you translate the lists to arrays then that’s an o(n+m) operation in itself.
Prosecute anyway.

> Frightened terns abandon 3,000 eggs after drone illegally crashes on beach

(original title of article, emphasis mine)

Was the crashing illegal or was flying illegal, or both?
Isn’t Lithium an anti-depressant? If it’s extracted from drinking water, won’t you end up with miserable people?
California Approves Pilot Program for Driverless Rides
If you are 30ish now, you will be 40ish in 10 years. Might as well develop a new skill or two. Though I completely agree that it should be something you are truly interested in.
A decent microphone and interface should not need muteing
They include selling the H and Cl gases also produced to bring the net cost down to $5.
How do you read the in-repo documentation? Search for all files named readme.md? I have never learned about a library from documentation scattered about the repo. There's the readme at the root, and everything else is on a web page, which is a better way to organize and browse documentation.
>(bcrypt maybe?) but I don't know if it's a very good idea

b/scrypt and all other password grade hashes are slow on purpose but they are slow per each use. Imagine the processing takes 0.1s (which is on the low side of hardness) per each request - you just killed all your servers w/o any designated DoS. If you abandon the nonce and use the same salt multiple times (so the computation is amortized), it'd take a replicated cache of IP->hash and even then it still doesn't accomplish much...
> The whole point of terminal programming is that you live within the abstraction which is the terminal

I really fundamentally disagree that there is a "whole point" to terminals (or any other kind of things we use when we use computers). They are just tools which are able to perform things and one should really not ascribe any kind of semantic layer to them, as this is always a very very brittle abstraction. Just look at things in terms of what they are able to do, not what they are called.
The idea is that when the cheap lithium is no longer available, this becomes the only viable alternative.

I remember in 2005 my earth science teacher told me "shale in north dakota will never be viable with all this saudi oil lying around"
In the UK if an individual gets paid with a loan, then have to repay it within a tax year or otherwise pay tax on it as if it was regular income (disguised remuneration). This has actually been applied retrospectively and drove many people to bankruptcy.

Why this cannot be applied to transfers between companies if they are related?
I really appreciated your composure in not calling GP an idiot. I'm not sure I would have managed to be been so kind.
I would assume they will go away pretty fast because of power usage.

SSDs are currently targeting performance because of the cost, but it seems possible to make them even more (and much more) power efficient when used as high latency storage.

For enterprise servers (I'm aware they are not relevant for AWS/GOOG etc), more and more often high-end machines are offered as SSD-only - for such price bracket SSDs price is already not an issue.
Can you blame people for getting fatigued from this kind of news? (Also it's been 16 years ;) )

Every 6 months there is a new use of graphene that promises 10x something, new cancer treatment that is revolutionary, new AI that can solve the worlds hardest problems ...

https://en.wikipedia.org/wiki/The_Boy_Who_Cried_Wolf
When are they going to make one of these with a Ryzen?

It seems Ryzens are really rare among higher end developer laptops. Is there a technical reason or is it just Intel using their clout to block the major vendors/oems from using AMD?
JS isn‘t a general purpose language, even though is has been shoehorned to be one.
Google Maps and Flutter based web apps are some big users of WebGL. Also Unity based web apps/games. 3D visualizations are a thing too but not sure if they are that popular.
Prosecute until it helps. People should be afraid by just having a thought of doing something like this.
i'd say that it depends on how you stock them once they're powered off.
It feels to me this analogy is rather weak.
Presumably, the point of semilattice (compared to tree) is that the hierarchy is not top-down but can have branches up and down.
I'd say the algebraic structure of joins and meets is not really natural here… it's just some form of graph.

Open to counter-arguments though!
Fantastic, do you have any idea how to solve this challenge?
I use documentation systems that publish the documentation from the repo to a website. Most of my projects use Sphinx and reStructuredText for this, but I recently tried MyST (Markdown for Sphinx) and I like that a lot.

Some examples:

- https://docs.datasette.io serves documentation from https://github.com/simonw/datasette/tree/main/docs - which has documentation unit tests here: https://github.com/simonw/datasette/blob/main/tests/test_doc...

- https://sqlite-utils.datasette.io/ serves from https://github.com/simonw/sqlite-utils/tree/main/docs - unit tests here: https://github.com/simonw/sqlite-utils/blob/main/tests/test_...

- https://django-sql-dashboard.datasette.io/ serves from markdown in https://github.com/simonw/django-sql-dashboard/tree/main/doc... - I don't have documentation unit tests for that yet

Those three are all hosted on https://www.readthedocs.org but I've also used this trick on web app projects that host their own documentation deployed as part of the build process.
Please tell us how exactly the candidate insulted you!
I’ve heard about this idea in a form: «All models are false. Some are useful.»
It would be a breakthrough for vehicles, but not necessarily for the electrical network.

Batteries still have a lifespan, their manufacture emits CO2, and they need to be disposable or to be recycled.

Nuclear is still the best energy in terms of carbon.