skysight-inc/HackerNews huggingface dataset:
iOS dependencies in Cocoapods are including less than 1 other packages on average (1). The most I see are Alamofire (a networking package people keep using for reasons that I do not fully understand) and Starscream (a Websocket implementation, that's pretty hard to write from scratch to be honest). Having unnecessary dependencies is pretty much frowned upon.

One of the reasons is that the iOS SDK is really complete by itself while Javascript doesn't even ship with a usable Date implementation. If somebody could just come up with a standard library for JavaScript that is really widely adopted I think the amount of packages can be cut back dramatically.

(1) totally based on gut feeling, not based on hard data
React would normally be a peerDependency and so you shouldn't run into this problem if dependencies are specified properly.

If not, NPM module flattening should take care of it.

Then worst case, you can also tell webpack to bundle a specific installation.

There are some ways to solve these problems...
That wouldn’t be p hacking, it would just be false positives from multiple tests. But yeah that seems a possibility
You don't have a roadmap problem, your company has a sales leadership problem, which if left unchecked will kill your company.

Sales leadership should know that they need to build a sales team capable of selling what you have now while providing a vision of the future. Just guessing, but it appears they are caught up in trying to sell using features rather than selling your product as a solution to the problems your potential clients have.

If they can not sell the solution and keep getting caught up in a feature to feature competition, your company is in significant trouble.

That said... the feedback from potential customers, new customers, current customers, what you see competitors doing, your support organization, and the engineering team plus your vision of what the product needs to become are all critical for you making decisions on what to build.

As many here have said, there is much more to your question than can be answered here. I'd be happy to talk if you'd like to.

By the way, I have a single KeyNote slide for our roadmap. Not fancy, but it is simple, cheap, and gets the job done so we can focus on the product.
Unix and Similarities with Foucault
Yep, there are even machines to do it quickly.

Still nice to know how to sharpen a chain to a certain degree so you don't have to change the chain multiple times before lunch.

Changing the chain easily takes a few minutes (opening the side, loosen the chain, change chains, tightening the new one to correct tension, closing the side.)
Coronavirus: 8% of recovered patients in one study didn't develop antibodies
So… smog.
I love elementary OS’ file manager and prefer it over any other
Could it have been a Mammoth Wasp?[1] I've seen one in the Netherlands 2 years ago. Very distinctive pattern on the abdomen.

1: https://en.wikipedia.org/wiki/Mammoth_wasp
there are two types of features: 1) Features that affects the overall product 2) Features that makes life easier for users

For the first category you need to look at the whole picture, as they often affect many parts of the system, and there need to be a coherent strategy/plan.

For the second category, just go ahead and implement any such feature if have the time to do so. But don't forget that all new features have a future cost, as users would miss those quality of life features if you remove them in future versions.
Added benefit to keep vampires away.
There's one important question I haven't seen on here that's saved me on more than one occasion.

"Are there any concerns you may have that I can address that may lead you to believe I'm not the right candidate?"

I've been able to address: lack of previous experience, lack of a degree, time in between jobs, time spent at the last job, all thanks to this question.
Brilliant series. I remember watching it when it was released. Recommended.
We don't have that option, unfortunately. In real life we're dealing with hospitals permanently jammed and new covid patients keep dying every 6 months, plus the huge economic costs from keeping hospitals _at_ capacity as opposed to 10x over capacity.
Noni?
What's the point of using 7 VSCode plugins for a language you don't even know? Just pick up any terminal, any text editor, and the freshest stable copy of GHC.
Just flatten your hierarchical paths to assiciative keys. Load your tree into a dictionary. Declare victr'y.
That's great for today. In 10 years? 20 years? Definitely worthless in 100. Even the $30 today is wasted money for me. I have friends that have antiquated tech laying around in a junk drawer that I could easily borrow if I needed. Instead, I just requested the vet attach the data on the disc in an email. Even cheaper and less tech waste involved.
The interesting part to me is that its nasally administered. Weren't we just reading in another article about Alzheimer's patients having some vulnerability in the upper nose. As well as also usually having some infection like herpes, where here a vaccine seems to provoke a good response to a condition like infection?
Archive.org has a lot of the Computer Chronicles, a TV show with news and reviews about computers that aired from the 80's to the 90's IIRC.
Only if you consider 70% or so to be close. There's some room for improvement over copper wires. Now, if there are any physicists here who want to jump in, I have a question about that. I heard waveguides are dispersive, would sending pulses of light through tiny channels slow it down as well?
Burning Man Falls Victim to Pandemic
thewayofmph@gmail.com
Exactly. A vaccine will take too long, but we could maybe afford to quarantine long enough for a treatment to surface.
Texas A&M pandemic expert: Coronavirus will have 5 stages. We’re in stage 2
There is no built-in help with that interpreter? I know Shakti K has built-in help.
You can never get 100%, but it seems you can get enough to prevent it from flaring into community transmission. Keep in mind if I'm wrong, this lock down never ends - that's the only way you can keep other hot spots in the world from reinfecting your country after you get it under control.
Java didn't have a decent date implementation until Java 8.

> If somebody could just come up with a standard library for JavaScript that is really widely adopted I think the amount of packages can be cut back dramatically.

As this article points out, I think that lodash is that for many people.
This is what happens with a wafer-thin standard library.
Even better, doctors would be prescribing cans of whipped cream.
But you can force them into quarantine for two weeks when they return? That's what we're doing here in Canada.
How is this even possible?

How are there 1 million interesting packages?!

In my job we use like, I don't know, 20 libraries total, out of, say, 50 alternatives that could do the job. Including dependencies of the dependencies I don't think we reach anywhere near 100. Every dependency is discussed with the entire team when we add it.

How do you even have time to manage 1 million?!
Ozone hole three times the size of Greenland opens over the North Pole
NYC public schools to stay shut for rest of school year
That is a fantastic question.
Piwik is free and does everything GA does. You can self host the analytics dashboard so no 3rd party privacy issues.
Is it Hacker News that re-edits the headlines? At first I thought the headline meant "attack Matrix", i.e. matrix.org, for the purpose of helping Kubernetes. Like a call to arms. But then it made little sense to me that the origin domain was microsoft.com. Man, capitalisation really matters, I guess.
Getting sunlight on your skin is probably the best option.

https://www.mdpi.com/1422-0067/14/1/191/htm#b4-ijms-14-00191

Although a study from China shows that higher UV exposure doesn't seem to slow down infection rates.
Apple Google Contact Tracing API – need for interoperability and standardisation
I agree that this isn't totally specific to JavaScript. It's just that the ecosystem is very extensive and so there are a lot of packages, because you don't need to write your own code for a lot of existing problems.

There is perhaps a something about the JavaScript audience tending to attract less advanced implementers. So you end up with a lot of otherwise considered trivial and low-quality utilities being published and pulled down from the registry.

Rust and Go tend to be for more advanced scenarios where things like performance, security and support matters tremendously.
Bahaha. It's a small world fellow HN user. As soon as ACM opened their digital library, I started looking for interesting APL papers and found that one and thought it was beautifully done. My takeaway is that you can make purpose-built AI in APL with very little code versus calling out to a large library like Tensorflow and having no idea what's going on.
"""
And even when people seem to care about distant risks, it can feel like a half-hearted effort. During a Berkeley meeting of the Manhattan Project, Edward Teller brought up the basic idea behind the hydrogen bomb. You would use a nuclear bomb to ignite a self-sustaining fusion reaction in some other substance, which would produce a bigger explosion than the nuke itself. The scientists got to work figuring out what substances could support such reactions, and found that they couldn’t rule out nitrogen-14. The air is 79% nitrogen-14. If a nuclear bomb produced nitrogen-14 fusion, it would ignite the atmosphere and turn the Earth into a miniature sun, killing everyone. They hurriedly convened a task force to work on the problem, and it reported back that neither nitrogen-14 nor a second candidate isotope, lithium-7, could support a self-sustaining fusion reaction.

They seem to have been moderately confident in these calculations. But there was enough uncertainty that, when the Trinity test produced a brighter fireball than expected, Manhattan Project administrator James Conant was “overcome with dread”, believing that atmospheric ignition had happened after all and the Earth had only seconds left. And later, the US detonated a bomb whose fuel was contaminated with lithium-7, the explosion was much bigger than expected, and some bystanders were killed. It turned out atomic bombs could initiate lithium-7 fusion after all! As Ord puts it, “of the two major thermonuclear calculations made that summer at Berkeley, they got one right and one wrong”. This doesn’t really seem like the kind of crazy anecdote you could tell in a civilization that was taking existential risk seriously enough.
"""
The VS Code plugin listed (haskell-ide-engine, https://github.com/haskell/haskell-ide-engine - to be more precise, it's a language server supporting many editors) is probably the one which sees the most development at the moment and comes with many of the other plugins listed or equivalent functionality (syntax highlighting, tab completion, linting via hlint, code formatting, refactoring) included. It certainly is the tool I would recommend to VS Code users.
What's helped our team has been just writing down the product roadmap. It's as simple as a bulleted list in a google doc with some estimates about how long things will take, who's working on them, and what's already been completed.

Every feature request from the business and customers goes on the roadmap, along with any features engineering needs like supporting infrastructure, and there are regular meetings to make sure the list is always in priority order.

We've found having everyone looking at the same roadmap greatly reduces tensions. Instead of arguing over badly-remembered, vague requests, we work together to strategize the best approach. It's actually fun.
Remember "mainstream medicine" includes countries outside the USA, where the profit motive is reduced, sometimes to zero.

In light of this, your claim makes much less sense.
It's in line with semantic versioning, point 4 [1]:

> Major version zero (0.y.z) is for initial development. Anything MAY change at any time. The public API SHOULD NOT be considered stable.

1. https://semver.org/#semantic-versioning-specification-semver
This oversimplifies the measure of complexity by focusing on the difference between distributed and monolithic systems. A potentially interesting example I recently encountered was a monolithic system that used internal interfaces. Transitioning these internal interfaces from a synchronized design to an unsynchronized design effectively introduced much of the complexity of a distributed system into monolithic design.

Ultimately everything about data flow, typing, abstraction, and so on has some effect on performance, encapsulation, complexity, organization. In a way all aspects of development from onboarding to builds and tests to release distribution need to be measured the same way we take into account of resource usage and basic performance criteria. If a piece of software masterfully meets all needs, but has internal interfaces that are simply too complex and brittle to be worth learning then that software will quickly decay and need to be replaced as the dynamic world alters the constraints of usage.
I use the app "Things 3" and set deadlines, works pretty Goode... only downside: Its only available in the Apple ecosystem and its not free.

Btw.: its also my preferred Task manager
I cannot understand how people work with this. I work with many different technologies and try to avoid JS, but some times I have to. The past weeks I have worked on a React Native project that was written by someone else; what a horror show. I mean it wasn't the worst code by the previous guy but even in a few months a lot is simply broken and not 'best practice' anymore. Compared to most other environments I work with, iteration is somewhat faster when you finally have everything working, but the dependencies and ecosystem is horrible imho.

A bigger issue with all of it is that in my line of work, for the backend of firmware I cannot just depend on 3rd party libs as they will get audited, so I need to audit them before. Ofcourse most people don't have that issue.
Fun fact: until the STOCK act was passed in 2012 there was nothing restricting insider trading by Congress.

https://en.m.wikipedia.org/wiki/STOCK_Act
Which is weird. I would have expected have the leftpad scandal that the community would have found a balance.

To me, culture is a feature, and despite using JS a lot since it has a monopoly on the browser, the community culture never clicked with me.

I often feel like they are reinventing the wheel, not learning from other techs solving the same problems, under and over-engineering, regularly guilty of the XKCD 927 syndrom.

Few projects taste integrated, working together, clean. The stacks looked like hacked together. Agreement on best practices and conventions are timidly showing up. It also seems popular tools are just starting to stabilize and the breaking modifications rhythm to slow down. At least more than anywhere else I worked.

There is no way I can be objective saying this, but anyone with the same feeling?
I wonder if it's a mistake to treat all "non-mainstream medicine" as a single group here.

I'm not a physician, but I find some elements of non-mainstream medicine (e.g. certain teas can ease certain symptoms) more plausible than others (e.g. burning down a mobile phone mast helps with prevent covid19 spread).
But light in a dielectric medium also travels slower.

If n=1.3 -> v = c/1.3 = 77% of c
Five Easy Steps to Becoming a 10x Commenter!
> Is it possibly not a management problem at the core? I mean, I know exactly what you mean about suits like to ignore the future, but I've worked with a few 'wizards' who, once they've got the job under their belt, use it to keep other people out.

> They'll not comment, help, document or whatever, and once they're doing that, they are uncontrollable. They can't be sacked because they're the only ones keeping the system running, and they won't help others train up. That seems a very difficult situation for the suits to deal with, even if they want to.

This sounds _exactly_ like a failing of management to me. If developers are expected or allowed to "just code" without documenting anything or training anyone, management is absolutely to blame for allowing it to go on.
From the same place as phising, leet etc.
Related: https://www.joelonsoftware.com/2000/08/09/the-joel-test-12-s...
Inspired by Marty Cagan is a great book.
To be fair, express is a production server itself whereas werkzeug is not, so you need to add something like gunicorn or uwsgi (yeah I know nginx supports uwsgi_pass natively). click is not necessary in production though (it's only used in the dev CLI).

That said, 4 dependencies is the norm in Python land, whereas 13 dependencies is an outlier in JS land.

Edit: oops, misread, gp said express has 51 deps, not 13.
Yeah but that's one of these constructed arguments. "People" outside of our community already had BT enabled all the time. That's not a new "leakage path" introduced by a protocol designed with privacy in mind.

This one for example https://m.rover.io/more-straight-goods-on-location-bluetooth... is from 2017 and estimates BT enabled percentage at above 60%. I'd bet with recent tech developments that number only went up.
I have to wonder if they controlled at all for heart disease. That seems like it would be a strong bridging factor.
Presumably almost all of the dependencies are transient dependencies, not direct ones.

I still can't fathom getting to a million though.
Yes and no.

Because of the small stdlib, you need dependancies, sure.

But why this idea that each dependency must be very small, forcing you to install a hundreds childs, which, themselves, will install a hundred until the pyramid of files start to turn node_modules into a stress test?
Relevant: https://podcastnotes.org/portal-with-eric-weinstein/bret-eri...

Link to full podcast (highly recommended listening): https://open.spotify.com/episode/0pSAI6UqXc2yLTdk2x4mZE
Sure (upvote) and we dealt with it accordingly after some confused digging. On a more general level I’ve never seen something like that in a package manager. It seems as though some of the language features (like the singleton I mentioned) would make it obvious that arbitrarily duplicating packages and scoping them to sub packages is a major no-no, as in most languages I’ve dealt with.
Maybe is too simple, but this approach:

https://www.youtube.com/watch?v=aNjpH5lBZ8w

go to around 1:09 in the video seems to me very practical if one wears glasses, otherwise one could use a similar approach with el-cheapo protective glasses or "over glasses" safety glasses.

From experience with wearing "magnifying lenses" for little works with high precision like these:

https://rukminim1.flixcart.com/image/832/832/magnifier/a/h/n...

the front strap is very uncomfortable/sweaty, so the issue, besides the design (and making DIY one similar to Apple's one but with more standard round holes is easy) is with the material that must be anallergic and prevent or absorb sweat.
I believe the parent poster's implication was not that your experience is invalid, but that it doesn't reliably transfer to covid patients (where the complication leading to death is fibrosis of the lungs, which incidentally explains the very high death rate of advanced stage disease, ventilator or not).
Why are small packages bad? Independent functions should be versioned and distributed independently. Otherwise we get several utility packages which are nothing but collections of independent functions.

Widely used packages should form the basis of a standard library that is distributed with the language itself.
And the way governments would take advantage of this is by having devices everywhere exchanging IDs so that when somebody has a disease, those devices will let the government figure out some of the places they've been? This sounds too roundabout to make any sense. The government can already request location history from cell phone providers and Google if it has a warrant. Why go through all that trouble to get lower quality data?
The test rate is next to useless.

Death counts are a less unreliable indicator. Current death counts in NYC- over 7,000 using both the health department counts before Apr 5 plus the FDNY counts, tho even that still has to be an undercount- indicate that at minimum around the time of lockdown (Mar 22) at least 300,000 were "infected"- at a 2% CFR and MTTD of 15 days- but more likely closer to 700,000 or 800,000. That's 3 weeks ago.

With known new death counts currently in the mid to high hundreds, that adds tens of thousands of infections 2-3 weeks ago.

My take is- we are already today at over 1M infections in NYC. And we have a grim fork ahead- either we see a steep drop in death counts, or we see a steady or gradual decline.

A steep drop from lockdown means lockdown works, but also means we still have another few million in susceptible population as things start to open up.

If we only see a gradual or steady decline, COVID more quickly becomes the largest cause of death in NYC for 2020, and we know that lockdown doesnt work well enough to keep from progressing through the population, but we also know we have much less of a susceptible population remaining.
Sales != Marketing.

Like the difference between Test and QA. Complimentary, but still distinct.

Marketing's job is to divine the business case. Size of market opportunity, price points, window of opportunity, initial MVP thru mature feature set, projected P&L, and so forth. While collaborating with devs, for sanity checks and buy-in, ideally.

Real marketing is a real job with real skills. Once you've seen a pro in action, it kind of ruins you for all the pretenders.

In my 30 year career, I've worked with precisely 2 marketing pros.

(Sales pros are pure gold too.)

PS- Lisa Horwich is one such marketing pro. If your product has a business case, she'll find the critical path. Watching her in action still seems like magic to me. https://www.linkedin.com/in/lisahorwich/
But that depends on the amount of oxidative stress you have...

" UVA-induced decomposition of the NODs, like nitrite, leads not only to non-enzymatic formation of nitric oxide (NO), but also to toxic reactive nitrogen species (RNS), like peroxynitrite. Whereas under antioxidative conditions the generation of protective amounts of NO is favored, under oxidative conditions, less injurious reactive nitrogen species are generated, which may enhance UVA-induced cell death. "
People are less gullible than you think
Beautiful build! Those GMK caps look amazing.
Please take a closer look at the first plugin listed for VS Code, haskell-ide-engine, https://github.com/haskell/haskell-ide-engine

It is under active development and is the closest you can get to a "unified coherent Haskell plugin" - it comes with all the features you would get from installing the 7 plugins individually.
Remote work: A series of best practices for a remote workplace
Most of the diseases we treat in mouse are "mouse-models" i.e. genetically engineered in the first place for the purpose of experiments, which may be completely different from the actual disease in humans.
1 million packages most of which have more than a single version.
Undoubtedly James Burke is the reason I give a shit about history at all today (without which one cannot really have a meaningful grasp on the current world or its inhabitants, IMO). I was lucky enough to be exposed to these at a young age.

I have a directory on my file server with local copies of everything he ever released.

If you’ve never watched this or The Day The Universe Changed, please do. (I say this as someone who hates TV.)
I believe "Design by Contract"[0], or "DbC", is the concept you are describing. In the Wiki page Notes and External Links sections there are some good resources IMHO.

0 - https://en.wikipedia.org/wiki/Design_by_contract