Category: Tales from work

It was that time of the year and everyone got an annual review whether they liked it or not. Vladimir felt this was not going to be time productively spent as Finley who may be a nice guy really didn’t understand IT and that can be a problem if you are leading an IT group.

There had been a number of misunderstandings and downright blunders on Finley’s part but today he was focusing on Vlad. Of all his goals for the following year two stood out. The first was that the team morale had been very low since Finley joined the group and so he wanted Vlad to improve it. The other interesting goal was for Vladimir to hand over his role of leading the interface group to another colleague. This goal wouldn’t be so ridiculous except that the recipient of the task will be taking paternity leave for three months, followed by extended paternity leave for another six months.

All of this was going to to take place in about 5 weeks so by definition this was a goal that either could not be done or could only be done in the most superficial way possible. The final goal was the improvement of Vlad’s communication skills. Finley wanted to give him a zero points on a scale of 1 of 5, but had to change to one point as that was all that the HR form would support.

In addition there was one more task that he wanted to be achieved by the end of the year. As previously mentioned, the team morale was quite low and so Finley wanted that one of Vladimir’s goals for the year would be to improve the team morale.

Finley’s ideas of what a successful review looked like was very different from Vlad’s, the rest of the team and the company standard. In the end, Vlad gathered some feedback from other managers and vendors and it was brought up to the workers council. The workers council were quite aware of Finley’s reputation due to previous run in’s with him and company policies. Thus due to this particular review a new page was added to Finley’s company file.

Finley was the “new sheriff” in town. He was now in charge of Arthur’s group starting on October 1^st. Finley had a rather odd management style and because he was only in charge of the group for two months Arthur asked that his old team leader be included in this year end review as well. It actually was not a terribly unusual request everything considered and so Arthur told Finley that would be fine. Imagine Arthur’s surprise when the meeting invite came only for the two of them.

Finley explained that he had contacted Arthur’s old boss who said that he would refuse to take part in the review. Arthur’s experiences with the new team leader were pretty rocky so he was very skeptical to hear his old team leader would not take part. This was especially true as his old team leader was an old friend of his who had promised him personally he would take part.

Finley “don’t you trust me”

Arthur (thinking not really)

It was because of this specific example not to mention a few other events with the new team leader that caused Carrie to refuse to have her yearly review without a representative from the workers council.

I had a meeting with Vladimir, Ivan, and Zachary. I got there a bit late but I was there to discuss problem ticket 233609. It apparently all comes down to what is basically “dickish” behavior between the support group and IT (er us). They created a ticket 233609 on Mar 18th, and are unhappy that it has taken forever for us to respond/fix it.

Well, as usual the problem is clear to me but in general not clearly described at all, other than “grunt grunt, problem, grunt fix it”. Due to the dysfunctional communications as well as political games between teams this was the best that they could do. I had to write into this ticket what I thought was the problem. I had to do this as Zach is not officially here working on anything except for project Galactica. I entered my solution on this issue as well as two possible solutions based on the problem description.

The second thing I put into the ticket was that one of the three software packages given to us was really only two of them were ours, the third was Bjoern’s package. Well, that makes it the support group’s package or actually the package of Katherine¹ who wrote up the problem ticket in the first place.

We would have responded earlier to this ticket but as it turns out the group that created it, which also happens to be the support group, failed to mark the ticket so it would show up in our view. Thus we really didn’t know about the ticket until they complained about it and we had a problem number to search for.

1Katherine inherited all of Bjoern’s packages when he left the project.

I was tired of the hotel I was staying at and my friend Martin told me about a new Holiday Inn Express that had just been built not too far away from our project. We went to check it out and when compared to the one star hotels that I had been frequenting, it looked like paradise.

The situation was they had free Internet and in Germany that is a huge draw with everything else being equal. I don’t understand how some other hotels manage to charge between ten and twenty five euros per day extra for wifi access, but I digress. The hotel wasn’t that full and the Internet speed was just perfect. Of course some doofus had to ruin it for us. Rather than to pay for a e-book, he or she, managed to find it on the Internet and simply download a pirated version to their computer while at the hotel.

Don’t believe the hype, German has just as many lawyers as America does and they are out trying to make doing just about anything difficult. In this case it was probably justified as when they contacted the hotel to determine which guest did this heinous crime they were probably told, “I don’t know we just rent rooms to people”. I never heard if the hotel ended up paying off the lawyer or if simply changing their setup was good enough although I suspect they had to do both.

The new setup was not that different from any other hotel or airport. You have to register with someone to get a username and password which will then be associated with your room. It didn’t always work as smooth as described but it did work much much slower. Yet this is where it gets a bit more interesting.

Martin worked for a telecommunications company who had a few ideas of their own about network security. You had to put a special card into a card reader on the computer when making a connection to their network. He needed to do this several times a day to pickup his email, enter his billable hours and book his train tickets. The sad thing was that this solution didn’t seem to work unless you had a simple connection to the Internet. So he could use his company laptop from home, but not on the wireless hotspots in the train, a coffee shop, or his hotel room.

His solution was to use the project DSL line at the client site, which actually was a fairly elegant solution for the longest time. Unfortunately, the client decided that to provide this service was making things too comfy for the externals and discontinued the service. In the end, Martin ended up using his personal cell phone to create a wireless hotspot just so he could do his time reporting.

I am glad I never saw Martin’s company provide any actual telecommunications work because they didn’t seem they were even capable of setting up a simple vpn for their own employees.

The bigger the organization the longer things will take to get done, but eventually they do get done. You may have heard stories about the left hand not knowing what the right hand is doing, and indeed that can and does happen, but sometimes there is misinformation and obstruction for political ends.

One such example was the rollout of a new Microsoft product as a company standard tool. It had been decided to sunset the old groupware product and use this product. There was of course a timetable that everyone should be trying to meet.

There are a couple of ways to rollout new functionality within a company. You can be first and face all the teething issues, you can wait and hope that all the teething issues are discovered and thus have an easier time, or you can be cynical and see if the product will be canceled or reduced in scope.

The problem with being first is that unless your departments usage is the simplest case, you may have problems and the company may not (yet) have the expertise to solve them. Depending on the circumstances you may be working with other consultancies or even other large cloud solution firms who had at least two or three addition levels of support who can hopefully solve your problem.

We were lucky enough to have other consultancies and other fortune 500 firms involved in this new cloud solution. The cost for a single iteration including the internal evaluation, external evaluation and rollout of the farm solution would feed a normal employee for one or two months. As there were lots of these farm solutions at the company I guess it was getting costly to keep this up. So management made the decision to have a six month freeze of all farm solutions that were not live. In three weeks, any solution that was not live would be thrown out and the acceptance process would start all over again middle of next year.

This is a real bummer to say the least as we have been fighting with configuration of our farm solution for months. Our consultants show that the solution works on their servers, the real problem is with our company’s internal networking and security.

We found out about this with only 9 days until the freeze, and when my boss found out he was understandably concerned that he had not heard about this. When he confronted his boss about this he was told that, with a rather sheepish grin, there was no communication budget for this topic that is why he did not send out an email about it.

Well, part of the problem was that his boss was a real idiot who should never have been promoted to a manager position.

Large companies have a lot of bureaucracy which may come in handy when you need a new key to the closets in your new office, or it may be soul crushing at the end of the year getting something approved when everyone is on holidays.

One of the temporary positions that existed at our company was that of intern. It was a position that was usually in sync with the type of study the student was doing. Of course in order to keep this position, you must be a student and copies of various school papers must be submitted in a timely manner for your internship to continue.

Our intern was named Konstance, she was actually a very detail oriented individual had a very well rounded background. She always seemed to have some interesting bit of information about any topic but she was not boastful, and if she knew more than someone else she never showed it. In general a very pleasant individual with a lot of promise.

It was in one of the bi-weekly team meetings that the group leader made a very special point in telling Konstance that he had extended her position for the next year and that she need not worry about it. Some short time later somebody from the HR department sent her an email saying that her internship would be terminated early next year.

Konstance contacted the group leader who said that the reason for this was because she had not submitted all of her paperwork in a timely fashion. Konstance went to the HR people in tears asking what was missing and please please don’t cancel her internship. The HR people informed her that all of her paperwork was up to date, the problem was that the group leader simply did not send his acceptance for her for the next year.

When approached he appeared to be quite surprised that this was the case and promised to send his acceptance to HR. The acceptance forms were never signed, Konstance was forced to leave shortly thereafter. Some of the people who work at big companies are just petty dictators.

In the movie “The untouchables” there was a scene where De Niro as Al Capone uses a baseball bat to correct a wrong. It was a very vivid moment in the movie but hey that kind of thing can only take place in the movies.

Well, I guess I am not the only one to have seen that movie as there was a real life manager who for a short while started to bring a baseball bat to his meetings as well. Timothy walking around with a baseball bat and patting it on his hand as went walked. The way he did it caused a bit of unease in both the internal and external staff.

This did cause quite a stir and the HR department probably added a new rule to the company manual – “baseball bats are prohibited from all company meetings”, as the baseball bat disappeared shortly from work shortly thereafter.

I was actually involved in supporting a testing environment for a large European bank. The bank was really well funded, they had no money / budget worries to speak of. The goal was to upgrade one of their financial systems and in that sense they had a very good test plan.

They had a list of reports, transactions, and various processes that had to be tested and had to work. Well, everyone had a list of things that have to work but in order to proceed with the upgrade each and every point on this list had to work, and because it was a big client the vendor kept fixing the bugs that they found.

When I was brought into this, I was between projects and the company was looking for some work for me to do. The bank’s IT department was quite busy with other tasks so they gave me the support role for this system. My job was whenever a new fix was available I had to integrate it into the testing environment. I then had to restore their database so they had a known state to begin all of their pre-acceptance tests.

All in all, it was a fairly easy bit of work and gave me a small insight into one of the large banks. The thing that you have to remember is that this testing was taking place not in the bank but on our equipment in our office. The bank actually had very nice production machines and also had very nice testing machines.

Their problem was not that their infrastructure wasn’t good enough, it was actually much nicer than most of our equipment. The bank simply couldn’t quickly and easily get a database restored or have an external consultant install scripts, stored procedures or programs on their own machines. It was simply much more efficient to pay the vendor for their own testing environment and get the tests done in half a day of the change being available.

I wasn’t even allowed to work on one of their internal testing environments without one of their IT people typing in every command for me.