Code change shouldn't be horrible

Was having a discussion with a developer and came across a topic about code change. Since he is very new in developing java stuff, now after getting thru the jungle for half a year. He looks back and realize many stupid implementation.

He then told me something he learnt from another developer, who has been writing code for some years that if code works, don't fix it.

I am quite surprised when he mention the rationale. It is the risk that the changes might break what works is inhibiting him from doing changes.

I can't help but "educating" this budding developer at the spot. With unit testing framework so widely available, there is no other reason but laziness or unrealistic timeline that no unit test is written.

Automated build and unit tests are so crucial that it should be conducted across the team as early as possible. Once it is in place, all code changes will need to endure through the bunch of test cases, before it is allowed to get into trunk. It is all the little test case that aggregates help us to build the confidence of code change.


Stress

Stress - the urge or tension that we felt. We usually feel the stress when we have deadline to meet, or task that has zero tolerance of getting wrong.

Working under these constrain firstly results in a highly focused and very efficient work mode. But when the period of tense is prolonged, it's not only efficiency drops, but also the motivation gets diminished.

That's why setting realistic schedule and priority is so important. But they are usually skipped or poorly done. Lack of time and over ambitious are usually the cause. Ambitious, desire to be a hero or simply don't want to be looked down as obstacle are what leads to un-realistic schedule.

Be honest to oneself, and also to the decision are keys to reduce the un-necessary stress. Get the whole team involved instead of taking it all over by oneself, there's nothing must be done by YOU.

Riccardo Chailly and Leipzig

I am attending the concert by Chailly and Leipzig, playing Bruckner #8.

Last time I heard of Chailly's recording is almost 10 years ago, which didn't leave me with any good impression.

Tonight, I am totally drawn by him and the orchestra. To describe what I have heard, I made the following analogy.

The sound is,

As thick as syrup.
As elastic as rubber.
As clear as water.
As crisp as chips.
As light as feather.
As powerful as a bull.

I envy him so much, that he can enjoy music from such a decent orchestra at will. What's more, it is apparent that, no matter how much you invest into your audio setup, it won't come close to attending a live concert.

His interpretation of this piece is so intense, with tones of layering and superb clarity. All the transition are so smooth that you didn't realize the joint. All phrases are built up like tidal - come and go naturally. The orchestra can whisper so lightly but you won't feel blur while in forte, the can play like no limit.

Apart from the concert by Celibidache and Rattle, this one has already taken a place in my memorial hall.

My Arts Festival 2011 begins with magical Bach

Masaaki Suzuki is my Bach expert. Many of the Bach vocal pieces I have listened, are conducted by Suzuki-san. Finally, I ca see him in a live concert and this also began my annual concert going season.

Tonight, the pieces he conducts are cantata by Bach. Apparently, they are written for religious purpose. They were all played before the church service, so that attendants can grasp the outline of the service. The content are story relates to Jesus Christ; his going to the Jerusalem, the joy of believing in God.

The first thing I spot is how strange the sound is. It is the auditorium which project a dull and flat soundscape. But then I am later amazed by our brain that it can work out how the sound should be like and reconstruct accordingly. This also triggered me into thinking, that many of us are spoilt by the stereo system invested.

Bach Collegium Japan played the pieces very cleanly and precise. This is also how Suzuki-san conducts. You can tell how he wants to express, or emphasis through his gesture.

The concert ended with BMV 147 which is a piece very familiar to the audience. Many of us should have heard of the chorale. Everyone is leaving in joy as it is such a nice concert.

Masterpiece Japan

Masterpiece is a company who specialized in making bags. Ranging from backpack, to messenger bag or tote bag. All the bags are hand made in Japan, by master in the industry and using material of very high quality. They do cross over with other brand but all the product are focused highly in functionality.

I've lately acquired a backpack, as well as a small shoulder bag from them. Both of them are using the Harris Tweed as the material. At spots which might get regular tearing, such as the bottom of the bag, it is reinforced by some leather. The leather is dyed naturally, without using harmful chemicals. The touch of the leather is very buttery and soft. This matches nicely with the tweed.

All the edges are nicely sew and the tweed they use are nicely presented. Resulted in a bag which has a "winterly" feel. The zipper is silky smooth which you can open and close with ease. The top outer pocket of the backpack has a short grip, it helps you to pull the zipper straight so you can pull easily.

I like the size of the bags. Both are not intent to bring extensive amount of stuff but definitely sufficient for daily commue. And since it is thin, it stay close to yourself and won'tmake you looking bulky.

The smaller shoulder us also amazing. I am getting thus as I usually need to take something with me, especially when I am going out with my daughter. There aren't a lot but not as little that can dump them all into pockets of shirts and pants. This serve the purpose nicely and I can still managed to take my D80 together with the essential with me.

WTF is "Devlosophy"

Developer, or engineer, is not any different from a skillful craftsman. They polish on the code they write, making sure it is robust and reliable.

And like any skillful worker, they possess their own set of tools to do their work. And what's more, they have their set of "standard" in defining what is good, or not.

Me as a veteran in the industry for years. I have also developed my own standard and working approach, towards fulfilling and leading the development.

And I sum this up as "Devlosophy" - the philosophy I believe in software development.


Craftsmanship

Before the establishment of factory, all things are produced by individuals. Nowadays, quantity dominates quality. Number of pieces got sold is what concerned most.

Luckily, there are still people who dares to invest the time and effort in building things that they are proud of. Looking into the minute details.

So here I am, sharing with you on the different thing that I spot, or owned. It could be clothing, bag or anything I can use in my day-to-day life.

I am seeing the embrace of craftsmanship not only a matter of taste, but a living attitude. I could share the story behind the bag I am using; like the canvas it is using, or how the cotton of my jeans get dyed, all natural without giving harm to the environment.

It is no longer me and my belongs but also getting connected to the people behind it.