Week 09/24/2017 - 10/15/2017 First 3 weeks at new job. Engineer on boarding

  First 3 weeks at new job. A lot of time spent on on-boarding and didn't get much achieved. Also I got interrupted pretty often by ripples from relocation. 

   Good news is these random interruptions are coming to an end. I've renewed a bunch of documents which are expiring at around the same time and settled down at my new apartment with all service activated. I can't really see any big interruption in the coming few months.

   At work, I spent ~3 days just to set up developing environment due to legacy code base as well as the fact that this is a very small & stable team. The last engineer they hired was a few years ago. 

   Knowing that there should be more engineering joining the team soon, I spent another 3 days going through all the engineer on-boarding process to simplify things. 

   The document used for engineer development environment set up has been reduced from 12 pages to 6, and I've created a setup shell script for each project (there are like 20 of those to set up) to automate the process. It's not perfect but all the tedious steps & undocumented things have been replaced with strict bash scripts, which would fail if any of the pre-requisite are not satisfied. 

   It's not exactly what I had in mind: one-button set up, but it's definitely easy now to set up all the components for this project.

   I've also participated in several architecture reviews. Caught up with the architecture quickly and found out a lot of problems with the existing architecture. Guess I'll have to work on that and change those one step at a time. Was transferred another project from another team, so more time spent on meeting & ramping. Good news is there are some really solid & smart people here so I don't have to worry too much about the quality of work.

   First few task of my new job will be DevOps oriented. Play with some persistent storage & user data first!

Comments

Post a Comment

Popular posts from this blog

Week 07/02/2017 - 07 /09/2017 Rewrite Memcached Cluster Accessor

Spent the week re-writing memcached accessor & configuration for our java server to support clustering. Initiative of this project: Multiple memcached clusters are used in my project and some of them need to be accessed by multiple services written in different languages, one of which being PHP. The old accessor does not support clustering at all, not even to mention ketama consistent hashing (on the roadmap). While other services do utilize clustering for memcached, the java server accessor create one memcached client per host in the cluster and run a multi-write &/ multi-read. On top of that manual hashing was done to decide which cluster a particular key goes to (based on an additional parameter, for instance, user id) Old format: memcached.name=<cluster_name> memcached.hosts.0=<mc00, mc01> memcached.hosts.1=<mc02, mc03> To fully utilize clustering support from memcahed library, a new format was proposed: New format: accessor.<accessor_name...
Read more

Week 10/22/2017 - 10/29/2017 Repository migration & Deployment process improvement

  In the past week I've been working on mainly one thing: migrating our existing repositories from bitbucket to github.   Git is the first source control tool I used and has become dominant over the past few years. To be honest I'm surprised to see my project uses mercurial.    The task of migration is fairly simple: fast-export will do the heavy lifting for you. Here 's an article on how to do it. The reason why it took me a lot of time is: my new project has baked a lot of secrets / keys inside source code and now it's going to be more public than only accessible by my group.   After I started digging into these secrets, I've discovered more issues:  - configuration management and secret management are done with the same configuration file  - configuration and source code is not a perfect 1:1 map. With a lot of copy-paste, many sections of configuration are not even being used in code  - deployment is a mess. some repos have dedicated (...
Read more

Week 07/09/2017 - 07/16/2017 Profiling & Performance Improvement

Image
My primary focus during the past week is improve the performance of event handling system on the java server. Context: We use one thread for processing room transaction related user actions. For instance, user move from one room to another. I added instrumentation for profiling data a few weeks ago and noticed that user disconnect is taking a long time to process while other transactions on the thread is usually done with 5ms. I added timer for sections of code that processes such even and ran profiling on production this week, and the result is astonishing. The majority of the time was spent on a synchronized block. In short, we kick off a call to update database on a different thread and move on with the current thread, and the next thing current thread does is to synchronize on user object. Unfortunately the database updater job locks the user object as well so essentially we're doing the database update on the same thread. And the worst thing is, the lock in database upd...
Read more