skysight-inc/HackerNews huggingface dataset:
https://youtube.com/c/3blue1brown

This is my favorite youtube channel. He makes advanced math videos and some videos on applications of math in cs such as Cryptography, Information Theory and Deep Learning.

Most of the videos don’t require prior knowledge other than basic algebra. For the ones that do, he has made some series to teach them. They include the essence of calculus, linear algebra, etc.
It just seems like you're not even registering what the other side thinks. Like, a total non-awareness or non-acknowledgement of what the disagreement even is.

You're simply assuming the conclusion - that the fetus/baby isn't a child in the normal sense the way a born baby is a child.

The rest of your arguments flow from the notion of how ridiculous it is to make a woman sacrifice to save a non-child fetus. And from your premises, you are correct.

But that's missing the point entirely.

Pro-lifers don't think it's a non-child fetus. They think it's a child. For them, it's the same as sacrificing to save the life of a born baby.
I had written a long comment about ZFS caching and still didn't do a good job, so let me link you to this instead:

https://www.truenas.com/docs/references/slog/

The short version is:

- ZFS caches reads into RAM. Gobs of RAM helps. You can also add a secondary read cache device (L2ARC).

- ZFS can caches synchronous writes to an SLOG device, but if you've disabled synchronous writes it won't make a difference. An SLOG device makes no difference for asynchronous writes.

I use ZFS for my Time Machine backups (among other things) and have synchronous writes disabled for the Time Machine datasets.

Before we had ZFS, the traditional way to speed up NAS was a raid controller with a battery-backed RAM cache.
I highly doubt the prospect of Metaverse. I just don’t think the current technology can ever make it like what people imagine.
I’m really tired of “your valid credentials aren’t good enough, comrade. Please come with us to print your extra papers!”
SFP is nice for the switch-to-device connection. It lets you choose between DAC (cheap and easy to route) if you're close enough, fiber, or copper (your choice). If I had an option, I'd use SFP+ everywhere.

But copper is usually a little simpler for consumer/prosumer devices. Someone does make a Thunderbolt to SFP+ adapter but that things like $300!
I think this company is probably more successful the less potential buyers know about it, the product sounds like total trash to me.
My understanding is that it's "solved" in the sense you say, we know that the solution obeys the NS equations. The problem is that we can't actually solve them on a sufficient range of scales to actually make that knowledge useful for making predictions, so we have to resort to approximations.
What's Semi in this context?
Good info! So I guess the answer depends entirely on the precise journey you want the horse to take - specifically the terrain, elevation, surface, and cart wheels/bearings.
I would like to post a slightly different angle to the discussion.

Assumption: the majority of commenters are working in technology fields, and perhaps even technology startups.

Let’s say that you have developed some software product that works pretty well for certain applications, but is certainly not perfect. But it works well enough that your customers are paying you to use your product.

Now, your customers decide to use your product in a way that you have neither intended nor prescribed. (In fact, your product comes with a disclaimer.)

In doing so, they end up in court. And you get hauled into the middle of it.

Should you have to expose your technology? This could endanger your entire business.
Thanks Daniel, I guess xD That was quite cryptic, but I think I get it haha. Cheers!
Why not both?

Waving a scientific magic wand from a crony-connected company is a great asset to would-be abusers in the justice system.
I disagree with you, wholeheartedly.

One of the problems you are facing is code quality, which you've eloquently solved by code review (LOL), but the other, more burning matter is, you are no longer in control of your own software.

-- hey now, I DID actually read all the code we brought in

I mean, sure, that's a possibility. I don't believe you, but that's besides the point.

The point, being, and here's a news flash for you corporate peps out there who love to "manage my team of peps using stuff I learned from someone I talked to at a bar"...

Nothing is free in this world, not even code. The shortcuts you are making aren't really shortcuts. Instead, they will become your doom.
This thread is the biggest crock of shit. It's a blog post about React, he's obviously not saying "don't use literally any libraries whatsoever".

The vast majority of libs that sit on top of React are completely useless time wasters that cost you more in dev time in the long run than writing it yourself. Just React, CSS and the Chrome dev tools is more "power" than like 99% of dev environments that have ever existed. The fact so many garbage front enders think you need to pile 80 more dependencies on top of the bog standard stuff is a joke.

Avoiding libraries as a default and knowing when to make an exception is the most important part of being a front end dev these days. Reaching for libraries as a default solution to any problem (which is what 90% of FE devs do) is a great way to fuck up every project you're on.
Out of interest do you know of any specific papers showing that Maslow's hierarchy of needs (or just what it recommends) is a good way of increasing dopamine and serotonin? I've heard of dopamine diets where you give up media etc for a few days to 'reset' so to speak, so assumed the absolute basics would decrease the amount. But I also have little to no understanding of this :)
I clicked the article by the OP, and immediately Ctrl-F "sway" thinking surely I'm not the first person to think of this being an orthodox vs. the unorthodox kind-of problem.

The comments give it away: the tmux-like or emacs-like productivity gains with sway (or its ilk) are only obvious in retrospect. And indeed, measurement of the productivity gains those of us in the tiling camp speak of, is elusive, anecdata, not well-documented or consensus-driven.

I'd suggest measurement lies somewhere around Fitts' law.

Indeed, what Fitts' law could not have foreseen is that we'd have devices that could solve this rather two-dimensional time-speed-distance problem by introducing Z-order navigation which is arguably instantaneous and non-linear with a keystroke.

https://www.interaction-design.org/literature/topics/fitts-l....

The key insight is that window management doesn't belong in your terminal or in your text editor. Rather, window management belongs at the same abstraction layer as the window, or window manager, or meta - one layer above.

Put intuitive, direct manipulation of window geometry in the window manager tied to the keyboard, not the mouse, and you get massive gains of time, space, and indeed, space-time that transcend terminals, text editors, and the limited frame of lower levels of abstraction such as CLI, TUI, etc. precisely because the real time, speed, distance problem is not in the physical, but rather the conceptual, or mental model.

The mouse, for all its brilliance is part of the impediment in spatial reasoning. I suspect we can test and measure this across cohorts, but I have no evidence. I don't believe the results are consistent across cohorts differentiated by spatial reasoning scores, much like tmux, emacs, or any sufficiently complex and advanced system that has few adherents, but those adherents can demonstrate productivity well-above average.

The one key missing link in the current implementations that I've examined is that they seem to miss the notion of shadow windows - windows that have only an invisible, mental component, not a visual one. I think they're getting there, but that concept is difficult to explain or learn.

To quote Kaja Perina referring to Alan Turing's read on Grothendieck's method of solving problems:

Grothendieck's approach was to "dissolve" problems by finding the right level of generality at which to frame them.

I'd argue that that is precisely what is wrong with most R&D around window management - it gets sucked into the pretty and beautiful visualization cult instead of the academic and more principled approach you'd see from Alan Kay and his protege Bret Victor as having this kind of perspective today. There are a few others, but they tend to be quiet academics.

And of course, I'd be curious what Kay and Victor think of the current state of the art in window management given the history and recent advances in tiling.
https://www.psychologytoday.com/us/articles/201707/the-mad-g...
> Has this ever been enough for anyone to pass an interview challenge?

Yes.

Ideally, you shouldn't be "memorizing" solutions. You should be first attempting problems on your own with your very best effort, and only after successful completion, or after sufficient effort, should you look at the solution. If glancing at the solution for 15-20 seconds is enough to understand "the trick" you should then close the solution immediately and try the problem again. If the methodology or technique is more complex, then you should spend more time trying to understand it, which may include revisiting some prerequisites and relevant foundational concepts.

If you understand a large enough variety of problems, then you will find that the techniques that you have learned are applicable for many novel problems you may be asked during an interview. After taking 5-10 minutes to properly understand what exactly the problem is asking, and clarifying assumptions/preconditions, you should already have an understanding of how you would solve AND code out the problem.

It is difficult to come up with a working solution in code in a short amount of time - practice makes perfect. Good interviewers try to filter out small bugs/discrepancies that are introduced due to time trouble, and will focus on the bigger picture of your algorithm and function design.

Some problems are simple enough that it is possible to:

* receive the problem description

* clarify all assumptions

* discuss a potential solution / thought process

* illustrate a couple of examples of input/output

* discuss edge cases

* implement a solution in code

* trace execution with some input examples, verify it matches expected output

* discuss how the algorithm could be expanded if the problem was amended

-- all within 60 minutes.
Curious, what brand of fish oil, and after how many days did you notice an effect on your vision eating "six softgels a day"?
First you can most of the benefits of gold as a currency by just buying gold and then selling it in 40 years. At a personal level a gold backed currency doesn’t change much. Anyway, if gold was actually the words medium of exchange it’s value would be vastly higher.

A reasonable estimate is the value of the worlds gold would equal the value of the words current money. As it’s a nice round number the US’s 20 Trillion M1 money supply and ~20% share of the world GDP suggests something like 100 Trillion for a reasonable estimate for the words supply of gold in that hypothetical situation.

The actual supply of gold is around 400,000,000 lb. So in that hypothetical world 1 lb of gold would in theory be worth ~100,000,000,000,000 / 400,000,000 = 250,000$/lb. Let’s again simplify to ~10x as much.

But wait if it’s worth 10x as much two things happen first it’s used less often in electronics etc which directly hurts the economy, but next it’s vastly more profitable to mine and thus the world spends more effort mining stuff that just sit’s in a vault. Except, governments can’t safely issue currency without being able to back it up with gold so they need to buy up most of this mined gold and then securely transport, store, inspect it etc.

As to keeping it in your own vault, you can secure it all you want that just makes home invasion vastly more profitable. As long as you have access to your gold at home, so does anyone with a gun to your head.
Hey fellow djangonaut!

Id say people don’t really care to see the instructor. Much better to just focus on content.

If you did want to include yourself as part of the branding the time to do that would either be before/after the video rather than during. Or as part of the website, etc. Plus your personality and who you are will inevitably come through anyway no need to focus on it.

Cheers!
I've seen highly scalable distributed DBs used as poor choices, and have used Postgres as a replacement in some cases.

It really depends on the kind of problem and the scale, but a good implementation that matches the problem will sing compared to a mediocre implementation on inappropriate yet highly scalable infrastructure. Even if it's supposedly inferior because it's centralized, etc.

Knowing the constraints of the engineering challenge and choosing wisely within that is key. You can sometimes leverage constraints and simplifications in ways that can stack and remove many layers of complexity. Immediate consistency is a huge one, as are transactions.

I avoided relational tech early in my career, when I was really just turned off by examples of poorly tuned implementations, and badly written schemas and queries. Once I finally opened my mind, I was better able to appreciate its role as compared to other DB models.

I think that's a natural maturation as you progress in your career/get more exposure. It's too bad most of us seemsto have to walk the same path though.
Minority governments are great, though. Keeps the gov from getting too crazy, and they have to make deals to get shit done.
Forgive me for my ignorance: why would the constitution be a good start for reasoned first principles? The constitution was written centuries ago by wealthy men who considered women and other men property and its updating process is so onerous that it still has nothing in it that considers women equal to men, despite women's right to vote, pay taxes, own businesses, etc. being established decades ago.
You left out the half of the sentence that qualifies what kind of position I'm not taking:

> I'm not advocating a position in re: schools and the closure thereof.

You seemed to me to be responding above to a position "Keeping the schools closed" that I am not advocating.

- - - -

> As soon as you propose a comparison...

I'm not proposing it, I am describing what the author wrote, using other words.

The author says "the value of life-years saved by COVID prevention is small compared to the value of reduced quality of life-years caused by this prevention", and I'm re-phasing that to point out that this is not a simple economic trade-off (the author is a Professor of Economics at George Mason University.)

> leave the other side without any epithets

Again, it's the author of TFA that is saying that school is mostly just "convenient daycare".

> a very visceral image

Yeah, I'm trying to emphasize the point.

> the offending part italicized

That's a description of how Covid kills you. I'm not sure how it's offending you. I'm not trying to be offensive.

To me it seems you could call it "offensive" in that it's a horrible way to die, eh?

Anyway, I hope this clears things up. I'm not interested in serving as some kind of proxy for the authors opinion, eh? If you want to debate my characterization of what the author is saying that's cool, but I'm not arguing with you about school closures.
The title would be better if it included "(2014)".

The data itself is from the same old study the internet has discussed and debated over the past eight years (eg: https://news.ycombinator.com/item?id=7600333).

Maybe the Youtuber who made the video only discovered the study last Thursday, but the information itself is almost a decade old, and the title should reflect that.
Turbulence is unsolved because Navier-Stokes is unsolved.
Excellent post!

To be sure, I don’t even live in Mark’s state and it’s on him if he wants another picture on his profile. You’re a stellar citizen, though, for taking action on your own!

I simply wanted to point out a trend on Wikipedia. Mark is just one of more than a dozen candidates with bad pictures or, worse, empty pictures that seem to be the result of sabotage. If you look on these candidates’ pages (or Mark’s page), you can look at the revision history and determine that there were past pictures taken down or replaced near election times.

Again, I don’t care. It’s up to these candidates to fix this stuff if they want to win. With the amount of money they’re bringing in, you’d think they could hire someone to spin them up nice profiles with ‘Political Stances’ sections and quirky stories about their family life. I wonder if they intentionally keep their profiles empty to funnel traffic to their personal websites instead.
The only question then is whether the police biased these installations in minority neighborhoods without connecting it to high amounts of shootings, which could easily be proven with data.

That's the sort of thing that would be useful in court if it's true.

Are local police required to publish where they are deploying ShotSpotters? Shootings and racial demographic data is certainly already public.

I've read the entire Vice court report and don't remember seeing that data. Haven't read the Chicago one.

Edit: reading the original Motherboard source all of the examples were described as small 'pilot programs' so they were usually only a single part of each city, in Cleveland for example :

> the Cleveland Police Foundation—has been deployed in a small section of Southeast Cleveland that city officials have described as a high-crime area.

> Those neighborhoods also happen to be among the least white in the city and those hit hardest by economic recession and the pandemic, according to local community organizers.

> The area the division chose for Shotspotter accounted for 37 percent of all shots fired calls, 37 percent of felonious assaults, and 45% of all homicides within district four, Sergeant Jennifer Ciaccia wrote to Motherboard in an email.

https://www.vice.com/en/article/88nd3z/gunshot-detecting-tec...

(Motherboard didn't provide crime stats in the other 3 example cities cited, only the demographic profile which was consistently non-white)
I believe camshaft profiles are designed for minimum jerk of the valve stem.
I see. Everything that is "same experimental design" with the same starting hypothesis. I like it.
If true, selective enforcement is bad.

But some minority demographics commit disproportionate (edit: violent) crime per capita so you expect some proportional scaling (more crime = more need for crime detection) if they happen to live in cities/areas where that's the case. (Usually big cities)
It is pretty frequently done when arguing in bad faith, or (sometimes deliberately) misunderstanding that "minority" refers to power and not numbers.
Ironically there's someone linking[1] today to someone with basically the same complaints about how Firefox has less customisation dialogs than it used to.

They literally post screenshots[2] showing less options (eg, the "Close it when downloads are finished" checkbox has gone! Oh no!!).

I was thinking exactly what you've posted here.

[1] https://news.ycombinator.com/item?id=32258822

[2] https://digdeeper.neocities.org/ghost/mozilla.html#historyof...
> Most rendering is outside the scope of state management and it doesn't matter whether you use providers or redux to manage it.

It does matter - a Context at the top of your app will trigger a full re-render on every change. Redux and other state management solutions specifically avoid using Context, and the new React 18 useSyncExternalStore hook was added for this very reason.
Correct. The owner of the co-working space was able to get rent for one dollar (for the co-working space, because it drives tons of foot traffic with meetings and such) and the coworking space is wildly profitable. However, his opinion on maker spaces is that they are wildly unprofitable and even he couldn’t find a good business model there
You nailed it. Thank you for clarifying for me
I typically have 5-10 videos in production in a given week (doesn't mean I'm working on them actively, but I'll sometimes shoot parts of different videos depending on the schedule).

Some videos are 10 minutes, others are more like 20. On average I end up with 100-200 GB/video by the end.

So you're correct that I don't need 14TB (that's overkill) for now... but anyone who plans storage knows you're better front loading the extra capacity if you can afford it, because needs always seem to grow faster as time goes on (e.g. 4K to 8K, ProRes LT to something with more color space maybe...).

And right now I keep all my "A-roll" (scripted takes, usually with about double the run time of the actual video), but I'm considering setting up a script to automatically convert those clips to H.265 afterwards so I can still have reasonably good archival footage but at like 1/100th the file size.

All B-roll shots (Dolly shots, handheld closeups, illustrations, etc.) I save at full original resolution, because they are often useful in follow-up videos. But that's usually only like 30-40% of that 100-200 GB per project.

(Edited to add: sometimes there's a unicorn video that also has raw Timelapse footage where you roll at normal rate then generate a Timelapse afterwards (and use some of the real-time footage). Those can have hours of footage and a couple have gotten beyond 400 GB. But I try to limit that just because of the hassle.

Easier to have one camera devoted to the Timelapse, and another for some other shots for real-time use.)
Probably a lot of early 20th century homes in towns around the US will be 'preserved' for a long time as it's become too expensive to tear down and build new homes for most buyers. People say that European homes last a long time because they are timber and stucco, but make teardowns expensive enough and with enough permitting issues, any town in a desirable location can be preserved indefinitely!
Some players just need killing.
Google was collecting point cloud data of US cities 15 years ago, I assume some GIS vendor somewhere is selling a copycat dataset to self driving car startups.
If your technology is being used as justification for incarcerating people and as a way for law enforcement to circumvent the law and escalate routine encounters into violence, then yes.

https://www.vice.com/en/article/qj8xbq/police-are-telling-sh...

https://www.vice.com/en/article/5db8vk/police-are-using-guns...

https://www.vice.com/en/article/88nd3z/gunshot-detecting-tec...
https://archive.ph/zIu90
How do you find work when you only use your own bootstrapped language on your own OS using your own FPGA board? And do you find difficulties getting your colleagues to use your own VCS? /s

In all seriousness I get your point, code supply chains are volatile beasts that can blow up, but it's the only realistic way to write code nowadays. You can reduce external libraries and tools as a tradeoff for time/cost or you can fork tools to host yourself, etc... These are all tradeoffs that shouldn't be seen in black and white!
Microsoft's OOXML spec was so much larger than ODF for at least 3 reasons.

1. OOXML is an XML-ization of a descendent of earlier binary office formats. You can do things in binary formats that don't map efficiently to XML. That resulted in OOXML having uglier and more verbose XML. If I recall correctly this was only a small part of the size difference.

2. OOXML was way more complete. This was a big part of the size difference.

The first approved standard for ODF for example gave no details on how formulas worked in spreadsheets. All you could get from the standard was that you should support formulas.

The OOXML spec on the other hand described in detail the format of formulas and gave detailed specs for a large number of functions. There were often 2 or 3 pages for a single function.

3. When IBM and Sun were touting that 6000 page number for the draft OOXML spec, they were using a printing that has something like half as many lines per page as the printing of ODF they were comparing with.