home again home again...
May. 23rd, 2025 07:10 pm![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
tielanGoing home today!
Seriously, I like travel, but not when work comes on top of it. Although being away from Sydney for the last two weeks has been good - the rain that is flooding northern NSW is also raining down in Sydney, albeit not as hard.
May need to check up in the roof cavity tomorrow to get an idea of how it's going up there. Might need to do a bunnings trip first for some decent lighting.
(ps. It's been raining pretty hard in Sydney the last couple of weeks. We're due for a few days' break shortly, just as I get back, hopefully enough to get the garden sorted out)
--
Last day on client site in Melbourne. Next week we're being included on the meetings (theoretically) and told about the issues that arise. And so begins the battle for (office) supremacy…
(ugh. I ate too much breakfast too fast and now I am having regret. Or indigestion. *burp*)
One of the issues in any translation from development to support is starting to recognise the issues that are arising and which ones are going to be perennial problem. There's also the manner in which we take on those issues.
I am a "we'll take it as it comes" kind of person.
My colleague (who is the team lead in this instance) is a "prepare for everything" kind of person.
So we are doing a lot of work to map everything out, determine what is going on, identify where things are happening, and look at possible solutions for issues that are not yet happening, but which might.
I personally tend to think that's a waste of time, but I am perhaps a little bit like the guy whose roof never leaks when it doesn't rain. Also, a lot of guys on the tech monitoring side tend to want pages and pages of directions. (Pages and pages of directions sends me to sleep.)
I'd rather dig out the issue myself than be fed what someone else thinks it is. Of course, that isn't how most support guys tend to think of it. And the up-tops really hate the "trust the techs, they know how to fix it" - which, granted, they often would find that maybe the techs in question don't know how to fix it as knowledge is lost between one support group to the next.
Next week, the processing of handing over the reins is supposed to begin. Whether it does, how much of it actually is given to us, and how we handle it? That's another question. I kind of miss the days of my last client, where if there was a problem, I would mostly fix it on my own cognisance. Then again, the system of the last client was set up to expect issues like this and things which might fall through. This client is a lot more insistent that every little issue be logged. I'm bad at that...
Oh well, colleague is on top of that at least. I guess I'm going to have to get up to speed on what's required to do this, that, and the other…
Seriously, I like travel, but not when work comes on top of it. Although being away from Sydney for the last two weeks has been good - the rain that is flooding northern NSW is also raining down in Sydney, albeit not as hard.
May need to check up in the roof cavity tomorrow to get an idea of how it's going up there. Might need to do a bunnings trip first for some decent lighting.
(ps. It's been raining pretty hard in Sydney the last couple of weeks. We're due for a few days' break shortly, just as I get back, hopefully enough to get the garden sorted out)
--
Last day on client site in Melbourne. Next week we're being included on the meetings (theoretically) and told about the issues that arise. And so begins the battle for (office) supremacy…
(ugh. I ate too much breakfast too fast and now I am having regret. Or indigestion. *burp*)
One of the issues in any translation from development to support is starting to recognise the issues that are arising and which ones are going to be perennial problem. There's also the manner in which we take on those issues.
I am a "we'll take it as it comes" kind of person.
My colleague (who is the team lead in this instance) is a "prepare for everything" kind of person.
So we are doing a lot of work to map everything out, determine what is going on, identify where things are happening, and look at possible solutions for issues that are not yet happening, but which might.
I personally tend to think that's a waste of time, but I am perhaps a little bit like the guy whose roof never leaks when it doesn't rain. Also, a lot of guys on the tech monitoring side tend to want pages and pages of directions. (Pages and pages of directions sends me to sleep.)
I'd rather dig out the issue myself than be fed what someone else thinks it is. Of course, that isn't how most support guys tend to think of it. And the up-tops really hate the "trust the techs, they know how to fix it" - which, granted, they often would find that maybe the techs in question don't know how to fix it as knowledge is lost between one support group to the next.
Next week, the processing of handing over the reins is supposed to begin. Whether it does, how much of it actually is given to us, and how we handle it? That's another question. I kind of miss the days of my last client, where if there was a problem, I would mostly fix it on my own cognisance. Then again, the system of the last client was set up to expect issues like this and things which might fall through. This client is a lot more insistent that every little issue be logged. I'm bad at that...
Oh well, colleague is on top of that at least. I guess I'm going to have to get up to speed on what's required to do this, that, and the other…
