auxbuss

LaunchBar doesn't use Spotlight's data. And so, as a result, can't search for data inside files. That said, it provides a Search in Spotlight command – that you can assign a shortcut, if you wish – which returns its results in a new Finder window.

I also host my own email. In my case, Google always routes the first email I send to a new Gmail address as spam. After the recipient marks the email as good, future emails are received as expected. The only way around this is to advise the recipient via Gmail that I've set an email to them via a different route, so that they can check their spam and mark the email as good. This has been going on for at least two years.

Basically, Google are shadow-banning me till they get caught. I think this should be illegal.

Gmail always rejects the first email I send to a new gmail account. It does this every time – and has done for years – despite the fact I have sent emails to hundreds of other gmail accounts, and send emails to such accounts every day.

This is the reason I personally will not touch any Google services. And in business, I excise Google services as a priority. If a company cannot handle email in a civil manner, it certainly can't be trusted with anything of importance.

Space en-dash space is standard British typography – whereas US uses em-dash and jams the words together on either side of it.

It took centuries for the written word to acquire spaces between words, and then the US decided to jam them back together again.

Curious why folk are using two hyphens "--" instead of en-dash.

I agree. And this together with the obvious misunderstanding of Exhalation re: thermodynamics led me to put down the article.

I don't think the article was written by an LLM, but I'm convinced it was LLM-enabled. Which is a pity, because the author seems to have some interesting things to say. But that's the problem with leaning on an LLM: you lose your own voice, and good writing is centred around voice.

Verily.

Years ago, I went to live and work in Strasbourg. My French was… rudimentary, school-level, but after a few weeks I was picking up the rhythm and following along. Then the grand chef came up from Paris. During the night out entertaining him, I asked him to slow down a bit as I was struggling with his accent. He completely lost it, insulting the locals as peasants, and claiming the accent was theirs not his. Kind of put a damper on the evening.

Obviously the Marseille “dialect” is recognisable, but otherwise, travelling throughout France, and even the French-speaking parts of Switzerland, I could understand folk.

Thanks. This is excellent, as you'd expect from Emily Maitlis.

Proper old school investigative journalism, and he didn't hold back. Terrific scam, but, y'know, PayPal – I'm an old timer and remember the early days of that outfit. They're still blocked at the firewall from events 25 years ago.

Remember kids: Marketing is a psychopathy.

> Not sure why the reply buro9 gave is dead

I vouched for it, so it should be visible now.

The best – and I think the only – way to discover what good code looks like is to work with it.

Eventually, after working on, say, half a dozen code bases, you'll start to understand intuitively what good code is, providing you get lucky enough to find a good code base, or a code base with a significant amount of good code.

It's a long old journey, but once you have the skill, it never goes away. It's like learning a musical instrument or a foreign language. (By which I mean you can read as many books as you like about it, but without application, you haven't yet begun. Nevertheless, read the books.)

Warning: most developers never attain this skill, but almost all of them believe – truly believe – that they write good code; just as everyone thinks they are a good – nay excellent – driver.

Warning: no one writes good code. Good code becomes good through iteration, just as good writing becomes good by iteration/editing. The reason for this is obvious; but if you don't know why, then you haven't done enough yet.

Warning: everyone has biases. Learn to recognise yours and when you are applying them. Learn to ignore them and see things through a different lens. Explore with an open mind.

Iterating to good code is one of the most satisfying things you can do with software development.