skysight-inc/HackerNews huggingface dataset:
One obvious requirement for bisect to work is that your code builds on every commit - and so does everybody else participating in the git history.

Straw poll - do you enforce this? If so, for literally every commit, or do you use partial squashing to maintain this property?

While that's certainly a _desirable_ property, I've never really been concerned if, say, the penultimate commit on a PR failed CI. It feels like it would be a hassle.
Time will tell if this will be any better than Chromium's (I say Chromium, because I actually don't use Google's tracking-infested Chrome) multi-process architecture in both security and performance.

I can say for sure that Firefox' hybrid approach is causing issues performance wise, and I doubt it's as good as Chromium's security wise, too.

Microsoft seems to follow Firefox more than Chromium here with this hybrid architecture, so I'll remain skeptical about its performance and security for the next few years until the architecture has proven itself to be better.
Timeline of Scientific Thought
Teams give FIA the data and Ferrari gives pointers and other help. The sensitive data is not shared with Ferrari.
Hey cool I was just looking at that.

I wonder if I could run Whatsapp in this, as a bridge to Whatsapp Web (for its Matrix bridge).. It should be more efficient than running a full Android VM from the Google Dev tools.

Has anyone tried this? I suppose the biggest issue will be the scanning of the QR code, as I don't think webcams are supported.
In the study they use onset of symptoms to derive who got infected first and spread
Tell him you'll do the service and support on an hourly basis.
Most filesystems that are designated as "modern" include checksumming, snapshots, cow, etc.

However, do some include support for CRC? That would allow not only detecting, but also correcting bitrot.
I assume that's what Raid6 does, albeit less granular than per file, and more aimed at recovering a full file than a few bits?

Can anyone point me to a FS that supports it, or to the reason it's not done?

As for ZFS, I think I'll keep avoiding it until it is mainlined. I don't really want to play that game.
Are you sure that forbidding non-competence clause was really a big factor in Silicon Valley success. This sounds a little bit to simple. I was reading that it was all about initial founding from the military, access to large capital investments, proximity of good universities and existence of whole ecosystem targeted into making creation of startups easier.

In Poland non-competence exists too, but in theory - it can last one year at most and employer has to pay 25% of the last employee income (missing a single payment invalidates clause), so, giving the trouble of paying, handling accounting, etc. companies rarely use that (oddly enough, if this clause is used, it is used for sales people) and I don't see another SV build anywhere here.
Opensuse with btrfs is my drug of choice.

Btrfs is on the kernel and just works.
If you are an engineer for Palantir: please quit.

I don’t judge you for taking the job, wanting to be paid well, maybe believing in some idealistic variation of the company’s mission that can be twisted to purport to help people.

It’s not about you or your reasons. It’s about the destructive force Palantir represents if it can go unchallenged while amassing deep connections to public sources of revenue in municipal police forces and national defense or intelligence agencies, and ultimately branching into corporate security and espionage and facilitate employers spying on employees.

Please quit helping the leadership of Palantir. It’s an awful, awful thing for the world - much more morally awful than rank and file corporate misbehavior. Palantir is a difference in kind - enabling & facilitating a vastly more oppressive future and stamping out pathways to achieve privacy and individual liberty in a big data world.

Be the person who can proudly tell your friends and family, your children, one day when looking back that you had the courage to quit and you put society’s welfare above your own potential path to luxury.

To everyone else: don’t consider ever working for Palantir. Don’t be lured by the pay or fooled by a false depiction of the company mission. It’s not helping people. It’s not a civic duty. It’s not a positive force for the world.
CDN providers often provide static website hosting as a separate service though. Cloudflare offers "Workers Sites".
True that. We seem to struggle so to get all that power on the road for quite some time:

- TVs: Went first to Japan and then Korea then China

- Cameras: Went to japan

- MP3: Went to the US

- Cars: We totally missed the trend to EVs

- Big engineering projects: Pretty bad track record so far, e.g. the Berlin airport. German companies are still supplying components and sub-systems to these projects worldwide, but they are rarely the general contractor anymore.

It would be nice to see that being changed, but everything that is new tech just seems to be an unsurmountable obstacle for a lot of German companies and institutions.
I guess It's my development culture is flawed, but as one-man-team I always time constrained. So I sometimes don't have sufficient time to write too detailed commit messages.

So I end up with "one commit per feature" rather than "one commit per logical change". So I actively using squash during interactive rebase when I prepare to merge completed branch since my commit history sometimes looks like this:

Backend: new set of APIs for XYZ
Backend: implement feature X (+ some long comment)
Frontend: implement feature X
fix for feature backend
fix for backend API XYZ
front fix
backend fix

Yeah again I know I could do better, but yeah I use squashing for this reason. A lot.
> I get 8ms even to my WiFi router, how can you have such a low response time?

That’s almost assuredly a sign of radio congestion on the channel you are on causing retransmits. It could also be a poor quality AP or you could have to many clients on your AP, but most likely it’s the first one (in band interference causing lots of retransmits) based on experience.
The argument for squashing is that minor updates like spelling, renaming, or test fixes during initial development can really clutter the history if they each have a commit. Many would rather see the actual change "Update X to use Y instead of Z" in the history, and minor details like "Fix mock in XTestCase" or "Perform renames from code review" within that single commit.

I'm sort of agnostic on this issue, but I do feel the article's author kind of overstated it here. Say 5 to 10 commits of this size were squashed together. Git bisect would've taken him 90+% as far and he'd have to read code or manually trial and error changes just slightly more. The binary searchable problem space would be slightly smaller, and the linear manual effort space slightly bigger. Less good, but really not that big of a deal.
But I guess that's why, in some countries, people who had a high probability of catching the virus are told to stay in quarantine even if they tested negative.
It seems that way. I hadn't noticed. Is there some alternative that's being maintained?
> Also, RAID is not a backup.
You are absolutely right, but there are use-cases where backup is too expensive, so investing into robustness and availability is the only option left.
You have to go dig the branch out of the central repo, though, which is annoying and takes time.

That was the price I was thinking of.

You're certainly right that PRs and large commits are orthogonal.
Having been wondering if it were he or Dumas who came up with that line, I found:

https://history.stackexchange.com/a/28484

but a quick perusal of de Motteville's bio suggests she had been exiled from court at Richelieu's behest, so she may not exactly be a disinterested observer, but was probably very aware of court politics in the years before her arrival.

For what it's worth, I haven't been able to find (Isaac de?) "Laffemas" via full-text search of any of the scans of her memoires I've turned up. (Two of them I searched for "innocent", a word seemingly rare in court memoirs, but no luck there either.) Gallica has a much longer scan (about 50% more pages) but it doesn't seem to have been OCR'ed, and I'm not going to manually check 630pp.
> Mercedes win, not because they also produce the engine, but because they pour nearly half a billion euros into the car

It takes more than just throwing money at the problem to win. Otherwise, Red Bull (paying for two teams in full) and Ferrari would be doing a lot better right now.
If you squash all the merge requests, you get ONLY merge commits.
A Common Plant Virus Is an Unlikely Ally in the Fight Against Cancer
No link between schools and coronavirus infection rates, global analysis suggest
Software development is a gigantic thing.

You can program microcontrollers.

You can simulate natural or artificial phenomena.

You can recognize-process sensors that measure the world.

You can train deep and neural networks.

You can manage hundreds or thousands of computers.

You can create web servers, services on Internet.

You can create web clients.

You can create apps for people to use or apps for companies to use.

Each of those areas has their own specific issues, and make development totally different.

To say that software development is a craft because what you do in particular is craft is just not being conscious about the huge landscape of possibilities out there.

I do software development and most of my work and my team's is software engineering.
I wish someone would do the same for Russian:
Basic Русский
The billionaire doctor duo behind President Trump’s experimental drug
I upgraded to a Xeon processor because LUKS encryption was way too slow on the stock Celeron.
Disclaimer: The following is my own speculation, and not to be taken as hard facts! I don't think it's the technology in the cars that are relevant, as much as the tooling around developing the car is. For instance advances in CFD simulations will help in developing cars, ICE and EV. In any case, road relevance is an odd reason to do racing, as rarely do anything directly trickle down to the road car division.
Maybe it depends on what you mean by "recipe for success of Silicon Valley" but I doubt weather has primary influence on the recipe. Sweden, South Korea, and Switzerland are considered the top 3 "innovative economies"[1] in the world and aren't particularly notable for their weather.

[1] usually this means a mix of #patents filed, number of phds/100,000 and r&d expenditure/gdp. Not sure how you would rather measure the success of silicon valley to set it apart.
Content vendors operating like this has cost me a lot of money. Not in terms of lost content, but in hard drives. I steadfastly refuse to relinquish control of anything I've paid for, so nearly every piece of licensed software or entertainment I've ever purchased has a pirated copy tucked safely in my archives.
Broadly speaking, the preferred approach to albedo modification seems to be sulphate aerosols in the higher atmosphere.

A notable secondary approach is to modify built-up areas like cities to be more reflective: mixing recycled glass into pavement, using light colored roofs, and other passive modifications. This has the special advantage of reducing the urban heat island effect, reducing emissions associated with cooling.
Please !!! Read the article; This is from CSIR Govt. Labs and not some BS company CEO.
It makes the initial bisect easier and faster as well, because every commit is a fully working one, and there are no trivial commits that still have to be rebuilt and bisected over. Plus all the commits are found in the order they were introduced to master, rather than randomly interleaved with other feature branches that were built at the same time. Personally I would think any kind of branch cleanup to get the history of a feature branch into a presentable state is a significant price to pay. I've only had to restore a PR branch a handful of times to find the particular culprit.
Buzzfeed News actually has quite a strong reputation for doing very good investigative work. Your comment is an unfair smear.
Those may look like jet plain candies, [1] but I think they are in fact tux the penguins feet.

[1]https://corpcons.nz/images/thumbs/0062343_pascall-deltas-jet...
I've seen this problem on /r/bestof on reddit - submitting 2011 comments and such, when everyone implicitly assumes comments submitted are present comments.

IMO any sort of news/event post that's not recent (say, in the last month or so, or at least within a year of the posting date) should be required to add a "[2012]" (or whatever year it was posted) to the end of the title.
I'm not saying this is definitely intended, but it kind of bothers me that this title seems to imply "Saying no to almost everything might make you successful".
They are relatively enforceable as part of a compromise agreement. However the last one I signed was quite restricted in that it was for 12 months and only listed 4 direct competitors. Normally the companies lawyer tries for more and your lawyer tells them to get real.

If you don't sign the agreement I suspect a lot of the time you'll just have to do gardening leave for the rest of your contract. Also don't forget if you were a director you still have a fiducary duty to the company once you've left.

What I'm slightly unclear about is how practical this is for sales folks where this is an expectation they will steal prospects or existing clients. I suspect you might only bother with lawyers if it looks like they are poaching from your existing clients.

In the UK non-competes in my view for engineering staff are basically unenforcable, IP theft is much more likely to succeed (and I've been involved in a direct copyright theft case).

24/7 IP ownership is enforcable but my experience is that most places don't care if you're not going to be a direct competitor. I always feel it's worth getting that in writing though, my current contract limits this to areas of the companies business. Our corporate lawyer limited this when we had to sign a new contract post a takeover (it was a bit broad and could have covered things like photographs of your kids). Also I have in the past asked if I'm contributing to open source as part of my work as like things to be clear.

IP rights is probably the one area I check in a new contract and usually it's fairly easy to get agreement for some minor changes.
A quick word of caution: RAID is not a backup (as already mentioned elsewhere in the comments). Even more so in home solutions whether they are DIY or off the shelf.

Why? Because storing a single copy of your data on a single local RAID array doesn't protect you from disasters such as fire, theft, accidental fluid spills, small children/pets, a power surge after a lightning strike, flooding, and so on. Basically, a lot of the stuff you'd fine in your home insurance policy.

RAID doesn't guarantee data integrity either. You lost data after an unintended deletion or corruption by some computer program? RAID won't help you get your data back any more then a single disk scenario would. If the original file got overwritten and mirrored across the array, and all you had was that one copy, you won't be able to go back to that original.

A more exceptional scenario would be a drive silently failing and RAID happily mirroring corrupted data across the entire array. Unless you use a filesystem that implements checksums - like ZFS - you wouldn't notice this unless it was too late. [1]

[1] https://superuser.com/questions/112683/does-raid-1-protect-a...

I'm not advising against RAID. I think there's merit in using RAID when it comes to convenience and availability. Like, your data remaining available when you experience a sudden disk failure, and not having to spend hours or days getting everything back on line again.

I'd say that RAID and backups are complementary.

So, what about backups then? The 3-2-1 backup strategy is a good start: 3 copies, 2 local, 1 physically remote. That could be as simple as copying your drives every week to a separate HD or SSD drive, and every month to another separate drive which is safely stored outside of your home, i.e. a family member, friend, or at the bank.

You could step it up a notch and choose to rsync your data across two connected drives, while rsync a third copy to specialized cloud storage service such as Borgbackup or Wasabi. Add in scripts that perform regular checksums control and reports the results daily and you've got a pretty solid solution.

The final step is looking at your data and differentiating between the stuff you absolutely can't afford to lose (e.g. family albums) and the stuff you may afford to lose (e.g. software downloads). The goal here is to calculate the costs associated with required storage volume and bandwidth, and land on an appropriate backup solution that matches your budget and your needs.

Finally, that's just safeguarding your data in the present and short term future. Neither RAID or backups are a long term preservation strategy. Which is a whole other can of worms, including such challenges as migrating obsolete data formats (Yeah, I have WordPerfect 5 and AutoCAD files in my own personal archive), or dealing with obsolete hardware I/O (Yeah, I have a bunch of old IDE drives in a cardboard box for which I had to buy an I/O converter).
I've done this maybe once or twice a year.
Cool, will check it out! Thanks. Yeah, you learn a lot from it. :)
I've always been careful about this even though I've not had the habit reward me yet (3 years of exp). If I'm rebasing, I go through every commit and make sure it builds.

TIL about `git bisect` and it's really vindicating.
I wrote "100 mb/s" - I now realise capitalisation is important.
Agreed, that contents page is oof. But given that it was last updated in 2012, I doubt it is something that will change.

It's dead Jim.
Phabricator has a quite different (I would say better, others would say worse) development flow philosophy to GitHub/PRs.

Phabricator’s preferred model, which is heavily influenced by Facebook, is to forgo feature branches entirely and just stack many small changes on top of each other, landing as and when you want (this doesn’t preclude you working on feature branches locally, of course, because Phabricator doesn’t care what your local checkout looks like).

Because of this, Phabricator considers each diff to be discrete, and if you have multiple changes making up a single feature they should in turn be broken down into separate diffs.

Personally, I think stacked diffs are the killer feature of Phabricator. Unfortunately I haven’t been able to find a similar flow with PRs (recently we migrated from Phabricator to GitHub for one of my projects), you end up fighting against the tool a lot.
I'm well aware. I did post the etymonline link, after all. However, it doesn't change anything. The series of glyphs used by the OP author hasn't represented what he meant it to represent for centuries. It's still a deeply archaic usage, whether we're dealing with a single word or two homonyms.
There is no such requirement, you can just skip commits which cannot be tested. You just make a simple test-case just for current bug outside the repo.
Here’s the real lede:

> Ibanez’s YouTube channel, which chronicles his life as a vendor, boasts 362k subscribers and now earns more than his machines.

The margins on vending machines are tiny and the net revenue is not enough to sustain much beyond minimum revenue. If you had a few hundred or thousand machines this would be a great business, but it’s a long way up from 1-2 machines. Many of the people in this feature are boasting about only having to do 2-3 days of work every 2 weeks, they won’t get the scale they need.
General comment: posting a random study and drawing conclusions from it seems dangerous. This kind of science is hard, so we usually rely on a spread of evidence from many sources, building literature until conclusions are more robust - often through meta studies.

I think it’s a bit dangerous for an intelligent HN reader to go looking at scientific papers without properly taking a systematic approach to cover all bases. A much sounder, yet less exciting, method is to rely on the advice of expert organisations such as the WHO.
What's a tarsier raven? I can't find anything describing that common name; I get back results about tarsiers and results about ravens, but nothing that combines the two. I wouldn't necessarily expect it to be in any of my bird books, which mostly only cover North America, but it's a surprise for Google to likewise come up empty.
I religiously squash my commits for each merged pull request.

I seems like madness any other way to me... why have a bigger granularity than a single merge commit?
> Multiple times I've designed systems where I've reduced the representable states to the minimum, and when some requirements change I realize I have to re-design the full system.

Yes, if requirements change, you change the design and code to support the new requirements.

Compromising the consistency and maintainability of the current design to accommodate a hypothetical future requirement change is a bad trade-off IMHO, since you can't predict the future. A requirement change may happen in a completely different direction than the one you anticipated, and then you have the worst of both worlds.

It is better to make code maintainable than making it flexible.
Navigate to PR -> Restore Branch -> `git checkout <branch>`

How is this annoying or time consuming? It takes less effort than adding, committing and pushing changes.
Another example is Go's runtime.LockOSThread(), which will run a single goroutine exclusively on that thread.
Lockdowns Intended to Preserve Our Health Are Making Us Poorer and Angrier
Apple: Remembering Steve
Yes, but that is still outside of IT's control.

For my team to use this I'd need to be able to store the data in house.
Well, there is also the LUKS encryption overhead which caps transfer rates from the RAID. I also run boinc (giving back to the community) which limits available CPU.
I was baffled in school how tRNA "moves" amino acid to ribosome. Asked and got no answer.

Found out much later — tag so many amino acids, that it would stumble on ribosome. Genius.
We go through ~600 commits per day. In my experience, there's nothing worse than looking for when a value was changed from 10 to 100, and finding it in a "Merged from X" commit with the history of why the value was changed from 10 to 100.

I don't often (ever?) browse the history, but I _do_ regularly search the history using tooling, (git log | grep <something>), and more is more in that case, even if the history isn't perfect.
We use JavaScript at work so even if a part of the application doesn't compile, we usually can run most of the tests. We don't bisect very often and so far, every commit has been good enough for the specific tests we wanted to execute in case of a bisect.
This is a pile of bitching crap. Google has a centralized synchronized model of work, constant Internet connection, a running build system and lots of compute power. Not everyone covers those bases and even the author does not offer something better at the end. Waste of time.
Cool, now take ALL of those things you listed and now include the fact that in F1 they have to develop and build an entire car as well
I've heard this a couple of times and it seems a bit strange. My bank is entirely online and has a very nice app (USAA) but there's absolutely nothing that can be done in the app and can't be done with their webpage.

Is this something that happens often in eg Europe?
Thanks for pointing this out. My recollection was inaccurate.