I just woke up from a dream where people were looking at a newly published book in English, and on one of the introductory dedication pages of the book was the translation of a Tamil poem. Both the book and the poem were as imaginary as the dream itself, but the first verse caught my attention and filled my senses:
Most people have daily stresses during this time of Coronavirus. Working from home is lucky compared to the impact on livelihoods and health. Social distancing is necessary but does have its own little impact. For the moments where you have time to connect with friends online and recharge by taking your minds off of the state of the world, here are some options:
Now that people are sheltering in place and cooking, it’s good to record some more recipes. It’s even better when they are the kind that can easily scale up (can be made in pots of any sort).
Here are some recipes for Tamil food using the Instant Pot. They represent the way I’ve been making these dishes recently for myself.
OmnICU is a new project to create Internationalization (i18n) functionality in multiple target languages and multiple resource-constrained runtimes. Two different approaches to solve that problem are wrapping a single common binary in multiple target language wrappers, and to write a source-to-source transpiler in a one-to-many fashion. Here are reasons why choosing Clojure (Lisp) would be a good decision for writing a transpiler.
Daily life in the West has finally been undeniably, indefinitely disrupted by the current COVID-19 strain of Coronavirus. It’s important to take precautions, but the situation isn’t so dire yet that we can’t learn a little more about what & why. Here is the more useful information that I’ve come across so far.
Finding text editors that properly support the input and navigation of various scripts’ Unicode-encoded text is no longer as rare as it used to be. Unicode has been well-established for a long time as the standard for encoding all of the world’s languages. However, when it comes to text editors specifically for programmers (IDEs), ironically, the situation is pretty bad. It looks like in Visual Studio Code’s most recent update, they finally have proper support for input and navigation of abugida scripts, or as they’re alternatively called, alphasyllabaries. The animated picture in the VS Code update page shows someone typing and navigating Tamil text, but the change should actually apply to several languages across East Africa, South Asia, and Southeast Asia.
Writing systems — the ways in which we write down a language — are fascinating. They may not be as diverse and surprising as all the animals and plants of the world, but you likely may be surprised to learn just how differently we have found ways to write down information, each with strengths and weaknesses. And if you don’t get all the details right, then what you end up telling the world is not “follow your heart” but “coward”. Oops. (Countless examples exist that could fill up several blogs — it turns out failures in cross-cultural appreciation & appropriation go both ways.)
People believe that, in the timeline in human evolution, language evolves first as speech, and only later does writing evolve to record it down. For example, when new words (ex: slang) or spoken forms derived from spreading process (ex: “gonna”, “hafta”) get coined, if they persist long enough, they will become normalized and enter the vocabulary. Whether these new words are defined as “official words” depends on if you have a prescriptivist or descriptivist view of the situation, but that is a small example in our own experiences where we see writing changing according to speech. (Btw, Shakespeare was a master of introducing crazy, made-up words into a language.)
What is fascinating are some of the more apparent examples in recent history in which we make choices on how to write, or change how we write, a language, and the implications those choices have. Or in one case, it’s the other way around — it’s the act of recategorizing dialects as separate languages through how we write.
When I interviewed for my current job, I didn’t pass the interviews on the first time that I tried. When I applied again 1 year later, I passed, but I had changed my strategy in preparing for the 2nd time to correct all the mistakes I made during the 1st time.
There were other factors of my growth as a programmer beyond the whiteboard problem practice that helped equally as much, if not more so, in my success in the 2nd round of interviews. But the whiteboard programming aspect is more immediate and usually more stressful.
To help others who may need the help in the way I did, the following is a summary of how I prepared the second time: