For anyone not familiar with the meaning of '2' in this context:
The Linux kernel supports the following overcommit handling modes
0 - Heuristic overcommit handling. Obvious overcommits of
address space are refused. Used for a typical system. It
ensures a seriously wild allocation fails while allowing
overcommit to reduce swap usage. root is allowed to
allocate slightly more memory in this mode. This is the
default.
1 - Always overcommit. Appropriate for some scientific
applications. Classic example is code using sparse arrays
and just relying on the virtual memory consisting almost
entirely of zero pages.
2 - Don't overcommit. The total address space commit
for the system is not permitted to exceed swap + a
configurable amount (default is 50%) of physical RAM.
Depending on the amount you use, in most situations
this means a process will not be killed while accessing
pages but will receive errors on memory allocation as
appropriate. Useful for applications that want to
guarantee their memory allocations will be available
in the future without having to initialize every page.
>> The most common objection is that writing proposals is “a waste of time” compared to writing code.
> The extra time spent writing is actually spent thinking.
Until someone decides that using ChatGPT to write your RFC is a good idea. Then you get something that looks great, but the person behind the prompt actually understands less.
"Eventually they realized that this was something they were going to have to sort out, and they passed a law decreeing that anyone who had to carry a weapon as part of his normal Silastic work (policemen, security guards, primary school teachers, etc.) had to spend at least forty five minutes every day punching a sack of potatoes in order to work off his or her surplus aggressions. For a while this worked well, until someone thought that it would be much more efficient and less time-consuming if they just shot the potatoes instead. This led to a renewed enthusiasm for shooting all sorts of things..."
- Douglas Adams, "Life, the Universe, and Everything"
(It took an unreasonably long time to find this quote!)
Oh I really worry about that. AI code at least needs to pass unit tests, but there's no way to prove that the ideas in an AI document make sense until you try them and run into issues. Writing is thinking. If you let a robot do it, you aren't.
I’m currently fighting the “don’t use Gemini to write internal documents” war at my company. It’ll be long and hard, but I think I’ll eventually prevail.
Every time someone throws a document written by AI at me, it feels so disrespectful.
Just a couple of days ago, I received an email from our HR department requesting information about a recent hire. Basically, they asked if I or anyone on my team had physically met that person. My company still embraces remote work, and everyone on my team is remote. As luck would have it, the person in question lives near another team member and they had met up for a company function (once).
I assume that the request was related to something like this: Preventing fraudulent remote workers.
My brain first started doing this with online ads as well.
The habit has adapted and evolved very strongly with the amount of exercise it gets from UIs, textbooks, signage, and basically every other visual medium possible these days. It has actually become a problem with how often I overlook important information due to it being situated in a "nothing useful will ever be here" zone. But it's difficult to consciously control that instinct when it's correct 99.999% of the time.
> Executives are considering potential budget cuts as high as 30% for the metaverse group next year, which includes the virtual worlds product Meta Horizon Worlds and its Quest virtual reality unit, according to people familiar with the talks, who asked not to be named while discussing private company plans
Buckaroo Banzai: You can check your anatomy all you want, and even though there may be normal variation, when it comes right down to it, this far inside the head it all looks the same. No, no, no, don’t tug on that. You never know what it might be attached to.
See, this is the point, for me, where it started to look like a problem. You know, I wanted to sacrifice the precentral vein in order to get some exposure, but because of this guy's normal variation, I got excited, and all of a sudden I didn't know whether I was looking at the precentral vein, or one of the internal cerebral veins, or the vein of Galen, or the vascular vein of Rosenthal. So, on my own, to me, at this point, I was ready to say that's it, let's get out.
I had an acquaintance who was a county constable. He once told me, "Let me watch you drive down the road, any road, for 30 seconds and I will be able to find a valid reason to pull you over." He implied that some part of their training was focused on exactly that.
One data point, and a highly regional one at that, I know.
The law is not on the citizens' side and never has been. Driving over the limit (even the smallest increment) is technically illegal. Driving under can be considered suspicious and warrant further surveillance (or more likely incite road rage from other drivers) in which you will likely make a mistake. Nobody follows every traffic law perfectly and in all likelyhood cannot. Every cop I have ever known has admitted to this fact and there are even more examples of former(or current) law enforcement officers going on record saying the same thing.
"Y.T.’s mom pulls up the new memo, checks the time, and starts reading it. The estimated reading time is 15.62 minutes. Later, when Marietta does her end-of-day statistical roundup, sitting in her private office at 9:00pm, she will see the name of each employee and next to it, the amount of time spent reading this memo, and her reaction, based on the time spent, will go something like this:
Less than 10 min.: Time for an employee conference and possible attitude counseling.
10-14 min.: Keep an eye on this employee; may be developing slipshod attitude.
14-15.61 min.: Employee is an efficient worker, may sometimes miss important details.
16-18 min.: Employee is a methodical worker, may sometimes get hung up on minor details.
More than 18 min.: Check the security videotape, see just what this employee was up to (e.g., possible unauthorized restroom break).
Y.T.’s mom decides to spend between fourteen and fifteen minutes reading the memo. It’s better for younger workers to spend too long, to show that they’re careful, not cocky. It’s better for older workers to go a little fast, to show good management potential. She’s pushing forty. She scans through the memo, hitting the Page Down button at reasonably regular intervals, occasionally paging back up to pretend to reread some earlier section. The computer is going to notice all this. It approves of rereading. It’s a small thing, but over a decade or so this stuff really shows up on your work-habits summary."
There was a recent case in Illinois where the district attorneys' office decided to create their own private police force that wasn't covered by any of the laws normally reserved for law enforcement, so it could do whatever the fuck it wanted.
I remember one guy they hired to sit and pull people over all day on the highway who said the same thing "I can find something wrong with every single vehicle that passes by. I can literally pull anybody over that I want." IIRC he had things like a corner of a mudflap being broken off, or some trivial insanity like that. The big one in Illinois was having any air freshener hanging from your mirror.
Law enforcement has enormous discretion for probable cause and can give straight up contradictory reasons for different cases, it is what officers are taught to do (i.e. something like driving too fast, driving too slow, driving too rigidly at the speed limit). This allows individual bias to overwhelm any attempt at equal enforcement. It's pretty well documented in both The New Jim Crow and Usual Cruelty, the Supreme Court has made it difficult to gather data in the last couple decades.
Any given american citizen is certainly breaking, at minimum, dozens of laws even while asleep in their own bed. If they want to pick you up and they are diligent enough they certainly can. They might be laughed out of court, but they also might not be.
I ignored the arrows and interpreted it as "move all elements lower than the marker in order to the left of the marker, and move all elements higher than the marker in order to the right of the marker". It's not clear, but if you use a bit of intuition you can come to this conclusion. Personally it took me about 5 seconds.
I agree it does a pretty good job of communicating that. I think the other commenters are pointing out that doesn’t show how to efficiently get all the smaller items left of the partition and larger ones to the right. While that’s probably second nature to most people who’ve taken an algorithms class or done a decent amount of programming, I guess it’s up for interpretation how obvious it would be to the “intended audience” of the ikea manual
I can't tell if this was serious. This really is how a pure Quicksort works, you just recursively apply this same algorithm and the result is sorted. In contrast the initial circles approach can't be recursed to draw the rest of the fucking owl.
The Linux kernel supports the following overcommit handling modes
0 - Heuristic overcommit handling. Obvious overcommits of address space are refused. Used for a typical system. It ensures a seriously wild allocation fails while allowing overcommit to reduce swap usage. root is allowed to allocate slightly more memory in this mode. This is the default.
1 - Always overcommit. Appropriate for some scientific applications. Classic example is code using sparse arrays and just relying on the virtual memory consisting almost entirely of zero pages.
2 - Don't overcommit. The total address space commit for the system is not permitted to exceed swap + a configurable amount (default is 50%) of physical RAM. Depending on the amount you use, in most situations this means a process will not be killed while accessing pages but will receive errors on memory allocation as appropriate. Useful for applications that want to guarantee their memory allocations will be available in the future without having to initialize every page.
reply