In the latest episode of their intrepid podcast, Ken and Robin talk Sense Trouble, fatbergs, William Stephenson, and doomsday predictor Albert Porta.

The Inconvenient Indian [Canada, Michelle Latimer, 4] Essay-format documentary examines the Indigenous struggle for sovereignty and cultural reclamation in North America, as hosted by novelist Thomas King and inspired by his nonfiction book of the same name. Makes its case through cinematic language, pushing the archival footage and talking heads format to the background.

Beginning [Georgia, Dea Kulumbegashvili, 4] Depressed wife of a pastor bears the brunt of a persecution campaign from a local man hostile to their minority Baptist faith. The camera acts as a pitiless eye in this harsh, austere drama of pervasive male oppression.

I Care a Lot [UK, J Blakeson, 3] Corrupt legal guardian (Rosamund Pike) who slaps unsuspecting seniors into care facilities to bleed them dry triggers a cat-and-mouse game when her latest prey (Dianne Wiest) turns out to be the mother of a wealthy gangster (Peter Dinklage.) Engaging thriller— until it betrays the contract it has established with the audience.

Concrete Cowboy [US, Ricky Staub, 3] After yet another expulsion from school, a troubled teen (Caleb McLaughlin) gets dumped for the summer with his father (Idris Elba), who belongs to Philadelphia’s threatened culture of inner city horse owners. A rich social milieu is the star of the show in this affirming drama, which could do with a stronger drive to activate its protagonist.

Lift Like a Girl [Egypt, Mayye Zayed, 4] From ages 13 to 18, under the tutelage of a volcanic, motormouth coach, with a rubble-strewn lot on a busy Alexandria street, weightlifter Zebiba trains to be a champion. Fly-on-the-wall documentary inhabits a hardscrabble community powered by loving verbal abuse.

The coach and his key athletes denigrate the skills of male lifters, while constantly referring to the girls as boys, urging them to man up, and telling them they need to grow balls if they want to win.

1. Right now, the Sun is far more active than predicted – and small satellites are paying the price  The Conversation
2. Unpredictable Solar Activity Sends Satellites Plummeting to Earth  ScienceAlert

1. New prime time kings as AFL’s 2025 Thurs night blockbusters revealed  Fox Sports
2. Three Thursday night fixtures revealed  Collingwood
3. What we know about the 2025 fixture: Thursday nights back with a bang, Smith to face Dogs in blockbuster  The Age

1. Outback Queensland residents spend thousands on flights, grapple with Qantas service changes  ABC News
2. Airlines that love competition: Do you see pigs fly?  Sydney Morning Herald
3. Predictably, domestic airfares surged after the collapse of Rex. There aren’t many good solutions  The Conversation
4. Report finds just how much airfares spiked since end of Rex. One route doubled  The Canberra Times
5. Qantas’ single excuse for fare price hike  news.com.au

1. Volcanic eruption grounds Bali flights, leaving travellers stranded  Sydney Morning Herald
2. Bali flight cancellations continue due to dangerous volcanic ash clouds  SBS News
3. Bali flight cancellations continue as volcano spews ash  9News
4. Aussies stranded in Bali volcano nightmare  Daily Telegraph

1. Murder charge after beloved Elvis impersonator found dead after karaoke night  9News
2. Beloved Elvis impersonator allegedly murdered after karaoke night  Sydney Morning Herald
3. Love Island winner's best mate is accused of killing beloved grandad - after the Good Samaritan had tried to h  Daily Mail
4. Video: Elvis impersonator named as alleged murder victim  WAtoday

When asking for a pledge, the fundraiser has many informational advantages over the donor. Simply asking for the proper amount ensures that a donor will consider giving at the level you request. Starting out with a sufficiently high donation request amount allows you to find your donors preferred level of giving as rather than targeting the amount which is the lowest possible amount that a donor can possibly give to your campaign.


If a donor could give more to their charity, they probably would. When donors who maintain a strict charitable budget and give a fixed amount annually hear requests for support that are above the amount which they are willing to give, they let fundraisers know just how much they are willing to give and when they intend to give it. In the rare event that a donor is offended by large or additional requests, a skilled fundraiser can apologize for the offense and leave the donor feeling good about the level of support which they do give.


There is no downside to “asking high”.




Becoming a better fundraiser is a continuing process. There is always more to learn and more skills to master.

The conclusion to this article will be posted here in the coming days.

This is not a political blog, although politics inevitably creep in to discussions of matters legal. I have followed politics since I was at school, although I was never elected to anything. The current situation beggars belief, and I imagine that today's crop of journalists will shake their heads in their old age, and say "but you should have been there in the summer of 2016; everything seemed to happen at once. " I am now even more convinced that my belief in the iron Law of Unintended consequences is the right one.

I have had to cut back on my sittings of late, as I am awaiting an operation to give me a new knee joint, and although I can get around in the courthouse it isn't always easy. As I am due to retire from the Bench in late October I have excused myself from getting to grips with some of the more complex innovations that have recently been introduced, such as iPads on the bench. I own a couple of iPads and I am comfortable with using them, but inevitably any government-issued software is over-engineered and the last thing from user-friendly.

My court has a few boxes that contain the iPads as well as charging them overnight, but those JPs who wish to use them have to submit to training as well as an elaborate procedure to keep them secure. It is worse for judges of course, but then they are paid £130k and more to cope.

Given my impending retirement, I cannot summon up the enthusiasm to get stuck in to this 21st century stuff  (albeit the technology is a decade old).

I am trying to avoid becoming what old Army types call demob-happy so I shall concentrate on justice before bureaucracy.

A colleague, who has sometimes posted here as Bystander N, has sent me the following, asking me to put it on the blog. It is gratifying, and I hope that it is true.

• Tomorrow is a particularly sad day for my bench. I know Bystander and he had no idea I was going to

  write this short piece. Tomorrow he will be officially “past it”, though of course in reality nothing like

  past it and he is as sharp as they come.

  Both here on this blog and in our retiring rooms we will miss his kindness, warmth, immense

  knowledge, sense of fair play, sense of humour and seemingly endless stream of amusing court

  anecdotes.

  I have not always agreed with him on bail and sentence decisions but that’s the way the system

  works. I have learned a great deal from him and I am really sorry he will not be amongst us any

  longer. I have heard him say that he thinks he saw the best of the bench many years ago. He may

  be right but I’m still sure, even if he will not miss all of it, he will miss most of it.

Great Britain's bobsleigh team call for all sliding tracks to be covered after heavy snowfall at the Winter Youth Olympics in Austria.

A Planetary Society-funded project to understand asteroids achieved its main goals and scientific objectives this year.

It’s been a great year for space exploration. Now you get to pick the highlights.

I'm a sucker for sage advice much as anyone else, and Kernighan is certainly right on money in the epigraph. Alas there comes a time in programmer's career when you just end up there despite the warning. It could be that you were indeed too clever for your own good, or maybe the code isn't quite yours anymore after each of your colleague's take on it over the years. Or just sometimes, the problem is indeed so hard that it strains your capacity as a coder.

It would usually start with a reasonable idea made into first iteration code. The solution looks fundamentally sound but then as you explore the problem space further it begins to seep nuance, either as manifestation of some real world complexity or your lack of foresight. When I run into this my first instinct is to instrument the code. If the problem is formidable you got to respect it: flailing around blindly modifying things or ugh, doing a rewrite at this stage is almost guaranteed to be a waste of time. It helps to find a promising spot, chisel it, gain a foothold in the problem, and repeat until you crack it. Comfortable debugging tools here can really help to erode the original Kernighan coefficient from 2 to maybe 1.6 or 1.4 where you can still have a chance.

Lisp users are fortunate with the options of interactive debugging, and one facility I reach often for is the plain BREAK. It's easy enough to wrap it into a conditional for particular matches you want to debug. However sometimes you want it to trigger after a particular sequence of events across different positions in code has taken place. While still doable it quickly becomes cumbersome and this state machine starts to occupy too much mental space which is already scarce. So one day, partly as a displacement activity from being intimidated by a Really Hard Problem I wrote down my debugging patterns as a handful of macros.

Enter BRAKE. Its features reflect my personal preferences so are not necessarily your cup of tea but it could be a starting point to explore in this direction. Things it can do:

• act as a simple BREAK with no arguments (duh)
• wrap an s-expression, passing through its values upon continuing
• trigger sequentially based on the specified position for a common tag
• allow for marks that don't trigger the break but mark the position as reached
• provide conditional versions for the expressions above
• print traces of tagged breakpoints/marks

If you compile functions with debug on you hopefully should be able to see the wrapped sexpr's result values.

(use-package '(brake))

(defun fizzbuzz ()
  (loop for n from 100 downto 0
	for fizz = (zerop (mod n 3))
	for buzz = (zerop (mod n 5)) do
	(format t "~a "
		(if (not (or fizz buzz))
		    (format nil "~d" n)
		  (brake-when (= n 0)
			      (concatenate 'string
					   (if fizz "Fizz" "")
					   (if buzz "Buzz" "")))))))

These macros try to detect common cases for tagged sequences being either aborted via break or completed to the last step, resetting them after to the initial state. However it is possible for a sequence to end up "abandoned", which can be cleaned up by a manual command.

Say in the example below we want to break when the two first branches were triggered in a specific order. The sequence of 1, 3, 4 will reinitialize once the state 4 is reached, allowing to trigger continuously. At the same time if we blow our stack it should reset to initial when aborting.

(defun ack (m n)
  (cond ((zerop m) (mark :ack 3 (1+ n)))
        ((zerop n) (mark :ack 1 (ack (1- m) 1)))
        (t (brake :ack 4 (ack (1- m) (ack m (1- n)))))))

In addition there are a few utility functions to report on the state of brakepoints, enable or disable brakes based on tags and turn tracing on or off. Tracing isn't meant to replace the semantics of TRACE but to provide a souped up version of debug by print statements everyone loves.

CL-USER> (report-brakes)
Tag :M is DISABLED, traced, with 3 defined steps, current state is initial
Tag :F is DISABLED with 2 defined steps, current state is 0
Tag :ACK is ENABLED with 3 defined steps, current state is initial

Disabling breakpoints without recompilation is really handy and something I find using all the time. The ability to wrap a sexpr was often sorely missed when using BREAK in constructs without implicit body.

Sequencing across threads is sketchy as the code isn't guarded but in many cases it can work, and the appeal of it in debugging races is clear. One of those days I hope to make it more robust while avoiding potential deadlocks but it isn't there yet. Where it already shines tho is in debugging complex iterations, mutually recursive functions and state machines.

.

CONTINUED TOMORROW.

Above: Every Autumn, I write a Halloween story, write it out on leaves (one word per leaf), photograph the leaves, and then leave them where.I found them. The story is then serialized, starting on October 1 and concluding on the 31st--All Souls Day.

 .

CONTINUED TOMORROW.

Above: Every Autumn, I write a Halloween story, write it out on leaves (one word per leaf), photograph the leaves, and then leave them where.I found them. The story is then serialized, starting on October 1 and concluding on the 31st--All Souls Day.

.

CONTINUED TOMORROW.

Above: Every Autumn, I write a Halloween story, write it out on leaves (one word per leaf), photograph the leaves, and then leave them where.I found them. The story is then serialized, starting on October 1 and concluding on the 31st--All Souls Day.

.

CONTINUED TOMORROW.

Above: Every Autumn, I write a Halloween story, write it out on leaves (one word per leaf), photograph the leaves, and then leave them where.I found them. The story is then serialized, starting on October 1 and concluding on the 31st--All Souls Day.

.

CONTINUED TOMORROW.

Above: Every Autumn, I write a Halloween story, write it out on leaves (one word per leaf), photograph the leaves, and then leave them where.I found them. The story is then serialized, starting on October 1 and concluding on the 31st--All Souls Day.

.

CONTINUED TOMORROW.

Above: Every Autumn, I write a Halloween story, write it out on leaves (one word per leaf), photograph the leaves, and then leave them where.I found them. The story is then serialized, starting on October 1 and concluding on the 31st--All Souls Day.

.

CONTINUED TOMORROW.

Above: Every Autumn, I write a Halloween story, write it out on leaves (one word per leaf), photograph the leaves, and then leave them where.I found them. The story is then serialized, starting on October 1 and concluding on the 31st--All Souls Day.

.

CONTINUED TOMORROW. (For those who came in late: The first sentence was posted here on October 1 and a new sentence was posted every day thereafter.)

Above: Every Autumn, I write a Halloween story, write it out on leaves (one word per leaf), photograph the leaves, and then leave them where.I found them. The story is then serialized, starting on October 1 and concluding on the 31st--All Souls Day.

.

CONTINUED TOMORROW. (For those who came in late: The first sentence was posted here on October 1 and a new sentence was posted every day thereafter.)

Above: Every Autumn, I write a Halloween story, write it out on leaves (one word per leaf), photograph the leaves, and then leave them where.I found them. The story is then serialized, starting on October 1 and concluding on the 31st--All Souls Day.

. 

CONTINUED TOMORROW. (For those who came in late: The first sentence was posted here on October 1 and a new sentence was posted every day thereafter.)

Above: Every Autumn, I write a Halloween story, write it out on leaves (one word per leaf), photograph the leaves, and then leave them where.I found them. The story is then serialized, starting on October 1 and concluding on the 31st--All Souls Day.

.

CONTINUED TOMORROW. (For those who came in late: The first sentence was posted here on October 1 and a new sentence was posted every day thereafter.)

Above: Every Autumn, I write a Halloween story, write it out on leaves (one word per leaf), photograph the leaves, and then leave them where.I found them. The story is then serialized, starting on October 1 and concluding on the 31st--All Souls Day.

.

CONTINUED TOMORROW. (For those who came in late: The first sentence was posted here on October 1 and a new sentence was posted every day thereafter.)

Above: Every Autumn, I write a Halloween story, write it out on leaves (one word per leaf), photograph the leaves, and then leave them where.I found them. The story is then serialized, starting on October 1 and concluding on the 31st--All Souls Day.

.

CONTINUED TOMORROW. (For those who came in late: The first sentence was posted here on October 1 and a new sentence was posted every day thereafter.)

Above: Every Autumn, I write a Halloween story, write it out on leaves (one word per leaf), photograph the leaves, and then leave them where.I found them. The story is then serialized, starting on October 1 and concluding on the 31st--All Souls Day.

.

CONTINUED TOMORROW. (For those who came in late: The first sentence was posted here on October 1 and a new sentence was posted every day thereafter.)

Above: Every Autumn, I write a Halloween story, write it out on leaves (one word per leaf), photograph the leaves, and then leave them where.I found them. The story is then serialized, starting on October 1 and concluding on the 31st--All Souls Day.

.

CONTINUED TOMORROW. (For those who came in late: The first sentence was posted here on October 1 and a new sentence was posted every day thereafter, to make a complete story.)

Above: Every Autumn, I write a Halloween story, write it out on leaves (one word per leaf), photograph the leaves, and then leave them where.I found them. The story is then serialized, starting on October 1 and concluding on the 31st--All Souls Day.

.

FINIS

Above: Every Autumn, I write a Halloween story, write it out on leaves (one word per leaf), photograph the leaves, and then leave them where I found them. The story is then serialized, starting on October 1 and concluding on the 31st--All Souls Day.

.

This year's Halloween story, written on leaves and serialized daily on my blog, one sentence at a time, is done. Every day in October, I added to it, it reached its last words on Halloween.

Funny thing, though. In conversations with two different friends, I learned that neither of them had realized it was a story. They each thought I was just posting random sentences written on leaves. One of them is an artist, and thinks primarily in visual terms, so I thought at first that was a misunderstanding curious to her. The other, however, is a well-known writer and, what's more important, quite a good one. I have no idea what's going on there.

Long story short, at my behest, my son Sean, put all the photos up on Imgur, subtitled. So, if you didn't realize that they told a story... Or if, somehow, you weren't able to hold all the sentences in your head until the story was complete... Now you can find out what was going on. (The stone angels mark the ends of paragraphs.)

You can find it by clicking on the link here.

*

Drop bears are scary right



View Comic!

Knights of old



View Comic!

1. Kanguva Box Office Day 1 Advance Sales: 568% Higher Than Suriya’s Last Release ET In USA, Selling 5,460 Tix/Hr In India!  Koimoi
2. Kanguva morning show: Tamilians miffed as other states get earlier shows for Suriya, Bobby Deol's film  Hindustan Times
3. 5 Reasons To Watch Suriya and Bobby Deol Starrer 'Kanguva' In Theatres  Zee News
4. Kanguva’s second half to be very crisp  123telugu
5. Kanguva advance booking: Suriya's film earns over Rs 4 crore ahead of release  India Today

1. Eight injured in explosion at oil refinery in UP's Mathura  ANI News
2. 8 injured, three critical in major explosion at Indian Oil plant in UP's Mathura  India Today
3. Eight injured in fire at IndianOil’s Mathura refinery  BusinessLine
4. Mathura refinery blast: Indian Oil refinery explosion injures 12 people  The Financial Express
5. At least 8 injured in explosion at Mathura refinery  The Indian Express