skysight-inc/HackerNews huggingface dataset:
If the code review process is (through your supportive wisdom) pushing the people you work with to follow those practices, then I would argue it is actually a pretty good process. Those are all very good things to do, that a good code review culture should definitely be pushing people toward.

For instance, let's imagine this without the code review process and your subsequent advice on how to make it go better: People would just be merging in the 20 file PRs, sight unseen, without validating a strategy beforehand, without really knowing how to approach the problem, with the code just written and slapped together without tweaking and refactoring, and without any self-review using a critical eye to catch low-hanging fruit like leaving in console.logs calls. I think the "flawed" code review process seems like a much better outcome!
US federal law says a search warrant can't be issued against journalists to anything that remotely looks like reporting. Instead police must subpoena a journalist instead to show up with the materials requested. The journalist can then get a lawyer and quash the subpoena in court.

https://www.mcguirewoods.com/news-resources/publications/med...
Economics in My Fiction
Google (for $reasons) doesn't do long lives code branches and doesn't use git, at least for the main repo. So in that context every commit is reviewed pre-commit, but you'd do the same workflow elsewhere with trunk-based development, small pull requests, and CI and automated and human review of all PRs before they're merged.
https://en.wikipedia.org/wiki/W._Jason_Morgan
It is also for submissions, T. It becomes apparent when you enable the "showdead" option.
Ahh interesting. I hadn’t come across this yet so I assumed they were not detectable!
The biggest problem with SE for me, and this is related to the culture issues you're talking about, is that the site has no good way of deprecating "formerly correct" answers. Even if a better, more correct answer is posted later, the reputation system has a huge incumbency bias in favor of older answers that have accumulated upvotes by being the best available answer at the time.

Their knowledge repository is slowly rotting under the weight of having to ask every time "okay, is this correct-sounding, highly upvoted answer actually (still) correct, or is it 10 years out of date?"
Even if there was white powder in the trash, there's an enormous number of substances and products that appear as white powders when desiccated.
You have no legal basis for saying this, because US freedom of the press rules are about prior restraint, and government retribution isn't prior restraint. You also have no philosophical basis for saying this, because nobody put you in charge of defining what freedom of the press means to everyone else, and you've offered no references to people more respected than yourself on the subject.

But good luck with a definition of freedom of the press that doesn't include when white mobs would break into black newspapers, break the presses, and burn the building down. Does freedom of the press give the government an obligation to prosecute, or nah?
There are auctions for IPv4 space, though they did not really become a thing until after the RIRs ran out of IPv4 blocks. The price per address is about $50.
> Are there incidents that were caused by Controller's error?

There is a nice wikipedia list here: https://en.wikipedia.org/wiki/Category:Aviation_accidents_an...

Of course I don't think it is correct to say that an incident were caused by controller error. It makes it sound like a single controller error was the only thing which went wrong. It is probably more correct to say that controller error contributed to the outcome of some incident.
When you take literally everything that isn't nailed down from a journalism business that needs its resources to operate, it's not really jumping to conclusions to determine what kind of action this is. This is an action to squash the article and attempt to drive the paper out of business.
real hackers were having fun ?
Alright code is a step up for some projects I've seen, lol.
Another great expression I've heard is 'tombstone technology' for pieces of hardware created in response to a particular tragedy.
Lots of little mistakes, here's an accurate back translation

I love Toki Pona. I've been speaking it from a short time. You can see my vehicle at https://www.youtube.com/@janPolijan. Toki Pona is good for fun conversation, but it doesn't have a lot of talking or ways of talking. Its sounds are nice and few. The toki pona community is growing the language. People do a lot of talking and have fun conversations. But toki pona is good for thinking in because of it and is fun for the mind. You'll be able to talk a lot in Toki Pona in the future. You'll be able to say large things. But you won't want to talk about transportation technology in Toki Pona. People talk in about big knowledge gadgets in book vehicles. [lol] Toki Pona is small, but it's fun and can say a lot of things.
It might be an issue with Cloudflare. Could you please try accessing the website using this link again? https://selldone.com
And it's the version I've actually heard used (multiple times) before now - having looked up 'carcinisation', I assume that comes via 'rustacean' (cf. crustacean), which makes it a bit more contrived and then sort of implies the result is a Rust developer, not Rust itself?

Makes more sense to me that a language/framework/etc. would 'oxidise' to Rust, and someone learning/getting hooked on Rust would 'carcinise'.

But this is all silly and doesn't matter anyway, ha!
This looks really cool, thx. How good it performs in practice? What are current bottlenecks, if any?
Unquailfied "freedom to publish without retribution" is obviously impossible. Publishing can be retribution; for an extreme example, see: "Will no-one rid me of this turbulent priest?"

You can make "freedom to publish without retribution" possible only by qualifying the kind of publishing and/or the kind of retribution.
Amazon is rolling out AI-generated summaries of customer reviews for products
This seems pretty intuitively obvious to me - of course landlords, especially those who own for the sole purpose of investing (as opposed to someone who buys a duplex and rents the back), are going to charge what the market allows.

I think Prop 13 is a good thing for the reason it was pitched for - you don't want old people on fixed income forced to sell their homes because property values are going up rapidly. Beyond that, though, it seems like it just extends way, way too far. Why should you get a huge tax break on a second home that you use for vacation or a property that you own solely for investment?
Recommender Systems in the Era of Large Language Models
I agree that the coding expectations are fine-- and I'm not saying you do this-- but conveying annoyance through pedantic, overly nitpicky, or snarky junior code reviews is a management and mentorship failure. In any field, someone consistently acting like a know-it-all is indulging their own emotional shortcomings under the guise of enforcing good practices.

Firstly, if this is a brand new junior and they didn't have the guidance to avoid this problem in the first place, that's on the senior developer(s). These are on-the-job-learned skills, and the reason junior developers make less money is because they need guidance from seniors figuring out how all of that stuff works. Secondly, if they did have explicit guidance, have been advised to tighten things up a few times, yet can't swing it, the senior developer needs to be a senior developer and empathically help them work through whatever strategic block is causing the problem. Finally, if the junior has been told many times and not cleaned up their practices, the senior developer isn't doing them any favors by playing the role of rankled, imperious elder-- the person is likely not cut out for the role, or needs to spend more time learning, maybe as an intern. It needs to be addressed with their manager so the right person can fill that position.

If senior developers don't want to do that then they should work some place that doesn't hire juniors.
Super important point. What seems to be missing at Google today is caring and initiative in fixing anything.

Maybe it’s more of a PM culture thing.

But as a dev (not at Google) I’m used to stepping into self-driven mode when PMs are slacking, and it’s a shame for Google that Googlers don’t exhibit this behavior.
The best is when the only possible reviewer is your Engineering Manager because you have no other engineers in your domain on the team.
I always felt like the Tractatus was similar in form to Sanskrit sutra texts—especially those with hierarchical structure e.g. Panini's Astadhyayi [1]. In the Astadhyayi, a sutra can serve as the anuvritti (context) for a subsequent sequence of sutras, and further anuvrittis may be nested within. This results in a tree-like structure where to understand any individual sutra, one must traverse up the tree to gather all the relevant context. While the enumeration scheme doesn't explicitly capture anuvrittis as the Tractatus does, later commentators did considerable work to uncover the hierarchical structure required to understand the text by clearly identifying anuvrittis.

[1] https://en.wikipedia.org/wiki/A%E1%B9%A3%E1%B9%AD%C4%81dhy%C...
The Paris Theater Celebrates Dolby Atmos Installation and the Return of 70mm
Apparently this is called the "Paper folding test": http://www.cs.otago.ac.nz/brace/resources/Paper%20Folding%20...
The big reason why this library exists is so that downstream consumers can be entirely memory safe in their allocations - it's the same way that the Rust standard library works. Library writers can use unsafe code to provide safe abstractions and APIs, so you end up with an unsafe core with a safe framework on top of it. I'm just continuing that tradition.

I actually haven't read that paper! Thanks for sharing it. What I'm doing is slightly different - it looks like they're building a conservative GC with an unsafe API, much like one might for C. My intent was closer toward building a GC which can be used with any safe Rust code more or less unconditionally.
Yeah the key differentiator was that the other hard disk MP3 players up to that point used 2.5" laptop harddrives and removable AA batteries and fit in a cargo pocket. The iPod used a 1.8" harddrive and a slim built-in rechargeable battery and fit in a jeans pocket (it was pretty huge for a shirt pocket but could fit in there if you didn't care about it ruining your lines).

The term "laptop harddrives" of course confuses the issue: the Macbook Air first shipped with a 1.8" harddrive before it changed to flash storage.
Depending on your intentions, the repo would benefit from a license instead of just using github for code hosting
I agree the onus is to establish a clear culture, guidelines, and mentorship to newbies and junior developers in this regard.

Almost everybody who started their career probably had their first code review torn to shreds. I'm not saying that's the right way to do it. But I will say, just like when a junior developer comes in thinking "well it works, so it's right", there are almost always other considerations than just the happy path.

A many-file, massive review might be 100% technically correct and flawless, and it's still going to take reviewers a lot longer to review than if they split it into 2-3.

--

> Merging side branch into side branch is a valid strategy

Completely agree! This is a fantastic strategy. You're not affecting the main branch, and generally people reviewing that specific branch can have the context of what your change is doing.
so much stress. It's too much like my dev machine.
Meta: a few years ago, HN was interested in on-topic discussion by informed people. Nowadays, the "informed" bit is irrelevant. It was inevitable that this place would become reddit, and now it has. Calling out incorrect information or pseudo-intellectual responses and nonsense has become unpopular. Fine, I'll stop doing it.
Yeah but ideally some PM spirit should also be built into a good developer culture so they can fill any PM gaps when needed, imho.
Forward Compatibility and Toolchain Management in Go 1.21
writing in general is a beautiful tool to give structure to your own understanding of anything.

i'm also genuinely convinced that people do this quite naturally, but that school beats this habit out of you as it replaces what you would normally do with what you're required to do. once you take people's free will out of the equation, their own natural talents suffer the consequences.
That's an interesting idea. Can you clarify some more on what the baseline memory model should be, if not a graph?
How to be successful as a research mathematician? Follow your gut
After the shooting at the country music event in Vegas, there is absolutely no doubt that every venue there takes every suspicion very seriously. The fact that they did multiple sweeps etc is not remotely suspicious. It just indicates that they are worried about missing a bomb and then it later going off.
That works fine for outbound connections but doesn't work for inbound connections. You can't have two devices listening for inbound connections on the same IP address.
No. This all got hashed out in the early 2000s when spammers tried to sue organizations that blacklisted them using everything from libel to contract interference.

One of too many to list: https://archive.is/jvJhl
https://archive.is/FrnY0
From a purely pedant point of view, the star item in 4 player versus in Tetris DS switch the standard 7-bag randomizer into one that only deals the I piece.
Perhaps it's not really a "talking" instrument (as an actual voice is modulating), but Peter Frampton always comes to mind.

https://www.youtube.com/watch?v=y7rFYbMhcG8&t=345s
Code reviews seem like a hellscape of "could do X".

Like man it's code, there's an infinite amount of "could do" with an infinite amount of contexts.

I found google's advice to be pretty good https://google.github.io/eng-practices/review/ while they give a lot of good advice / suggestions, they also make a point that there aren't a lot of hard stops and generally if the code works and isn't horrendous you let it go.
> I wonder what the fine will be when current gen iPhones are slowed down with iOS updates.

I know this is TikTok gospel, but our kids use iPhone 8s and run iOS 16 just fine. My take is that most of these posts are by people who truly do need a battery replacement, or are by the kind of person who has to have the latest phone and gets peeved when it no longer is.
If a weapons manufacturer made a gun that 1 in every billion times shot you in the head instead of your target, we wouldn't say, "well, sometimes accidents happen" and brush it off.

There would be a full investigation as to how and why this happened and someone somewhere would be held accountable.

Google in its current form is immune to the consequences of the decisions of its robots, and that is not acceptable.
Milton Friedman in "Monetary History of the United States" shows that fluctuations in the money supply were significantly more pronounced after fiat money began. The fed's enlightened hand on the tiller simply isn't as good as the blind actions of the free market.
>Official guidance from the International Civil Aviation Organization, or ICAO, which signatory nations use to create their own regulations, did not say what to do if TCAS and ATC issued conflicting avoidance instructions. Similarly, European regulations failed to cover this scenario.

Technical in the sense of giving priority one over the other; the priority was clear in the US but at the time not strictly set in Europe or Japan (a near miss happened one year before because of conflicting instructions) and in Russia the opposite (highest priority ATC) was true with TCAS being a new thing obligatory for flights to Europe, of the five crew members only one pilot seemed to be aware that the two TCAS are tightly coordinated (CLIMB/DESCEND) for a last resort, but nobody listened to him.
There is something I've started to notice as I've been working as a platform-layer consultant for the past few years. Many of the companies I've worked with don't have anyone in their company with any meaningful level of experience or expertise in environment administration, security, really anything ops-related. I see this especially when I start trying to hand off work I've done into maintenance phase operations and they don't have any kind of operations team to take over, but my contract sure as shit doesn't say I'm going to come in at 3 AM on a Sunday morning and I never will. So they may try to identify someone in the company to train up or they may try to hire, but the core problem they face isn't that it's impossible in principle to tell good apart from bad. The problem is it's impossible for them to tell the difference because they have no one in their company even qualified to conduct such an interview.
Tell me you didn't read the article without telling me you didn't read the article :)
If I'm an old person on fixed income, and my equity doubles from $1M to $2M, causing my property tax to double, I can take out a home equity loan against my house and be not only just fine on payments, but far ahead of where I was otherwise.

This argument was also a lie.
"he individual Kiva lenders earn no interest;" That's why I never bothered with Kiva. You want my money but you're not going to give me even a small cut? No thank you.
Who cares what NPR thinks? You're like one of those people who chooses their positions based on the opposite of what Trump said. How can you recognize NPR as illegitimate, yet give them control over you?
Would be nice if someone at CloudFlare or Substack saw this. I noticed one of my podcasts not appearing in Overcast and happened to run across this in my Mastodon feed.
The renter equivalent of Prop 13 is RSO.
Why speak in absolutes? Swift data for example is a data first ORM https://developer.apple.com/documentation/SwiftData

Nobody is saying only use an ORM, but the anti-ORM crowd seem to think that there’s only one true way to do things.

I don’t know why so many programmers think purely in binary “good or bad”. Different projects may have different requirements.
Don’t forget - commercial properties enjoy prop 13 as well. There was an effort to repeal it by zuck foundation in 2020 which failed
toki pona is not an attempted universal language! it is a pidgin between a number of languages but neither its creator nor its community wants it to be a universal language.
Thoughts on high-stakes college admissions
The ones that were not killed are atrociously shoddy and have been now for, you’d think I was going to say years, but it’s actually decades.
This. Someone dropped the ball.

There's a form to get your corner of the codebase exempted from readability temporarily. This gives your team a quarter or two to build up readability.
Found the MCSE.
>you don't want old people on fixed income forced to sell their homes because property values are going up rapidly

Why not? Regular turnover is healthy for both markets and neighborhoods. These beneficiaries of rapidly appreciated properties could sell their home to a new family, and take their profits to downsize to more age-appropriate housing.
That was my mistake, not the founders', and I've changed the term to source available (edit: now open core) to try to avoid misunderstanding. I assure you there was no attempt at fraud!
As I mentioned above, the additional sweeps should really be considered in the context of the previous Vegas shooting. The venue and police have every reason to be cautious.
Fire the gremlin, it's never worth picking an IC over the team morale. Folks can learn to be better programmers, assholes will always be assholes.
I forsee any social media driven board including that of tech to have an eventual decline. As that is the way of technology, something newer and more relevent of the masses that utilize arise.
Yes, and the existence of difficult classes does not warrant the exclusion of learners' perspectives from policy decisions.
Thanks for pointing it out, forgot to add it.
Edit: here's the actual presentation, not just the slides: https://www.youtube.com/watch?v=ztspvPYybIY

What's interesting about this talk is that Ryan doesn't even mention Javascript at all (other than briefly to say that NodeJS is built on it) until nearly 13 minutes into the presentation. And it's clear that he's using Javascript as a means to an end -- he's going with Javascript largely just because Javascript by default has a single threaded event loop that every JS programmer had to learn to work with it.

So he brings up going with JS because JS programmers are used to callbacks already -- and then roughly 2 minutes later he immediately moves back to talking about I/O and request handling again. Very little of his presentation is about Javascript beyond an aside of "JS already does this and JS programmers are used to it, so we might as well go with that and try to copy JS conventions." He almost spends more time talking about common SQL libraries than he spends talking about JS.
Just to nitpick

> strong positive correlation between altitude and suicide rate (r = 0.50, p < 0.001).

That is not strong. Put differently, altitude only explains 25% of the suicide rate. I know some fields have lower thresholds for what they consider strong, but still. An effect, sure, but I'd bet on this pointing to something else.

Not familiar with the demographics vs geography here, but how do typical high-altitude places look like in terms of society? They control for median household income and population density, but what about social attitudes? (are these places more rural? more traditionalist?), number of ways people can engage socially (say, cultural events, clubs, and so on), does their diet differ? etc etc.

Also, maybe putting the year (2011) in the title might be good. There may be more recent work / reviews.

EDIT: I forgot to mention diet
A Street-View Photographer's Journey to Contribute to Mapillary
Probably anathema to the dreams of IPv6+ IP-for-everything, but in your putative scheme, could we also make a carve out for local network? I like that 192.168.*, 10.* are defined as local.

So 0000:0000 local network, 0000:0001 legacy internet.
This is something I struggle with. I have a weekly meeting which includes TL, Manager, PM and sometimes Staff engineers, Data analysts, Managers of downstream teams etc.

I try to keep the details to the lowest denominator, which usually means mentioning what the problem is and what the proposed solution is in few lines. But eventually someone will ask for more details, and then the conversation veers off to technical discussion that I am sure the PMs and Analysts don't understand.
> Just like when YouTube nailed the lid into the coffin of ie6.

That was the work of a few people on the YouTube team, not the company itself taking a stand:

https://blog.chriszacharias.com/a-conspiracy-to-kill-ie6
Art, Embodiment, and Internal Necessity
> easy by replacing brittle SQL scripts with object-oriented Python

There is a lot to unpack here. Can you explain this in more detail?
Or it means inflation.

I've also had credit report hiccups because of the "debt" on my credit card.
Is this related to being a slow metabolizer of catecholamines?
Obviously, landlords are price takers, charging the maximum anyone will pay to rent their unit. The question is whether prop 13 increases supply in the medium to long run which would lead to lower rents. Unfortunately California NIMBYism makes that impossible.
Astera’s Science EIR Program