1. Legitimacy of two Victorian local government elections in question after duplicate votes detected  ABC News
2. Victorian council election results 2024 LIVE updates: Suspected postal vote tampering in council elections  Sydney Morning Herald
3. VEC investigates potential vote tampering in two Melbourne councils  The Age

Fund raisers working in outsourced call centers, or directly for just one non-profit, face many of the same problems. While non-profit fund raising can be a very rewarding career choice, it can also be very stressful at times.

Donors who support a given charity don't always feel that being contacted by their non profit whether by phone or by means of a direct mail campaign, is something that they want to have any part of.

Often times, a fundraiser will feel that the campaign they're currently raising contributions for is a perfect and fool proof campaign. Donors have other ideas. At times it seems that donors who give to groups like The Humane Society Of The United States or PETA are far more receptive to a general appeal for animal welfare than those donors who support Oxfam International, or Habitat or Habitat For Humanity, when considering helping out on an emergency appeal.

Why should this be so? A quick answer to this question is that those fund raisers who are less emotionally invested in a campaign are better able to communicate the wishes and needs of an organization. Quite frankly, believing that one particular type of campaign is less important than another, will limit your ability to do well on either type of campaign in the long run.

After a year or so of professional, fundraising I had an epiphany; it doesn't really matter so much what you say on the phone to a donor. What matters is how you say it. My attitude changed at that point. I became less concerned with asking and more concerned with communicating. My performance improved, I felt far less burned out at the end of the day, and I began to raise more money.


There are certain truths that are universal to all campaigns. Mastery of these axioms of fund raising can only bring about better performance from fund raisers, and better results for the non profits we work for. Scientists who look deeply into the universe become mystics, fund raisers who strive to perfect their craft do as well. This is the first in a more abstract series of posts known as Fund Raising:102

The first is: Always regulate your mood.

No matter how enthusiastic a fund raiser is about a charity, or a campaign, being in control of ones emotions at all times will provide the best results. Donors can hear our emotions on the phone. Most people would rather hear a calm and compelling fund raiser map out the key strategies of a fund raising campaign than unbridled enthusiasm that borders on mania.

There is perhaps no better skill a fund fund raiser can have than the ability to match their tone, their emotional state, with that of the donor's.

Be enthusiastic, but remember that you are a complete stranger to your donor. You've interrupted their life and what always seems to be a critical time, and you want them to give you money!

So build your enthusiasm during the course of the call. Allow the donor to catch up to you rather than bowling them over. A single moment in a good fund raising call is like an eternity. Donors are compelled to listen the the truth of a good pitch.


Fund raisers who speak slowly and clearly, with a mastery of their fund raising campaign, are far less likely to be hung up on at all. Knowledge of the subject matter of a campaign, confidence in the virtue of the cause you are fund raising for, and empathy with the donor with whom you speak, create instant gravitas.

Instead of a rambling mendicant, a skilled fund raiser personifies the true meaning of the word solicitor; An authoritative figure who by virtue of the truth of their cause, and the strength of their argument, compels those who hear to listen, and those who listen to act.

This brings us to the second rule; focus on listening at all times, even while speaking.

If a donor shows a high level of enthusiasm for your campaign then by all means match that enthusiasm. Always strive to be listening to the donor listening to your voice. This concept surpasses what can be taught about fund raising, it must be experienced first hand; an experienced professional fund raiser can measure the attitude and attentiveness of a donor.

Listening to a donor while speaking at the same time is done by knowing, and believing in your campaign enough to stop listening to yourself say the words, and focus solely on the fact that you are speaking with another human being. Not a name, or a telephone number on a screen, not a statistic in a database, a person. The donors can hear this in your voice.

This strategy can change the outcome of virtually any fundraising call in a positive way. If a random donor plucked out of a database somewhere in an autodialer in the belly of your call center can tell what kind of mood you're in, how much better at doing the same thing should a fundraiser who makes 500 to 1000 calls each week?

Anyone who's had even limited success at fund raising through telephone campaigns has had life changing and inspiring conversations with people from all walks of life. Great fund raisers enjoy these moment several times per day.

The short answer to this question is, yes. While the rules have changed a bit since the early days of raising money online, the necessary elements all still exist in great supply. These are; a large and motivated donor pool, innovative organizations and fundraisers and the technology that brings it all together. This post will cover this complex topic with updates to come. In the mean time, voice your opinion on the relevancy of online fundraising in the comments section below.

The first step to success in online fundraising is the cause. While its possible to raise money for just about anything, what really promotes success is having a well defined mission statement. This is something that resonates with donors quickly. The shorter it takes to express your mission statement, the more likely it is that donors will stick around to learn more about your organization and its needs. This does not necessarily mean that they'll make a contribution, but donors who leave your site out of boredom, frustration or confusion certainly wont be making any.

After a well defined cause, presentation is the next most important element of online fundraising. Donors are quick to leave sites that are'nt easy to navigate. Ideally donors should be able to make an online gift in just one or two steps, the more complicated a donation system is, the less likely donations are to be made. Simple. modern interfaces are the key to increasing online donations.

Excellent fundraisers, as well as average ones often find themselves reaching a plateau when it comes to their fundraising abilities and the dollar amounts that they raise.  On a plateau, it is just as easy to move upward as it is to slip backwards; losing progress. Fundraisers are only interested in moving in one direction; upward.

pla•teau (plæˈtoʊ; esp. Brit. ˈplæt oʊ) 
n., pl. -teaus, -teaux (-ˈtoʊz, -toʊz) 
v. -teaued, -teau•ing. n.1. a land area having a relatively level surface considerably raised above adjoining land on at least one side.
2. a period or state of little or no growth or decline, esp. one in which increase or progress ceases: to reach a plateau in one's career.v.i.3. to reach a state or level of little or no growth or decline; stabilize

Definitions #2 and #3 have the most significance in fundraising, but definition #1 can be a useful visualization tool.

So how do we get beyond the fundraising plateau?

1. Go back to basics. Find something in your fundraising routine that can be improved and work on it. Can your greeting be made more friendly? Can your donation requests be tightened up? What ever it is, work on it. Working on any one issue has the added benefit of providing new perspectives on other issues.
2. Ask the donor. Ask donors, whether, they give or not, what they thought of your performance. Most will provide at least one useful bit of information. Some donors will provide so much valuable criticism that you may find yourself reexamining your entire fundraising strategy.
3. Ask another fundraiser. Sometimes we let shyness, pride or professional competition get in the way of improving our skills. Every fundraiser, at every stage, goes through the plateau problem. Reach out to your fellow fundraisers and get their advice.
4. Become an expert. Often after fundraising for a certain cause for a long time, fundraisers began to feel like experts on the issue. There is always more to learn. Find books magazine articles and any other materials that you can. The more you know about your issue, the better you can fund raise for it.
5. Remember, Plateaus aren't permanent. Keep slugging away, doing the best job that you possibly can. Eventually, you will begin to see some progress.

"To what extent is science a strong-link problem?", Sauropod Vertebra Picture of the Week, 10/30/2024 [emphasis added]: Here’s a fascinating and worrying news story in Science: a top US researcher apparently falsified a lot of images (at least) in papers that helped get experimental drugs on the market — papers that were published in top […]

A serious volcanic eruption on Flores Island has been going on since October 30: The Pusat Vulkanologi dan Mitigasi Bencana Geologi (PVMBG) reported that eruptive activity intensified at Lewotobi Laki-laki during 30 October-5 November, which included a major eruption resulting in fatalities. The large explosive eruption began at 2357 on 3 November, generating pyroclastic flows […]

Registration is now open for National O.T.O. Conference XIV, to be held in Denver, Colorado, August 3-6 2023. NOTOCON is normally held every two years, but it was canceled in 2021 due to the pandemic, so this will be our first NOTOCON since 2019.

The deadline to propose a presentation for National O.T.O. Conference XIV in Denver, CO, is May 10, 2023.

For potential speakers, a handy FAQ full of useful information is available here.

NOTOCON XIV is fast approaching! The cutoff date to receive our group rate at the hotel is Friday, July 21st. Please reserve now. The speaker schedule has been published on the NOTOCON website. Event registration is still open! We can’t wait to see all of you in August, and wish you all safe travels!

SAVE THE DATE for NOTOCON XV: The Crowned and Conquering Child to be hosted in Portland, Oregon from July 25 through the 27th, 2025 EV. The call for speaker proposals is now open and we are accepting Volunteer and Vending sign-ups. Registration and hotel reservations will be available in August 2024.

Hello and howdy. I usually describe myself as turning the "ripe old age of so-and-so" on my birthday posts, but I may need a new adjective as I'm solidly in my mid-40s, now (44). Perhaps "fermented." The birthday's come and gone without incident, although there were minor contemporaneous incidents:

Still in the math hole. It might be an infinite hole. Trying to get out. But I have improved my console fonts and ANSI color libraries and GPU programming skills, at least. I was very pleased that a recent release of NVIDIA drivers came with a brand new updated OpenCL, which I previously assumed had been abandoned like so many computer things that I become fond of. Kudos to whoever at NVIDIA pushed on this. I am making myself laugh privately to myself (well, no longer private now) by imagining someone who spells it out like an acronym, N-V-I D-I-A.

Also, like usual, I ran the Pittsburgh Great Race, a mostly-downhill 10k. No encumbrances this time. I've been in good shape this summer, but I got sick last month and it set me back a bit, so this wasn't a star performance. Still 43m22s is not too bad and I didn't push myself all that hard. Fewer minutes than years old.

The new GPU is mostly for math, but I wanted to try it out for its Intended Purpose, (N)Video Games. So I played through Far Cry 6, which was okay. I liked it better than 5, which among other things had a bunch of technical problems (this one was much smoother and more stable), but I probably should have read my review of that game before downloading, as I say something like "I should probably stop playing this series." Still slowly savoring Tears of The Kingdom, which remains great. I also started Return To Monkey Island. I loved the first two in this series, but couldn't get into the later sequels; of course I'm interested in giving this one a shot since it's made by the original designers (and I did like Thimbleweed Park). Too early to render a verdict, but I did like how they deftly handled the canonicity of the end of 2.

Then there's this: I think this is Taylor Swift wearing a homemade t-shirt of her "Pegicorn" (sometimes "Pegacorn"), a Unicorn-Pegasus hybrid. The text is in my font Action Jackson:

Taylor Swift Pegicorn (Action Jackson font)

You can also see this drawing/font at the beginning of the "Making of" video for You Belong With Me". I think she posted this to twitter in May 2009, but somehow I'm unable to find an archive of her tweets from this time (inconceivable??).

Wow, this month sure went by fast. I'm sure I say that every October, as this is the busiest time of year at work, and stuff like football and Maybe The Last Nice Day This Year keep me busy.

I've been plugging away at this math/programming project, currently porting some numerical code that I don't fully understand and finding bugs in it and improving its performance. It's relaxing, at least, but there's nothing good to share here yet and I'm not sure it'll ever make an interesting story. I did make some version-2 circuit boards for a project I've been working on in parallel, too, but the next step in that one is going to be annoying ("Why won't it boot?") so I've been putting it off.

They brought the small neighborhood race called "Run Shadyside" back this year. This is a 5k course that I can easily walk to the start of, and Shadyside is about as flat as it gets in Pittsburgh, so it's a nice race to try to PR in. I've been keeping in pretty good shape (despite the setback due to illness mentioned previously), but that morning I was having some burning lungs so I didn't push myself too hard. (Could have been mold? Bad air quality? Slightly sick?) I finished in 20m19s, which is probably my third best official 5K time, although a bit disappointing since I ran several unofficial treadmill 5Ks under 19 minutes this summer. I finished 3rd in my age group. The results feature a new capitalization of my name, the elusive Stegosaurus CasE: "Tom Murphy ViI"

Craving a game that would make proper use of the GeForce 4090, I installed Call Of Duty: Cold War. Actually this game is a couple years old, and graphically it's not anything particularly special. I am liking the single-player campaign more than usual for these kinds of games, and avoiding getting sucked into multiplayer. I gave the "zombies" mode a shot and I think I finally understand it, like playing a roguelike on a single seed. I think I'm at the point where I need to set myself some kind of challenge and complete it and retire to more artful things, though.

Hello again,

This month I've been plugging away on the project I mentioned in the previous post which involves among other things a PDF generator and now an implementation of ML (as in Standard ML, but also the other one). This is probably the 10th "compiler" I've written in my life, and it's kind of fun to revisit these problems that you've done many times and try out different approaches, although this time one of the approaches is "Use C++" (for reasons of making good on a joke, but also for reasons of mlton doesn't work on my computer any more). And although C++ is a fine tool for many applications, it does have some deficiencies for the task of writing a compiler (one of the most irritating: a very modest limit on the stack depth? Like my computer has 256 Gigabytes of RAM and 2^64 virtual addresses and somehow it can only manage 1 megabyte for the stack and there's no standard way to increase it? Get off my lawn). But then you can also experience new ways of struggling with C++, like: A middle of the night power failure wrecked my computer's GPT (as in GUID Partition Table, but also the other one) and I was deep in the depths of taking the computer apart to reset its parts, its BIOS (its Basic In/Out System, which is where it stores its biography) and its hard drives were everywhere on the floor, and it could not be saved, and this after I already broke my computer this year by trying to put the world's biggest video card in it, too hard. And I could not merely perform recovery because of Unknown Error, so I had to begin anew again and restore from backups. But when you restore from backup and you're in the mood of "why is this so complicated and I don't understand how computers work any more?" it occurs to you (me) to also change your underlying development environment instead of reinstalling the devil you know. So I ended my friendship with Cygwin64 and switched to new best friend MSYS2. Both of these things are different ways of wishing that you were using Linux while you're using Windows. The main reason I tried this new way of struggling is that Cygwin is very behind on its version of x86_64 clang (C++ compiler), which I wanted to try because it supports AddressSanitizer and clangd on Windows, and I wanted to give LSP in emacs a shot (it's finally good!). There were a few growing pains, but I think MSYS2 is what I would recommend now. One of the nice things they did was create multiple different environments depending on what you want to do (e.g. "I want to use clang to compile x86_64 code" or "I want to do 32-bit cross compilation for ARM") and in that environment, you just say "g++" and it invokes the compiler you want, instead of the weird contortions I've been doing for years with manually invoking x86_64-w64-mingw32-g++. I was also able to get clblast working before being too filled with rage to continue, so that is nice for the ML inference on the world's biggest graphics card. I made these graphics to help me tune the correct settings of GPU layers (y axis) and number of threads (x axis):

tune-single
tune-batch

In some sense the results are obvious (more threads and more layers is faster) but it was interesting to me how the cliff of performance drops off at a different number of layers for single and batch mode (I guess because the batch needs some memory itself?) and how it's clearly better to use fewer threads than cores for batch as well. I was not surprised to see performance drop off for >32 threads (everybody knows that hyper-threads kinda suck) but I was very surprised to see performance pick up again when it gets back up to 64? And only for single mode? I wish I understood that better. But mostly I'm a sucker for the custom visualizations.

Right but when writing this compiler I realized that I wanted to use some Greek letters, and I can't handle it when some characters are in a different font in my source code, so I finally made some space for those in my programming font FixederSys. These certainly still need some tweaks, but it's already better than just being in some other weird font:


{{{caption}}}

You can also see that I have been adding some "useful" emoji at the top. It is an interesting puzzle to try to make these things recognizable (especially for the 1x version, whose charboxes are 8x16 pixels). I am pretty sure I will not try to do all of the emoji (like, the flags are totally hopeless at 8x16), but it is tempting to round out the Unicode support somewhat. Like I was trying to make a ¯\_(ツ)_/¯ today and had to settle for ~\_( :) )_/~ which is pretty much (ノಠ益ಠ)ノ彡┻━┻.

Also: Adam revived our old game jam game Headcat, which I described in post 927, now over 16 years ago. You can play it online at Headcat.org. It is harder than I remember, perhaps explaining why it did not reach #1 on the One Appstore Per Child charts.

Also: I started and finished (true ending, but just with one character) Slay the Spire. Good game, but you don't need me to tell you that. Same for Alwa's Legacy, which is the sequel to Alwa's Awakening. Both of these are very true-to-form "8-bit" and "16-bit" platformers that I enjoyed and would recommend for genre fans, though I did not try to 100% them. The graphics are the highlight and I thought it was very cute how these could easily have been a pair of games from the NES and SNES. The good old days. And speaking of good-old days, I am now playing Katamari Damacy, which I had played at a friend's house many years ago, and always wanted to spend more time with. It totally holds up (aside from stuff like: You have to play through the tutorial and first level before you can access the menus at all, like to make the game fullscreen?) and it's honestly inspiring how unhinged the game design and writing are, and how fun it manages to be. What an accomplishment!

OMG. I can't believe October is over already. I blame Satisfactory which, okay, I do get it now, and it did destroy my body and mind. I am inches from being done now; I just want to make sure that I finish it with enough force that I do actually put it away, as I could imagine tinkering with my saddest factory forever.

The game isn't without flaw, but I think most of those flaws are not interesting to talk about. I do have one petty but important criticism, which is mildly spoilerful and anyway will only be interesting if you played the game. There is an object called the Somersloop ("cool S") which allows you to double the output of a machine. Canonically this item is some kind of "loop" and the flavor text talks about how it is able to create more energy than you put into it. So when I'm out hunting for Korok seeds I have this thought that maybe I could create a loop of factories whereby it would create infinite resources by repeatedly doubling. And I'm thinking about it but the crafting tree doesn't have any notable loops in it, but I remember the "packager" which allows you to put a fluid in a container or the converse, and I'm like: Yes, that's great! So I get back to base and I am doing this, just for fun to create an infinite fuel factory or whatever, and I realize that the packager just doesn't have a slot for a Somersloop. They must just hate fun, elegant twists. It would not break the game to allow this (you can always get infinite resources lots of other ways) or cause any other problem I can think of. Hmph!

The thing about constructing a factory and watching it churn is that it's basically the same thing as a programming project that you invented for yourself, and it's probably better to do the programming project. Here's progress on my mysterious rectangle:

Minusweeper 2

It's good progress if I do say so myself! Anything but black here is a Satisfactory result, which is 90.55% of them at this point. I may need heavy machinery for the remaining 9.45%, but that is part of the fun.

I think that's really it for this month! Please vote in the US Elections if you can (but I guess also vote in any important elections. And obviously, vote for the good guys???). And happy Halloween!

In the six months since my retirement from the bench I have not had cause to visit the courthouse. This week, however, I volunteered to show some local people around the building, and I was agreeably surprised to find that I still remembered the pass code for the car park. Our visitors were very interested and full of questions, which reminded me of my very early days as a JP when I found out just how little people knew about the court and its workings. That was a prime reason for my starting a blog a decade ago.

Great Britain's Elizabeth Yarnold wins a bronze medal at the women's skeleton World Championship.

Canadian skier Nick Zoricic dies from head injuries after crashing heavily in a World Cup skicross race in Switzerland.

As of November 10, 2015, BORROWED TIME (the sequel to CHRONAL ENGINE) is now available in bookstores everywhere as well as online (in hardcover and ebook)!  Signed copies are available from BookPeople.

In an article titled, 'Borrowed Time' mixes paleontology and fantasy, Saturday's Austin American-Statesman had a great review of BORROWED TIME, stating it's "a slam-dunk for dinosaur aficionados and will appeal as well to those who are fans of literary time travel and outdoorsy adventure."

Sunday was the launch party at BookPeople! I had great fun doing a presentation discussing the connections between the book, Charles Umlauf, dinosaurs, Johnny Weissmuller, and me (really).

The dinosaur standees for the photo booth were a hit, as were the refreshments including water, soft drinks, wine and cheese, and crackers. (The wine, from the Languedoc region of France, is made from grapes grown in Cretaceous clays where dinosaur fossils have have been found).

But the real eye-opener was the mosasaur cake by author/cakelustrator Akiko White. About two feet high, it featured a mosasaur sculpted from modeler's chocolate on a chocolate cake base with buttercream frosting! She'll be doing a youtube video on the making of it soon (and I'll link when it's available).  Suffice to say that still pictures don't do it justice -- it was mounted on a motorized turntable and illuminated with a blue strobe that made it look like it was underwater!

Here are the pics:

Me and cake

Carmen Oliver and T.rex

Akiko assembles! (photo courtesy Akiko White)

Presenting (photo courtesy Akiko White)

Cake!

Refreshments

Signing

Frances Hill and Lindsey Lane (photo courtesy of Shelley Ann Jackson)

Shelley Ann Jackson and Lindsey Lane (photo courtesy Shelley Ann Jackson)

 Many thanks to BookPeople for hosting the event, to everyone who came for the event, and to everyone who helped out: Akiko, for making the awesome cake; Cynthia Leitich Smith; Carmen Oliver; Lindsey Lane; Shelley Ann Jackson; and Cory Putnam Oakes!

Cake topper in its natural habitat

I'm just back from a twelve day trip up to Chicago, Milwaukee, and Minneapolis-St. Paul, where I did a bit of research and visited a bunch of schools and children's indie bookstores.

The trip started inauspiciously, when my flight was canceled because the wind blew the plane onto a belt conveyor.

Eventually, I made it to Chicago, though, where the weather looked like this:
Still, I had arrived ahead of time so I could go down to the Museum of Science and Industry, which has a World War II German u-boat and a chicken incubator.
Next two days were the actual school visits, arranged at Henry Puffer Elementary  and Liberty Elementary by Anderson's Book Shop and at Attea Glenview School and Rondout School by The Book Stall.  Afterwards, I got to hang out with Robert from The Book Stall and stopped by for a couple of pics.

Posing with posters

Then I was off to Milwaukee for a school visit at Atwater Elementary arranged through the Boswell Book Company.
It was my first time I'd ever been to Milwaukee, but sadly didn't have a chance to sightsee, because it was off to Minneapolis-St. Paul for three days of school visits.

Visits at North Trail Elementary and Brimhall Elementary were through Addendum Books; those at Crestview Elementary and Little Canada Elementary were through the Red Balloon Bookshop; and at Valley View Middle School, through Wild Rumpus Books.

Snake!

I had some free time, so I went over to Addendum Books for some pics and had a fun lunch with Katherine and Marcus, the proprietors.

In front of the "Purple Rain" wall

Since I was there over the weekend, I spoke at Red Balloon for the Minnesota SCBWI about Research and the Suspension of disbelief.

I also had the chance to go run a couple times on the Mississippi Riverfront trail and visit the Science Museum of Minnesota.

T.rex!

Triceratops

Stegosaurus!

After Monday's school visit I had a fun lunch with Drew and Jordan of Wild Rumpus Books at Pizzeria Lola (a separate Pizza-a-Day Diet post will be forthcoming).  Then I visited the bookstore, where I met the menagerie.

Copper oven and decorative birch logs

Chicken!

Ferret!

Then I was back to Chicago and spent a day at the Field Museum of Natural History and showed Madeline Smoot of CBAY Books a bit of the city!


Many thanks to all the librarians and booksellers and Blue Slip Media and everyone else who made this happen.  Thanks also to Quinette Cook and all the folks from MN SCBWI who came out for the workshop.  It was great fun meeting you!

For information on how to book me for school visits for the 2016-2017 school year, contact Carmen Oliver at The Booking Biz.

It's the eve of the Texas Book Festival so make sure you check out the festivities on the Capitol grounds! And here's a tentative list of projects from Austin authors and illustrators releasing next year! For previous years, go here.

Picture Books, Easy Readers, and Board Books

WHAT DO YOU DO WITH A VOICE LIKE THAT? by Chris Barton, ill. by Ekua Holmes (Simon & Schuster/Beach Lane 2018).

MIGHTY TRUCK: ON THE FARM, by Chris Barton, ill. by Troy Cummings (HarperCollins, May 2018).

PENGUIN AND TINY SHRIMP DON'T DO BEDTIME, by Cate Berry, ill. by Charles Santoso (Balzer + Bray/HarperCollins 2018).

ABRAHAM LINCOLN'S DUELING WORDS, by Donna Janell Bowman, ill. by S.D. Schindler (Peachtree, 2018)

THE BOOK THAT JAKE BORROWED, by Susan Kralovansky (Pelican 2018).

COUNTING COLORS IN TEXAS, by Susan Kralovansky (Pelican 2018).

KATE, WHO TAMED THE WIND, by Liz Garton Scanlon, ill. by Lee White (Schwartz & Wade, Spring 2018).

FRANCES IN THE COUNTRY, by Liz Garton Scanlon, ill. by Sean Qualls (Neal Porter Books/Roaring Brook Press, Summer 2018).

DEAR SUBSTITUTE, by Liz Garton Scanlon, ill. by Chris Raschka (Disney-Hyperion, Summer 2018).

STALEBREAD CHARLIE AND THE RAZZY, DAZZY SPASM BAND,  by Michael Mahin, ill. by Don Tate (Houghton Mifflin Harcourt, 2018).

PAR-TAY: DANCE OF THE VEGGIES (AND THEIR FRIENDS), by Eloise Greenfield, ill. by Don Tate (Alazar Press 2018).

POTATO KING: THE STORY OF JUNIUS G. GROVES, by Don Tate (Knopf 2018).
 

Middle Grade

THE BOY, THE BOAT, AND THE BEAST, by Samantha Clark (Paula Wiseman Books/Simon & Schuster, Summer 2018).

KNOCKOUT, by K.A. Holt (Chronicle, Spring 2018).

DEAR ME (tent. title), by K.A. Holt (Scholastic, Summer 2018).

THE PARKER INHERITANCE, by Varian Johnson (Scholastic, Spring 2018).

THE CAMELOT CODE: THE ONCE AND FUTURE GEEK, by Mari Mancusi (Disney-Hyperion, Oct. 2018).

GIRLS WHO CODE: LIGHTS, MUSIC, CODE, by Jo Whittemore (Penguin Workshop, Spring 2018).

REVENGE OF THE TEACHER'S PETS, by Jennifer Ziegler (Scholastic, June 2018).

Young Adult

HEARTS UNBROKEN, by Cynthia Leitich Smith (Candlewick Press, 2018).

AVENGED, by Amy Tintera (HarperTeen, May 2018).

I just completed my second Ironman 70.3 ("half-Ironman") in Galveston, Texas!

It was different, but not too different than the first. In some ways it was more challenging than Austin, although I did manage to eke out a personal best, so I count myself pleased, although I've identified several areas where I can improve :-).

The Galveston site presented a couple more difficulties than the Austin one, viz., transportation of people and bicycles, as well as housing therefor.  The race site was at Moody Gardens, which has its own resort hotel, which we might have done if we had planned on going on Friday and staying until Monday.  Ultimately, we decided to drive down the morning before the race with our bikes, rent a house via Airbnb, and drive back the evening of the race.

Leaving Austin at 7 AM...

With two bikes on the back, three people (and one bike) in the car, and all our gear, we were pretty packed, but the drive only took about three and a half hours, even accounting for coffee breaks.

We drove directly to Moody Gardens to pick up our race packets and drop off our bikes.  The first thing we discovered when we arrived was that it was cold and rainy and the swim venue (Offats Bayou) was a bit choppy...

Under the triumphal arch the day before the race...

Registration/packet pickup was in a big white tent overlooking the bayou (the same big white tent Moody Gardens had used for a cool dinosaur thing a couple years back).

The white tent with dinosaurs five years ago...

The pickup and registration and dropoff were strangely inefficient: You wait in line at a first table to show your ID and USA Triathlon membership; then you go to a second table to pick up your waiver and other forms. Next, you go to a third table to fill in and sign your waiver and forms, and go to a fourth table to drop off your signed waiver and forms. Thereafter, you go to a fifth table to pick up your wristband and swim cap and bike and helmet stickers; go to a sixth table to pick up your backpack/goodie bag and T-shirt; and finally, go to a seventh table to pick up your timing chip.

Then you exit via the Ironman store and vendor village where you can wait in line to buy stuff.

Inside the big white tent

The course talk was outside and the rain had died down enough so that it wasn't all that unpleasant. Behind us was the paddlewheeler Colonel and a whole lot of choppy water with whitecaps. We were assured that the weather could be better the next day, however. No rain and significantly less wind, although there would be a headwind on the return portion of the bike route.

The paddlewheeler Colonel.

The swim course, with the finish right by the paddlehweeler

The Airbnb was a nice little three-bedroom cottage about five miles from the event site and across from a large cemetery.  It had a complete kitchen that would come in useful later that night when we couldn't get into any of the nearby Italian restaurants without reservations.

The house we rented

Cemetery across street.

Making spaghetti dinner

That evening, we gathered all of our gear and made dinner and looked forward to the race. I went for a three mile run around the nieghborhood to loosen up a bit, and then we made dinner.

I managed to get around five or six hours of sleep and only hit the snooze button once when the alarm went off at 4:30 in the morning. After a couple cups of coffee, a banana, and a bagel, we were off!

The temperature felt good: low fifties, not too much of a breeze. I decided I didn't need gloves, but would take along my arm warmers for the bike just in case. We arrived at Moody Gardens a little after six and discovered we had had to park about a fifteen minute walk from the actual transition area.  A remarkably long line greeted us to enter transition (for body marking), but since we had already done so, we were able to get in with only a brief wait and some judicious weaving through the crowd.

Testing out the wetsuit when I first got it.

There was then the ritual of putting on the wetsuit and pumping the bike tires and then transition closed! (We might have cut the timing a little close).

We then made our way separately to the swim start: they did a wave start by age group. You jump off the pier (see above map), hang around in the water for a couple minutes, and then swim like the wind when you hear the starter's horn.

The water was a nice 72 degrees, about twenty degrees warmer than the outside temperature. The water felt good, although it took a few minutes to get used to the waves and occasional mouthful of salt water. I felt pretty good, though, and noticed myself passing a lot of people.  More importantly, I managed to beat my swim time from last fall's Austin Ironman 70.3.


 Once I was out of the water, the wetsuit strippers were efficient and I had no problem getting to my bike (even without my glasses), stowing my wetsuit and taking off. Because it was relatively warm, I decided not to bother with my sleeves, and I wouldn't have worn gloves even if I had brought them.

The first half of the bike portion was glorious. The temperature was perfect and I had no problems staying in aero position almost the whole way.  Unfortunately, at the turnaround, I was made to realize just how much of a tailwind I had been benefitting from. The rest of the ride felt like I was pulling a mobile home...

Grimacing with miles to go...

Also about that time, the temperature dropped by about ten degrees, and it started to rain. And then my back started to hurt from being in aero position for so long.  In short, the ride back was completely miserable...But I managed to break three hours, which had been my goal.

In addition to the lower back pain, I got a pain between my shoulders, and every time I tried to stand up in the pedals to stretch, my legs felt like they wanted to cramp up.  And my hands were so cold I could barely move them to squeeze my water bottles.

Trying to squeeze out the last drop from my water bottle.

By the time I got back to transition, my hands were so numb that I couldn't operate the clip on my helmet. Putting on my shoes and tying my laces was equally an ordeal. It didn't help that my legs and abs kept cramping up when I bent to tie the laces.  After a ridiculously long transition, I made it onto the run course and my watch died.


But my legs felt good and I enjoyed the run a lot more than I thought I was going to on the return bike. :-). My pacing was a bit off and I came in somewhat slower than I would've liked, but it still felt pretty good.

Victory!

Overall, I came in a couple minutes better than the Austin Ironman 70.3, which I'm pleased with (although I think my run could've gone better).

Mugging with the finisher's medal

Using the R8 recovery roller thing...

All in all, it was a great experience and I'd definitely do the race again. A big thanks to all the organizers, volunteers, sponsors, and first responders who made the event a success!

If passed, it would be the first standalone NASA authorization since 2017.

With all the advances in private space exploration, why do taxpayers still pay for space science missions?

When a skyscraper-sized asteroid narrowly misses Earth in 2029, three spacecraft may be along for the ride.

Looking to the past to guide the search for life.

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

NASA is preparing to launch its flagship mission to explore Jupiter’s moon Europa. Launching sometime in October 2024 and arriving in 2030, the mission will explore the icy world with a subsurface ocean that scientists think could have conditions favorable to life.

The European Space Agency (ESA) is preparing to launch a mission to study the aftermath of DART's impact on the asteroid moonlet Dimorphos.

Catch this once-in-a-lifetime comet over the next few days.

The European Space Agency’s Hera spacecraft launched on Oct. 7, 2024, from Cape Canaveral, Florida. It will travel to the Didymos-Dimorphos asteroid system to study the aftermath of the first-ever field test of an asteroid deflection technique.

NASA’s Europa Clipper spacecraft launched today aboard a SpaceX Falcon Heavy rocket from NASA’s Kennedy Space Center in Cape Canaveral, Florida.

How the inclusion of Katie Taylor v Amanda Serrano on the bill legitimises the carnival of Mike Tyson v Jake Paul in Texas

I've been messing around adding to the bear to days and trying not to rush myself. I'm so desperate to get some paint on it that I almost started today. However, I stopped myself and just added a bit more fur. This time I also ad buyded some to the bears face and now I'm finally happy with it.




Cheeky!
Some more help turns up to bolster Lake town and just in the nick of time.


Two of these bases are really shoddy militia types. Pitch forks are a great short hand for 'rabble'. I can't imagine they will hold for long against the goblin horde.

Another hero base .

I think he looks angry, ragged and damn right mean now...let's get him painted up.


I've added hints of blue so the whole force will tie together.


 The men start to suffer from the fierce wolf packs.

The men with their long swords and the tough veterans from the Iron hills.

The last Dwarf base done just in time for the big weekend. It's the Other Partizan show this weekend and I'll be there with my armies. So if you fancy seeing a massive Hobbit battle...pop along.

The battle will be fought using the new Midguard rules by James Morris. It proves to be a great Sunday especially if you're a Tolkien fan.

Today I have collect everything together and pack it as best I can to stop any travel casualties. I have always painted my figures to play at home so have never magnetised them onto metal sheets.Finally the two meet, Bolg and bigger Beorn.
My old Beorn figure is dwarfed by the new addition. The new bear has a lot more presence to him and should look the part on Sunday.

 

It's time to dig out the old stones and compare them. A lot of these previous models had a greenstuff carving in them.

The two weapon shrines. One is a place of worship, the other, sacrifices.


The two stones of the dead. These could be used for any undead project.

 New projects: 

• adp-github — ADP extension to generate github markdown files. — MIT
• adp-plain — Add Documentation, Please... using plain text. An extension of ADP to generate files with barely additional features. — MIT
• allioli — Alliolification — MIT
• alternate-asdf-system-connections — Allows for ASDF system to be connected so that auto-loading may occur. This is a fork of asdf-system-connections and incorporates a load-system-driven mechanism for loading dependencies and also loads the dependencies of the connections. — MIT
• cbor — CBOR encoder/decoder — MIT
• charje.documentation — Documentation is an opinionated yet customizable docstring parsing library. — AGPL V3 or any later version
• chipi — House automation bus in Common Lisp — Apache-2
• cl-aseprite — Aseprite file format parser — GPLv3
• cl-astar — A heavily optimized yet flexible A* pathfinding algorithm implementation — MIT
• cl-ceigen-lite — A Common Lisp wrapper around CEIGEN-LITE - which is itself a C wrapper around the C++ Eigen library. — MIT
• cl-cf — Computations using continued fractions — GPL-3
• cl-concord — CONCORD implementation based on Common Lisp — LGPL
• cl-duckdb — CFFI wrapper around the DuckDB C API — MIT License
• cl-fastcgi — FastCGI wrapper for Common Lisp — BSD License
• cl-flx — Rewrite emacs-flx in Common Lisp — MIT
• cl-frugal-uuid — Common Lisp UUID library with zero dependencies — MIT License
• cl-gog-galaxy — A wrapper for the GOG Galaxy SDK — zlib
• cl-lc — List comprehensions — MIT
• cl-naive-ptrees — Functions to make it easier to work with plist(s) and plist trees. Works with plist(s) pairs as units and not as individual list items. — MIT
• cl-qoa — An implementation of the Quite Okay Audio format. — zlib
• cl-reddit — Reddit client api library — BSD
• cl-resvg — An up-to-date bindings library for the resvg SVG rendering library — zlib
• cl-trivial-clock — Common Lisp library to get accurate wall-clock times on multiple platforms — MIT License
• clack-cors — A Clack middleware to set CORS related HTTP headers. — Unlicense
• clack-prometheus — Clack middleware to serve stats in Prometheus format. — Unlicense
• clith — Common Lisp wITH macro. A general WITH macro. — MIT
• clj-arrows — Implements Clojure-styled threading/transformation macros. — MIT
• clos-encounters — A collection of OOP patterns benefiting from the CLOS MOP. — Unlicense
• coalton — An efficient, statically typed functional programming language that supercharges Common Lisp. — MIT
• cocoas — A toolkit library to help deal with CoreFoundation, Cocoa, and objc — zlib
• com.danielkeogh.graph — A fast an reliable graph library. — MIT
• fast-mpsc-queue — Multi-Producer Single-Consumer queue implementation. — MIT
• file-finder — File finder. Enable rapid file search, inspection and manipulation. — GPL3+
• golden-utils — A utility library. — MIT
• hiccl — HTML generator for Common Lisp — MIT
• hsx — Hypertext S-expression — MIT
• hunchentoot-stuck-connection-monitor — Monitors hunchentoot connections and logs the connections stuck in the same state for a long time (due to slow or inactive clients and network stream timeouts that hunchentoot tries to utilize not working properly). Offers an option to shutdown the stuck connections sockets manually or automatically, thus unblocking the connection threads and preventing thread and socket leak. See https://github.com/edicl/hunchentoot/issues/189 — BSD-2-Clause
• incless — A portable and extensible Common Lisp printer implementation (core) — BSD
• inravina — A portable and extensible Common Lisp pretty printer. — MIT
• invistra — A portable and extensible Common Lisp FORMAT implementation — BSD
• knx-conn — KNXnet/IP implementation in Common Lisp — GNU GPL, version 3
• machine-state — Retrieve machine state information about CPU time, memory usage, etc. — zlib
• myweb — simple web server written in common lisp for educational reasons — LGPLv3
• noisy — Perlin noise for arbitrary numbers of dimensions. — MIT
• nontrivial-gray-streams — A compatibility layer for Gray streams including extensions — MIT
• open-with — Open a file in a suitable external program — zlib
• openai-openapi-client — Openai API client — AGPLv3+
• openrpc — CI for Common Lisp OpenRPC library. — BSD
• parse-number-range — Parses LOOP's convenient "for-as-arithmetic" syntax into 5 simple values: from, to, limit-kind (:inclusive, :exclusive or nil if unbounded), by (step) and direction (+ or -)). Further related utilities are provided. Intended for easy implementation of analogous functionality in other constructs. — Public Domain
• precise-time — Precise time measurements — zlib
• pregexp — Portable regular expressions for Common Lisp — MIT-like
• progressons — Display a progress bar on one line. — MIT
• quaviver — A portable and extensible floating point string library — MIT
• quilc — A CLI front-end for the Quil compiler — Apache License 2.0 (See LICENSE.txt)
• qvm — An implementation of the Quantum Abstract Machine. — Apache License 2.0 (See LICENSE.txt)
• random-sampling — Functions to generate random samples with various distributions — zlib
• rs-dlx — Knuth's Algorithm X with dancing links. — Modified BSD License
• scrapycl — The web scraping framework for writing crawlers in Common Lisp. — Unlicense
• smoothers — Statistical methods to create approximating functions that attempt to capture important patterns in the data, while leaving out noise or other fine-scale structures/rapid phenomena. — MS-PL
• trivial-adjust-simple-array — A tiny utility to change array size ensuring it is simple. — MIT
• trivial-system-loader — A system installation/loading abstraction for Common Lisp — MIT
• trivial-toplevel-commands — Trivial Toplevel Commands allows to define toplevel commands available on most implementations in a portable fashion. — BSD-3 Clause
• trivial-toplevel-prompt — Portability library to customize REPL prompts. — BSD-3 Clause
• utf8-input-stream — A UTF-8 string input stream over a binary stream for Common Lisp — MIT
• whereiseveryone.command-line-args — Automatically create a command-line-argument parser for a given Common Lisp function definition. — AGPL v3 or any later version

Updated projects: 3b-bmfont, 3bgl-shader, 3bmd, 3d-math, 3d-spaces, 40ants-asdf-system, 40ants-slynk, access, acclimation, action-list, adhoc, adopt, adp, agnostic-lizard, alexandria, alexandria-plus, anatevka, anypool, april, arc-compat, architecture.builder-protocol, array-utils, arrow-macros, assoc-utils, async-process, atomics, auto-restart, aws-sdk-lisp, babel, bdef, bike, binary-structures, binding-arrows, birch, blackbird, bordeaux-threads, calm, carrier, caveman, ccldoc, cephes.cl, cepl, cerberus, cffi, cffi-object, cffi-ops, chanl, chunga, ci, ci-utils, ciao, cl-6502, cl-algebraic-data-type, cl-all, cl-ansi-term, cl-async, cl-atelier, cl-autowrap, cl-base32, cl-bmas, cl-bmp, cl-bnf, cl-brewer, cl-buchberger, cl-cmark, cl-collider, cl-colors2, cl-confidence, cl-containers, cl-cookie, cl-csv, cl-custom-hash-table, cl-cxx-jit, cl-data-structures, cl-dbi, cl-digraph, cl-dot, cl-enchant, cl-environments, cl-fast-ecs, cl-fbx, cl-fluent-logger, cl-form-types, cl-forms, cl-freetype2, cl-gamepad, cl-github-v3, cl-gltf, cl-gobject-introspection, cl-graph, cl-grip, cl-gserver, cl-hamcrest, cl-hash-util, cl-html-readme, cl-i18n, cl-info, cl-ini, cl-ipfs-api2, cl-kanren, cl-lib-helper, cl-liballegro, cl-liballegro-nuklear, cl-log, cl-markless, cl-marshal, cl-migratum, cl-mixed, cl-modio, cl-mount-info, cl-mpg123, cl-mssql, cl-mustache, cl-mysql, cl-neovim, cl-netpbm, cl-oju, cl-opengl, cl-opensearch-query-builder, cl-opus, cl-patterns, cl-plus-ssl-osx-fix, cl-ppcre, cl-project, cl-protobufs, cl-pslib, cl-pslib-barcode, cl-rashell, cl-readline, cl-sat.minisat, cl-sdl2-image, cl-sdl2-mixer, cl-sdl2-ttf, cl-sendgrid, cl-sentry-client, cl-skkserv, cl-smtp, cl-ssh-keys, cl-steamworks, cl-str, cl-svg, cl-telegram-bot, cl-threadpool, cl-tiled, cl-torrents, cl-tqdm, cl-transducers, cl-transit, cl-unicode, cl-unification, cl-unix-sockets, cl-utils, cl-vectors, cl-vorbis, cl-wavefront, cl-webdriver-client, cl-webkit, cl-webmachine, cl-who, clack, clack-pretend, clad, classimp, clast, clath, clavier, clazy, clerk, clgplot, climacs, clingon, clip, clj-con, clj-re, clobber, clog, clog-ace, clog-collection, clog-plotly, clog-terminal, clohost, closer-mop, clss, cluffer, clunit2, clx, cmd, codata-recommended-values, codex, coleslaw, collectors, colored, com-on, common-lisp-jupyter, commondoc-markdown, compiler-macro-notes, conduit-packages, consfigurator, contextl, croatoan, ctype, cytoscape-clj, damn-fast-priority-queue, dartscluuid, data-frame, data-lens, datafly, dbus, decompress, defenum, definer, definitions, deflate, defmain, deploy, depot, deptree, dexador, dissect, djula, dns-client, doc, docs-builder, dsm, dufy, easter-gauss, easy-audio, easy-macros, easy-routes, eclector, equals, erjoalgo-webutil, erudite, esrap, event-emitter, external-program, external-symbol-not-found, fare-csv, fare-scripts, fast-http, fast-websocket, file-attributes, file-notify, file-select, filesystem-utils, fiveam, fiveam-matchers, flexi-streams, float-features, flow, fn, fset, functional-trees, fuzzy-dates, gadgets, generic-cl, github-api-cl, glfw, glsl-toolkit, harmony, hashtrie, helambdap, http2, hunchentoot, imago, in-nomine, inferior-shell, introspect-environment, ironclad, jose, js, json-mop, jsonrpc, jzon, khazern, lack, lass, lemmy-api, letv, lichat-protocol, lichat-tcp-client, linear-programming, lisp-binary, lisp-chat, lisp-critic, lisp-pay, lisp-stat, lispcord, lla, local-time, log4cl-extras, logging, lru-cache, magicl, maiden, maidenhead, manifolds, math, mcclim, memory-regions, messagebox, method-combination-utilities, mgl-pax, misc-extensions, mito, mk-defsystem, mmap, mnas-package, mnas-string, moira, multiposter, mutility, mutils, named-closure, ndebug, neural-classifier, new-op, nibbles, nibbles-streams, ningle, nodgui, north, numerical-utilities, nytpu.lisp-utils, omglib, ook, open-location-code, openapi-generator, orizuru-orm, overlord, papyrus, parachute, parse-number, pathname-utils, petalisp, phos, picl, plot, plump, plump-sexp, pngload, policy-cond, polymorphic-functions, postmodern, ppath, prometheus-gc, psychiq, purgatory, py4cl, py4cl2, py4cl2-cffi, qlot, qoi, query-fs, quick-patch, quickhull, quri, random-state, reblocks, reblocks-auth, reblocks-file-server, reblocks-lass, reblocks-navigation-widget, reblocks-parenscript, reblocks-prometheus, reblocks-typeahead, reblocks-ui, reblocks-websocket, rove, s-dot2, sandalphon.lambda-list, sb-fastcgi, sc-extensions, sel, select, serapeum, shasht, shop3, si-kanren, sketch, slime, slite, sly, snooze, spinneret, staple, static-vectors, statistics, stepster, stmx, stripe, swank-crew, swank-protocol, sxql, symath, system-locale, taglib, teddy, ten, testiere, tfeb-lisp-hax, tfm, tiny-routes, tooter, trivia, trivial-arguments, trivial-clipboard, trivial-file-size, trivial-gray-streams, trivial-main-thread, trivial-octet-streams, trivial-package-locks, trivial-package-manager, trivial-sanitize, trivial-shell, type-templates, typo, uax-15, uiop, usocket, vellum, vellum-binary, vellum-csv, vellum-postmodern, verbose, vernacular, vom, websocket-driver, winhttp, with-branching, with-contexts, woo, xhtmlambda, xml-emitter, yason, zippy, zpb-ttf.

Removed projects: abstract-arrays, ahungry-fleece, cl-cheshire-cat, cl-darksky, cl-epoch, cl-naive-store, convolution-kernel, dense-arrays, extensible-compound-types, extensible-optimizing-coerce, fast-generic-functions, flac-metadata, freebsd-ffi, listoflist, luckless, one-more-re-nightmare, postmodern-localtime, stumpwm-dynamic-float, stumpwm-sndioctl, unicly.

To get this update, use:

 (ql:update-dist "quicklisp")

Sorry this update took so long. My goal is to resume monthly releases.

Enjoy!

Last week I finished a new service written in Common Lisp. It now runs in production© every mornings, and it expands the set of services I offer to clients.

It’s the 4th service of this kind that I developed: - they are not big - but have to be done nonetheless, and the quicker the better (they each amount to 1k to 2k lines of Lisp code), - they are not part of a super advanced domain that requires Common Lisp superpowers - I am the one who benefits from CL during development, - I could have written them in Python - and conversely nothing prevented me from writing them in Common Lisp.

So here lies the goal of this post: illustrate that you don’t need to need a super difficult problem to use Common Lisp. This has been asked many times, directly to me or on social media :)

At the same time, I want to encourage you to write a little something about how you use Common Lisp in the real world. Sharing creates emulation. Do it! If you don’t have a blog you can simply write in a new GitHub repository or in a Gist and come share on /r/lisp. We don’t care. Thanks <3

We’ll briefly see what my scripts do, what libraries I use, how I deploy them, what I did along the way.

Needless to say that I dogfooded my CIEL (beta) meta-library and scripting tool for all those projects.

Table of Contents

• Scripts n°4 and 2 - shaping and sending data - when you can write Lisp on the side
  • SFTP
  • Deploying
  • Script n°2 and simple FTP
• Scripts n°3 and 1 - complementary web apps
• Lasting words
• Links

Scripts n°4 and 2 - shaping and sending data - when you can write Lisp on the side

My latest script needs to read data from a DB, format what’s necessary according to specifications, and send the result by SFTP.

In this case I read a DB that I own, created by a software that I develop and host. So I could have developed this script in the software itself, right? I could have, but I would have been tied to the main project’s versioning scheme, quirks, and deployment. I rather had to write this script on the side. And since it can be done on the side, it can be done in Common Lisp.

I have to extract products and their data (price, VAT...), aggregate the numbers for each day, write this to a file, according to a specification.

To read the DB, I used cl-dbi. I didn’t format the SQL with SxQL this time like in my web apps (where I use the Mito light ORM), but I wrote SQL directly. I’m spoiled by the Django ORM (which has its idiosyncrasies and shortcomings), so I double checked the different kinds of JOINs and all went well.

I had to group rows by some properties, so it was a great time to use serapeum:assort. I left you an example here: https://dev.to/vindarel/common-lisps-group-by-is-serapeumassort-32ma

Dates have to be handled in different formats. I used local-time of course, and I still greatly appreciate its lispy formatter syntax:

(defun date-yymmddhhnnss (&optional date stream)
  (local-time:format-timestring stream
                                (or date (local-time:now))
                                :format
                                '((:year 4)
                                  (:month 2)
                                  (:day 2)
                                  (:hour 2)
                                  (:min 2)
                                  (:sec 2)
                                  )))

the 2 in (:month 2) is to ensure the month is written with 2 digits.

Once the file is written, I have to send it to a SFTP server, with the client’s codes.

I wrote a profile class to encapsulate the client’s data as well as some functions to read the credentials from either environment variables, the file system, or a lisp variable. I had a top-level profile object for ease of testing, but I made sure that my functions formatting or sending data required a profile parameter.

(defun send-stock (profile &key date) ...)
(defun write-stock (profile filename) ...)

Still nothing surprising, but it’s tempting to only use global parameters for a one-off script. Except the program grows and you pay the mess later.

SFTP

To send the result through SFTP, I had to make a choice. The SFTP command line doesn’t make it possible to give a password as argument (or via an environment variable, etc). So I use lftp (in Debian repositories) that allows to do that. In the end, we format a command like this:

lftp sftp://user:****@host  -e "CD I/; put local-file.name; bye"

You can format the command string and run it with uiop:run-program: no problem, but I took the opportunity to release another utility:

• https://github.com/vindarel/lftp-wrapper

First, you create a profile object. This one-liner reads the credentials from a lispy file:

(defvar profile (make-profile-from-plist (uiop:read-file-form "CREDS.lisp-expr"))

then you define the commands you’ll want to run:

(defvar command (put :cd "I/" :local-filename "data.csv"))
;; #<PUT cd: "I/", filename: "data.csv" {1007153883}>

and finally you call the run method on a profile and a command. Tada.

Deploying

Build a binary the classic way (it’s all on the Cookbook), send it to your server, run it.

(during a testing phase I have deployed “as a script”, from sources, which is a bit quicker to pull changes and try again on the server)

Set up a CRON job.

No Python virtual env to activate in the CRON environment...

Add command line arguments the easy way or with the library of your choice (I like Clingon).

Script n°2 and simple FTP

My script #2 at the time was similar and simpler. I extract the same products but only take their quantities, and I assemble lines like

EXTRACTION STOCK DU 11/04/2008
....978202019116600010000001387
....978270730656200040000000991

For this service, we have to send the file to a simple FTP server.

We have a pure Lisp library for FTP (and not SFTP) which works very well, cl-ftp.

It’s a typical example of an old library that didn’t receive any update in years and so that looks abandoned, that has seldom documentation but whose usage is easy to infer, and that does its job as requested.

For example we do this to send a file:

(ftp:with-ftp-connection (conn :hostname hostname
                                   :username username
                                   :password password
                                   :passive-ftp-p t)
      (ftp:store-file conn local-filename filename))

I left you notes about cl-ftp and my SFTP wrapper here:

• https://dev.to/vindarel/ftp-and-sftp-clients-for-common-lisp-1c3b

Scripts n°3 and n°1 - specialized web apps

A recent web app that I’m testing with a couple clients extends an existing stock management system.

This one also was done in order to avoid a Python monolith. I still needed additions in the Python main software, but this little app can be independent and grow on its own. The app maintains its state and communicates it with a REST API.

 

It gives a web interface to their clients (so my clients’ clients, but not all of them, only the institutional) so that they can:

• search for products
• add them in shopping carts
• validate the cart, which sends the data to the main software and notifies the owner, who will work on them.

The peculiarities of this app are that:

• there is no user login, we use unique URLs with UUIDs in the form: http://command.client.com/admin-E9DFOO82-R2D2-007/list?id=1
• I need a bit of file persistence but I didn’t want the rigidity of a database so I am using the clache library. Here also, not a great activity, but it works©. I persist lists and hash-tables. Now that the needs grow and the original scope doesn’t cut it any more, I wonder how long I’ll survive without a DB. Only for its short SQL queries VS lisp code to filter data.

I deploy a self-contained binary: code + html templates in the same binary (+ the implementation, the web server, the debugger...), with Systemd.

I wrote more on how to ship a standalone binary with templates and static assets with Djula templates here:

• https://lisp-journey.gitlab.io/blog/lisp-for-the-web-build-standalone-binaries-foreign-libraries-templates-static-assets/

I can connect to the running app with a Swank server to check and set parameters, which is super helpful and harmless.

It is possible to reload the whole app from within itself and I did it with no hiccups for a couple years, but it isn’t necessary the most reliable, easiest to set up and fastest method. You can do it, but nobody forces you to do this because you are running CL in production. You can use the industry’s boring and best practices too. Common Lisp doesn’t inforce a “big ball of mud” approach. Develop locally, use Git, use a CI, deploy a binary...

Every thing that I learned I documented it along the way in the Cookbook ;)

Another app that I’ll mention but about which I also wrote earlier is my first web app. This one is open-source. It still runs :)

 

In this project I had my friend and colleague contribute five lines of Lisp code to add a theme switcher in the backend that would help him do the frontend. He had never written a line of Lisp before. Of course, he did so by looking at my existing code to learn the existing functions at hand, and he could do it because the project was easy to install and run.

(defun get-template(template &optional (theme *theme*))
  "Loads template from the base templates directory or from the given theme templates directory if it exists."
  (if (and (str:non-blank-string-p theme)
           (probe-file (asdf:system-relative-pathname "abstock" (str:concat "src/templates/themes/" theme "/" template))))
      ;; then
      (str:concat "themes/" theme "/" template)
      ;; else :D
      template))

He had to annotate the if branches :] This passed the code review.

Lasting words

The 5th script/app is already on the way, and the next ones are awaiting that I open their .docx specification files. This one was a bit harder but the Lisp side was done sucessfully with the efficient collaboration of another freelance lisper (Kevin to not name him).

All those tasks (read a DB, transform data...) are very mundane.

They are everywhere. They don’t always need supercharged web framework or integrations.

You have plenty of opportunities to make yourself a favor, and use Common Lisp in the wild. Not counting the super-advanced domains where Lisp excels at ;)

---

Links

• https://lispcookbook.github.io/cl-cookbook/
• awesome-cl
• companies using Common Lisp in production (at least the ones we know)
• Common Lisp course in videos – it helps me, and you ;) I added 9 videos about CLOS last month, and more are coming. It’s 86 minutes of an efficient code-first approach, out of 7+ hours of total content in the course. After this chapter you know enough to read the sources of the Hunchentoot web server or of the Kandria game.

I have done some preliminary Common Lisp exploration prior to this course but had a lot of questions regarding practical use and development workflows. This course was amazing for this! I learned a lot of useful techniques for actually writing the code in Emacs, as well as conversational explanations of concepts that had previously confused me in text-heavy resources. Please keep up the good work and continue with this line of topics, it is well worth the price! [Preston, October of 2024]

A comment on my previous post said,

The most difficult thing when coming to a different language is to leave the other language behind. The kind of friction experienced here is common when transliterating ideas from one language to another. Go (in this case) is telling you it just doesn't like to work like this.

Try writing simple Go, instead of reaching for Lisp idioms. Then find the ways that work for Go to express the concepts you find.

That's not at all how I approach programming.

A friend of mine once paid me a high compliment. He said, “Even your C code looks like Lisp.”

When I write code, I don't think in terms of the language I'm using, I think in terms of the problem I'm solving. I'm a mostly functional programmer, so I like to think in terms of functions and abstractions. I mostly reason about my code informally, but I draw upon the formal framework of Lambda Calculus. Lambda Calculus is a simple, but powerful (and universal) model of computation.

Programming therefore becomes a matter of expressing the solution to a problem with the syntax and idioms of the language I'm using. Lisp was inspired by Lambda Calculus, so there is little friction in expressing computations in Lisp. Lisp is extensible and customizable, so I can add new syntax and idioms as desired.

Other languages are less accommodating. Some computations are not easily expressable in the syntax of the language, or the semantics of the language are quirky and inconsistent. Essentially, every general purpose fourth generation programming language can be viewed as a poorly-specified, half-assed, incomplete, bug-ridden implementation of half of Common Lisp. The friction comes from working around the limitations of the language.

 .

 

I am always happiest when a story of mine comes into print. Today, I have the joy of introducing you to "Unquiet Graves," a seasonal tale of graveyard misbehavior and betrayal. Oh, and there's nothing supernatural about it at all.

You can read the story here. But if you're like me, you'll just go to Clarkesworld, look over the table of contents, and decide which story you want to read first. Mine by preference, but follow your whim.

 

And for those who like trivia . . .

I came up with the handheld's app many long years ago and it took forever to come up with a story for it. You'll notice that it is left unnamed in the story. That's because its secret name was "The Graveyard Reader." Which is the title of a well-known story by Theodore Sturgeon.  While I was writing the story, I thought of it as "The New Graveyard Reader." But Sturgeon's story and mine go off in totally different directions, and giving mine (or even the app) a title suggesting there was some implicit connection between the two would only cause confusion.

The title I finally came up with was derived from "The Unquiet Grave" by that most prolific of all poets, Anonymous. If you look it up, I suggest you do so after reading my story. It gives away some of the plot.

*

 

.

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.

*

Estonia 039 s National Animal



View Comic!

1. Chennai doctor stabbed by assilants posing as patients  The Times of India
2. Chennai Doctor Stabbed 7 Times By Son Of Woman Who Had Cancer  NDTV
3. Doctor stabbed by patient’s attendant at Kalaignar Centenary Super Speciality Hospital in Chennai  The Hindu
4. Patient's son stabs doctor 7 times in Chennai hospital, arrested  India Today
5. Doctor stabbed multiple times in Tamil Nadu government hospital by patient’s relative  Deccan Herald

Full Article