skysight-inc/HackerNews huggingface dataset:
I was running into a similar issue and after a lot of research ended up adapting the scaled agile framework (SAFe) to our team.

SAFe is designed for larger companies, so you have to learn enough about it to understand where you can trim the fat. The big applications to your issue come from 2 places.

1. Lean Portfolio Management
2. Program Increments

LPM is a process of setting priorities by using real numbers where possible and best guesses otherwise. The result is a process that tries to measure value and urgency against your development capacity. Small things with high value float to the top. Big things with low value drift to the bottom and don’t bog down your team.

The Program Increment (PI) is an intense process that lets your dev team put out a plan for the next 8-12 weeks and gets the business to agree to it. Aside from getting everyone to agree to the current plan, it changes future business requests to “be prioritized for the next increment” which happens via the LPM process.

The PI plan still adapts to new feedback and can change, but those changes come with “if we do this, we can’t do that...is that acceptable?” Time for small changed and some variability is built in, so those conversations only happen for something major.
> Immediately, after posting it was clear it was a major concern by others as well. So what did Evan do with that criticism? He spent the opening part of his European talk mocking it [0].

I just watched that segment. He argued his position with a satirical touch. A summary of his position that characterizes him as "mocking critics" is inaccurate, imo.
my company has the same rules, and i’d expect any publicly traded company that doesn't want to see their stock drop due to insiders activity or lawsuits against it would do the same.

i think it’s fair, you’re not restricted from trading other companies. this prevents unethical people from taking advantage of insider knowledge.
While it's very encouraging that the (current) technology is being developed by such a capable group, there are plenty of tangential worries to be had, especially if this is viewed as a "foot in the door." Who's to say such an emphasis will be placed on privacy going forward? Ultimately, this is the government and large corporations conditioning people to being tracked on an ongoing basis and blindly self-isolating themselves because they got a notification on their phone. It may be opt-in and privacy-preserving now, but my experience with governments suggests that's unlikely to remain the case for long.
Sure legal repercussion and severe punishment is not perfect, nothing is, but it does significantly lower risk of getting murdered.

And of course we should keep trying to attack and fix the mental health issue itself.
Inviting the question of why the culture hasn't sprouted a "package rationalizer" to produce a curated, tested, noise-filtered distribution of useful functionality.

Come to think of it, something that does for packages what jQuery did to bring (some) sanity to browser incompatibilities.
Particles observed in Antarctica could be evidence of an alternative reality
Hola
fdc
Why Do Some Sex Workers Work the Street?
Edsxz
Ah, so that's why MicroFocus stock suddenly started surging a few days ago. I got stuck with some shares when they spun off from HP. It's my worst performing stock and I couldn't figure out what the heck they did. But now COBOL oriented companies are booming.
Getting people to understand how useless roadmaps are is the hard part.
Not the GP, but have you ever tried using a laptop outside, especially on a sunny day? It's not terribly pleasant, and you'll probably be squinting the whole time - the reflective surface is particularly troublesome.

I haven't tried a large e-ink display (though I'd love to, especially for coding), but I've been using Kindle e-book readers for years - the difference compared to a glossy, or even matte, Led display is incredible; it's just like reading a printed book. No squinting, no eye-strain, just really pleasant to use.
Only if you want to minimize the total complexity, which is almost never a good idea. What is more important, is the minimum amount of complexity needed to be understood in order to make a change. If you are able to test a small subset of components in isolation, you can also understand them in isolation, and modify them without the need to understand the whole system. I'd rather read 20% of 110% code than 100% of 100%.

The advice to write mostly integration tests is a terrible one. Particularly when they test integrating of everything. When such tests catch bugs, they don't tell where the problem happened. They also take long time to execute.
There have been a bunch of posts about this, including this paper, on https://www.reddit.com/r/covid19stack. E.g. here is an interesting post with a bunch of natural breathing techniques for boosting nitric oxide production:

https://www.reddit.com/r/covid19stack/comments/fp3i6l/natura...

There are a bunch of YouTube videos demonstrating how to do it if you search for them. The FDA also recently granted compassionate use authorization to a device that produces inhaled nitric oxide:

https://www.fiercebiotech.com/medtech/fda-expands-access-to-...

This is a great example of why people don't trust mainstream medicine. You have the WHO very publicly "debunking" the idea that garlic could prevent Covid-19, and then the FDA approves use of some multi-million dollar device with the same mechanism of action and the company's stock increases 5x in a day.
Newsletter on the State of Work During Covid – UBI, Buybacks and Work Beliefs
There are bad packages in rust, go, python (1), even C. The worst of these are closer to the norm for JavaScript though. Personally I don’t feel comfortable running JavaScript packages outside of some kind of sandbox (usually a VM) on my personal computers.

(1) in fact, seeing some of the worst kept me away from python for far too long until I realized plenty of python software doesn’t even need pypi and most only need it for a couple things with no transitive dependencies
I have a project with a total of eight dependencies. I walked away for six months as it was stable. I come back to add a few features and npm tells me I have over 38 000 vulnerabilities of different severity levels. So many that 'npm audit' just freezes up.

So there's that too.
Go in particular has an amazing standard library and very clear guidelines on how to write code. JavaScript does not have either of those things so it promotes people releasing competing libraries with similar functionality written in various different styles.
How interesting. You have given me quite a lot to think about it. I am still unable to get past the following, but I will continue to consider everything you have said in our discussion very carefully.

Issue: I carried out theoretical physics energy calculations on the work done by cells as a result of cell self-replication in the human nervous system (recall the nervous system primarily functions to send signals at ~the speed of light from one part of the body to another)

The thing I am unable to get past for arguments of the type you made, e.g. when you stated:

> "There are fewer than 10 billion people in the world. That's a finite number. Even a quadratic problem remains quadratic if there is a bounded number of compute resources"

The issue is: the human body does not completely fall apart, it all works fine and there are no issues like this, there is some kind of bound from being a physical object in the real world, but physically and quite practically for all purposes the human nervous system is capable of expending an exponential amount of energy

Question: Since the human body does not fall apart despite the fact that its doing cell self-replication, given how theoretical physics shows there truly is an exponential level of energy expended during cell-replication, how are these types of issues that you raise, quite legitimately from a pure-math/theoretical comp-sci perspective, not also a major issue for the human nervous system?

Thanks again! This discussion has been enlightening
Unfortunately most companies don't know any better that it is not the job of a PM to "invent" a whole bunch of features that may or may not work.
Your job is to bridge business and engineering. If both of these sides trust your judgement your job is easy. You will win arguments when you can translate between these sides. Turn business concerns into engineering projects and express engineering projects in terms of business outcomes.
AU summons Chinese officials over maltreatment of Africans in China
I thought electric charge in conductors already moved very close to C? https://en.wikipedia.org/wiki/Speed_of_electricity
Show HN: Tablist – a chrome extension to copy and paste lists of open tabs
Yes. Using third-party code is not a binary decision between “write everything yourself” and “use all the things”, it is part of the ongoing conversation about optimization: Development time, deployable size, build time, tool support, community support, training, documentation, etc.
Just saw this again - I listened to that track and really enjoyed it! I typically go for softer, more melodic stuff, but there is still a teenage metalhead in me that really digs this.
I mean, you don't have to sharpen them yourself. All it takes is a good stash of chains, and someone in the area who does it, and you can drop off half of them and pick up the other half every time you swing by, it's not that big of a deal.
Archived two days ago - https://archive.is/kVhuN
It’s really hard to know what to make of this data without a control arm. The patient selection becomes key to estimating the effect of on the outcomes, but the patients were not all extremely sick to start, and the patient inclusion criteria is super unclear.

https://emcrit.org/pulmcrit/pulmcrit-eleven-reasons-the-nejm...
I really like working with ancient codebases. There is no more satisfying thing than deleting 10k+ line of spaghetti code. Yes, you have to spend days or even weeks to figure out how it works. Hunt down edge cases, bugs. If you like playing detective you will like it.

I rather work on a huge legacy codebase than rewrite the same CRUD app in the JS flavor of the week.
Ok, I think I understand better now. We typically turn on the feature for internal users first and then do a gradual rollout using feature flags so it's not as high stakes and can be rolled back easily in case of problems.
I think that we are in a situation where the number of dependency doesn't have any meaning anymore for people working on web frontend projects. Recently while revamping parts of the CI/CD at $WORK, I found out that running npm install for one of our frontend project downloads around 1 million dependencies. And npm audit reports a completely ridiculous number of security issues with them.

It's just so absurd and nonsensical, nobody can understand what that even mean.

Seems to me to be a crazy huge liability, but quite a lot of people seem to be fine with that.

I don't know what to do from that information, but trying to create some awareness around the issue feels like talking about the number of operations per second a CPU does with someone who has zero idea what a realistic range is. It's seen as a high number, but doesn't have any meaning attached to it.

Edit: I don't have access to the project anymore to check more details (such as installation time), but I checked some personal notes I took when I found this out, the redacted output from npm audit is the following

$ npm audit
<REDACTED> vulnerabilities found - Packages audited: 927016
Severity: <REDACTED> Low | <REDACTED> Moderate
Done in 41.62s.

So slightly below the 1 million mark.

Edit 2: Now I'm wondering ... maybe the "packages audited" from npm audit doesn't mean "you have that number of packages, and I audited them". But if that's the case, that's a terrible UX, and I have zero idea what that number mean, which kind of support my point.
Books, because they demand attention, might be good quarantine antidotes
Twitter list of people and companies doing remote work before it got popular
One thing that is rarely discussed (I think?) is how to test things which don't have a correct answer. It's not just "refactor until you can test" it's output that may be subjective. For example, suppose you write some code to do some image processing like a stereo matcher. How do you check your code works? Usually you have some ground truth which you can compare, but it's difficult because you'll never get 100% accuracy. At best you can declare a baseline, eg that your algo should be say 90% accurate (if you implemented it properly based on literature results) and if you don't get that, then error. In that case you can use a numerical metric, but other applications you might care about the result being aesthetically pleasing (eg a video ISP where you do colour correction on the stream coming from a low level camera).

Or hardware where the advice is usually to mock the device under test. But if you don't own the hardware the most you can do is try and emulate it, and maybe check that your simulated state machine works. In my experience its easier to run with hardware connected and just skip those tests otherwise. There are also extremely subtle bugs that can crop up with hardware interfaces like needing to insert delays into code (eg when sending serial) that will otherwise fail in the real world.

OpenCV has some interesting approaches to this, for example testing storing a video in a certain format, inserting a frame with a known shape (like a circle), then reading back the video and checking that the shape can be detected.
When writing code, we often think "according to the design of our system, this condition must be true at this point of execution.” Examples are:

1. The argument x must not be 0.

2. The variable x must smaller than the variable y.

3. The list foo must be non-empty.

4. The variable x should have value 'Success' if it had value 'Try' in the beginning of the function call.

These 'invariants', or assertions, can be extremely useful for testing the correctness of the code. Put simply, if an invariant is violated (during unit test, integration tests, or system tests), it indicates that either the design or the implementation is wrong. An article on testing methodology would be more appealing if it had some discussion on exploiting invariants/assertions.
I dunno man, I was really surprised by the behaviours I saw; maybe I have been particularly fortunate in my career but it definitely seemed to me like it was worse in the US.

Perhaps it's bad in other places too. I personally think it's idiotic, as the point of interviewing is to find great candidates, and I have never felt like the University they attended was a particularly good predictor of that.
log (x) is approximated by
√x iterated n times x^(0.5^n), multiplied by a constant equal to (2^n + [fudge factor for √'s finite precision])

The best answer is a link to
https://m.imgur.com/s9eBx5Z
which solves the problem in math notation.

There's another comment that describes that in words, and a bunch of reddit chitchat.
If large screens with a decent refresh rate were readily available and competitively priced, I imagine they'd be a huge hit with devs - I know I'd love one.
imagine you happen to open this page at work while someone walks past your desk. if they say "hey, are you looking at penises at work?" you have the opportunity to explain "no, actually this is a representation of one of the greatest works of western art". more often than not, they will just keep walking and not ask for an explanation. do you really want to be the person they remember this way?

some people just don't want to open a picture of a penis at work (or be surprised by one at home), no matter how artistic. I don't find this disturbing.
My stuff breaks whenever I try upgrade it. People refactoring stuff.
Progress in semiconductors, or Moore's law is not dead yet
Location: Oregon

Remote: Been working remote For 10 years

Willing to relocate: No

Technologies: Hardware Design Engineer focusing on system level design for 15 years with 16 years of Altium PCB experience

Résumé/CV: available on LinkedIn @ https://www.linkedin.com/in/shaolo/

Email: yc@shaolo.com
So it's like the feature gmail (and perhaps others) have that allows hello+randomsite@gmail.com.
https://fastmail.blog/2018/10/01/use-unique-email-addresses-...

That's great because occasionally email parsers on sites/apps don't accept emails with the + in them.

Sounds good for throwaway emails and not using personal info, however overall, this still has a few problems:

- your accounts on different services can easily be cross referenced in the event of a data leak, etc. They will all have @hello.example.com.

- if you actually use hello@example.com for something important, that will be gleaned as well (worse, this is true even in the event of a data leak/hacker on a single service) since this rule/feature you explained is common knowledge.

Seems the only way to overcome that is use a separate custom domain for any site you want to completely isolate, or a custom alias or new email on a major service for each.
- http://dashupdate.com/
- I made it
- Because I made it
With location services off, I don’t believe that occurs.
It's not just the blood level. Breathing oxygen at a partial pressure over about 0.5 atm also gradually impairs lung function due to toxic effects.
The Latest Hydroxychloroquine Data, as of April 11
For debug there is Debug.Trace which is about perfect.

For non-debug, you may be overestimating how useful it is to output from pure functions in production.

In general when you are in a situation where you need to change the Monad you're under, there's techniques and libraries for that (one way you define it once, give it a name, etc.).

The biggest pain tends to be going from pure to monadic in the first place, which last I used Haskell there wasn't much for but to just do it. There may be more tooling now, haven't seen.
From what I understand, this is important for people who show (severe) symptoms of Covid-19, not as a preventive drug. So no reason to take it until clear symptoms show up.
Pour Reception (UX experiment with machine learning and tangible computing)
There's a good piece in today's FT on the extent to which Son is leveraged:

https://www.ft.com/content/bd8ed81a-4d62-4b10-a41c-2efa8dea0...
A million dependencies sound horribly excessive, even by JS standards.
That was my reaction too.
Pretty well. Half a dozen guys from IT went into the office on March 16 to prep laptops and a printer or two for staff requiring them. The building shortly went into lockdown, with only an engineer visiting a couple of days a week. I'm not sure that anyone from IT has been back.

I don't do much support, but I know our guys have been doing a lot of Zoom training and support.
Javascript doesn't have a standard library (something a lot of languages provide), and nodejs's built-in functions library are... lacking. Also, the culture of providing small packages, being around for longer, and so on and so forth...

I have a project I haven't even started yet in Rust. Three dependencies in Cargo.toml. They download and install 34 dependencies.

I've now added three more (from kube-rs readme). It's now 197 dependencies. And so on.
Virgin’s VOX Space snags $35M Space Force launch contract
Entirely harmless. They never sting unprovoked, but they do seem very intimidating with their size and their inquisitive demeanor.
Bears repeating. Just because it works in a mouse doesn't meant it will work in humans.

If you did have a pet mouse, i think we cured every alignment it could ever get.
Different things are hard or easy in Haskell compared to other languages. Mergesort would be the first one I'd reach for in Haskell if I'm implementing from scratch.

Quicksort isn't really hard, you just do it in IO and it looks about like what you'd see in any imperative language. (or you can use ST, but then you have to know about ST).
It's now whataboutism. It's finger pointing from a lot of people who develop in languages whose story is only marginally better.

As I wrote in a sibling comment, I have a project I haven't even started yet in Rust [1]. And it's measly 6 dependencies pull a total of 197.

[1] https://news.ycombinator.com/item?id=22841742
If you mean that javascript gets a disproportional amount of hate, that might be because of how much more it is being used. It is true that rust seems to be ignoring the sins of the past and diving right in to having lots of dependencies, with the solution being to manage them instead of weeding them out in some way.
I'd like to back up what you say because I wasn't clear enough in my first post - I've known a few people like that, a very few. Most are good and do their best. Despite the impression, idiots as I described are very much a minority.
This is an interesting approach for primary key obfuscation.

I recently stumbled upon something that I feel might be even more powerful - Hashing complex types into 256-bit keys. E.g. If you had some type representing the composite keys of a Customer in your system (email address, phone number, etc.), you could serialize this instance, run it through SHA256, and as long as the same process is used for lookups, you can get everything back out as expected.

Essentially, you can compress your entire scope of composite key data into a single 256 bit value. Just like with GUID keys, this can be pre-computed on each client (whereas autoincrement cannot). This approach is very clever IMO because it can be used directly on top of any universal byte[]/byte[] key-value store. Your keys are all 256 bit values corresponding to the SHA256 of a serialized complex key instance. The type information can be encoded into the key itself (e.g. hash the fully-qualified type name as well).
That page itself is an example what's wrong with using JavaScript on the web: It's used in places where it's not necessary. In this case the site doesn't apply a stylesheet with JavaScript disabled.

JavaScript is great when it's used for enabling interactive websites, but nowadays more and more websites use it to break features, which don't need JavaScript at all.
New York City Schools Are Closed for Rest of Academic Year
'pip freeze' results from a few other py web frameworks:

sanic = 18, fastapi = 3 but one of them is a 7MB download (pydantic)

yeah it's less, but also python has an amazing stdlib
What's a good brand? Really hard to find a trustworthy brand on amazon. Thanks!
Gun ownership is, in aggregate, about as dangerous to the US population as car ownership.

Millions of lightly armed people have stood up well to the US military. What you're talking about isn't a fact at all -- it is a myth, that overwhelming technology can decisively determine the outcome of wars. It is certainly a factor but there is no way F-35s would be sent to bomb houses (for example): the cost, relative scarcity and long periods of maintenance for advanced weapons systems like that are all factors that limit their deployment. In limited war -- which is what all insurrections are -- application of advanced weapons is difficult.
What’s worse is that the whole installing multiple versions of the same package for different sub dependencies doesn’t make any sense when when the language supports singletons and module level variables with has no way of specifying which version to import.

I was shocked this behavior exists when a site broke by upgrading a sub dependency. Turned out they both installed react so they used a different “creatContext” and now there were two context instances instead of one.
The first item (LPM) sounds a lot like our current process, which has worked well for reactive work based on business needs, but all of our long term work feels like it is prioritized ad hoc, based on gut, or worse, doesn't even get done. If be interested in hearing more about PI and how it works.
NOx? NO is a naturally occurring cardiovascular signalling molecule of enormous importance in the body so its actions may well be of significance in disease events.
gets() wont compile today.
how long does that take to install? is there a local npm mirror / cache?
bfgv