skysight-inc/HackerNews huggingface dataset:
Exactly.

Plus, we need to hold all other variables equal, so we can be sure what the causation is. And best of all we should use the gold standard, randomized controlled trials. With this method, some states/countries get randomly selected to implement a policy, but they don't even know about it, and to make it double blind, we also don't know about it until after the trial.

Anything less is unscientific, frankly.
This argument I'll classify as "might makes right."
Please Give Us Feedback
I’m worried that our landing page is not optimized for conversion. Can you please give me feedback? https://www.sumizeit.com
sqlite> create table numbers (val int);
sqlite> insert into numbers values (7);
sqlite> insert into numbers values (8);
sqlite> insert into numbers values (9);
sqlite> insert into numbers values ("hi mom, I'm a number!");
sqlite> select * from numbers;
7
8
9
hi mom, I'm a number!

I agree that SQLite is great, but do you really want to standardize on that behavior?

People will write applications that insert 41 characters into a varchar(40). And they will care when their sites break when constraints start to be enforced.
Has been true since the days of Web Audio and is still true.

Context: I was a member of both the Firefox and Chrome development teams at different points.
mmap would make WebAssembly a lot better, unironically. Even if it was only supported for read-only pages. A lot of cpu time and IO are wasted doing reads into temporary buffers that then get copied into the wasm heap.
I was looking into java and kotlin - but even the people talking about modular monoliths weren't happy with the current module support in java.

The language should support separate teams writing modules to be used by other teams. The modules themselves would publish their public methods but really allow a group to turn up the encapsulation and hiding to the max. Users of a module would be forced to not even know about private variables or methods. They'd just get a compiled artifact and documentation.
On the Internet nobody knows you are a mouse
> What do you do with libraries shared between different deployment targets?

The short answer is "make an awkward compromise". If it's a library that mostly belongs to A but is used by B then it can live in A (but this means you might sometimes have to release A with changes just for the sake of B); if it's a genuinely shared library that might be changed for the sake of A or B then I generally put it in a third repo of its own, meaning you have a two-step release process. The way to mitigate the pain of that is to make sure the library can be tested on its own without needing A or B; all I can suggest about the case where you have a library that's shared between two independent components A and B but tightly coupled to them both such that it can't really be tested on its own is to try to avoid it.
That's a style decision, not a correctness issue. You are claiming it is a correctness issue.
Don’t, keep things simple. Maintain a separate archive of each individual repository and any history can be referenced in that repository when necessary.
The pressure from well distributed static load divided by area is not, but on the tiny scale where the difference between grippy and less grippy surfaces happens there isn't so much "well distributed" going on. And once you add lateral force to the mix all bets are off: there will always be a point getting better grip (is surface interference the correct term?) than others, see a local force concentration and when that causes a tiny spot of phase transition there will very soon be a new point of least local slippyness getting all the attention of lateral force.
It is easy for children to come up with questions for biologists that none can answer, and that none has even tried to answer.

Biologists are almost unique among scientists in being happy to say how little they still know about their subject. Up until last year nobody had thought to see whether anything eats viruses! Turns out some do.
The imperial system (or any adhoc system developed over the centuries) corresponds to the scales of human body and condition. Le Corbusier attempted a synthesis of a rational (mathematical) system that scaled appropriately. He used the Golden Ratio as the scaling mechanism. The very fact of that attempt carries an implicit critique of using the metric system for human centric design.

https://m.media-amazon.com/images/I/51hAE7WuQZL._AC_SY1000_....
Does anyone have a pointer to a tutorial or example of what a successful monorepo and process looks like?
The Partition Function
Think of the universe as some sort of information system. The speed of light caps the rate at which information propagates, which is a desirable or at least necessary property at scale. But there’s some discrete substrate underlying that propagation of information. That substrate can multiply, like inserting nodes in a graph or empty spaces in a linked list. That makes it longer to traverse from one end to the other. The rate of propagation stays the same but the map keeps changing.
Feb 2022 Safari said it's available in Safari in macOS 12.2 and iOS 15.2 https://webkit.org/blog/12257/the-file-system-access-api-wit...

However the sqlite demo page says OPFS is unavailable for me in Safari https://sqlite-wasm-opfs.glitch.me/ ...unsure whether it only supports a subset of the APIs that the official sqlite build uses?
I think that's a bit misleading (disclaimer: I very much like Bazel existing, though I think a better version of it could exist somewhere).

Surely a lot of work is put into Bazel core to support huge workflows. But a huge amount of work is put into simply getting tools to work in hermetic environments! Especially web stack tooling is so bad about this that lots of Bazel tools are automatically patching generated scripts from npm or pip, in order to get things working properly.

There is also incidental complexity when it comes to running Bazel itself, because it uses symlinks to support sandboxing by default. I have run into several programs that do "is file" checks that think that symlinks are not files.

Granted, we are fortunate that lots of that work happens in the open and goes beyond Google's "just vendor it" philosophy. But Docker's "let's put it all in one big ball of mud" strategy papers over a lot of potential issues that you have to face front-on with Bazel.

Once it works though... beautiful stuff.
ZipWall Dust Enclosures and Temporary Walls Review (2012)
But, but, my modularity microservices as my self shibboleth that we are going to google scale next week right after I figure out what our product is!
The PM role gets described as the "CEO of <product area>" which I think translates to people thinking the role is ultra high status.

The best PMs I know operate like CEOs in the sense that it's someone's job to scrub the toilets, and until you figure out how to afford/hire someone to do that for you ... you're scrubbing the toilets yourself. Someone has too!

The 0% interest free capital environment distorted the PM role though, especially in land grab cultures. Imagine having enough budget to hire a 4-6 person squad of toilet scrubbers (and golden toilet) so why ever clean it yourself?

So sorry for the crappy metaphor, but that's why I believe PMs are on the chopping block right now. Not because there's something intrinsically not-valuable about the role. From the perspective of Tech Lead / Staff Eng in a Big Tech Co, good PMs created clarity and helped my team(s) execute. The worst PMs created ambiguity, and the worst of the worst pushed ambiguity+responsibility down as far as they could.
Cheers to getting our hopes up. Hope is pretty cool.
He's passed, but jacob bekenstein?
,,a loss of epigenetic information is a reversible cause of aging''

While it's probably the most important cause of aging, reversing it may be not enough.

Also currently there's no way to prevent cancer cells from being created.

,,Simply titrating the amount of Yamanaka factors that we express, whether by using mRNA, or by having inducible promoters or whatever… these things will stop the mouse or the human from getting teratomas, but I don’t think they’re going to stop them from getting regular cancers, simply because the body of even people your age or my age is already chock-full of cells that have spontaneously accumulated most of the mutations needed to become cancerous.''
Lost manuscript: How to overcome procrastination and achieve higher daily LOT as a scribe.
That's more or less it, as far as I understand. There's the hexagonal lattice of solid water ice, where hydrogen bonds form a 3D tetrahedral structure which is very stable. At the boundary, there are no molecules "above" the solid latice, so those water molecules are held less tightly. The exact dynamics are challenging to predict because we can't exactly see what's going on (most simulation based).
Don't just look at the execution you are building for, but also the team that will be maintaining it. That is, there are several values for "who" that you are building for. Each will have cause for you to reach to more complicated seeming solutions, as you go.
The first successful space mining company will be one that “mines” the debris currently orbiting earth. It’s simply a matter of physics. There’s over 5 thousand tons of already refined metals orbiting earth in the form of rocket stages and defunct satellites. Even accounting for all the orbital changing manoeuvres and the necessary fuel, it’s easier to go after a couple of old retired heavy geostationary satellites than a far away asteroid.
I don't know which idea is harder for me to conceptualize.

That something has always existed or that it came to exist out of nowhere-ish.
All current nuclear reactors run on U235 or the barely significant dregs of Pu239 left over.

They do varying amounts of breeding to produce up to 50% of their energy from Pu, but the fuel source is always U235. Leaving more U238 with it in a HWR doesn't change this.

> And we certainly have enough uranium to not run out of it for 200 years, with the current technology

At the current (insignificant) portion of final energy they produce. Increase it 10x for just the current electrical grid and it's <20 years. Switch to SMRs which are inefficient and it's <10.

If you want people to take nuclear seriously, try telling the truth about anything at all at least once, ever.
I've been skeptical of shamans among us in Western civilization, assuming we've moved too far passed that and lost it, but recently I watched "The Mindscape Of Alan Moore (2005)". Moore is certainly a shaman.
You seem to be conflating violence and murder. Yes, mens result in death more often, but data shows women and men are both comitters of domestic violence.
Didn't that happen within like the first 2B years? First Sol-like systems were I think at 5B years, which would still make Earth ~3B years late to the party.
The same reason people keep playing a MMORPG even though they have already maxed out.
You still didn't prove the non existence of cryptographic backdoor, hardware backdoor or anything else in the chain.

There's also a decent chance the audit fail, then now what do you do? A person can be unreachable. Do you now cancel the entire system because a person was unreachable? If the answer is no, the audit is useless. It was already proved many times that audits which don't have any penalty or contingency when they fail are meaningless.

Moreover, You can't trust anyone's random other than your own. In this case, the so called auditors are also a small point of failure, and if you allow any1 to audit, people will eventually find someone who's missing.

Audits are like stack cookies, they are terrible security practice. You need to have security boundaries and defend them to have a good security system. Attempting to check if the horses left the stable is not a reliable boundary, it's good only as supplemental security measure. Just like having a blue team and a red team isn't enough, you need to have firewalls, you need to have defensible network architecture. You need endpoint protection, and you need to keep everything updated.
Not it's not possible. Bike transportation reduces automobile demand for the main demographic that buys Teslas - urban professionals.
Agree with all the above comments. Making a bunch of rapid DNA cuts outside of genes is not all that convincing of a model for aging. "The mice began to look and act old". You could say that about someone exposed to massive amounts of nuclear radiation - they move slow, they hurt all over, their skin sluffs, etc. Also afaik, aging has been linked to telomere depletion after many cell divisions - not the cumulative effects of random DNA cuts. Lastly, I have reservations about the author's statement that this approach is better "because it’s easier to manipulate epigenetic molecules than to reverse DNA mutations". This might be true if they are globally altering DNA methylation or acetylation. But that will surely have its own side-effects due to globally altering gene regulation. However if it turns out that it'd be best to only target particular methylomic sites, it will be similarly difficult to implement. In general, it's typically better to be precise when it comes messing with DNA and gene expression - of course the tradeoff is that being precise is very difficult. I'm interested to read the original article, to see what they've actually done. as it is my sentiment is the same as those above - I'll get excited when their method significantly extends the lives of mice that have underwent otherwise normal aging.
Step by step guide to defining your company core values
And Wizards delaying the new OGL release amid protests: https://gizmodo.com/dungeons-dragons-ogl-announcement-wizard...
Submodules are hell. I work somewhere with a polyrepo topology, with the inevitable "shared" bits ending up integrated into other repos as submodules. Nothing has been more destructive to productivity and caused so many problems.

A plain old monorepo really is the best.
Most countries don't. American immigration is a mess with unknown delays and archaic processing techniques. Just because the employees get a 2x multiplier in earnings doesn't mean the immigration pain is worth it.

In a land of immigrants - having such a poor immigration process for highly skilled employees will only mean that the best and the brightest talent will no longer be interested in moving to the US when they could get treated much more fairly in other countries. The result will be the workforce will be filled with mediocre and sub-par talent who are willing to go through the painful delays in the immigration process.
> For me, personally, I'm on friendly terms with neighbors I meet on walks, plus the ones that live in proximity to me. The news gets shared as it always has done.

Except by the time it gets to neighbors on a walk it's yesterday's news. What I'm talking about is up-to-the-minute safety for events that have happened in the past 15 minutes. Only online communication and instant phone alerts are fast enough for that.
I mean, Elasticsearch does a whole lot of stuff, and I wouldn't expect a 'super light alternative' to do everything Elasticsearch does. If I were still dealing with ES, I'd look to see if it did the small section of stuff in my use case and if the API was reasonable and if it had a sensible operational profile and if it hit all those points, I'd try to use it, because I sure wasn't happy with ES.

Note that a reasonable API doesn't require it to match the ES API, and if I'm feeling really bitter, doesn't even include the ES API.

Now when someone says they're a replacement that's a lot more specific; I see ZincSearch makes a qualified claim of that form, if that's not accurate, then yeah, it's worth complaining. But lots of things are alternatives without being replacements (and really replacement doesn't always have such a narrow meaning either, kind of depends on usage)
Model facts, not your problem domain (2020)
Hopium is a powerful drug
Given the lack of details, my guess is that your role at those startups is wildly different from your role at the middle-sized company and also that these aren't necessarily comparable companies outside of size and age. 3 is also a stupidly small sample size for what it's worth.
> as if that would even matter, as I've discovered that no one actually ever seems to look at open-source code

there are 3 circumstances in which i regularly look at open-source code:

a. i want to fix a bug or improve some rough UX.

b. i want to add new functionality.

c. i want to borrow something from it for use elsewhere.

you’re right that the better your code, the less likely i am to read it for reason (a). and the more sophisticated your code, the less likely i am to read it for (c), as i’ll be hunting for reusable libraries rather than cribbing directly from applications.

but consider that for any commercial product, i’m also less likely to read the code for reason (b) because of largely unwritten cultural norms (if i contribute code to a project that has paid devs and don’t get paid for that, it feels like i’ve been suckered).

this being an iOS app exacerbates all this because even if i find a bug and suspect a one-line fix that would be worth my time, i won’t pursue it because i have absolutely no idea how to deploy my patched version (i have to register with app store, maybe pay some licenses/fees, does Apple even allow me to distribute patched versions of someone else’s software?)

so, yeah, you’re not wrong, but you’re also working in a context that really amplifies what you witness around open source (and if you specifically want your beautiful code to be read by others maybe this shows which approaches are more/less likely to get that).
Pop up with 'accept all' for cookies, no 'only necessary' button. I would click away based on that alone.
> It's one of those non-linear messy quantum things that's a pain in the neck to solve.

That is exactly equivalent to "dunno, maybe something".
A GitHub Action to overcome the limitation of GitHub's built-in traffic stats
I mostly agree with this, and haven't been happy developing JS for some time. I don't enjoy having to deal with bundles, webpack, TypeScript, bloated dependency graphs.

Luckily I can use Go for new projects, and even when picking it up at first I quickly found it more pleasurable to use than NodeJS. I don't JS on the backend if I can avoid it.

On the frontend, I would still argue on balance SPA/bundling is the best option when your company is developing an application. I appreciate that for many things HTML/CSS with minimal JS works well, but for anything dynamic where you have a team of devs, the community and dependencies around React are too useful to replace with much else.
Geothermal Heat Pumps
Well I can see the attraction
For everyone who complains about monorepos, remember some of the most forward thinking engineering companies like Google and FB also use monorepos. All the arguments that people make in favor of polyrepo are making so because of lack of strong tooling for monorepos. That's also why Google and FB would not have scaled if they were using GitHub / GitLab but had to build their own. Also Google's original source control was built on top of perforce!
Because breeders with closed fuel cycles don't exist, and Pu240 breeders double don't exist.

They're just a fiction used for marketing and to buy social license for the plutonium separation facilities.
Is the 6GHz burst mode faster per MH, per core compared to, say an AMD Athlon T-Bird @ 1.4GHz.
Hmm, interesting. I feel like that clustering/grouping part is like... the first stage on the way to finding an abstraction, but if all you've done is that part of it, then you haven't reasoned about what the abstraction is, or extrapolated out to a new hypothesis, or grappled with the other consequences of the grouping.

Thinking of mathematics, an abstraction is only as valuable as what it can tell us about the underlying system— a laplace transformation into the frequency domain isn't particularly interesting unless we either a) happen to care about some frequency domain property of the function, or b) we can manipulate the transformed function and then un-transform it afterward, yielding a novel insight in the original time domain.

My layman's assessment is that the current state of the art for machine cognition is about on the level of identifying that such a transformation might be possible, but not actually applying it or doing anything about it, much less unapplying it afterward.
I agree that ubiquitous ar is going to happen and that is indeed a big thing. But I’m not sure the metaverse is going to be its beginning. Facebook is looking for the next big thing they own. And no one will wanna play ball with them as they lost everyone’s trust. (See the mess that was libra)

For me it’s more probable that the ar stuff are going to start off with someone like apple, with a very different vision than fb. Think smart tags with uw1 chips around you in the physical world that your ar glasses can see and read metadata off them that allow you to annotate what you see and interact with them. I don’t think ar will start in vr, but rather the real world.

Ofc this is all complete speculation and wishful thinking.
I suspect this is why simulation theory is popular.
I have the most expense with Nx and can only speak to that. Nx projects are tied together with a dependency graph. The workflow/pipeline replaces something like "npm build" with with "nx affected --target=build --base=main". Nx compares the code to the base branch, identifies the leaves of the tree (projects) affected by the code change, and runs the specified task for each project.

Each project can specify what that task (technically the "target") means in it's own context by directing it to run a specific "executor." For some projects, "build" may run a Weback executor, others may map it to run a Vite executor.

Edit: To summarize, if you change something deep down in the tree like a design token, you can run the "test" and "build" tasks for everything affected by that change to make sure none of your apps break. If those projects are SPAs built in different frameworks, each can map the task to run the framework specific "test" or "build" executor. Now you have automatic assurance that all your apps still work. If that sounds like a lot for the CI to do, that's where distributed caching the of task results come in.
Oh, let me introduce you to metastability ....
Not really? From what I read temperature there is few hundred degrees higher than here.
Unless it's tidally locked "eyeball world" then probably not too livable.
Cook helped make those devices commercially viable at scale. They’re secret one day, announced the next, and become available to millions within a month. All of this with a huge margin and a global supply chain.

People misunderstand Jobs role in all of this IMO. He wasn’t doing the inventing, not personally. He was responsible for identifying and hiring people like Cook and getting them to play well with other brilliant people, like Ive. He talked about this, like, all the time.

These brilliant people would then create coordinated design/production processes that gave the company such strong inertia that the products arrive improved and on schedule every year.

All Cook has to do is keep the course - and he’s clearly very good at it.
100% worth it to me. I love typescript. Working on large enterprise applications where one function calls other function and it goes 10+ layers deep I don't know how I would work without typescript. Just being able to see this function takes argument of type FOO and returns type BAR[] is incredibly valuable.
I look at open-source to learn new programming languages, especially their idioms.
Yeah also this CPU user won't utilize it at 100% on 24/7 so it's same efficiency as non-K for most of time.
JR East has 12,500 bits of rolling stock and 50,000 employees. BNSF has 8,000 locomotives and 41,000 employees. They're listed on the stock exchange and clearly have more than a few garden toys.

Also, who implied that railways need to be privately owned?