I have recently joined a new company, and I know there has been a few issues with trust and time wasting. But just as much of my time is wasted.by being locked off certain things. As the systems administrator, I need access to about everything. I wasted a shed load today by not being able to get hold of certain downloads because torrents are evil.
No torrents are not evil, illegal file sharing is.
An exposition into the workings behind the mysteries of communication systems
Monday, 26 September 2011
Wasting Time
Wednesday, 21 September 2011
Working with colleagues
Communicate with your colleagues, use simple clear instructions and sentencing. Waffle and indeterminate expression may save some feelings, but it does not help. This is business get things fixed, make the time for socialization over coffee at other times.
Use sensible limestone of communications. Email is not suited to discussion. If you are giving multiple people information or instructions, but require for everyone to know what is going on, make sure each person knows the bits they are responsible for.
Never email some who sits next to you for a rant, if you have some issues. Either talk or if you are unble to talk instant message.
If you are under strain, ask for help, sensible help, make clear what you need, and thank them afterwards. Keep and amend those instructions for next time.
As an admin your job is a bunch of procedures, that hopefully you can put onto a junior. Find those procedures, get someone else to do them, then find a quiet corner to drink your coffee or play with something fun.
Tuesday, 13 September 2011
Making things complex
System complexity has little to do with the nuts and bolts of an application.
Take for instance the use of the modern car. You can literally have a start/stop button, the steering wheel and the gas and brake pedals and no other control is necessary to rum the car. Gear changing, lights, wipers are all automatic in higher end cars.
So the fact there maybe 10th individual software apps underneath mean nothing to most administrators of a system. If it has a simple operation and a sensible setup then the system is not complex.
Which brings me to my second point. The last thing you need to care about with a system is wondering if you are on the right one. A half broken system is worse than a broken one. Trying to work around "features" is so annoying I would rather not use it at all. Even worse is working around self induced issues.
Maintain what you have more than work on new systems you have, and stand on your principles if those that be tell you to do otherwise.
And thus ends today's lesson
Monday, 12 September 2011
New job again
Some respect, a comfortable working environment (I.e somewhere they can keep toilet roll in stock), and a job that you actually get to do and some acknowledgment of a good job.
Now I am not talking constant reminders of what good little engineers we are, but when we pull it out the bag at the last minute, a "thank you" would be nice.
The previous place I was at, we were finally offered to be taken out as a thank-you for a real big ask of our skills. Two months later I left. No meal. Apparently still no meal talking to those left behind.
So the lesson is think of your minions, they give what you put in.
More updates to come, I commute on public transport so more time to blog.
Wednesday, 10 August 2011
Planning ahead
So as providers of communications, things need to work. They need to be understood, and provide rock solid services.
As such changes, new products, and management requires planning and time. It is not the sort of thing you hash in at the last minute. I believe most customers would prefer a stable working, well supported and understood product.
How frustrating is it when you buy a service and it either doesn't do what it says (or actually not quite in yet but in the pipeline) or stops doing what it did, and then you have to wait for a seemingly uncaring support team to fix the issue.
In defence of the support team, there is probably nothing they can do, it has possibly been passed onto an overworked engineering team, or another third party.
So think again when you design a solution. Is it ready for release, do you understand what is actually wanted. Do not release something before it is ready. Ensure it is supportable.
Monday, 18 April 2011
Pot calling kettle
"Parent company, Microsoft, claims that Google has used its dominant position to limit rivals' products."
Not like Microsoft has ever done anything like this.
I can't decide whether this is due to Microsoft's fear of Google, or their complete lack of any morales in search of the almighty dollar/pound/yen/etc
Wednesday, 23 March 2011
Someone having a rant, other than me
The fact that the crematorium is next door (also sign posted), and accessed by a different entrance, is not our fault. We regularly get a few confused and slightly upset visitors.
But today we had a first. An irate mourner complaining to US that the crematorium is not well enough sign posted and it's not good enough (slamming the door on the way out).
Everyone has always been courteous, understanding the that person is possibly a little upset already. However, this slightly angered us and in some way amused us.
The main moral of this is one of general civility. Using abusive and threatening speech to someone who is unrelated to the issue you are complaining about is hardly going to endear them to helping you. If we had not already told them where to find the crematorium I would have given her false directions.