skysight-inc/HackerNews huggingface dataset:
The origin of the "standup" is just a regular daily coordination meeting - like thousands of organizations have always had.

Ever heard of a "morning sales meeting"? They've existed for decades - short, to the point, 15-20 min. No one's ever heard of scrum in sales meetings. This kind of thing exists in hundreds of other businesses as well.

Much like everything else in scrum, they are just trying to take credit for something people already did - so they can package it and sell it back to people as if it were a novel idea.

There's nothing new or special about scrum - except a reduction in productivity because of the additional overhead and meetings.
Damn ... I never thought of it! Mental illness and addiction must be the cause! living in a homeless encampment might be the best solution for mental illness! How foolish to think that being homeless might drive someone to become addicted!
Yep. I was told very recently by someone in a position to know that "everyone does that, didn't you know?" No, I didn't.
Pardon my ignorance, but it seems like there should be standard ways of irrevocably anonymizing data and reversible means given a private key.

Off the top of my head, only the latter is necessary if throwing away a random key for the previous to be equivalent (or run the plaintext through SHA-3 20 times in feedback instead.). Say 100 rounds of AES-256 in feedback. Fixed integer-only fields could be XORed with a private key of the length of the field (OTP).

Any other ideas, please add a comment.
It's definitely brute force, in that it's the equivalent of printing a document onto paper and then scanning it back in. This "flattening" is highly effective at sanitising, but also removes all the semantic content in the process; the output should be several times larger than the input (and if it isn't, then it's an indication that something very suspicious was in the input....)
We actually allow you to plug in any existing model (including your own). So we should be able to support AllenNLP as well. happy to chat further!
I very rarely go back more than a month or so. Very occasionally I have gone back 10 years but only for the weirdest problems and to get a sense of what the person was thinking when they added that code. I think I could live with just 6 months of history, and in most cases 30 days and never have a problem.
Isn't 1-2% significant for an employee that also gets a market-competitive salary & thus takes no risk? How much did early employees who joined amazon in 1994 or google in 1998 get?

IIRC the "rule of thumb" is that the first batch of employees share 10% of equity, the next batch get 10%, etc but each batch is much larger than the previous (e.g. from <10 to 10s-100s to 1000s).

So as an early employee you'd get a single-digit % but if you come in the next phase you'll get permill(s) & later on even less.
I worked for the "Canadian JPL" back in the previous "climate change" panic, "the ozone hole."

Even though it was a government agency, working at a national lab felt even more productive than the private sector.

The reasons are that the departmental leadership is 100% done by research scientists who are ruthlessly efficient at doing science and writing papers about them.

My department had approx. 4 senior scientists, a computer hardware engineer, a payload engineer, a CNC technician, a sysadmin, 2 technical consultants, and one administrative staff.

We did custom payloads for the Shuttle, balloons and rockets which did atmospheric measurements. The software was primarily custom in C for telemetry and HP Basic/etc. for plotting.

I highly recommend working for a national lab for a couple of years. Besides an unlimited budget, it's great having a sense of mission.

Factoid 1: We used Fidonet to copy data from launch sites to the lab for quick turnaround and to ensure the instruments were functioning and calibrated properly.

Factoid 2: Since this we pre-WWW, sample source code was often hard to obtain. So we had the world's shareware on a single optical disk with an index file so people could find sample code.

Factoid 3: But since it was a national lab, if we needed, we had access to SOTA civil and military systems that came with source code. I was familiar with those systems, but we never needed them while I was involved.

https://en.wikipedia.org/wiki/Ozone_depletion

What was more tractable about studying the ozone hole than climate change was that we could make direct observations and reducing CFCs had a fairly immediate effect. There wasn't an issue with "ozone hole deniers."

To see the lab's papers, do a scientific search for Dr. Hans Fast and his co-authors.
>I think the guy running the place matters more than the franchise name these days.

More to the point, most Starbucks in the world, other than kiosk ones in larger establishments, are corporate-owned. So Seattle's decision to open all Starbucks to unlimited loitering and bathroom usage affected all of them, leading to what people are discussing here.

Less than 10% of McDonald's are corporate-owned. Franchisees, whether owning one or a hundred stores, are much more focused on the bottom line and less willing to tolerate homeless people driving away paid customers.
Since progressive JPEGs are displayed while downloading and the connection could just be closed at any moment anyway ... I don't think that'd be a problem. Whether that's more efficient than an extra thumbnail is probably the more interesting question.
Odd question. Why would a webviewer be safer in this case?

edit: Thank you for both answers. I thought it had to do with sandbox rationale, but couldn't mentally get past the fact that sandbox could potentially be escaped too. Eh, I think it is time for sleep.
> You cannot spin up 100K native threads to handle 100K requests that are IO bound (which is very common in a microservice architecture, since requests will very quickly block on requests to other services). Or well, you can, but the native thread context switch overhead is very quickly going to grind the machine to a halt as you grow.

Why? Bigger MySQL servers regularly use 10k native pthreads which spend most of their time waiting on IO.

Context switch overhead isn’t linear with the number of threads! The Linux scheduler runs O(logN). Moving from 10k MySQL threads to 1 thread per core will give you less than 10% extra throughput.

Doing IO means context switching. Goroutines don’t get a free pass here.
That sounds like a very unrealistic scenario. This is using OAuth2 behind the scenes (same as Facebook and Google login), so you only need to integrate another provider, not integrate a completely different authentication system. That means you need a couple of URLs, a secret key, and a new button on your login screen.

I'm not a mobile developer, but I do run a SaaS that has Facebook and Google login, and adding Apple login would take me a couple of hours tops. I can't see how it would be magnitudes different on a mobile app.
This is a good mathematical analysis. But here's another way of looking at it: the hot hand fallacy is stating that every shot is strictly independent. You don't have good days and bad days, every day is exactly average. Which is ridiculous, especially in the negative direction:

- A player could be sick

- A player could have an minor injury they are playing through

- A player could have not eaten properly before the game

- A player could have been practicing a new shooting form and not quite adjusted properly yet

If you can have bad days, by definition all the other days are good days even if they are only "normal" days.
... and all the koolaid drinking Kubernetes fans are now going to refer to Kubernetes as legacy and start creating a new cottage industry of Firecracker migrations.
Slightly cynical yes. But also a bit true.
anyone who looks at my comments on Boeing knows I’m fairly critical. However, it’s probably fair to say anyone with any bonafides in commercial aviation by definition is a Boeing insider since it has either squashed or acquired all of its domestic competition. We talk all the time about banks are too big to fail yet when it comes to defense we simultaneously create projects that only Boeing can bid and look the other way when Boeing acquires companies that might represent an alternative while increasingly taking delivery of weapons systems that don’t work as intended. One doesn’t have to look that deep into history to see scandals like the Air Force tanker which rose all the way to the Supreme Court, or the failed SLS project which has sent so much pork spending to specific congressional districts that Spacex could build something like 300 falcon 9’s instead, to see that Boeing’s relationship with the US government is problematic at its very core. Blaming both parties is surface level equivocation that does nothing. The simple fact is Boeing is too big, they know it and the government knows it and unless we want our defense to be outsourced to foreign ownership, preserving this status quo is quite literally the only thing keeping Boeing from reverse-mergering itself out of this country. We have overlooked our own strategic resources - be it pharmaceutical, manufacturing, telecom, etc, for far too long and have pursued incredibly near-sighted policy objectives to our own detriment. In the spirit of HN, I’ve already gotten too political here but I will say one final thing: don’t equivocate both parties as equal, neither should you be complacent and assume what your party is telling you is the right direction either — there’s more to this issue than simply saying oh let’s arm the regulators with more regulations and vice versa.
I guess you could backoff based on an ID, but then spoofing IDs would need to be defended against. So that doesn't solve anything either. I think DoS is fine to deny attackers entry because most sensible fobs have a backup key with a chip so the driver could just unlock their car like an animal.
From the article it sounded like it wasn't just "who is this person we would like to question them", it was more along the lines of "we need access to this person's email and other data".

The former seems possibly okay to me, but the latter is definitely not.
Good on you for considering this. I had one job where the company owner loved his naps, so napping was tolerated at the company. Half the people would have a 30 minute nap after lunch. Heaven! Made the afternoons so much more pleasant, and more productive. I'd just set my watch alarm and put my head on my desk (with proper drool precautions).
It's literally taking other people's content, putting their own ads on it, and paying you fake money for the privalege. If I create content, I should be allowed to charge for it. I'm okay with people not wanting to pay or being worried about their security and disabling those ads. I am 1000% not okay with them stealing content to run their own ads. I don't want their fake money, they are essentially running a scam. They may as well just rehost other people's articles and videos with their own ads and skip the whole browser thing entirely, same scam different name.

I don't care that a tonne bat shit has real monetary value. I don't want it. It's not legal tender, I'm not willing to accept it. I don't care that their fake internet tokens have monetary value. I don't want them. Brave is stealing from people and paying them in shit.
A good example is the Arc virus. Research at some point proved that removing it from a creature’s genome, removed the creature’s memory. More: https://www.nih.gov/news-events/news-releases/memory-gene-go...
As a DBA, I use git blame to see who wrote slow queries. Then I assign a jira to them. :)
They are very clearly trying to balance public health with economic losses.

It certainly doesn't help that Milan citizens are ignoring restrictive measures, bars are offering free drinks to "restart the normal life", and companies are attacking the government for the lack of profits because "it's just a flu". Meanwhile hospitals are getting swamped and are calling for selection of who should or should not have access to ICU.
For homelessness, not having a home is the very definition of the issue. We don't want to build "affordable housing" in the US. We literally feel it's better to let people be homeless than provide crappy housing. Then we run around claiming the nationwide, well-known not remotely a secret shortage of affordable housing is totes irrelevant and the homeless are all junkies and crazies.

Studies show that increases in rent correlate 96 percent to increases in homelessness. Build enough housing. Make it cheap enough and possible to live life without owning a car. If that reduces homelessness by 96 percent and the remaining four percent are hardcore, seriously screwed up junkies and crazies, we can throw extra resources at them because we spend more on average on trying to help the homeless than annual rent would cost.

Sometimes hospitals provide free housing to seriously ill homeless because it's a fraction of the cost of leaving them homeless and seeing them in the ER constantly and hospitalizing them regularly.

You want to see fewer homeless? The single best thing you can do is advocate for more housing in your city.
The Case Against Microsoft and GitHub
I don't know anything about that world...

But honestly that sounds reasonable to me. Old money wants to keep their money, so they are risk averse. New money is in the process of making their fortune so they are more interested in betting big.
At least with Netflix, you can get their Appliances and cut your inbound Netflix bandwidth by 80%+ for the cost of power and 4U.
Correct me if I'm wrong but all of that only applies to LGPL if you dynamically link the libraries and it doesn't apply to GPL proper at all.

When people say "embedded" they usually mean devices that run on low end bare metal hardware without an operating system (or even a memory controller!), which means nothing to provide dynamic linking, let alone the kind of end user control that the GPL philosophy is meany to promote. The vast majority of embedded software is statically linked by design so even the permissive parts of the LGPL don't apply.
There needs to be Australian Standards developed that everyone must comply with to annonymise personal data
It is interesting that so thought hundreds of Estonians regardless of government strong recommendations to avoid areas in Northern Italy.

9 of them returned with the virus and at least two had public contacts before being detected regardless of mandated self quarantine.

To be honest this raises some questions about the actual spread in Italy. Common sense tells that it should be statistically small change to meet a person with the virus, something between around - 0.05 and 0.1 (calculated "on the napkin") but somehow they managed to get it.
Surprised nobody mentioned asyncio.run_in_executor yet. It's designed to offload the event loop from long running cpu bound tasks, by moving them to another thread pool (or process pool if you are afraid of GIL). Eventually that thread pool will obviously also get starved given enough load but at least you wont have CPU blocking IO and vice versa. Tricky thing is knowing when an operation might grow to become too slow for io-thread given dynamic inputs.

https://docs.python.org/3/library/asyncio-eventloop.html#asy...
Well is it safe? Don't know.

Safer: definitely. Given that the collective amount of PDF attacks is some number, now this particular PDF needs to attack PDF and the webviewer. Assuming that 1% of all PDFs do that, I'd say it's 100 times safer than not using a webviewer.

If you still think that 1% of all potential PDF attacks is too unsafe, then that's a different discussion.

If you think my 1% is off, then that's a different discussion too. All I'm saying is that it's safer.
I looked for a demo of progressive JPGs online and found this: https://pooyak.com/p/progjpeg/. Pretty cool
If it's rendering locally, at least the browser is sandboxed. And if it's rendering server-side, then at worst someone else's machine gets compromised instead of yours.
Lol, true that. I prefer all of:

- superglue and baking soda in the lock tumblers

- 10 lbs / 4.5 kg of sugar in the gas tank

- pulling the fuel pump relays and spark plug wires

- unhooking the starter positive solenoid wire

- slashing the tires' sidewalls so they can't be repaired.

DoS complete. :) Maybe a swift kick in the bumper to set off the alarm at that point. ;)
ECU is usually an Electronic Control Unit. Some OME's name one of there ECU's, Engine Control Unit to make stuff more complex. Not app manufacturers have Engine Control Unit or a Body Control Module. The electronic architecture of a Volkwagen, GM, Volvo or Tesla is very different. Hardly any of the ECU's have the same name.

It looks like Wikipedia agrees with me and in addition, the Engine Control Unit article state that they are usually called the Engine Control Module (ECM) to lower confusion.
https://en.wikipedia.org/wiki/Electronic_control_unit
https://en.wikipedia.org/wiki/Engine_control_unit

Different OEMs vary in architecture and naming. Making it a bit of a hassle working in a teir-1 with multiple customers.
I disagree. Spectre vulnerabilities are not new. They didn't make a factual error in their reply.
South Korea has tested 140k people for the coronavirus. The US: 1,500 people.
NodeJS also doesn’t have a function to convert camel-case to PascalCase, should you not do that too because it’s not in the stdlib?

I’m going to be honest: you have not only not made a good point, you've gone out of your way to actively ignore that problems around concurrency regularly require one to use locks even in the absence of parallelism and have since long before multicore computers, and you're being weirdly hot-under-the-T-shirt besides.

Quit while you're behind, my dude.
Sounds like it should be possible if you can terminate the transfer of the file early:

> libjpeg has some interesting features as well. Rather than decoding an entire full-resolution JPEG and then scaling it down, for instance (a common use case when generating thumbnails), you may set it up when decoding so that it will simply do the reduction for you while decoding. This takes less time and uses less memory compared with getting the full decompressed version and resampling afterward.
Actually, people from academia still are offering me academic opportunities, apparently, so you are not correct when you say the chances are over.
I think you can get around this. Break the physical space up into blocks, say 100' square. Break the time component into 1 hour blocks. Concatenate the space and time components and hash them, then upload the hashes. If someone wants to see if they've potentially been exposed they can just hash their own time/location history and see if it gets a hit against the database.
Those memorable demos were called things like "The Mother of all Demos" not "Cute things [...]"
Thanks, I can't edit it anymore unfortunately, but I appreciate the tidbit of knowledge that was escaping me the whole time.
Because of Hand-to-Hand contact.

Have you ever seen Italians speaking?

They speak and use their hands to support the talk, doing explanations and emphasis on hands gestures.

As they speak saliva goes in the air and land in the hands and as they touch other surfaces contaminating it.
I am taking legal action, it's plain illegal discrimination at a tax payer funded institution.
Unbelievable??? The alternative is the complete collapse of the health system.
Ah I see, you were more focused on the utility of our infrastructure than our individual skill sets and knowledge. My points do help my argument, but from a different point of view than you were arguing from. And obesity rates are not irrelevant; they demonstrate how able people are to keep surviving, both mentally and physically. I think if a governmental collapse occurred in the US, 60-70% of the US population would be dead within 5 years. The major population centers entirely dependent on government infrastructure, regardless of how close to the "frontier" they live. Yes, there is much farmland here, but it is very reliant on water and equipment that only come from a functional economy.

I was a bit hasty in my first comment; I read your argument as "the US is made of frontiersmen, they tamed the continent, and they are hardier and more skilled at survival for it." At this point it is apparent that was not your intent, and I do agree that we'd be better off than many places. One county in the Americas that would do a lot better is Mexico though; full of off-the-grid peoples who are fully self sufficient and happy to be so. Much of the US is just functional because of money.
Oh I know, I started programming in '92 or so.

The idea of creating a program and sending it across an abstraction boundary for execution to avoid the cost of continually navigating the abstraction boundary for each step in the program is reasonably trivial. It was an approach I used in my first job for optimizing access to data in serialized object heaps - rather than deserialize the whole session object heap for each web request (costly), I'd navigate the object graph in the binary blob, but this required following offsets, arrays etc. The idea of a 'data path' program for fetching data occurred almost immediately.

In the end a different approach using very short-lived objects which were little more than wrappers around offsets into the heap combined with type info turned out to be more usable, and with generational GC, was plenty fast too; the abstraction stack was thin, the main cost avoided was materializing a whole heap.
I did work for a company where they had a few important vendors who would run legacy versions of their software and demand a bugfix for that version. They did this only once or twice a year, but being able to reproduce and patch old versions was enough to get some clients to shell out absurd amounts of money. These companies were swimming in cash and didn't like to learn anything new. Needing old commits is rare, but important.
We've tried every drug we have and they all made the problems worse, but don't worry, we've got a new drug coming that will fix all of those problems. Ask your doctor about it.
Yes! My company has source that is 20-30 years old, sometimes just going through the history to see who has committed on it and checking if that person is still in the company is already a win, other times there's a code review link or a ticket system link that gives possibly more context to why something was made.

(Granted code review systems and ticket systems change overtime)

Git blame on gitlab is also a good way of getting context of why something is there to begin with.
Sample
Sample Text
I’m a QA engineer and I go back pretty frequently so that I can see when a issue popped up and what might have caused it. It’s super useful for root cause analysis on bugs. also I use it to troubleshoot legacy versions for customers. Although I see less of that since I work on a saas product now.
With the exception of rare uses of git blame (hate that name) to figure out who made a change so I can ask them if they happen to remember about it (and if it was more than a year so my expectation is “I don’t remember” which is fair enough)... virtually never. I don’t care if my git history is “clean” or “dirty” (if you never use a tool to make a visual of the branches then you’ll probably never notice or care).

We put Jira ticket IDs in our commits and sometimes that’s useful. But the value tends to be in the content of the tickets as much as the commits.

If we decided to squash everything more than a year or two old into a single commit I doubt it would affect us very much in practice.
I navigate through unfamiliar code almost daily, completely different projects and different authors. I use the blame feature a ton to understand in what context a method was added: by blaming it, I can usually see what other code was added at the same time, and its evolution.

I've used git-svn[0] to use git within svn, it's been working flawlessly in my case.

[0] https://git-scm.com/docs/git-svn