Links
Under the heading Don’t be shy:
Tell everyone you see. Be a nuisance.
I find the hardest part of blogging is telling people I have a blog. 🙂
🔗 Manuel Moreale: On em dashes
What if they tweak the instructions next week and tell it to use more full stops or commas? What are we gonna do then? Stop using those as well? Hell no. I’ll keep writing however I want, and if someone decides to stop reading what I write because they suspect it’s AI-generated because I use too many em dashes, or parentheses, or any other punctuation or word or whatever, well, good riddance.
My feelings exactly. To stop using em dashes because of AI chatbots seems ludicrous to me.
🔗 HN Comment by IanCal in a discussion about RDF (emphasis added):
Someone will suggest modelling to solve this but here lies the biggest problem: The correct modelling depends on the questions you want to answer. Our modelling had good tradeoffs for mapping academic citation tracking. It had bad modelling for legal ownership. There isn’t one modelling that solves both well.
That may be why I was turned off by RDF all those years ago. One seeks to model a domain, but domains can be extremely complicated, and even if you cover everything, it’s still only one domain. But the biggest crime is assuming that the model is necessary for all use cases. And it just isn’t. Does every website that tracks books need to know the full legal name, publisher name, the legal entity of the company that supplied the typesetting? Simplify, man.
Via: Simon Willison
🔗 Dave Winer: We Make Shitty Software
We know our software sucks. But it’s shipping! Next time we’ll do better, but even then it will be shitty. The only software that’s perfect is one you’re dreaming about. Real software crashes, loses data, is hard to learn and hard to use. But it’s a process. We’ll make it less shitty. Just watch!
It’s true. Speaking for myself, I too make shitty software. Probably have my entire career. It’s only today that I’ve internalised it. And it’s a hard thing to admit. How hard? Well, try four attempts at posting this declaration publicly.
Via: Coding Horror
🔗 GitHub: Gopher Hawaiian Shirts
Patterns for printing Hawaiian shirts with the Go gopher. I think I’ve found what I’ll be wearing to work in the future. 😄
Via: Golang Weekly
Virtual machines of early PC operating systems, such as Windows and OS/2 1.0, that run in the browser. For anyone else who’s interested in a nostalgic kick. Don’t forget to check-out the list of included software installable via the virtual floppy drive.
🔗 Ludipe: Intro to Puzzle Design
Filing this under good tips for game development.
Via: GMTK weekly digest.
🔗 Wikipedia: White-winged chough
I’ve seen this bird before and I had no idea what they are: black, white tips on the wings, red eyes, and an interesting call. Their presence in a random YouTube video I was watching revealed the answer.
A very nice exploration of webpage design using a monospace font. The first thought I had when I saw this was that this would work great for online man pages, which never look as good online as they do in the terminal.
Via: Robb Knight
🔗 How we built Bluey’s world: tales from original series art director, Catriona Drummond
As someone who knows absolutely nothing about animation, I found this fascinating. Some nice bits of theory in this, such as the “language” of shapes:
Circles are round, friendly and soft. No hard edges!
Triangles are sharp, aggressive and evoke pain.
Squares are sturdy, steady and firmly planted.
Then on top of that, even directional lines have implicit associations! Horizontals are calm, verticals awake and upright, and diagonals off balanced.
🔗 Aresluna: Frame of preference
This walk through the various preference windows of MacOS is amazing. The way they integrate Infinite Mac alongside it: genius. Best explored while listening to ATP Overtime.
🔗 Daring Fireball: Microsoft Introduces ‘Copilot Mode’ in Edge
Some follow-up from my recent pondering about chatbots in browsers. From Gruber:
I think something similar is behind Microsoft trying to make Copilot front-and-center in Edge, and Google’s concurrent move to junk up Chrome with AI-generated suggestions. Their goal is to make their web browsers chatbots faster than OpenAI can make ChatGPT a web browser.
Okay, that’s plausible. If it’s just a fight for mindshare than I can understand this. Still not sure what OpenAI’s motivations are, but it does look like these other companies are just reacting here.
🔗 Daring Fireball: Google Chrome Adds AI-Generated Store Summaries
Now browsers themselves will be adding their own layers of distracting cruft atop the websites. The entire premise of Chrome — the reason for its name — is that it was originally designed to simplify the UI of the browser app itself, the “chrome”, at a time when Internet Explorer and even Firefox were increasingly cluttered and confusing.
I’m confused as to why Google and all these AI companies are so gun-ho about adding AI agents to browsers. What do they get out of this deal? Is it just a way for them to win users and get data from their browsing habits? Is it protection against Google potentially dissuading these users away from using their chat-bots? These are not problems Google has, so why are they doing this?
They seem like features designed to turn the dial up on Google’s slice of commissions from web transactions.
Maybe, but how can they collect? If they run AI over the web-pages that a user visits, when the user converts, how are they going to tell the website owner that they help “bring in the eye-balls” thanks to AI and have earned X% off the top? Maybe they’ll only run these AI agents on sites that “opt-in” in some way, either by using Google Pay or paying more for Google ads. I can see that happening.
All very strange. In either case, I’m glad I’m rocking Vivaldi these days.
🔗 Manuel Moreale: Why this matters
Manuel Moreale celebrates and reflects on reaching the 100th People and Blogs. Congratulations, Manuel! Here’s to many more.
We’re entering the 3 digits era of People and Blogs, and the next milestone is going to be the beginning of the 4 digits era, which will arrive in the year 2042. […] I’m not even sure if blogs will still be a thing by then.
Oh, I bet you they will be a thing.
🔗 MacSparky: A Remarkable, Unremarkable Thing
We often talk about how people can’t put their phones down while in line at the market, but what about during moments of joy? When taking in a theme park with your family, at the beach, or on vacation? Those moments are found solely in your immersion in the now.
A thought-provoking post.
🔗 Simon Willison: Identify, solve, verify
No matter how good these [coding LLMs] get, they will still need someone to find problems for them to solve, define those problems and confirm that they are solved. […] It’s also about 80% of what I do as a software developer already.
Hey, I’m a software developer too. And I acknowledge that my job is more than just typing things into an IDE. In fact, it’s probably closer to what Simon Willison does, where I’m identifying problems, and writing Jira tickets for others to fix rather than do it myself. And it might be that with the introduction of coding LLMs, software development will simply be more of this going forward. It certainly the direction things look to be going.
But I would be lying if I said I wouldn’t be disappointed to see all these coding tasks go away, and all my job description reduced to finding problems and verifying fixes. Like some sort of… manager 😖. I got into software development because I like to code. And part of this is finding problems, but I only get the dopamine hit after fixing them. I get nothing if I simply tell someone (or something) else to fix it.
And okay, we’re talking about a job here. And I’ve reached the age where I recognise one doesn’t always achieve a fulfilling life from their careers alone. So might be that this is something that I just need to recognise that sometimes jobs suck and identifying problems is all I’ll ever do in the near future.
But I would tell employers thinking of outsourcing all coding tasks to LLMs to consider this: if I’m faced with two employment opportunities, and one has 0% coding tasks, and the other has >0% coding tasks, I’d take the latter any day of the week.
🔗 LMNT: I’ve Got Better Things To Do Than This, and Yet
It’s one thing for QuickTime UI to “get out of the way.” Please, do. I’m watching a video. I don’t need a big honkin’ pause button in the middle of the window, you know? But wait a minute, why is there a big honkin’ pause button in the middle of the window anyway? That’s not how it used to be.
I don’t always agree with Louie Mantia but he’s absolutely right here. When did hiding UI or moving it out of various bars become synonymous of “getting out of the way of content”? Slapping UI over the content is not getting out of the way. In fact it’s the exact opposite.
Pretty impressive to see what’s possible with CSS nowadays. Viewing the page source is quite illuminating.
🔗 Search Engine Land: What 1,000 food blog audits has taught me about SEO
I’m wary about posts on SEO but I found this one discussing the techniques attempted by recipe bloggers quite interesting. In short: cargo cult thinking around SEO myths is resulting in many bad food sites.
Via: Pixel Envy
🔗 Spyglass: Apple Lives Long Enough to Become the Ad Villain
People pay a lot of money for these devices from Apple. And part of the implicit bargain is that they won’t have adware or ads themselves shoved at them in every direction.
Now I’m no marketing expert, but I do know that understanding one’s customer base is important for success. And I understand that Apple’s is generally made up of people who pay a premium for a good user experience. I wonder if Apple understands this. I also know that generally pissing people off with stunts like this will not get them to come to your party.