Links: Tom Edelson's home page; Tom Edelson's LiveJournal
This is about my work with computers: primarily, as a software developer. In particular, it introduces you to the projects I've done since mid-2006, when I retired from my last regular job, as a developer with SAS Institute. During that time, so far, I haven't been working for money, though I am not averse to doing so.
The first thing I did was a backup and archiving utility, written in Perl. It creates a Zip archive, using a control file to determine what should be included. It can do incremental backups as well as full ones.
I use this utility almost every day, but I don't have definite plans to release it publicly. However, if it sounds like something that you might find useful (and especially if, in addition, you are a Macintosh user), then let me know that; if some people do, it will greatly improve the likelihood of an official release.
See the "Contact Information" section, below, for how to get in touch with me. If you write about the backup utility, let me know if you'd be willing to try it before the official release, that is, to be a "Beta tester".
Except for the backup utility, all of my completed programming projects, since I retired, have had to do with personal financial software. Also, all of them have been for the Java Runtime Environment, though not all of them have been written in Java.
I haven't created a new personal finance program; each project has added value, in a different way, to one (or, in one case, both) of two existing programs in this category. These two programs are:
Moneydance: a commercial program, not open-source; but it does have a published API (Application Program Interface) which allows one to write extensions for it.
Each of these applications is written in Java, and each uses Swing to create the GUI (Graphical User Interface) which it presents to the user.
I have used both jGnash and Moneydance: mostly at different times, but sometimes, both of them in parallel for a month or more. I like them both; I really couldn't call either one "better" across the board. I prefer the user interface of jGnash, when doing data entry; Moneydance is more complete in features for getting data back out, such as searching and reports.
My work on personal finance software, to date, falls into three categories:
direct contributions to jGnash;
the "Security Price Entry" extension to Moneydance; and
code which produces an "Asset Allocation Report", which works with both jGnash and Moneydance.
I have written Java code that has become part of the jGnash application. Most of it is bug fixes ... especially, making things work on Mac OS X which previously didn't, though they did work on Windows and Linux.
Another niche role I have in relation to jGnash: around the time that jGnash 2.0 came out, I became the "maintainer" of the jGnash 1.x series of releases. That is, I add bug fixes, and the occasional small enhancement, for the benefit of those who need to, or for special reasons prefer to, continue using jGnash 1 rather than migrating to jGnash 2. jGnash 1.12.0 was the first such "maintenance release", and jGnash 1.13.0, the most recent, was released on January 17, 2011.
For more information on the ongoing maintenance of jGnash 1, including reasons why one might have occasion still to use it, see the page in the jGnash Wiki titled JGnash 1.x Lives! (And Why).
Also, you can download any of the jGnash 1 releases, including the two of them released after jGnash 2.0, from this page at SourceForge.
I have a few mutual funds, and so I track the changes in their prices within my personal finance program. I am accustomed to entering the closing price of each security I own as of the end of each month, information I receive on the monthly statement from the broker.
In Moneydance, I found this cumbersome: I had to type the "as-of date" (the last day of the statement month) over again for each security. (I haven't tried Moneydance 2010 yet; perhaps this has been changed in this release.)
So I took advantage of the "Moneydance API": that is, of the published information that allows the creation of a "Moneydance extension" in Java. My extension is called "Security Price Entry", and I believe that it makes this particular task much less repetitive.
This Moneydance extension has not been officially "released" (though I do intend to do so). But some users have tried it. For more information on it, see the page titled Moneydance Extension: Security Price Entry, here on my site at The Well.
If you, also, would like to try out this Moneydance extension, without waiting for its official release, then please send me an email. Specifics about contacting me are in the "Contact Information" section.
If you are an investor, you are likely to be familiar with the concept of "asset allocation". This means, roughly, that you want to be aware of what proportion of your assets is invested in ("allocated to") the various classes of investments, such as stocks and bonds. One reason why it's deemed valuable to know this is that there are rules of thumb about what this proportional allocation should be. One of the simplest of these rules of thumb is that in general, the proportion invested in stocks should go down as you get older.
Since this is pretty much received wisdom among investors, I was surprised that I could not readily find software tools for calculating what one's current asset allocation is. Or at least, in my judgment, not good ones. For example, I've never come across one which could deal with the fact that some mutual funds hold both stocks and bonds.
So I wrote one. From my perspective, one would expect that there would be other investors out there who are serious enough about asset allocation that they would want to use this software.
Unlike my other contributions to financial software, my asset allocation report module is not written in Java (though it is written for the Java Runtime Environment). It's written in SISC, an implementation of the Scheme programming language which is itself, in turn, written in Java.
My Asset Allocation Report code has not been "released", that is, there is currently no URL from which you can download it. Before creating one, I would like first to find out if anyone is interested.
Investors might be interested in this software as potential "end users". Programmers (particularly Scheme programmers) might be interested in looking at it because of some of the techniques it uses, such as one that I call the "zombie application technique".
To learn more about my Asset Allocation Report software, start with the introductory document about it. That will then give you the option of following an "information for [potential] end users" path, or one that is directed at programmers. I have tried to be even-handed: in particular, to describe reasons why an end user might not want to try this software (or at least, not until it is made easier to use), as well as the features which I think are likely to be attractive to investors.
After looking over the relevant information about this report software, if you do find that you have some interest in it, it is important that you let me know. That's because not only have I not released it yet; (unlike the case with the Security Price Entry module) I have not committed myself to releasing it. Unless at least a few people do express an interest, it probably won't happen.
The above project descriptions have mentioned some circumstances in
which you might want to contact me by email, so here's how to do it.
In the (possibly vain) hope of foiling spammers, I will give you my
address in a round-about way: take the user name
edelsont", and the domain name
well.com", and put one of those "at-sign"
thingies (the symbol "
@") between them.
This page created: 2010-08-20
This page last modified: 2017-08-09
© Copyright 2017 by Tom Edelson.