@hotdogsladies @siracusa
https://overcast.fm/+AAoIe-niCbA/11:39 this is the same as “impor-ant” right? I don’t think I’ve ever heard an American say “bu-on” before.
=> More informations about this toot | View the thread
Resigning in the age of LLMs.
2023: you type a polite resignation letter into your email client and click send.
2024: you type “polite resignation letter” into an LLM. Paste the output into your email client and click send.
2025: you type “resignation letter” into your email client. Click “polite”, click send. Recipient’s email client summaries the letter back to “polite resignation letter.”
2026: you type “polite resignation letter” into your email client. Click send. Your sentiment is sent directly without first being inflated by, or recompressed by an LLM. We simply communicate in prompts.
“Goodbye, jovial, dystopian.”
=> More informations about this toot | View the thread
It is upsetting that this is effective engagement bait but it does speak to a problem with the BIMDAS/PEMDAS/BEDMAS/PIMDAS acronym in that some neighbours have equivalent precedence. People are replying 0 because they think addition comes before subtraction. Which makes no intuitive sense but a rule is a rule I guess. I assume their logic is that, if you wanted the subtraction to happen first, you’d need brackets. But maybe I’m being too kind.
=> More informations about this toot | View the thread
Another developer quirk of mine (this one is particularly quirky).
If I'm conforming to a protocol, and a function is being intentionally left blank, I'll put the opening and closing brackets on the same line, after the declaration.
struct ConsoleLogger: Logger {
…
func flush() {}
}
This signals that the function has been left blank deliberately, not accidentally.
=> More informations about this toot | View the thread
It is unfair to tease a person for their name, or appearance, or any other aspect over which they have no control. This usually extends to a person’s fashion but, in the case of Zuckerberg, I think it is appropriate to make an exception. He only dresses like a skibidi rizzler because internal metrics forecast that it would enhance brand advocacy and optimize loyalty with generation’s Z through Alpha.
=> More informations about this toot | View the thread
I regularly find this on my desk and it breaks my heart a little. The 3 year old’s toy digital camera is broken and he is still trying to charge it- by sticking a lightning cable into where the SD card is meant to go. 💔 I don’t think he really is that bothered, but I think I need to replace it.
=> More informations about this toot | View the thread
A little Swift treasure: list formatting.
[“Tom", "Harry”].formatted()
"Tom and Harry”
[“Charles", "Delia", "Lydia”].formatted()
"Charles, Delia, and Lydia”
It is, of course, locale sensitive, and supports a ListType of and and or.
[“Carreras", “Pavarotti", “Domingo”]
.formatted(.list(type: .or).locale(.init(identifier: "it_it")))
"Carreras, Pavarotti o Domingo”
=> More informations about this toot | View the thread
One of my developer quirks, (i.e. a sign that you're looking at my code) is that I avoid 'default' in switch statements. If a new enum case is added, I want my code to break. For example, I don't do this:
switch format {
case .date: // Handle date
case .dateTime: // Handle dateTime
default: break
}
If a new kind of date format is added, (e.g. dateTimeLocal), this will continue to compile. This is bad. I want the compiler to direct my attention to this switch so that I know I need to support the new case. My code would look like this:
switch format {
case .date: // Handle date
case .dateTime: // Handle dateTime
case .text, .richText, .number:
break
}
If a new type is added (date or otherwise), I’ll be forced to revisit this switch.
=> More informations about this toot | View the thread
Nate Bergatze dressed like he’s about to receive a medal for blowing up the Death Star.
=> View attached media | View attached media
=> More informations about this toot | View the thread
Google should hire Hollywood actors to show what it really feels like to talk to a HomePod. Obviously they should add some cute marimba and ukulele music.
Samuel L Jackson: “Siri, add garlic powder to the shopping list.”
Siri: (long pause) “who is speaking?”
SLJ: “Sam.”
Siri: “who is speaking?”
SLJ: “Sam.”
Siri: “hi!”
SLJ: “Siri, add garlic powder to the shopping list.”
Siri: “hm, something went wrong.”
SLJ: “Siri, add garlic powder to the shopping list.”
Siri: “hm, I’m having trouble with the connection.”
SLJ: “Siri, add garlic powder to the shopping list.”
Siri: “who is speaking?”
=> More informations about this toot | View the thread
Happy new year from Apple intelligence
=> More informations about this toot | View the thread
Curiously, my phone decided to charge to 100% last night despite my charge limit being set to 90%. Hasn’t happened before.
=> More informations about this toot | View the thread
Don’t you even know dignity when you see it?
=> More informations about this toot | View the thread
Just a reminder that Darth Vader made C3PO.
=> More informations about this toot | View the thread
@mattiem hey Matt, thanks for https://github.com/mattmassicotte/ConcurrencyRecipes/blob/main/Recipes/Structured.md
I had written the anti-solution without considering the flaw. Then I wrote solution #1 and didn’t like that it was using unstructured concurrency. So I googled, found your recipe, and it tracked my thought process exactly :)
=> More informations about this toot | View the thread
Natural White Noise for Babies is the banger that I just can’t seem to get enough of.
=> View attached media | View attached media
=> More informations about this toot | View the thread
(4:45AM, reading the Swift compiler source on my phone while I wait for my flight.)
=> More informations about this toot | View the thread
Looks like the Swift compiler (constraint solver) defines “reasonable time” as 10 minutes. There are other ways to trip the “too complex” flag though, like using too much memory (512 * 1024 * 1024 bytes) or examining too many choices (1024 * 1024).
=> More informations about this toot | View the thread
[#]swiftui tip: Did you know that Binding.init(get:set:) has an overload that provides the Transaction on set? It’s not even obvious by looking at the documentation. https://developer.apple.com/documentation/swiftui/binding/init(get:set:)-6g3d5
You need to implement this if you want animations to work.
Binding(
get: {
// get value
},
set: { newValue, transaction in
withTransaction(transaction) {
// set value
}
}
)
=> More informations about this toot | View the thread
I suppose that clarification is intended for developers experienced in concurrent programming who are new to Swift Concurrency. For a long time I was puzzled by the goal of Swift’s data race safety, I conflated it with a goal to eliminate race conditions wholesale. It doesn’t intend to do that; that’s impossible.
=> More informations about this toot | View the thread
=> This profile with reblog | Go to mattcomi@hachyderm.io account This content has been proxied by September (ba2dc).Proxy Information
text/gemini