![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
I've realized that I've never really told people about my job since starting it (and the frequency of my journal entries has gone down a lot as well), so as it's lunchtime I thought I'd explain a bit more about what's happening just now.
I'm working with a company that writes content management systems for other companies (online document stores and that kind of thing). Their list of past clients has been pretty impressive, and at the moment, they're putting together a version of their software for Marathon, an oil pipeline company.
What I've been doing is writing a plugin for XMLSpy, an piece of software for writing XML files, so that the program can connect to the company's online service and retrieve, save and check documents. To do this, I've been working on almost completely undocumented code on Visual Studio (an IDE that I'd never used before) in C# (a language that I'd never seen before), but ignoring the obvious difficulties I've been enjoying it so far.
My daily routine mostly consists of going into JIRA, a bug-tracking system that the company uses, and looking through a list of current issues, suggestions for new features, and so on, then selecting one that I like the look of and starting work on it. Once an issue's been dealt with, it's marked as fixed and I move on. Periodically, a test is done of the plugin and the fixed issues are either marked as confirmed fixed or still not working, and the whole cycle goes on.
In fact, I've been so impressed by this system (and because I'm undeniably broken in the head) that I've developed a strange compulsion to write my own basic copycat version of it for my next project - it would have come in handy for the testing of Special Agent last week (it'll be released this weekend, by the way). I think other people in the Click community will find it pretty useful as well, as otherwise releasing a game is a process of putting it out and continually updating it when people suddenly find all the catastrophic bugs that you've missed.
I'm working with a company that writes content management systems for other companies (online document stores and that kind of thing). Their list of past clients has been pretty impressive, and at the moment, they're putting together a version of their software for Marathon, an oil pipeline company.
What I've been doing is writing a plugin for XMLSpy, an piece of software for writing XML files, so that the program can connect to the company's online service and retrieve, save and check documents. To do this, I've been working on almost completely undocumented code on Visual Studio (an IDE that I'd never used before) in C# (a language that I'd never seen before), but ignoring the obvious difficulties I've been enjoying it so far.
My daily routine mostly consists of going into JIRA, a bug-tracking system that the company uses, and looking through a list of current issues, suggestions for new features, and so on, then selecting one that I like the look of and starting work on it. Once an issue's been dealt with, it's marked as fixed and I move on. Periodically, a test is done of the plugin and the fixed issues are either marked as confirmed fixed or still not working, and the whole cycle goes on.
In fact, I've been so impressed by this system (and because I'm undeniably broken in the head) that I've developed a strange compulsion to write my own basic copycat version of it for my next project - it would have come in handy for the testing of Special Agent last week (it'll be released this weekend, by the way). I think other people in the Click community will find it pretty useful as well, as otherwise releasing a game is a process of putting it out and continually updating it when people suddenly find all the catastrophic bugs that you've missed.
