Eye of the storm
Sep. 10th, 2020 09:25 pm![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
mtbcI have had a busy year. Applying for jobs since I returned from Asia, interviewing, sometimes intensively, then weighing offers and preparing to relocate: paperwork, making ready here for my departure, researching for my arrival. A couple of aspects of this relocation have had me interact with staff at various levels as my new employer has engaged companies who then subcontract to local partners.
I get a couple of quieter weeks this month. I am reasonably on top of everything that can be done right now, flights and rental car are booked, I even have a cellphone with an American SIM awaiting activation and it is not until next weekend (after the coming one) that I take time off for the shipment of (legally distinct) household goods and personal effects. Most stuff is sorted, inventoried, the customs paperwork is largely filled out, I just have to put the last items in and finalize the by-box lists. My previous anxiety is thus somewhat calmed.
After that, the real effort follows after I move next month: proving residency, opening a bank account, booking and passing the written and on-road tests for my driver license, buying a car and arranging its insurance, renting an apartment and arranging my stuff in it, getting broadband installed, buying soft furnishings, kitchenware, groceries, a street map of Oak Ridge, etc. Once that is done I will proceed to learning my way around my new employment, in terms of colleagues, working practices, technologies, and projects.
My current employment is in a good state so that now feels calmer too. It feels fitting to be leaving having gotten a new round of work done on the kind of project in which I am at my best. A few years ago I mentioned developing a general framework for operations on subgraphs of typed model objects, the edges being relationships among them. I have further implemented a general subgraph copying utility. It works out what to copy, preserving cycles and other structure, and, according to the request, can truncate the copy, splice it among the original, etc. Further, it acts correspondingly on the underlying filesystem as some graph nodes relate to various file types that follow their own rules. The copying process is itself complex while also using the previous complex model graph work so I wish the best of luck to whoever needs to get their head into it next. At least I tried to make the code reasonably simple and clear, including by naming and comments.
I get a couple of quieter weeks this month. I am reasonably on top of everything that can be done right now, flights and rental car are booked, I even have a cellphone with an American SIM awaiting activation and it is not until next weekend (after the coming one) that I take time off for the shipment of (legally distinct) household goods and personal effects. Most stuff is sorted, inventoried, the customs paperwork is largely filled out, I just have to put the last items in and finalize the by-box lists. My previous anxiety is thus somewhat calmed.
After that, the real effort follows after I move next month: proving residency, opening a bank account, booking and passing the written and on-road tests for my driver license, buying a car and arranging its insurance, renting an apartment and arranging my stuff in it, getting broadband installed, buying soft furnishings, kitchenware, groceries, a street map of Oak Ridge, etc. Once that is done I will proceed to learning my way around my new employment, in terms of colleagues, working practices, technologies, and projects.
My current employment is in a good state so that now feels calmer too. It feels fitting to be leaving having gotten a new round of work done on the kind of project in which I am at my best. A few years ago I mentioned developing a general framework for operations on subgraphs of typed model objects, the edges being relationships among them. I have further implemented a general subgraph copying utility. It works out what to copy, preserving cycles and other structure, and, according to the request, can truncate the copy, splice it among the original, etc. Further, it acts correspondingly on the underlying filesystem as some graph nodes relate to various file types that follow their own rules. The copying process is itself complex while also using the previous complex model graph work so I wish the best of luck to whoever needs to get their head into it next. At least I tried to make the code reasonably simple and clear, including by naming and comments.
no subject
Date: 2020-09-11 02:20 am (UTC)