Gerard Weatherby

@1ssve I wonder if there would be any way to work around such a feature?

Dear Apple, create a safety feature in iMessage that doesn’t allow people to screenshot text messages unless both parties have given permission.

@BohuslavskaKate We don't believe him.

Hegseth: "We're still dealing with the environment Joe Biden created—depleting our stockpiles and sending them to Ukraine instead of our own military. Every time we face a challenge, it traces back to 'Well, sent it to Ukraine.'" It looks like they’re just going to blame Ukraine whenever anything goes wrong now, doesn’t it? It’s depressing to watch because while this administration will eventually leave office, a segment of Americans will keep hating Ukraine without even remembering why.

@megbasham Lol, first time I've been called a leftie. That's some false dichotomy BS. No one is saying to expose your kid to the Internet. They're saying don't send texts in her name. Text the Mom directly. And maybe keep your parenting stuff off social media in the first place.

Of course, I should’ve known that my very innocent and funny family story would turn into a bunch of lefties telling me that I should give my 16-year-old free access to the p*rn, propaganda, predators, and other bad actors who might target her on social media etc. No. Not doing it. And btw, as I said, the girls thought it was funny. These are sweet, innocent girls and both the other girl’s mom, who I know, and I aim to keep them that way!

@StephenFleming Time dilation

Over a month ago, I bought tickets to “Project Hail Mary” for release day this Friday (March 20). How are all these people on Twitter getting to see it days earlier?

@miles_commodore Mondale was from Minnesota, so Reagan lost that one.

I was just a kid, so maybe someone can explain to me how Ronald Reagan won 49 states in 1984? Especially when you look at where we are today.

@arpit_bhayani Array should be O(1)

Let me talk about something obvious but with a bit of quantification... Theoretically, both arrays and linked lists take O(n) time to traverse, but here's what actually happens when you benchmark by summing 100k integers - Array: 68,312 ns - Linked List: 181,567 ns Summing an array is ~3x faster than LinkedList. Same algorithm, same complexity, but wildly different performance. The reason is cache behavior. When you access array[0], the CPU fetches an entire cache line (64 bytes), which includes array[0] through array[15]. The next 15 accesses are essentially free. Arrays hit the cache about 94% of the time. Linked lists suffer from pointer chasing. Each node is allocated separately by malloc(), scattered randomly in memory. Each access likely requires a new cache line fetch, resulting in a 70% cache miss rate. This is a good example of why Big O notation tells only part of the story. Spatial locality and cache-friendliness can make a 2-3x difference even when the theoretical complexity is identical. I am sure you would have known this, but this crude benchmark quantifies just how fast cache-friendly algorithms can be. Hope this helps.

@blackroomsec Backend servers are overwhelming Linux. Mac is *nix based. Forcing backend developer to use Windows is stupid.

Yeah, the org dodged a bullet with this one. I know it's been really popular for the younger generations to think it's cool to go around spewing their personal opinions at work but Corporate America has not changed in any way just because you happen to be alive. No one wants to hear your opinion, unless they ask for it. Which means you absolutely should not give it unless you are asked.🙄 And, if you are being given a standard issue laptop and aren't in any way responsible for the decisions that go behind purchasing those laptops then that's a good bet that nobody at work cares about your opinion because it doesn't matter and you're not that important in that particular org's food chain. And that's really the crux of it right? People like this thinking that they are more important then everybody else. That the rules don't apply to them. The IT staff isn't lazy. HR is not there to serve you but the company. Check your attitude and arrogance at the door. I would especially not be giving anyone an attitude in today's job climate because that's just insane. You're lucky you even GOT a job offer, let alone an actual job. READ THE ROOM,KID, SIT ALL THE WAY DOWN AND SHUT ALL THE WAY UP. As far as Windows is concerned it holds over 95% of the market share of all computers on Earth. 10 times out of 10 the computers are going to be Windows whether you personally agree with that or not. No one is going to change to Linux or a Mac for you. Macs are also very expensive computers and the org isn't going to buy 5,000 of them because of that. It's a budgetary decision and a sane one. Try to be a little self aware and ask yourself why all of these organizations aren't putting Macs on every desk and maybe consider that a lot of other people smarter than you, older than you and who have been working longer than you, have run the numbers and realized it just doesn't pay in the long run. That doesn't mean that the Mac is a bad computer. It isn't. It's a great computer. But it's really expensive. It would be really great if every organization I ever worked for would serve me lobster everyday but the reality is they're not going to do that because it's an expensive lunch. And even at the highest levels I got a ham sandwich if I was lucky. The only reason that I was going out to expensive dinners every week with my boss in my last role is because he was personally paying for it. You're also supposed to be putting your best foot forward and not embarrassing yourself with your own ignorance. So in closing check yourself when you get a job and stop thinking that the world revolves around you because it doesn't.

@bariweiss @TheFP For $8.33? No, I don't have to read it.

Science Has a Major Fraud Problem. For decades, scientists were above reproach. Not any more. @TheFP our Joe Nocera investigates the murky world of fraudulent research, and the sleuths exposing dishonest science. Must read. thefp.com/p/science-has-…

@trikcode I call it Buggy Super Compiler

stop calling professional work “vibe-coding.” “Vibe coders” are the people who don’t look at the code. and even if they do, they have no idea what they’re seeing. When a pro does it, it’s called something else: AI-assisted coding. Let’s not mix those two worlds.

@WSJopinion @MJ_Koch This boomer was less than two when JFK was shot, so it it wasn’t a defining moment for all of us.

Each generation remembers the historical moments of its time, the days when everything changed. For Gen Z, it’s the Covid pandemic, writes @MJ_Koch on.wsj.com/4ssKNbs

@AdrienneRoyer Who are these “people”? Do you have a list?

Do people not realize that the days get longer because of the seasons and not daylight savings time? If we stayed on standard time, we would still have later sunsets until the summer solstice because that’s how the earth orbits the Sun! People don’t seem to grasp this and credit DST for sunny evenings.

@runthinkwrite @playthegame_org It is true you’ve blocked Pielke?

There's a new paper out in BJSM arguing against sex testing. It's authored by some of the usual suspects, including Pape and Pielke (link at the end). Rather than going through it in detail, I'll refer you to this video from @playthegame_org ... castr.com/showcase/36607…

@brankopetric00 Yes.

Honest question: Has anyone ever successfully restored from a database backup on the first try? Or is that just a DevOps urban legend?

@rbarbosa91 While I’m willing to believe you’re qualified to provide care to humans Gandalf is clearly not human.

Elderly patients who sustain falls (such as Gandalf here), would also benefit from being taken to a Level 1 Middle Earth Trauma Center. At the time of his fall, Gandalf was at least 2000 years old, putting him at higher risk of complications of all kinds.

🧵regarding Lord of the Rings - related traumatic injuries, and whether access to modern Level 1 trauma centers could have decreased morbidity and mortality within the Fellowship. Here we will take a more evidence-based approach to some of the injuries in Middle Earth (1/ )

@ThePrimeagen You’ll start calling your ham bacon.

hey, i have a really important question, if you could answer. After switching from Phillips-head to Robertson screws inside the bathroom cabinet, how should we expect that to affect the flavor of food stored in the kitchen pantry on the other side of the house?

@__apf__ It’d be crazy to listen to opinion of random on twitter instead of doing what makes you happy.

we ripped all the 1970s stuff out of our turn-of-the-century carriage house. look at that old growth redwood. new drywall is supposed to go up but would it be crazy to skip the drywall and leave it like this??

@Math_files Notation conventions are not math. Meaning comes from context.

@SamaHoole Yeah I learned this in 1970s.

Here is a fact so perfectly constructed it seems like something a polemicist invented, except it is simply true and sitting in every etymology dictionary on the shelf. The Anglo-Saxon peasant kept a cow. He raised it, fed it, moved it to pasture, treated its ailments, watched it give birth, and if things went badly in winter made the decision about whether the family could afford to keep it. He called it a cu. It was his animal, his responsibility, his labour. He did not eat it. The Norman lord ate it. And he called it beef. From the Old French boeuf. The Anglo-Saxon kept a pig. He called it a picga. The Norman ate it and called it pork, from porc. The Anglo-Saxon kept sheep, which he called scep. The Norman ate them and called the meat mutton, from mouton. The Anglo-Saxon watched deer move through the forest that had just been legally declared the king's personal property under the Forest Laws. He called them deor. The Norman hunted them and called the meat venison, from venaison. The animal in the field has an Anglo-Saxon name because an Anglo-Saxon was looking after it. The meat on the table has a French name because a Norman was eating it. This division is sitting in plain sight in the English language and has been sitting there for nine hundred and fifty years, which is roughly the amount of time it has taken for anyone to notice that it tells you something important. Walter Scott noticed it in 1819. He put it in Ivanhoe. The swineherd Gurth says to the jester Wamba: the swine is Saxon when he is kept and Norman when he becomes pork. The observation got filed as a colourful literary detail rather than as the class analysis of the food system that it actually is. The language is the record. The record has been in every dictionary the whole time. The Anglo-Saxon raised the food. The Norman ate the food. The English language has been commemorating this arrangement ever since. I genuinely cannot believe this isn't in the national curriculum.

@tqbf Typora

Another tool I wouldn't have thought I'd ever need or want, but now I do and I can't find one: a decent Markdown *viewer*. Not an editor; I just want a clean simple fully rendered view of a .md, on macOS.

@arpit_bhayani Huh. How did you learn this?

Deleting a large number of rows (say, a million) in a single query feels efficient. It is not. It can crush your database. When we run a large DELETE in one go, the database has to hold locks on every row it touches for the entire duration of the operation. If it takes 30 seconds to run, those locks are held for 30 seconds. Every other query that needs those rows is stalled, waiting. On busy systems (high query or update load), this has a ripple effect. Reads pile up, writes get blocked, and your connection pool starts getting exhausted. This cleanup job will likely become a production incident :) There's also the transaction log (WAL) to think about. A massive DELETE generates a huge amount of log data in one shot, which can spike disk I/O and slow down replication. Your replicas can fall behind, sometimes significantly. The fix is pretty simple - batch your deletes. DELETE ... WHERE ... LIMIT 1000, then sleep for a small interval, then repeat. It's slower in wall-clock time, but the locks are short-lived, the log writes are spread out, and your database stays responsive throughout. Fun fact: Databases cannot protect you from yourself :) This is one of those things you learn once, usually the hard way. Don't ask me how I did :)