I was watching an excellent technical session about Java GC. When the speaker said “Pause is inevitable no matter which collector you use”, a thought suddenly came to my mind that this is also true for living a life.
I was watching an excellent technical session about Java GC. When the speaker said “Pause is inevitable no matter which collector you use”, a thought suddenly came to my mind that this is also true for living a life.
I took a two days vocation in Koh Samed a months ago. In the second night, I came across a beautiful fire shows on the beach near a restaurant. My Canon 6D was very good with low light so I took a lot of photos. I could not move around easily since the place was crowed so I missed some excellent actions. The show ended leaving me wanting for more. I waited there for a while in hope that there will be a next round but there was no sign of it. While I was thinking about going back to my room, I saw the light of fire from a show in another restaurant like 100 meters away. I grabbed my camera and run.
I almost forgot that I have this story in my to-be-blogged list. I was assigned to perform performance tuning on a system in my previous project. I found a concurrency bottleneck and rearrange the synchronization pattern to gain noticeably throughput. I later had a chance to read about the Instance Confinement technique which could be applied with the case. The technique uses the normal object encapsulation to make the code easier to understand in term of concurrent access aspect.
I gave a talk in the internal un-conference in my organization. The original title is “What I want to tell my junior developers” since I aimed to talk mostly about technical things. It turned out that the top ranks of my topics were about non-technical stuff but I didn’t get a chance to change it when I gave the talk that day. The topics are about some of my observations and perspectives toward things that I want to share with my junior staff. Here is the content of topics I have presented in the session.
A couple sprints ago I did a small refactoring on a piece of code. The code is short but able to clearly express the concept of distributing knowledge between objects
One of the big gaps between seasoned developers and the less experienced ones is the troubleshooting skill. Unlike any other knowledge, this kind of skill is difficult to teach and learn. Developers invest tons of hours to develop his or her own techniques in gathering information and seeing through details to find the root cause of the problem. Sometimes the problem is new or you don’t have enough knowledge in the tool or system that you are working on. This may lead to the dead end that you have run out of all the ideas. I have one simple technique I often use when I cannot think of anything else I can do.