Math Formula

Showing posts with label self-management. Show all posts
Showing posts with label self-management. Show all posts

Thursday, August 1, 2013

Think logically!

Some while ago, I reflected upon mantras and sayings, which often more or less accurately represent people's schools of thought. Not quite as severe, yet annoying at times, are platitudes. They tend to be not so deeply burned into our minds as mantras, but nevertheless sometimes their shortsightedness is striking.

One of the platitudes which made it to the olymp of particularly stupid platitudes is: Think logically!
What I find surprising about this statement is NOT that typically it is plainly wrong in the strictest meaning of the word logically. What I find surprising instead is that it reveals an extremely widespread misconception about how knowledge is obtained and applied. Let me elaborate.

While this statement has merit in certain situations (e.g., in a course on, guess what, logic), most frequently it is simply misused. A few examples:

  • When boiling noodles, do you put the salt into the water before it starts boiling or afterwards? Think logically!
  • How do you hang that picture? Think logically!
  • How do you calculate the area of a circle? Think logically!
Again, what I find irritating here is NOT the misusage of the word "logical" in the strictest meaning of the word. More than not, what the speaker really means is: "Apply your knowledge about the principles of our world onto that particular matter.". But even then, this statement does not make sense at all!
Most likely, asking that respective question about doing something does not only show a lack of understanding of the matter per se, but also about which questions to ask in order to come up with a solution.

Someone who already knows how to boil noodles might ask back further on: Think logically, how do water and salt react with each other (in chemical terms)? How will you level the picture after you hung it? Just look at that circle, how many square-units does it consist of?

All of these questions make perfect sense - in hindsight. Just as like the correct questions that lead to the ultimate answer to the initial question could be: What is the seeding point of noodles? Which material is picture made of? What is the square root of 2?

Obviously, none of these questions make sense in the context at hand. Yet, there is no way the initially asking person can possible know this; otherwise he would not ask at all!
Learning something is not only about the respective application, but also learning which questions to ask during application. 
Telling somebody to "think logically" gives him the impression of failing to realize something obvious. But the contrary is true - telling somebody to "think logically" reveals failure to realize how you yourself obtained that knowledge! 

Think logically! Remove that platitude out of your dictionary - your kids, classmates and colleagues will thank you for your nonviolent communication.

Wednesday, December 5, 2012

3 Simple Steps To A Perfect Day

1) Ask yourself: For the next 30 minutes, do I want to do something I will remember, or will be remembered for?
2) Do something that is worth remembering, or being remembered for, for the next 29 minutes.
3) Take 1 minute to go back to 1)

Wednesday, November 28, 2012

The Power Of Eating Alone - In Silence

Many people make big mental efforts during the morning shower. Not only do they make their daily schedule, but they also mentally prepare for meetings and make important decisions.
This doesn't come as a surprise, because for many people, the morning shower is one of the rare moments when they are truly with themselves and simply let their thoughts flow.

Afterwards, for the annoying morning commute, you either sleep (which, apart from drawing certain conclusions while dreaming, cannot quite be considered a very active activity) or you are exposed to some form of stimulation. Stupid morning shows on radio; plug in your headphones and your favorite band, on full volume of course; or if you are really motivated, read a book. That way or the other, you are not with yourself and your thoughts - and won't be during the whole day anymore.

Thus, let me ask you something: When was the last time you ate alone, at home and in true silence? That means no radio. No TV show. No computer. And of course, also not texting, reading, whatsoever at your ubiquitious pocket-computer.

Obviously, it is great to go for lunch with your family, have a barbecue with your friends, or a candlelight-dinner with your significant other. There are even books which recommend to never eat alone. Obviously, there is much to gain from such talks and events.

In fact, there was also a time I totally avoided eating alone. When I served national service at the Red Cross, I didn't feel very good mentally. In such moments, eating alone was quite counter-productive, because it triggered even more depressing and negative thoughts - I do totally recommend seeking for company in such occasions, and even the TV might make good company at times.

Most of the time, however, your subconscious is your biggest, unique treasure. You just need to open a door, instead of trying to constantly kill it with audio and video stimulations, in order to "let it out".

A perfect way of doing so is eating alone - in silence! Sounds ridiculous and / or boring? Give it a try, it comes for free and won't hurt!

Monday, July 16, 2012

Why I Try To Avoid News - Part II

A few days ago, I outlined what made me trying to avoid news. Today, let me tell you why I stuck to that approach.

First, I think it is important to realize what makes journalists, news agencies and TV stations provide news at all. While there are of course some with the best intentions, I'm quite convinced that the majority of news is broadcasted for mainly one reason: entertainment. Consequently, you cannot expect to be purely informed about certain issues, when TV stations generate their profit out of your entertainment.

Second, have a close look at the composition of news. I'm not aware of any scientific studies on that topic, but I claim that most news are of the type: "X said Y about Z", where the source information is only the actual event Z. Technically speaking, the signal to noise ratio is quite high. Why would I care what any self-proclaimed expert thinks about a certain topic? Even more, when her today's opinion is rejected by another self-proclaimed expert the other day.

Third, I strongly sense that following mass-media draws your attention to certain events, for example, robberies in your neighborhood, suicides or plan crashes. People who follow media regularly tend to over-estimate the likelihood of such events. Nassim Nicholas Taleb refers to this perception as "ludic fallacy". The only way to escape this deception is simply avoiding news altogether.

Forth, as much as I try to filter all information I'm exposed to and to take it with a "grain of salt", and as much I would trust all journalists to do a faithful job (which I don't), there is still no way to protect me from shaping my mind in a certain direction.
Imagine reading a newspaper which reports about the great successes of a political party every day. I bet that if you keep reading that newspaper for a year, you will be more inclined to believe that this actually is a successful party, even though that is contrary to your initial beliefs.
And now think about reading a newspaper which focuses on the negative aspects of that party only. Again, I bet your perception will be totally different.
The only protective measure I can think about is avoiding this kind of news altogether.

Fifth, I wonder, what would I actually gain by following news? Does it make any difference in my daily life whether this year's rice harvest in China was a successful one? Will the supermarket around the corner stop selling beer, because the Higgs Boson was found (or, in accordance with #2 from above, because somebody said that the Higgs Boson was found).
Things that are likely to have an impact on me I will hear about sooner or later anyways, so no need to seek for them actively.

I understand that this position sounds pretty rough and ignorant. After all, you are still a human being and should care what surrounds you, right? I totally agree; but that doesn't stop me from deciding how I want to spend my time (which, according to some, is the most precious resource you have). I think you can care for others and be genuinely interested in the people around you - and still try to avoid news.

Thursday, July 5, 2012

Why I Try To Avoid News - Part I

Until February 2011, I used to follow news frequently. Reading teletext, watching news on TV in the evening, constantly hitting F5 on my favorite online news pages, waiting for updates in Google Reader ... I think I was close to being news-addicted. But then something happened that instantly gave me a tremendous amount of additional free time, plus a new perspective to perceive certain things. While the world passionately followed the events surrounding the Arab Spring, I kept my TV black and stopped following news for good.

Some people are quite surprised when I tell them about this decision and cannot imagine a single day without news. But how do you know about the latest elections? Don't you care about the poor child that was killed the other day? How will you know that the oil price is about to rise, we will be on the border to a collapse of the financial system, and the USA will attack Iran?

Well, there are a couple of reasons, so let me elaborate.

First of all, let me tell you why I initially started that experiment with myself. In the upcoming days, I will outline why I stayed with it ever since then.

It was in 2009 when I first got in touch with the idea of not following news, when I read Nassim Nicholas Taleb's generally inspiring, mind-provoking The Black Swan: The Impact of the Highly Improbable. Even though his works deeply shaped my way of thinking about probability, randomness and other aspects until today, the idea of not following any news any more seemed quite rigid to me back then. However, the seed had been planted.

When in January and February 2011 the Egyptian masses started assembling on the Tahrir Square daily, I was totally bought by the happenings. Just nine months before, I had had a great time there myself, and now I followed the events from far away. Al-Jazeera live stream, Facebook, Blogs ... I was totally into this stuff, several hours a day. Eventually, the peaceful demonstrations where interrupted violently.
It is not too surprising that there were contrary reports about the reason for the both-sided violence. One side claimed that the protesters had started throwing stones; the other side claimed there were shots from the army, and the protesters had to defend themselves.
How can I verify one claim or the other, from a 2.000 km distance? What if both of the reporters are right, not only because politics demand the according report, but because they report what they really saw and experienced from their point of view?

Frustrated and depressed, I turned off Al-Jazeera, and didn't open it or any other news page ever since then again.

In the upcoming days, I will explain why I stayed with this approach, and what I think I gained from it.


Wednesday, June 27, 2012

When Your Boss Calls You, It's Never A Good Sign

My high school teacher in bookkeeping was a nice person, with our well-being in mind all the time. Even though she was a little bit inconvenient occasionally, I'm inclined to think that she did also that with best intentions.
And similar to many of my teachers (I attended a high school for IT and business administration), she had worked in the private sector several years before becoming a teacher.

Thus, she would tell us innocent students a story from the "real business world" every now and then.

"When I still worked in that company, we were afraid whenever the telephone rang and the display showed the extension from our boss.", she began one day.
The story-telling attitude she showed now awoke some of us, as it was known already that at times the bottom line of the story could be interesting. Yes indeed, sometimes even more interesting than continue playing Counter-Strike.

So, one of the motivated dudes in the first row devotedly asked: "But how's that, why were you afraid? Maybe he just wanted to inform you about something?"
"Wrong", she replied, holding her breath for a second. "For it was known, when the boss calls you, it's for one of two reasons: Either he has some nasty task for you ... or he rants at you. When your boss calls you, it's never a good sign."


I'm still surprised about the purity of Management 1.0, Theory X attitude shown in that one sentence.

Do you remember #4 of the 13 top habits of how not to manage?
"4. Only contact them when something is wrong, but never praise them" (me)
I think common sense tells you how wrong that behaviour is, so let me propose something else instead:

Respect and credit what somebody is proud of! Do it frequently, at least by showing genuine interest. (me)

It doesn't matter whether it's a co-worker, a child or your parents - all of them will appreciate your interest. Even if it's something small which might seem insignificant to you, for them it's maybe not, so it least praise their effort. Maybe it was done better than the time before?

Whatever it is, let them know ... and mean it!

Wednesday, June 6, 2012

My Top 4 (Work-Related) Mistakes

When I wrote about my motivation to write this blog a few months ago, among the reasons I described there was the possibility to reflect upon my mistakes later and learn from them.

A crucial part of learning from mistakes is acknowledging them. While this is rather inappropriate for some mistakes (say, having cheated on your wife, especially when she doesn't yet know about it), others qualify for being announced publicly.
I think there are two main functions of such a public confession:

  1. You show that you are past the point where you feel ashamed, and are ready to move on.
  2. You allow others to learn from your mistakes, which not only helps them, but also establishes a certain level of trust among you

In the light of the above, I will today share my biggest work-related mistakes so far. Maybe I'll share some non-work-related ones in the future as well.

Please note that due to my IT-background, some of these might sound a little bit nerdy. I'll try my best to cover the IT-stuff as much as possible.

My biggest mistakes:

No. 4, Shopping carts

When I was in high school, I was short of money all the time. So, imagine a big shopping mall. On the entrance, dozens and hundreds of shopping carts are available for customers. However, once the customers return with carts full of stuff they don't need anyways, and loaded more of these items into the trunk of their car than fit into it, they obviously don't feel like walking those fifty meters back to the entrance of the mall. No, instead they prefer to leave the shopping carts directly where they parked their car.

So, the shopping carts have to get back to the entrance, in order to be filled with new customer's wishes. The carts being unable to move themselves, somebody is required to push them. And that somebody was me, every Saturday afternoon.

Naturally, you don't only push one cart at a time, because the continuous stream of customers would simply overwhelm you. Instead, you are required to take multiple carts at once, say, 20 to 25.
Strangely, the 25th shopping cart in the front of the queue develops something like its own will, which might be contrary to the young lad pushing it.

Thus, I once lost control over it, and the carts crashed into a brand new, golden BMW, which was parked innocently over there, and leaving a nice scratch along the driver's side.
Now, that would still be understandable; that's not the mistake I want to talk about. Yet, to make it even worse, I thought that nobody had seen me, and simply moved on without informing anybody.

However, when I was called to the information desk five minutes later, facing a rightfully upset customer kind of falsified my former assumption.
Taught me an interesting lesson about honesty, tough!

No. 3, Broke the Build

During my time as an intern in the first software development company I worked for, the senior developer was preparing a presentation of our software to some key-clients the other day. Therefore, he told us to hold back with our most recent changes, in order not to introduce new bugs that close to the presentation.
However, me still being simply inexperienced with version control systems, I could not see the potential harm of a small check-in.

Useless to say, that "small check-in" was not quite compatible with the rest of the repository, and obviously broke the build.

Cost the senior developer half a day, and me a beer :-)

No. 2, Test it faster!

Later on in my development career, I noticed that one of the systems we were developing became increasingly slow the more data we added. Initially, it was fast enough (remember, everything is fast for small n), but the more data we added, the slower it became; to the point, where it was not test- and usable at all any more.

Now, instead of searching for the root-cause of the performance issues, I simply introduced a debug-switch which would prevent loading more than 25 entries from the database at once. Bang, problem solved!

I think you can imagine what happened once we turned that switch off again to test in a real-world environment ....

No. 1, Ignore the need for feedback

Being entrusted with managing my first IT-project on my own, we had to re-develop a legacy system, plus adding certain features. It was agreed that in a first phase, the features of the existing system should be copied, the data migrated into the new system, and the users start working on it in order to give feedback about usability issues. In a second phase, the new features should be added.

However, once we were close to releasing the first version, the client changed his mind and did not want to go to production without the new features.
In strict violation of a very important principle, "version 1 sucks but ship it anyway" (see also here), I was too weak to resist him back then.

Of course, once we finally introduced the full new version including new features, there were still several glitches, because it was the first time users started really working with it. The resulting changes caused a big delay in the project schedule and consequently, it was not quite "on budget" anymore either.


Dear former colleagues and current co-workers, bosses and clients, please excuse both my mistakes mentioned, as well as all the big and small ones I forgot to mention. If you think there is a nice complementary to this list, feel free to leave a comment below ;-)

So, these are my biggest work-related mistakes (so far) ... and what are yours?

Wednesday, February 8, 2012

Progress Report: My First Mobile Application

A couple of weeks ago, I made a bold claim on this place: I want a tiny little piece of the mobile development cake. So, three weeks later, how am I doing with my first mobile application? Time for a quick update!

As I indicated in the last post already, I'll try to sharpen the knife on a simple, yet maybe useful application: a currency converter. Unlike other converters, though, on mine it is NOT required to select base and target currency yourself. Instead my converter has the ability to automatically "guess" your most probable conversion (based on your native and current location), and consequently I call it Auto Currency Converter.

Key features are:

  • Support for more than 170 countries and more than 130 currencies
  • Automatically maps a country to a currency
  • On app start, automatically provides conversion between your most probable choice
  • Keeping track of your most recent conversions, and thus providing even better suggestions
  • Capability for offline conversion (NO Internet required)
  • Fully automated update of all exchange rates
  • Conversion in both directions (from base to target currency, and vice verse) at the same time


In order to get feedback from potential users as early as possible (remember, I want to fail fast and fail often), here is the first draft of the user interface:


First draft of the user interface of the Auto Currency Converter
Even if you are not interested in my self-estimation of the progress and don't continue reading, I want to ask for your first impressions on that draft. You like it, you hate it, you would never use an app with such awful a background color, or you would love an icon of an unicorn in the upper right corner - whatever it is, please drop a comment below.

I'll describe the progress against three different dimensions: 1.) State of achievement; 2.) Problems encountered; 3.) Future activities.

1. State of achievement
I familiarized myself with the development environment (Eclipse with Android SDK). Running the device emulator is a bit slow at time, but it's doing a fairly good job.

The Android documentation is pretty good either, and for all the things that are not fully covered there, odds are that somebody else encountered a similar challenge already. For most questions arising I found an answer on the web very fast.

Accessing the Yahoo Finance service for exchange rates is not a big deal, either. I am happy to say that all calculation-related modules are in a proper test harness, as simple as they may be.

What I'm really impressed about is the great, flawless, built in SQLite database in Android. Easy to use and just working! I'm using the database both for the exchange rates and keeping track of the user's last conversions.

So, most features envisaged are in place. Also, I managed to provide a first draft of the user interface.

2. Problems encountered
As expected, the biggest challenge for me will be the user interface.

For a small application like this, providing the required functionality is a piece of cake; providing a good-looking user interface for me is not. Not only are there some challenges unique in mobile development, but even more, it is simply time consuming.

Ensuring the application

  • looks good several different devices (imagine a smartphone vs. a tablet screen) and
  • different operating system versions (most smartphones still run Android 2.x, but some nice features were added in 3.x, which I want to use if available)
  • supports both landscape and portrait screens (and ideally, also the transition between those two)
  • finding proper free icons
  • supporting different user-languages and preferences (what should be displayed as "08.02.2012" in most European countries should better be "02/08/2012" in the US)
etc. ... it simply sums up.

Some of the other potential challenges I did not face up to now (such as marketing and the likes), simply because I did not yet publish my application.

3. Future activities
Most features are in place; what remains to be done is polishing up the user interface.

What I have not yet decided, is whether to include ads (the easiest choice probably being Google's AdMob) in that first application, or not. I guess users are most likely much more opposed to ads if they are introduced later, compared to having seen them from the very beginning.
On the other hand, if I keep seeing this first app as a pure learning field, and may be a "reputation builder", there is no need for ads at all.

Oh yes, and then, finally, I should publish the app as well, and make people aware of it.

Apart from that, there is another thing that concerns me: I think that I totally lack any vision of what exactly I actually want to achieve (not with this first application, but with the others yet in the pipe). What can I provide?
Even though I know I should have a clear picture on that upfront, I hope it will work the opposite for me and will evolve over time.

For the moment, I'm just interested in getting my first mobile application done, and I feel that I'm on a good track. In order to progress further, I need your help. I would be very grateful for a brief comment about your first impression of the screenshot above.

Wednesday, October 12, 2011

Fail fast, and fail often

A few weeks ago, I wrote about mantras in general, but with particular regard to lifestyle and attitude towards life.
Today, I want to talk about my favorite mantra at work.

Similar to the stupid ones I mentioned in that other post, obviously there are several suggestions you hear over and over again. What comes to my mind as a perfect example is 'I will work harder', as followed by Boxer in George Orwell's Animal Farm. Another one, as already mentioned earlier: Those who can go out can also work ("wer fortgehen kann kann auch arbeiten").

Anyways, let's not waste time on things that are useless, but rather focus on the ones I do consider helpful.

My favorite two mantras at work are:
  • Make better trade-offs
  • Fail fast, and fail often
I currently work in a software development company, but I think those two can be applied quite universally.

So, what does "make better trade-offs" mean? For me, that short sentence highlights the fact that quite often possibilities and decisions are not only black and white, but there is something in between. 

Taking an example from software development, quite often you face the question of implementing a particular feature the 'quick-and-dirty' way (which might do the job in short-term, but be rather poor to improve and maintain in middle- and long-term) or the according-to-the-book, super-perfect, elegant and time-consuming way. I feel that business people tend to gravitate towards the first statement, whereas any self-respecting geek would favor the second one.

Now, I don't want to make the case for the one or the other extreme. From my point of view, both of them are wrong, as they ignore that whatever they do is and will always be a trade-off. Thus, the only thing you as a decision maker can do is accepting the fact that you face a trade-off, and make better trade-offs.

For all kinds of decisions and actions, I think there is a strong aversion against failure prevails in our Western European culture. (Some people claim that this aversion is even stronger in former-communist Eastern European countries. Cannot yet judge about them, and even more so about people from more distant countries ... probably have to figure it out myself one day.) I think that this attitude is fundamentally wrong.
If you always keep doing the same things you are already confident and good at, you will keep doing them forever.
Instead, you should seek to fail, value to fail, and learn from your mistakes.

And I think not only should you seek to expose yourself to situations where you can fail, but you should seek to fail fast. And often. The faster you fail, the easier you can incorporate the findings and the feedback from that failure to you future actions! The same is true for the frequency of your failures. Faster failures, more frequent failures, clearly result in a much higher number of possibilities for improvement.

Admittedly, that thought is not new at all. In my understanding, it is one of the key advantages of Agile software development. As Juergen Appelo puts it in Management 3.0, "Software is produced in short time frames, often in time  boxes or 'sprints', and delivered in many incremental releases, where each release is a potentially shippable product." Shortening feedback loops is also something heavily encouraged by successful entrepreneurs, as young entrepreneur Carl Taylor reveals in an interview.

Again, I think these two principles can be applied in pretty much every industry. I'm sure you can find ways to apply them at your work, right away and right now. And I wonder ... what is your mantra at work?

Search This Blog