pdpi
I find it strange that they'd have an AI-driven followup email days after the survey. If you're automating it, why the delay? "Delay the response so it seems more human" is way too cynical.
It's worth noting that OP is talking about Ocado, too. I've been a client of theirs for over ten years, and the number one reason why I keep buying from them is that their delivery drivers never feel super-hurried. They have lower quotas than drivers for other services, and they always have time for a little bit of banter. Compare that e.g. to Amazon Fresh drivers, who'll always just leave the groceries at the door and knock. They're already gone by the time I open the door.
I find it unlikely that they'd automate this sort of second-level customer support response while not squeezing the everliving shit out of their drivers.
That's a lesson everybody on this site should learn — Every senior is a leader, even if they don't think they are. People (mostly the more junior sorts) look up to you as a role model whether you (or they) know it or not, and that's very real power that you must learn how to wield.
I've given negative reviews to technically excellent candidates in the past because just about everybody in the org would look up to them if they got hired, and they would be a terrible role model.
A judge might be a little more lenient with procedural mistakes to a pro se litigant who's trying to comply with the spirit of the proceedings, but smartarses won't get any such luck. At best they'll get a sternly worded warning the first time they get "creative".
That paragraph was never intended to be read by the judge or opposing counsel, it’s a deliberate attempt at messing with the tools they use to analyse the filing. The fact that it’s white text on a white background makes it an incontrovertible attempt at deceit.
We can discuss how wise it is to use AI to analyse legal documents for you, but that doesn’t change how outright deceit should be handled by the court.
If I were buying a display for work (which is to say, mostly programming), my choice would probably be the £600 BenQ RD280UG — a 28" 3840x2560 display, which is 4k vertically enlarged to a 3:2 ratio.
£700/£800 buys you a 24" display (with an unspecified refresh rate, so presumably 60Hz), a keyboard, and a mouse. I loved my 27" iMac to pieces, but it's really hard to justify buying this thing today.
A bunch of the complexity comes from having to write both client and server, and the communication protocol between them, then some more comes from the client being responsible for spinning up the server. As with every network service, client/server traffic is the slowest part of the architecture, so a bunch of complexity then comes from having to minimise the amount of network calls (or draw calls, in this case).
Then you hit the part where all of this is performance critical (soft-realtime requirements), so the whole thing is geared towards “writing your own userspace IP stack in C++” rather than “writing a flask application in Python”.
Jokes aside, there is a very definite difference in how my brain "feels" when I'm walking around, camera in hand, looking for things to photograph. It's like I'm in a different "cognitive mode", for the lack of a better term. It's not just about being present and in the moment, but about seeing the world around you from a different perspective.
0. https://drive.google.com/file/d/1tnMlazV0g1syoRPLALJ6576YSYQ...
“Cathedral” refers to development behind closed doors, where you just get a release and a source dump to go with it.
“Bazaar” refers to development done in the open, where you have constant access to the bleeding edge.
At the time of the essay, GCC and Emacs were ESR’s examples of Cathedral-style development, and Linux was the premiere example of the Bazaar style.
The Cathedral style has become a lot less common over the years, but it’s still how e.g. SQLite operates, I think? E.g. Google definitely operates like that with AOSP, but that's arguably more a fruit of them being maliciously compliant with their Open Source promises.
I would argue that, even though it's not my preference, there is real political value in the monarchy today still. E.g. Charles's speech to Congress[0] has a certain weight to it that wouldn't be there if Charles were an elected leader instead of a monarch.
I wouldn't qualify that with "even". Numerical stuff like that is one of Python's most well-developed niches, and Python's numerical ecosystem is the benchmark everything else needs to be compared against.
A bunch of European countries (including all of Scandinavia) are constitutional monarchies, and they don't devolve into the sort of anti-democratic behaviour we're all seeing from Trump. As a UK resident, I would prefer if the UK were a republic on general principle, but I fail to see the monarchy causing any real large-scale harm to society (individuals like Andrew notwithstanding).
The real point they should be making is "no more despots". Some despots are kings, but some are styled presidents, such as Xi Jinping, Vladimir Putin, and Kim Jong Un.
Also, legitimately elected or appointed officials become despots all the time. Hitler had a plurality (but not outright majority) of votes in 1932. Salazar was an MP and minister of finance, and actually legitimately tried to resign from that role several times over many years before he was eventually nominated to the role of prime minister. Ferdinand Marcos won the Philippine presidential election in 1965 with some amount of intimidation, and the Philippines only formally became a military dictatorship under his rule in 1971.
In many ways, that's the scariest scenario — people who legitimately get elected to power, and then use that power to solidify their illegitimate rule.
Given the quality of the output when I ask it to do things I do know how to do, I'm not particularly comfortable with the idea of using AI to do things I don't know how to do myself. It reeks of the Gell-Mann Amnesia Effect.
I have a slightly more nuanced take on it — I use Claude to write Ansible playbooks for my homelab because I know enough about server management to have a clear opinion on how I want things done and why, and enough Ansible that I understand the fundamentals and can recognise (but not write) idiomatic playbooks. That's the perfect storm of getting the LLM to do something I'm not good at, while still being able to judge its output.
use winnow::{Result, ascii::digit1, combinator::separated_pair, prelude::*};
#[derive(Debug, PartialEq)]
struct Roll {
count: u32,
sides: u32,
}
fn number(input: &mut &str) -> Result<u32> {
digit1.try_map(str::parse).parse_next(input)
}
fn roll(input: &mut &str) -> Result<Roll> {
let (count, sides) = separated_pair(number, 'd', number).parse_next(input)?;
Ok(Roll { count, sides })
}
#[cfg(test)]
mod test {
use super::*;
#[test]
fn test_roll() {
let input = &mut "3d6";
assert_eq!(roll(input), Ok(Roll { count: 3, sides: 6 }));
}
}Works like the Black Perl[0] are decidedly artistic in nature. Demos (in the demo scene sense) are an artistic endeavour. Competitions like the Obfuscated C Contest or the Underhanded C Contest are very much judged on aesthetics.
I understand why you'd want it, and that's why RFC10008 introduces QUERY as a GET-with-body alternative.
A bit tangential, but I really *really* appreciate them making this distinction, and wish more people did this. Way too many tools try to advertise themselves as all things for all people, catering to all use cases, and that helps nobody.
"Slop" just means something is low-quality and of poor craftsmanship, irrespective of who or what made it. If it's slop, you don't need to look for tells, you can just tell it's slop. Sure, AI is prone to specific types of mistakes, and humans are prone to other types of mistakes, and you can often tell whether a specific poorly-crafted UI is man-made or machine-made, but bad is bad is bad.