Showing posts with label Work. Show all posts
Showing posts with label Work. Show all posts

Thursday, 17 January 2019

Exploring Buenos Aires

I have some trips in the backlog, so I'll start with this one that I did in September/October. I was in Argentina in the Iguazu area only, so I consider this to be the first time I really visited.

This time I went to Buenos Aires, for a month, to help with the Youth Olympics.

For starters, in this trip I was working, and because there were not enough people I worked a lot. I only had 1 single free day every 4 or 5, which means that this free day you need to do a lot of things together that you could distribute better if you had a full “weekend” or 2 days in a row. Also, this meant I would only visit the city, a trip further away would be complicated. And there was one more thing, one of my best friends was working there and I was going to visit her too and do things together, which means less time overall to do touristic things.

Nevertheless, I managed to get some impressions from this city and country and to see a bit of the things that were around me.

Buenos Aires seems…European. Maybe it´s the architecture or how the streets are organised, but the centre of the city reminded me of Madrid, or Paris a bit maybe, and also some Eastern European cities. It looked very different from Rio, but then again, I did not visit any other big city in Brazil, so maybe it´s not that different. The only thing is that you do notice the poverty, in the fact that buildings and streets look dirtier, more abandoned, less maintained.

I was staying in the centre of the city, in a massive square that contained the parliament, and where there were daily protests for any topic. However, this was the norm, so I never felt the protests were a problem or disturbed me. The hotel itself was like 2 minutes from work, which was great because I had morning shifts starting at 6:30. However at this day and age, there´s a thing that any hotel that wants to be respected must have: good internet coverage while in the room, be it cable or wifi. Sadly, my room didn’t have. The wifi lost signal plenty of times or it was too weak to use, to the point of not being able to send whatsapp messages. Especially when travelling this is a big deal breaker, and even after warning about it they said they could not do anything.

Anyway, being so centric allowed me to be near several nice spots, one of them being the same square I mentioned. It was big and usually sunny and felt quite relaxing. I also was at walking distance from the Obelisk, a big monument in the centre where there was celebrations and protests, and that looked nice too.

Apart from those scenic places, I did the tourism I enjoy more, which is to just randomly walk around and get a feel of the city.

As I said the centre reminded me of certain cities in Europe, but there was a lot more poverty, and you could see clearly homeless people. However, you didn’t feel the insecurity of Rio. Later I learned that this might have been not entirely correct (I heard shootings, twice, once right next to the office while we were on the roof of the building and some coworkers saw the shooter shoot against a house and leave), but in Rio a lot of the homeless people looked like on drugs, while here they just looked homeless.

Close to this hotel there was a big street filled with theatres. A friend that also lived in the city meet with me one day and showed me this area, and it was shocking the amount of shows and actors and events that were on display. I had heard lots of Spanish actors and musicians toured south-america in general a lot more than Spain, but before seeing this I may not have understood the true scope of such things in Argentina at least. Maybe in Barcelona or Madrid there are as many theatres, but in here the way they accumulated so many in such a small area was quite surprising. A bit further there was another beautiful section, Puerto Madero, next to the sea. I saw it at night, and with the lights it had it was very nice. 


My friend lived in an area called Palermo, so when we coincided we walked around there too. This felt more similar to Ipanema actually, had amazing restaurants and bars and was less centric-looking and more relaxed, very nice. We went a couple of times to a nearby restaurant strip that had very nice food and amazing cocktails, and we could see the night atmosphere, with people ready to go out. However, with the limited time we had, we didn’t really go out while in there, or at least no to clubs: It seems most places in Argentina were just playing “cumbia” music, and after seeing some examples we agreed we both despised it, especially her considering she had spent there some months already before me. Only one night we tried to go out, and the place we tried was busy with a private event and told us anyway we had to dress up more nicely, meaning a suit and a dress (and after that we hated it and would not like to go back there).

We worked too much these days to do much more, but we did have the chance to use a bit the fact that we work for such events, and we visited several stadiums around the Sarmiento park and Tecnopolis. This area was used to hold several competitions, and it looked curious. I'm unsure how Tecnopolis is used normally, seemed to me some type of science museum/exposition area, but it had funny statues and structures. Of course we had full access and we skipped queues and restricted areas, which makes you feel a bit special and good^^. This event is smaller than a normal Olympic of course, but it was organised in a way that there were plenty of people following the different competitions and it had a very nice and friendly atmosphere.

All in all, the month passed too fast because of work, and didn't get to see much, but what I saw was nice. It did had its problems though, of bad service sometimes, bad taxi drivers, massification in the centre, poverty, some lack of general maintenance of public things and other issues, but for a visit it felt like a relaxed place and I enjoyed it (when I had free time).

Ah! I cannot finish without mentioning a couple of things: Yes, the food was...weird. The beef they have there is really really good, but the cooking style is a bit weird, a bit too well-done for my taste. And they have a lot of fat food, heavy, with butter and sauces and oil. Or sweet, that's the other thing, they eat a lot of sweet things in the morning (facturas), and the alfajores and dulce de leche are awesome but they're digestive bombs (that didn't stop me from coming back with close to 6kg of the things). And the last thing: Argentina and elevators had a weird relationship. Lots of them are old, badly maintained and fragile-looking. I was stuck in an elevator, twice, in this month. It has never happened before in my life I think and here it happened twice. One of the times we even had to get out forcing the doors open while it was stuck between two floors, which was a bit scary but also a bit funny.

It was a short and busy visit overall, but I'd be curious to see more some other time if there's another chance. 

Saturday, 23 January 2016

Working in Integration

When people ask me what I studied or in which field do I work and I say IT they always ask me if I develop. When I say no, if they know a little about IT, they ask if I test or if I'm a system administrator. And I keep saying "No", which just confuses people. In the end I say that I "integrate", which people take as if i have said "assimilate" or some other word that, while kind of knowing the meaning, doesn't tell you anything....

In one of my earliest long posts I mentioned a little what does it means, but I though I'd spent some time explaining it a bit more...

Integration, for starters, is really a meaningless word. It means to basically put everything together, and in a way that's what I do, but not really...

I do not program, apart from sometimes automatizing some tasks. I do not test much, although there is some testing. I do not administrate systems, although I do connect to servers and run things in there sometimes.

What I do mostly is to act as a firewall between all the teams involved in providing a service and the final users and clients. I'm also (in theory) the person who should know more about a service so, when issues arise, the right team receives work.

This is still pretty vague and sounds as if I spent all day sitting in my chair and twirling my fingers waiting for people to contact me.. so, let me explain  a bit more..

I plan, or help plan, things. For example, we have a new version of the system and we need to install. The team that installs needs to tell me how long will they take and when they can start doing it, and then I go to the users, check what are they doing the day we need to install and plan when can we do it. I then prepare all the paperwork necessary, including requests to the team that installs about what needs to be installed and where.

We also have paperwork(well, it's all Web-based and through computers, but it is basically bureaucracy) about what do we have in our servers and computers, so i do paperwork updating these versions once new deliveries arrive.

Another important part of the job is to help the users  (mostly testers, except for the operational period when we're actually live and the users change) to use the system. Loooots of times someone comes to me and says "your system is not working".

After punishing them adequately for their lack of details regarding what is really not working or in what way it is not working(by being adequately sarcastic or passive-aggressive or as clear as they were when answering about it), I go to where they had the problem to visually see what they mean , check the system and the different monitoring tools we have to check the system status (here I'm not talking about system administration but more on the line of checking logs to see what our application says it's wrong), and find the cause of the issue and a solution. If the cause is not evident, finding a solution first also works.

Most of the time the solution is to smack them on the head and point them to the fact that they missed a step when doing the initialization steps. However, sometimes I need to smack someone in my team (or myself) for breaking something temporarily after having done something stupid,  or passing the problem to another team more qualified to know what's wrong. This could range from security and network teams (the real sysadmins) if things are slow or crashing for no reason, to the company that produces the data that our system reads (because they are giving us the data in a crappy format), to the people that actually prepare configuration files and parameters of the system during installation, or to the developers if we really have a bug in our code. A big part of the job is this, to investigate problems until you can figure out more or less what is happening,  why, and even ways we can fix it.
As usual, the trick is knowing enough to send to the correct team while offering a solution or workaround if possible. It is like in that joke where a guy goes to fix a machine, presses one button and everything works, and charges a lot of money for it. In the detailed bill, he writes that pressing the button costs one dollar, and the rest is the cost of knowing which button....

We have plenty of users and special moments when we need to give extra help, so I have a team that helps me in doing all that...so, I also need to teach my team, prioritize problems and plan stuff with them like vacations and such things .

I also need to speak with the clients, understand what they want and try to make sure they are happy and that when they check the service nothing breaks.

Apart from all that, I help to guide where the service will go in the future. This is not my job directly, but by having the knowledge about how people use it, my opinions in the matter are at least considered, and when something is a pain in the ass to do I try to warn so it gets improved later on. As part of this, I need to manage all petitions to change stuff in my service. Again, this is mostly paperwork, but you can see which changes have been requested, when are they going to be done and stuff like that. Another part of the job precisely is to check that these changes have been done at the time people planned to be done.

Since all this means interacting with other companies and other teams in different parts of the world, there's lots of meetings, conference calls, presentations, trainings, etc...in some of them I am presenting, in some of them I am listening only and in some of them I'm commenting on stuff.

I also do some testing, but not much. I just test things that could not be tested before. For example, you may have tested part A of a system, and it's fine, but after installation you have A connected to B and C, receiving from F and saying hi to Z every 10 minutes...and you cannot test all that until the whole thing is in place, especially because sometimes Z and F are done by another company. Most of this test is done by another team, but my team sometimes needs to test one of those interactions(like A with C, for example).

Another important aspect is to calm down tempers...as the guy people go when there is a problem, part of this job is to make sure there are no panics and things are treated with the level of importance they deserve. If we really need to panic I will say so,  but I also need to assure users and show that it is going to be fine and we're working on it, that things are under control. Perception is very important, and sometimes it does not match with reality. Therefore you need to calm down things, shown is not that bad, offer solutions, etc, not only until things work but also until people realize things work.

Finally, there is periods called operational periods where we give extra help doing work shifts(yes, that means night and weekends sometimes). These periods can be testing periods or the real thing, but in anyway during these periods we work from this nicer area that looks like NASA with lots of screens and projectors and TVs. From there we need to use our systems to prepare the sevice to be live. During the testing phase the users do that, but if we are in operations my team does it. We also practice steps required to do each task, and therefore I need to write plenty of documents about these steps, and improve them from time to time. This way anyone with some knowledge of the project can theoretically do these steps. It's usually in these steps that we can try to do some scripts or little programs that are not oficial but that make our life's easier, but that's the extend of our programming in this position.

While in operations we also take care if issues differently, with more pressure on fixing things faster and in any way possible. Again, all this without touching code, just using back doors,  emergency solutions and our knowledge of the systems. This period also means we have several teams together so we need to interact with all of them,  learn communication channels and how to propagate information to the people that will come next day. I also need to manage the people in my team in these periods, ask for reports, do daily reports myself, track problems, all that...

I don't know if these explanations help to give an idea of the type of job or the level of work we have, but I can tell that it fills our days quite completely, and the fact we are in front of the clients makes everything more intense, fast and stressful...but I do kind of enjoy this^^

Thursday, 17 September 2015

Power and Choice

Nowadays at work I have managed to get into a position a little higher than before. This is normal once you acquire experience. Once you have experience, there's plenty that does not surprise you, and you have more solutions to things, so people ask you more and more and depend more on you than before.

This gives you a certain power. They say power corrupts, and well, there's some truth...it is not that it corrupts so much as that it is fun to use power. For example, knowing a second language is a great power. It allows you to expand your communications and meet new people. So it is fun to have this power. Once you have it, you want to use it.

In the IT world, depending on the complexity of the company, one of the great ways of having power is when you can influence what is being done at several levels. In the end, most IT is based on a guy somewhere doing code, and this guy usually has the ultimate power of screwing the whole thing or making it work fine. Companies should remember to treat this guy VERY well, but they don't always do.

However, apart from this guy, there's usually a big list of other people deciding on what the guy will need to do and how the code will be used. Currently I'm one of these people, and hell, it feels nice....

It feels nice to get the extra attention, to be consulted and considered. Very often in big companies your voice gets lost in the middle of the mess that they are, so it is nice to reach a position where you can be heard, even if just a little.

It is amazing to finally be able to influence monolithic things, and see them change slightly. It feels nice. And I understand that it is easy to get addicted and want more. Not only to influence, but to direct and manage.

However, of course, not all is just fun. As the movie said, power comes with responsibility. You need to use it wisely. And part of having power in a company means that you have power over other people, and choices to make. Power to have to ask someone to come on Saturday. Power to tell off someone if they did a bad job, Power to keep everyone working one extra hour because it is needed. And this part sucks, of course...

We all create a narrative in our lives. We imagine ourselves in our story, and we tell ourselves stories about it. We play parts, we follow patterns that we detect in real life.

Recently, I had a person on my team fired. Not really fired fired, but he did not pass the selection period. He did not do anything wrong. He was not someone who got upset, or complained too much, or someone lazy. He was just...not smart enough.

It would have been easier if he had been a bad person. We had one of those too, in another team, and firing him was not a problem. But this guy in my team was just not good for this job, nothing else. So in any stories, this is the part for the bastard,the bad guy, the boss that fires the innocent worker.

Life is never that simple, but still, it's a shame I had to fire him.

With power should come also a higher awareness of consequences, Anything that I needed this guy to do I would have ended up doing myself, which means I would have had double the work. I was not willing to go through that, so I made my choice.

After all, obtaining power is giving you the possibility for more choices, and some of them are the hard ones....