Sunday, November 17, 2013

Final Reflection on Learning

When I took this module, I was initially skeptical. I initially doubted the value proposition of ES2007S, as it was not a content heavy course. My reasoning then was that communication could not be taught. It could only be improved through a large degree of practice. Therefore, when semester started, I doubted that I would learn much from this course.

Seldom have I been proven this wrong. Just a week ago, I was writing my final year project report. Usually the final year project has a mid progress report, which in my case was due last semester. As I analysed my writing, comparing my mid progress report and my final report, some very prominent differences emerged.

In terms of clarity, my final report was significantly clearer than the interim report. Now that could be because I now had a much better understanding of my project, which was partially the case. But even sections of the report that were supposed to feature the same content were rewritten because I felt I had done a poor job earlier.

Writing the research proposal in ES2007S helped me gain more consciousness in this regard. One particular area where my writing seemed immature earlier was citations. My earlier report had inconsistent and missing citations, which rung alarm bells in my mind when I read it again.

So my initial premonitions have pretty much completely altered. And this module has not just had an effect on my writing alone. I've gained considerable insight into writing application letters and resumes, and that too in very good time, right before I start applying to companies for jobs.



Sunday, November 3, 2013

Reflection on team based proposal

It took my team quite some time to reach a topic for the proposal. Initially I wanted to discuss something controversial like racism, political apathy, or migrant worker rights. However my team mates believed that a controversial topic would divert attention from our proposal to inflammatory debates on other aspects of the problem. Therefore we decided to reconsider our topics and focus on issues that were relevant to us.

And there it struck me. I had been in Singapore when the transboundary haze of 2013 was at it's peak. I had witnessed the panic, the constant polling of PSI readings, the distribution of N95 masks and the political discourse that echoed in the media. I suggested the haze to my team mates, who immediately agreed.

A major dilemma we faced was coming up with an appropriate proposal that would be original enough, yet effective. The Singaporean govt had taken many effective measures to circumvent the effect of the haze.

Therefore we decided to focus on dealing with the source of the haze, rather than mitigating its effects. That was an area where the government's response had not been as effective.

We conducted most of our initial meetings online over google hangouts. These were pretty effective as they allowed us to work on our proposal on a google doc while discussing it simultaneously. We also dedicated another google doc to be our research repository. Here we dumped our findings for other team members to use, and kept track of what each of us was supposed to do.

Usually teams prefer face to face meetings, but in our case online meetings turned out to be more suitable because a large part of everyone's work was research. And within my experience, research is better conducted individually, without the time constraints of a scheduled meeting. Furthermore we did not have to worry too much about syncing out timetables to find an appropriate meeting slot, as the discussion was logged. So even though I missed an online meeting, I managed to keep myself updated by reading the meeting minutes and adding to the research repository in my own time.

However our workflow began to have issues when we started formatting and preparing the final draft. As google docs had limited formatting available, we decided to use Microsoft Word for the document. Our workflow typically involved downloading the word document from google drive, adding our patches and uploading a revised copy. This was not optimal as it lead to problems when two people edited the document simultaneously. One person would have to manually find and merge the other person's changes. Therefore only one of us could work on the document at any given time.

I think we should have either stuck to using Google docs, which supports simultaneously editing, even though we would have had to suffice with lesser formatting options.

Being a software developer, I face version control issues all the time, and for code we usually use software like git (http://git-scm.org) to efficiently manage versions. However learning git is not an easy task, especially if you aren't from a software engineering background. Therefore I sadly could not recommend it as a solution to our workflow.


Sunday, October 6, 2013

Evaluating Intercultural Behavior

The 21st century's metropolis is a cosmopolitan melting pot of diverse cultures. Today's professional settings are above borders, races and cultures. That also however, implies that effective communication despite those cultural barriers is of prime importance.

In general, a cosmopolitan professional setting usually has its own "culture" so to speak. Part of this culture for instance, is using a common language as an interface, (English being the most frequent). Another aspect of this global culture is an appreciation for local cultures and customs. It is deemed impolite or disrespectful to judge another's cultural behaviours, no matter how strange they may seem.

This post-modernist[1] interpretation of cultures however is not necessarily universal. A particular case of interest for instance is the issue of religious headwear in professional settings.

France, for instance recently declared wearing the burqa in public to be illegal[2]. This may seem un-tolerant and contradictory when the cited motive was the advancement of a liberal and secular culture. Bear in mind France is a melting pot in its own right, hosting a significant number of immigrants from Northern Africa, and where Muslims form 5 - 10% of the entire population. However upon closer inspection the law makes a bit more sense.

Statistics show only around 2000 of France's 5 million muslim population adopted the burqa. They also demonstrate that 80% of the French populace supported the ban. Furthermore the Grand Mufti of Paris and clerics of the Al-Azhar mosque in Cairo (an influential center of Islamic thought) supported and applauded the move, claiming that the burqa and niqab has no basis in Islam.

Discussing facial wear is particularly interesting in the context of communication because it directly and indirectly effects the dynamics of communication. The niqab for instance, fully covers the face leaving only slits for the eyes. This implies that a person adopting the niqab in an workplace would find it difficult to communicate with peers of mixed genders. A part of that is probably due to stricter interpretations of Islam not allowing communication between opposite sexes. One of the motivating factors behind the ban was to advance assimilation of conservative Muslims into the French identity.

So is facial wear an issue which doesn't simply melt, at least in the French context? Does an overt display of religious symbols have any role in today's globalised culture? It is certainly an interesting fissure in intercultural behaviour.


1. http://en.wikipedia.org/wiki/Postmodernism
2. http://en.wikipedia.org/wiki/French_ban_on_face_covering

Sunday, September 1, 2013

Resolving Interpersonal Conflicts

Interpersonal conflicts within a professional setting are a tricky affair. What stance is one to take, without being too comprising on one hand, and too aggressive on the other. Power hierarchies in professional settings complicate matters considerably. Although optimal solutions are highly situation dependent, we probably can identify a few trends in successfully resolving such conflicts.

In my opinion, the most fundamental solution is obviously prevention. Interpersonal conflicts rarely ever benefit either parties, and should be avoided at all cost. Hot discussions should be cooled immediately, instead of being stoked to blows. The primary reason here is that conflicts very quickly loose their original cause, and transform into an issue of personal pride. As David Hume remarked, "man is a slave to his passions", the line between "rational" argument and impassioned conflict is thin.

Of course, if the conflict has already begun, one should aim to reduce hostility in my opinion. This does not necessarily mean compromising over the issue that started the conflict. But it could be as simple as using softer and friendly tones when communicating. The primary aim is to separate the conflict from the relationship. One should try to absolve the conflict from personal pride, as an immediate measure.

So if the conflict is between two team members over the content of a presentation for instance, the ideal approach would be to avoid associating that content with each other's pride. The next step would be to listen to the other's opinions as rationally as possible to reach an acceptable compromise.