skysight-inc/HackerNews huggingface dataset:
> what, you have to press enter to send? primitive!

Is that really good UX? I want to have a chance to fix my typos and other errors before sending.
Problem is, as the hiring manager you're not going to see the resumes that didn't meet the keyword minimum. You're only seeing the resumes that made it through the filters.
Perhaps from a US-centric perspective. I don't know for a fact if a company or non-person is universally allowed to direct the facility that is the government to do something or not do something everywhere in the world.
Same thing happened at one of the largest employers in the state. They have several entities all with different domains. Now everyone's login is different from their email domain. Even though no matter which domain you use in the To: field, It will still be routed properly.
Looking through this page, it looks like the last mention of 10.8 was 2017. Definitely not safe on the Internet.

https://support.apple.com/en-us/HT201222
+1 - I think they should be able to for sure - with current tooling, this is basically impossible without manually doing it; which I've seen a lot of product folks do!
One trick that often improves numerical stability with computing the sum is to first sort the data.
As yourself how long it took you to do the most similar thing you completed in the past and how long that took. Then without at all accounting for you being more skilled or learned now, use that as a value. It sure beats the everliving shit out of every other estimation method I ever tried, including really extensive planning and prework.
cPanel: there were like 3 different APIs if I recall, and most people had to use API v1 and API v2 together. Neither was feature complete or bug free enough to use independently and it was an insane amount of trial-and-error to figure it all out.

Old PayPal APIs: while generally not many APIs are required, figuring out what ones to use was horribly painful.

Google Workspace: even though our company was large and had account reps to help, sorting through their horribly written documentation and figuring out the APIs was a shocking nightmare. You couldn't help but compare to this to the earlier days of Stripe: awesome docs, great API design, trivial to get sandbox accounts, responsive and knowledgable free support.

Too of often I think these APIs were written by people who had no good fundamentals on what the complimentary side of development life is like as a consumer of the API. Happy to grant that these people were rockstars at solving other problems... but this was NOT strong point.

Even what should be trivially easy (e.g. did the request succeed or not?) required parsing API-specific responses. And if it failed, good luck trying to know why and whether anything could be reasonable shown to an end-user.
I've wondered about this - I have no idea what endorphins feel like. Either I've never experienced the "runner's high", or it is too subtle a feeling to register.

Perhaps it is no coincidence that I don't like to exercise. I am not at all sedentary, but I do physical things because I enjoy the activities (skiing, climbing, hiking, etc) and not because the muscle burn somehow feels good. I don't mind being tired and sore afterward if the thing itself was worth doing. Going to the gym, though - that's just tedious, boring work, and feeling lousy afterward is a bummer. So I don't do that.
Amazon's scientific approach to meeting – and measuring – its climate goals
Apparently there's a new-fangled thing out this year: a human Tax Accountant.

I'm a little ahead of the curve, I've been using that system for decades.
Alternatively, face masks are this much more effective at blocking much-larger virus particles.
> If the government built a train station on the middle of the trail

I don't understand why people are so deeply muddled about this.

There is no train station.

It's for bridges over the railway in the middle of nowhere, far from train stations, along country footpaths.

You cannot traverse the footpaths on a wheelchair, so you cannot even get to the bridge in the first place.
> no company has stayed at the top of the S&P500 for very long

Microsoft, Google, ExxonMobil etc. seem to have done OK.
I wish I knew more about meteorology. It must be incredible (and maybe a little harrowing) to be in that profession these days.

Does anyone have any idea how this heat wave will conclude? Does all that energy just fade out into a nice polite rainstorm, or should we expect something more dramatic to cap it off considering the unprecedented circumstances?
It was very bad in Seattle, most building AC systems couldn't even keep up with the load. Lots of wildlife certainly died, there were so many heartbreaking posts about finding dead cats and birds.
These subjective questions are pointless to try and answer.

The idea is that a future person could freely deep dive through a rich well indexed history of media about whatever specifically interests them

I wish people would stop trying to assess the value of a given piece of media and just tag and archive the stuff.

For instance, high quality footage of live music from 100 years ago would be very interesting to some.
Perhaps in the same way the civil engineers signal to south Florida condo boards that their buildings are about to collapse? It's the same problem, really. Collective action by a political body controlled by older people who are trying to just hold on to their wealth until they die is impossible. We need new political structures to write down the capital loss on all the junk we built in the 20th century that has no purpose in the 21st, and the political will to tell a handful of people that yes your underground mineral rights are being expropriated.
In particular, a sufficiently advanced business looks like an undemocratic, authoritarian, central-planning government. Basically, the problem with large corporations is that they are communist dictatorships.
Sorry, I should be more cognizant that not everyone's English is perfect. Yours is far better than my Cantonese!
That's not how it works, though - you never deal in terms of individual team members. The team is the unit of delivery. Otherwise you end up with people who should know better putting more people onto teams to "help".

Teams above a certain maturity level do often settle on a certain number of delivered tickets per month, and when you're looking at that sort of resolution, dependency problems and other factors like those you mention are represented in the data. It's not so much a measure of how productive the team is, it's a measure of how much work the team can get done embedded in the organisation they're in, which covers off their ability to resolve blockers and communicate with other teams.

There's a very different cognitive framing if you count tickets, too: you're not saying to the team "come up with a number, you're going to get shouted at if it's wrong, and you've only got 10% of the relevant information to hand", you're saying "do your usual design process, and we'll use the output to make a projection based on the history." Functionally it might be equivalent to "can estimate accurately" but it doesn't work like that when you're the one in the hot-seat.
A margin of error of 13.8cm in current 3D scans of human bodies? I think their baseline is bogusly large.
Yeah, this is the only thing that practically worked, in a complex product I used to work on.

- If you ask the devs to do QA, you'll get no bugs other than the ones they already caught during testing and deployment.

- If you have a mostly independent QA team, they will find somewhat silly/trivial bugs like the login page not working in an extreme edge case scenario.

- However, when you ask your Product team to own QA, you get the real good stuff - "Why does this feature not actually work well with this other feature when you combine the configuration" etc. It's great!
Firstly, this fine was issued by FINRA, not the SEC. Secondly, which laws did they break exactly?

This is a substantial fine for the scope of violations that were being investigated, as this has nothing to do with any of the gamestop restrictions earlier this year but their messaging, outages and vetting of customer expertise during 2018-2020.

It boils down to a $70M fine for not having a high avilability system, being bad at explaining trading concepts and allowing people to take risks that other banks would not. That's quite a reasonable amount.
Nah, BEAM is not suited well for that. It has a big startup time. BEAM is designed for long-running daemons, not "wake up, do small amount of work, get shut down".

For something like this I'd choose Rust or OCaml due to their insanely fast cold startup time (if the program is a CLI tool).

Erlang/BEAM is not there yet and it might not soon be.
Bits?
Alondra Nelson Wants to Make Science and Tech More Just
You're right - not the best analogy in this case. Not sure about the race car though. I will think about that. Analogies aside...

Let's agree that estimation is possible to a certain degree. We know this and accept the inherent uncertainty.

Modern project management is whole sale copied from industrial construction and manufacturing. It seems no one stopped to ask whether the same logic applies to software creation. And it doesn't.

The business side of IT is stuck in a mental model build on construction and manufacturing. Yet the process of creating software contains neither of those concepts with the exception of automated build and deploy (and costs for those are negligible).

It is also interesting that no distinct vocabulary for software exists. We build, deploy, construct, have factories and so forth. Again copied from disciplines which are complicated - but not complex.

It is not possible to obtain the information you refer to by analysis. That's a property of a complex system. Analysis of parts neglects the interaction between parts and in software more or less everything is connected.

This is one of the reasons why we cannot forecast weather and why we cannot reliably estimate software.

Now, if I start my explanation this way I'm also sure to lose their attention. So what do we do? Which intellectual approach will captivate these people, retain their attention and at least plant a seed of doubt in the established way of working?
The whole "companies get political speech through untold millions $$" makes lobbying more like a quid pro quo bribery system. Its fine that companies have a vested interest in how the gov't runs and policies are put forward but the bastard child of "political speech" and capitalism is IMHO a lot like corruption. Obviously my opinion is not original and a lot of people talk about this... but lets not forget how this works.
The level of effort and personal commitment necessary to commit your life savings toward starting your own business vs. putting it all into meme stocks isn’t even remotely comparable.

One of these can be done in ten minutes from your couch while stoned with a handful of clicks. I’ll leave you to guess which of the two it is, but suffice it to say that’s the one I think should have some additional guard rails.
PRs are perfect in open source . In companies they’re just an illusion of minimising risk.
Weird, it was the opposite for me. Went from 60 hours in consultancies and low tier to 30ish at FAANGish. Remote probably helped with COVID, but the output is consistent.
When you scroll tho y the end of the reviews they have a link that says something like show reviews from other countries. If the reviews for different versions worked this way it might cut down on some of the version scamming.
It's even worse - if you don't opt-out of the data sharing, they have an absolute field day with all your financial data.

They soak up a lot of the tech talent in San Diego, and every person I've met that works there on the TurboTax team has admitted to me that they feel ethically torn about what they do.
it's already happening:

https://mobile.twitter.com/JimBair62221006/status/1354175511...

I don't understand the downvotes. These tweets are documenting record droughts/floods and crop losses in the last year and people are dying of starvation and the numbers of people starving will only go up.
A breakthrough in neural network explainability with counterfactuals?
That looks like basic filtering by z score

Someone should also try median filtering, would that be considered another breakthrough?

Edit: just read the code, they also filter by the distance to the median.
The Matrix!
It'd be cool if counter-points to a principle could also be documented alongside it. Reasoning that highlights why you may not want to adopt a principle is helpful when considering it.

For example, take "One single source of truth".

>Data should be held in one location, duplicates of that data should be by reference only.

>Why

>Changes to data are always propagated to the rest of the system.

>Mutations to the data need only happen in one place.

>Single source of truth means no data will be out of sync or fail to be updated.

>How

>Only allow data writes to happen in one location. Whether that be a call to a rest API, system call or other write actions.

>Don't allow data to be stored anywhere but the single source of truth.

That won't work in many situations. If you need to support high throughput OLTP use-cases but also want to support advanced filtering/sorting of large datasets, you may need something like a combination of a NoSQL DB with something like ElasticSearch. Eventual consistency is something you accept as a trade-off for enabling higher levels of performance.
I'm not celebrating people dying of thirst, but I also think that's the only thing that will get the world properly focused on the issue. We need to make big structural changes to the global economy to fight climate change, and those changes are going to have an outsized negative impact on today's wealthiest and most powerful people. They aren't going to let change happen without a fight.

People dying is what it's going to take to muster up enough of a fight to make the actual change. But the sooner we can hit the panic button and get people focused on the magnitude of the issue, the less people that need to die to get the population properly motivated.
These folks are serious and they just raised 30 million to provide vast quantities of cheap, desalinated water:

https://www.terraformation.com/

Seems crazy now, but vast forests covering most of Algeria may be entirely possible in your lifetime.
He was the president, he cannot be the target of misdirection. The last president needed the media in a symbiotic relationship. Something to rile against. In form he spoke badly about MSM, but in practice he needed them just as much to stay relevant and have something to rebel against.

Yes, media need the clicks, but that’s portraying it wrongly imo.
Lobbying isn't directing the government. It's presenting your point of view to the government. What the government does with the information you give them is then up to them but sometimes they're obligated to show they've considered it. It's a super-basic part of democracy everywhere. It's usually a right and also actively encouraged through consultation periods while legislation is drafted.

I can't understand anyone suggesting that we should not be allowed to present our opinions to the government. What are you in favour of? Just voting once every four years or so and never saying anything else the rest of the time? Bizarre.
I totally agree. Just note that heat (higher than average temperatures) doesn’t necessarily translates into drought (the absence of precipitation).
My thinking definitely aligns with yours on this:

> if you're making significant changes to a unit of code anyway, clean it up or rewrite it; otherwise, make the smallest change necessary and leave it alone. If it ain't broke, don't fix it.

Don't be afraid to rewrite something when it needs it, and build knowing it's very possible you'll rewrite later.

If there are good unit tests, and it's a sufficiently small/decoupled piece of code, then rewriting is not so bad. These are all self-reinforcing things: small, decoupled code tends to be easy to rewrite; Testable code tends to be decoupled.

Systems always get more complex over time. The key thing is figuring out when your simple component is starting on the path to getting too complex, and taking the time to rewrite it as early as possible -- maybe it should be two smaller components, or maybe the entire organization of that are needs to be different. If you wait, and just keep adding "small" things, eventually you have a monster that's an order of magnitude more complex to deal with.

The other bit of this is writing code knowing you can (and may likely) rewrite it later. If you try to predict the future complexity early in design, 9 times out of 10 you will get it wrong, and you'll end up in a lose-lose situation: you have a overly-complex component to deal with, and it ends up needing a rewrite later anyway. Rewriting this is even harder because you have to undo the unnecessary complexity. This is also known as YAGNI ("You Aren't Gonna Need It").
Archive.org has OS Retail DVDs for at least Tiger: https://archive.org/details/macosx10.4tigerretaildvd

But this is awesome! Lots of old photo software will no longer run on modern MacOS
At my previous company I administered a Microsoft 365 setup shortly after they switched over from an on premises AD setup with mixed results.

One bug which stuck out was trying to sync sharepoint directories with a length of over 255 characters locally on a windows machine with onedrive.

In Sharepoint you could create such directories and put files in them no problem through the webapp, but try to open a spreadsheet from the directory within windows file explorer and it would fail to open due to windows 255 character path limit.
There always has to be a ruling class according to Orwell. But that isn't a bad thing necessarily, and i'm sure that any peasant from any period would happily sell his left arm to enjoy the privileges we all enjoy.

>Now I know what it felt like to live during the dark ages.

really?

>Massive hypocrisy all around.

Hmm. (i'm not attacking you personally, i'm also a terrible hypocrite, but trying to put things into perspective)
You being the operative word, as in 21st century, patents are the definition of holding up progress.
Same in Vancouver. The hotel I stayed at couldn’t get the room to go below 25C - about 80F. Extremely uncomfortable, albeit better than 95F outdoors.
They did not announce anything - this is just clickbait trash.

In November 2020 Elon said this "In Europe, it would make sense to do a compact car"

If HN wants to run with this as a June 2021 announcement of a $25K hatchback go for it, but there has been nothing of the sort announced, this is just conjecture on old tweets.

Some kind of SEO optimization I think to do "just announced" - seeing it more lately so it must be working.
> Your argument is a cogent one for why Erlang is not great if you only care about parallelism. Being able to scale a program to use 20 cores is no good if the same program written in another language could beat the pants off that program using just one core. However, that is an independent concern from concurrency.

I think this sells it short. Serious software has to cross machine boundaries at some point. There are pieces of code and styles of writing them that work really well on one core. They may also do okay on one machine. But once you have to go to two machines they become a huge burden. A liability.

Part of the way people like IBM used to make tons of money was off of people who had software that could not cross the one machine threshold. They sold really, really big machines. They sold unobtanium that let you continue to scale your one machine vertically. Like $20,000 hard drives (1990's dollars) that were essentially battery backed RAM, meant for things like putting your WAL on to speed up transaction commits per second.

Speed doesn't mean much if it's taking you in the wrong direction.
"touchscreen focused control system" is misrepresentative when the driver is mostly expected to control everything from the steering wheel.
This is a consequential article. Does anyone know the source, Bradley Kuhn or the Software Freedom Conservancy? The names ring a bell.

> We expect that you may be surprised by this, but we can tell you that: in private, companies that contribute to key copylefted projects are not so subtle. They have communicated to those of us in the GPL enforcement community on several occasions — a message delivered by many executives over a period of many years — that they would prefer both Conservancy and FSF to curtail, or outright end, GPL enforcement. Their view, as communicated to us, is that GPL enforcement causes customers to think copyleft is problematic. As one executive once said to me: “We consider it a failure if any customer ever even asks us if they have to worry about GPL compliance”.
You should pull the PR you're reviewing down into your IDE and you should spend like, an hour reviewing it carefully and trying to break it. Have a mental checklist: say they renamed a function ... is the file named the same as the function? Did they remember to rename the file? Did they delete parts of the code? Did they remember to delete everything related to that? Often the most challenging parts are negative: it's harder to remove properly than it is to add new things. Say they changed the validation on a model: is this going to work well with the production database? Do we need to write a migration to catch the database up to the new reality of the code? Automated tests are just automated warning flags that give you confidence that the codebase is basically hanging together. You still need to be very careful & thoughtful as you're making changes.

I like to actually reset the branch so I can see all the raw changes in my IDE, this helps me to think it through, in git you can do this via:

git pull feature-branch;
git checkout develop;
git checkout -b my_initials/feature-branch;
git merge feature-branch --squash --no-commit
One of the more compelling geoengineering strategies I've seen discussed has been Olivine weathering:

https://en.wikipedia.org/wiki/Olivine
Even an Earth ravaged by big rocks and volcanoes would be much more survivable than Mars in its current state.
Technarte Call for Proposals
Different websites (such as https://ivmmeta.com/, https://c19ivermectin.com/, https://tratamientotemprano.org/estudios-ivermectina/, among others) have conducted meta-analyses with ivermectin studies, showing unpublished colourful forest plots which rapidly gained public acknowledgement and were disseminated via social media, without following any methodological or report guidelines. These websites do not include protocol registration with methods, search strategies, inclusion criteria, quality assessment of the included studies nor the certainty of the evidence of the pooled estimates. Prospective registration of systematic reviews with or without meta-analysis protocols is a key feature for providing transparency in the review process and ensuring protection against reporting biases, by revealing differences between the methods or outcomes reported in the published review and those planned in the registered protocol. These websites show pooled estimates suggesting significant benefits with ivermectin, which has resulted in confusion for clinicians, patients and even decision-makers. This is usually a problem when performing meta-analyses which are not based in rigorous systematic reviews, often leading to spread spurious or fallacious findings.

Concluding, research related to ivermectin in COVID-19 has serious methodological limitations resulting in very low certainty of the evidence, and continues to grow. The use of ivermectin, among others repurposed drugs for prophylaxis or treatment for COVID-19, should be done based on trustable evidence, without conflicts of interest, with proven safety and efficacy in patient-consented, ethically approved, randomised clinical trials.

Source: Misleading clinical evidence and systematic reviews on ivermectin for COVID-19; https://ebm.bmj.com/content/early/2021/05/26/bmjebm-2021-111...