![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
*DEFINE Class
Jan. 9th, 2013 08:28 pmI've decided that after I run out of degree audit jobs, I'll try for other UT jobs, including temp jobs. One of my old co-workers told me that if I were interested in temp jobs, I should look into accounting, because they always have trouble finding accounting temps, by which I think she really means bookkeeping temps. I saw such an opening, and no sort of accounting degree was required, only experience in *DEFINE, UT's mainframe program for doing accounting work.
A couple of days ago, I noticed that a class in "Introduction to *DEFINE" was being offered today, so I signed up and attended.
I didn't learn much, partly because I am already quite familiar with how UT's mainframe systems work. And they didn't go into how to actually do any of the work, but just how to navigate to the different screens, how the system is organized, and how the authorizations are organized (all at least somewhat new to me). I also got to learn a few short cuts and things to be careful about--the sorts of things that normally you learn the hard way if you're stuck with the jump-in-and-swim method of training, so that was nice.
And the instructor mainly used the travel voucher form for his examples because filling in that form is a common duty for people who have to learn how to use *DEFINE. (This is needed when employees need to get reimbursed for their travel expenses.) Robin says his employer has a full-time person to do this just so their real accountant can do all the other work. So that gives me an idea of where to go next.
I also saw a course called "Introduction to Accounting at UT," taught by someone I actually know (though not currently on the list of offerings). That instructor told me there is an online video version of that course available, and looking for that, I found a whole page of useful resources.
And doing all these things has not totally turned me off the idea. The job looks a bit boring, with a frustrating learning curve for new people who don't get mainframe stuff but an easy learning curve for me, and involving mostly data rather than mostly people, so I might like it just fine.
So, I have a Plan B. And it might even be realistic. In the past, I have mostly only gotten jobs with employers who were so desperate they were willing to hire someone they didn't know who had not already done the exact job before. And this might be just that sort of job.
A couple of days ago, I noticed that a class in "Introduction to *DEFINE" was being offered today, so I signed up and attended.
I didn't learn much, partly because I am already quite familiar with how UT's mainframe systems work. And they didn't go into how to actually do any of the work, but just how to navigate to the different screens, how the system is organized, and how the authorizations are organized (all at least somewhat new to me). I also got to learn a few short cuts and things to be careful about--the sorts of things that normally you learn the hard way if you're stuck with the jump-in-and-swim method of training, so that was nice.
And the instructor mainly used the travel voucher form for his examples because filling in that form is a common duty for people who have to learn how to use *DEFINE. (This is needed when employees need to get reimbursed for their travel expenses.) Robin says his employer has a full-time person to do this just so their real accountant can do all the other work. So that gives me an idea of where to go next.
I also saw a course called "Introduction to Accounting at UT," taught by someone I actually know (though not currently on the list of offerings). That instructor told me there is an online video version of that course available, and looking for that, I found a whole page of useful resources.
And doing all these things has not totally turned me off the idea. The job looks a bit boring, with a frustrating learning curve for new people who don't get mainframe stuff but an easy learning curve for me, and involving mostly data rather than mostly people, so I might like it just fine.
So, I have a Plan B. And it might even be realistic. In the past, I have mostly only gotten jobs with employers who were so desperate they were willing to hire someone they didn't know who had not already done the exact job before. And this might be just that sort of job.