One of the best films of the Alfonso Cuaron, showing his most famous specialty in camera works

Some films have very special attraction. Before actually seeing whole film, you instantly know how you will feel about it, how you will like it.

When I saw the trailer for the first time, I began to think it’s going to be one of my best films in 2013, and once the director’s name was revealed to be Cuarón’s, I instantly had satisfaction as if I’d watched whole movie already. It was so predictable, in a good way.

Finally saw it, and the film did exactly what it promised to do. Since watching Children of Men, knowing and being fascinated by Cuarón’s specialty no matter they are artificial or not, his great works in extreme long sequences were so effectively done in the film. Taking advantage of being in space, where no up or down exists, the camera flew around so freely, becoming the main character of the film.

I believe the positions of cameras in the film are more important than the objects they are taking, and Cuarón’s Gravity gave me the best example for emphasizing such idea, and I’m very thankful for it.

While the narrative itself is great too, I think there will be more interesting story about how film making was done, and I’m sure I will spend some amount of time searching for “Making of…” videos or blogs, speculations from other professionals. Hope our techniques in film making continue to innovate themselves, and the great examples like Gravity will not stop being presented and beloved by many.

P.S. At the end of the film, I’ve notice the name of the actor, who did “Mission Control voice.” Knowing his past involvements in some famous films, I couldn’t help but smirk. I wonder if the producers did know there will be reactions like mine when casting him.

Advertisements

Do your best to spend time for the Real Work

Recently, I had to work so much time on one element of the product, requested by the colleague who was not completely sure if the application was perfect enough for her to think that the product was alright to be released.

At the end, we have found that perfecting the element was impossible since it relies on the external conditions like network status. I had known about this, but I had to show it to her to convince her that it was impossible. She usually don’t understand about software limitations without actually seeing them.

I don’t disrespect perfectionism. Sometimes, even I can see myself spending so much time for just a few things of whole product, to satisfy my purposes for them.

However, it’s false to consider getting the perfect result is directly related to and only possible by working a lot of time on it.

And if such hours were spent for the sake of reenacting already known and proven limitations, you should accept the fact that you just wasted precious time which could be spent for the real work.

I am trying my best to use my work hours for the real work. But it’s irritating when it’s not possible because of incompetencies of others.

Steve Jobs, the artist of User Experience

On October 6th, 2011, the news of Steve Jobs’ death started spreading.

As a professional iOS developer, I was busy updating the applications to be prepared for upcoming iOS 5.

When I heard the news, like many people, sadness immediately fell on me.

It was just like what a fan could feel when our hero died.

He was like Michael Jackson to the pop music fans, Gregory Peck to the film lovers, and Bruce Lee to the martial artists.

Unlike them, however, Steve had used  the electronic devices and their software, which could provide the great user experience.

Probably, he could be the first one who had chosen this form of art, I think.

And Steve’s art was so entertaining and so right. None of us had to be ashamed of enjoying it.

Like BMW drivers, Harley Davidson riders, and Stephen King readers, us Apple users are so proud of our objects.

Thank you, Steve Jobs, for all your awesome artifacts joyfully shared to us. We will miss you a lot.

Coding while Commuting

Last week, I’ve been coding while commuting to my office. Due to busy schedule for our projects, being required to learn Cocos2d framework, and having own desire to utilize my time to its fullest, I began to train myself to be more comfortable at coding while commuting using bus.

[New York Time] Wi-Fi Turns Rowdy Bus Into Rolling Study Hall
from New York Times
I use long distance bus from my home to subway station, and take a train to the office. It takes about an hour for bus ride and about 20 minutes for subway transit. And almost every time, I’ve been able to take a sit in the bus. In other words, I have an hour at my disposal to do something productive, such as coding.

Typing and building using Xcode works just fine, especially if you are free from needing to use big external display, comfortable desk and chair. When I do occasionally need to use internet, my iPhone 4 can provide personal hotspot. However, coding without internet browsing is not bad at all for me, since it lasts only about an hour.

During this hour of coding, somehow I could be able to focus on my coding more efficiently than while sitting  comfortably in my office. I suspect it’s because of using only Xcode with all other apps being closed, and encouraging myself to find solutions from my own stuff, rather than passively search answers from internet. Also, knowing the bus ride would last only for an hour, I could just focus on finishing miniscule but important matters which could be fixed quickly.

Because of this good experience, I began to have stronger desire to get Macbook Air. This lightweight compact laptop will surely make my coding while commuting more enjoyable, though my current 13″ Macbook Pro is not so bad at all. Guess I need to find about opinions of the developers using Macbook Air with Xcode, and how to deal with disadvantages.

Why having personal projects is critical for a software developer?

I would like to share my reasons, based on what I learned from other developers, to have personal projects outside of professional jobs.

Unless you are a super genius, who can implement newly acquired knowledge flawlessly at once, it’s inevitable to make mistakes in programming based on new ideas. Your choice for solutions will need to be revised repeatedly. It may require number of customizations to accommodate merging these solution with codes from other developers or from older projects, though they are working just fine with no problems by themselves.

At early stage, your professional job will provide this kind of challenges many times, allowing you to grow patience in dealing with errors and testing implementations to find the right solutions. Sooner or later, you may find yourself simply customizing lines of codes for already solved problems. In other words, your job will get easier as your professional experience grows.

Unlike many other professional fields, new technologies are introduced so often, much faster than we can keep up with. But until your project manager or supervising developer decides to use these new technologies, you may only hear about them, if this is the worst case.

Your ability to implement new ideas, that you’ve practiced so hard, will become dull or inefficient. And what makes it more depressing is that this kind of backsliding happens very quickly and drastically. When finally new technologies are required for your projects, it could be embarrassing that your development skill is much like how it were at the early stage of your profession.

Having your personal projects not only mean that you build something, but also that you make own decisions. Because you are in charge, you can test your implementation skill with new technologies without waiting for anything. Whether your attempt to use new ideas is successful or not, you will be prepared to deal with issues later when it’s much needed for real jobs assigned by your employer.

Along with technical decisions, you can also make scheduling one on your own, without any constraints. Of course, once it’s public and used by many others, you may have to listen to their requests and satisfy their demands as soon as possible. However, it’s done proactively, being able to lengthen or even shorten the development time as you like. This sense of controlling time is probably only possible if you have complete ownership of your project, which is by having personal project outside of your job.

Also, no matter how much dedication you’ve put into your works, technically these jobs assigned by your employer are actually not yours. These useful evidences for proving your skills may not be permitted to be used when you are applying for a new job from another company. But with you own personal projects, you can just submit them to be fully analyzed without any guilt but with great confidence. It’s always better to silently show what you are so good at, than just loudly speak about it.