Winter Fundraiser 2014, Day Three
Our focus during this week’s fundraiser is on “odd jobs”: how Dymphna and I came to take this particular odd job, and all the other odd jobs we’ve had to take over the years to keep going.
The unusual thing about this particular job is its distributed paymasters. We don’t have one boss; we have hundreds of them. By holding these quarterly blegs, we’ve crowdsourced our income — a most peculiar situation. That’s what makes this the oddest job of all.
The crowdfunding process gets a bit tricky when we need a raise, which is the position we find ourselves in this quarter. As I mentioned on Monday morning, the costs of keeping this blog going rose substantially after DoS attacks and increased traffic forced us into a more robust type of hosting. This is a not unexpected consequence of prominent Counterjihad activism, but still, it makes for a financially anxious lifestyle.
The first two days of the fundraiser are evidence that our readers paid attention to our need for a raise. The response has been swift and generous, and we are grateful to all of you, the issuers of our paychecks.
As I mentioned in the first post of this series, by the time I left college I had decided to become an artist. I tried it for a year after I graduated, and failed miserably. Not at painting — I painted some pretty good pictures during those months — but at making enough money to stay alive. I remember buying A&P Tudor Premium beer at $2 a sixpack; that’s how desperate I was. I used to say that after the first two or three, you didn’t care how it tasted.
So the following summer I moved back in with my parents and got a job. Two of them, actually: driving a taxi (during the daytime) and working as a sales clerk in a tuxedo rental store (in the evenings). Those jobs were a temporary holding pattern until I landed a position in my field of expertise, which was mathematics. That fall I took a job as a mathematician/programmer at the VA hospital in Washington D.C.
I’d only had a two-hour course in computer programming when I was in college, but that was enough to get me the job. Those were the early days of the computer boom, and the demand for programmers was fierce. A bachelor’s degree in Math and a working knowledge of FORTRAN was all that was needed to find a good job in the field.
I spent the next five years programming in FORTRAN on CDC and IBM mainframes, changing jobs halfway through to move into the private sector and take a position as a systems analyst downtown on Lobbyists’ Row. But I never intended to make a career of it; I was just marking time until I could get back out into the sunshine and start painting again.
When I saved up enough money I quit my job, abandoned the glitzy life, and moved as far away from D.C. as I could get. I wound up in Central Virginia because this area has the lowest cost of living — and hence the cheapest rents — in the state. I was able to rent an entire two-bedroom house for $95 a month. Well, it was kind of two-bedroom — one of those rooms was really just for the space heater in back. But the house had indoor plumbing, a woodstove, and a tin roof. What more could a starving artist want?
I was hoping to last five years, if I was lucky. I managed twenty-five. All those years were good ones, and I’d make the same choice again if I had it to do over.
A year after I moved to the country I met Dymphna, and she moved down here when we got married. We still live in the same house all these years later — although it has been greatly augmented in the interim: we bought it from our landlord and slowly fixed it up over the years. After the future Baron was born, we converted the back porch into another bedroom. Some years later, when Dymphna’s mother became terminally ill with Parkinson’s disease, we had a two-story addition built onto the back so that she could live comfortably in the downstairs, while the fB moved into the huge upstairs room. That’s the same room I’m typing these words in right now — an incredibly cluttered office-cum-attic.
A lot of other stuff happened, too, during those years. But all those stories will have to wait.
I never really quit programming, not for any length of time. In the early ’80s I moved into microcomputers, starting with the Kaypro and the Osborne I, then later the IBM XT and AT, and eventually all the various “clones” that became the PC universe. My primary language was BASIC, beginning with MBASIC on that Osborne (and a little Atari Basic, when building entertainment apps for the fB).
Interpreted Basic gave way to a compiled version of Basic called QuickBASIC, a Microsoft product from before Windows was launched. Later, under Windows, there was Visual Basic, and then VBA for MSOffice applications, along with SQL, SQL Server, HTML, XML, and various other odds and ends of programming arcana. I was laid off in 2006 just before the office converted to .NET, so I never picked up the next level in the sequence.
Programming jobs were what paid well, and they made a lot of difference during the hard times. We had seven fat years when I worked full-time in a senior analyst position, but the other twenty-some have been pretty lean, generally speaking.
It was in those lean years that I took the most interesting and bizarre jobs — in addition to contract programming, of course — in order to get by. I’ll describe some of those in future posts.
On the second day of this week’s fundraiser, our very generous donors chipped in from the following places:
Stateside: California, Colorado, Florida, Illinois, Michigan, New York, Oregon, and Washington
Near Abroad: Canada
Far Abroad: Australia, France, Israel, the Netherlands, Slovenia, and the UK
Our deepest gratitude goes out to all of you for stepping up when we most needed it.
The tip jar in the text above is just for decoration. To donate, click the tin cup on our sidebar, or the donate button, on the main page. If you prefer a monthly subscription, click the “subscribe” button.
I’m not sure this is the “next level in the sequence”, but have you tried Java, using Eclipse as the IDE? After a career#1 as a chemist using Fortran, to career#2 as a programmer using COBOL on the mainframe and PC, my last 3 years before retiring, I was forced into learning Java, using Eclipse. The big hurdle was learning to think in object-oriented terms. But now in retirement both Java and Eclipse are free, and there’s a huge amount of help, tutorials, examples, libraries, etc. available on the web. Any question you have — someone has already asked it, and there are 4 or 5 solutions, from naive to sophisticated, probably to occasionally erroneous. But maybe you’ve already been there and done that.
Actually, after I got laid off in 2006 I took on a series of contracts using Java and Eclipse. I learned to use Java, but I never became fond of it.
I have nearly 20 years of experience in object-oriented languages, mainly VB and its derivatives, so that’s no issue. But for someone as old as I am (and with eyes as bad as mine), picking up a new fourth-generation language that is structured so differently is a difficult task. Java is very powerful and effective, but also a pain in the butt to deal with.
I don’t learn any language just for the heck of it, anyway. I’m not interested in them for their own sake, just when they’re required for a job. That’s how I picked up Basic, VB, SQL, XML, HTML, .asp, etc. — they were needed for various jobs.
Over fifteen years, I got so good at manipulating MSOffice objects and automating from one application to another with VBA, that I made that my specialty. That’s how I maintain the constellation of databases and Word objects that comprise what I call my “Auxiliary Brain” — the automated processes that make Gates of Vienna doable with only one person doing most of the work.
But MSOffice and VBA are archaic now, what with .NET and the supremacy of the Cloud. There is still some demand for my skillset, but not like there was fifteen years ago.
And I’m an old dog now — no new tricks for me.
An old dog maybe, but as long as you can still bite…
Good heavens, Baron and Dymphna, where do you get these fantastic pics?…oil workers drenched in the oil of their success; an ice truck (it was red letter day when my grandmother switched from an “icebox” to a refrigerator; what looks like a trio of competitors of Edison and Bell. Please, may we have a speakeasy?
I’m an adept at digging out period photos and illustrations using Google image search. It’s one of my favorite activities.
My precise algorithms for choosing search terms remain a trade secret.
Just imagine the JCL stream needed to execute this site in COBOL…..
My programming days started on a 3165 running OS VS2 in 12 MB. during the days of Diffs and Doffs, mids and mods!
IMS rules OK!
The Osborne I had 64k of RAM. The MBASIC interpreter took up half of that. Everything else had to be crammed into the remainder. The operating system was CP/M, which I have totally forgotten (although I’m still fairly good at MSDOS).
I remember when the new model Osborne came out with 128k, and it seemed like such a luxury. And then the XT, with its unbelievable 10MB of hard drive space!
Yea – Bank switching, 2 x 32k banks on a z80 machine….
I had to write code on early IBM PC’s too, rom basic and x86 assembler (on a 3270 ‘irma’ card).
We used to have to force “garbage collection” in the string heap when performance slowed down.
I remember when programs sometimes crashed with a message “string heap corrupt”. It reminded me of an Indian chief giving me a stern lecture about my twine…
All right, guys. This is starting to sound a whole lot like the conversations around our table at many a Thanksgiving dinner. Back then, the air was blue with jargon and techie argot.
But even now the lurking liberal rilly rilly cutting-edge programmers in Lotus Land are ROTFLTAO at you stone-cutters with your dulled adzes. They are holding their sides, gasping for air through their spluttering laughter, and pointing…
…heh…just wait until they, in their inevitable turn, creep to the rocking chair and nod off after dinner…