![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
It's been one of those days around here.
I tagged along with Galina yesterday to Natalie's house, to help out with some of the myriad tasks that must be done if you expect to find a renter in something less than a geological time frame. I took my backup computer with me, but still managed to miss an assignment that was not exactly a rush, but one I was asked about again after a little while.
Galina went again this morning, but this time without me, so that I could devote myself to some work around the house (cutting grass, trimming it, gathering up the clippings... we sure do spend a lot of time preening our St. Augustine!) and to take care of work left over from this past week.
In between everything else, I felt I had to address the deficiencies of the default feature offered by org mode to create "busy" invoices—which I define as any invoice that's going to run over a page because of the detail that's involved, either because of the complexity of an assignment or the number of assignments being invoiced at one time.
It finally dawned on me that I was going to have to write some LISP code to address the issue, and so I did. After overcoming a few issues, of course, associated with having forgotten most of my LISP. But in the end, I got the result I wanted and now, I'm loaded for bear for next month.
And just to prove it was no fluke, I wrote more code that goes through my list of projects and outputs relevant information only about those that have not been invoiced yet. This information, as it turns out, is exactly what is required to know the ever-lovin' "State of the Plate" (as in, "what do I have on my plate at the moment?"). This is more than just something that's nice to have for myself, as I have a client who, from time to time, sends me multiple jobs with multiple documents in each job, and once I've logged in all of the new work, running this code will create a nice chunk of text I can send back to the client so that we are both on the same page, as far as what has to be done is concerned.
I never was a hard-core LISP programmer, but it seemed a lot easier, these past two days, to come up with suitable Emacs LISP code for my immediate needs than it did way back when I wrote mostly in C and wrote LISP code here and there, on the side, while skittering about the periphery of a huge expert system written in Common LISP.
Cheers...
I tagged along with Galina yesterday to Natalie's house, to help out with some of the myriad tasks that must be done if you expect to find a renter in something less than a geological time frame. I took my backup computer with me, but still managed to miss an assignment that was not exactly a rush, but one I was asked about again after a little while.
Galina went again this morning, but this time without me, so that I could devote myself to some work around the house (cutting grass, trimming it, gathering up the clippings... we sure do spend a lot of time preening our St. Augustine!) and to take care of work left over from this past week.
In between everything else, I felt I had to address the deficiencies of the default feature offered by org mode to create "busy" invoices—which I define as any invoice that's going to run over a page because of the detail that's involved, either because of the complexity of an assignment or the number of assignments being invoiced at one time.
It finally dawned on me that I was going to have to write some LISP code to address the issue, and so I did. After overcoming a few issues, of course, associated with having forgotten most of my LISP. But in the end, I got the result I wanted and now, I'm loaded for bear for next month.
And just to prove it was no fluke, I wrote more code that goes through my list of projects and outputs relevant information only about those that have not been invoiced yet. This information, as it turns out, is exactly what is required to know the ever-lovin' "State of the Plate" (as in, "what do I have on my plate at the moment?"). This is more than just something that's nice to have for myself, as I have a client who, from time to time, sends me multiple jobs with multiple documents in each job, and once I've logged in all of the new work, running this code will create a nice chunk of text I can send back to the client so that we are both on the same page, as far as what has to be done is concerned.
I never was a hard-core LISP programmer, but it seemed a lot easier, these past two days, to come up with suitable Emacs LISP code for my immediate needs than it did way back when I wrote mostly in C and wrote LISP code here and there, on the side, while skittering about the periphery of a huge expert system written in Common LISP.
Cheers...
