Much unknown to many is the fact Crisp has entered an autopilot mode since January. We’ve moved on to others, while keeping tabs on certain internal changes. What a recent change to situations at my end gave way to, is the long pending changes to surface. Migrating the data pipeline which is one of the two “close to heart” components of Crisp, I’ve been working on and off. Late last week, sat with migrating the core of the pipeline to C++ and performance has been much on expected lines. Last September when I repurposed most of the content fetcher, we achieved a 50s running time. As much as it was good enough for running as a cloud function, the overheads of runtime were a point of contention. ...

Learning for the day - When shit hits the fan, it is bound to spray all around. Running in a frenzy is never a worthy solution however. Had a disastrous event at work midway through the day. Guess gut is right once again; starting the day on some unknown uneasy note should have been noted. This being the third week of me trying to put affairs in order (pun not intended), was a bit sceptical when it became the crux of discussions. ...

I arrive at the last three days of my resting schedules. So, it is time for an update. My ~six year run with crisp wrapped up on NYE and the last month or so has been a hard one to both think about, and pen down. As I told an acquaintance, the day we wrapped up, saw a lump that called its home my throat. Or, to the melodramatic me, was akin to a father (my gender, nothing otherwise) losing his kid. ...

Late last evening, was discussing with a colleague who wanted to build small APIs. While looking at the pro-s and cons-s of choices like Sails and how some of them come with batteries included. Quite reminiscent of my earlier days with Django I should say, some of these features. As the discussion got into specifics, I had mentioned about the HTTP framework I wrote for NodeJS. And, a line of code says more about things than an hour of talk, does it not? Natural progression then was trying to setup a minor REST-ful API using the framework. The primary focus to show how Express is completely open while the likes of Sails enforce a pattern. Some, not so hard bound, some quite otherwise. ...

And the oddity from Friday becomes even more with a fix that comes by. Given I’ve been dealing with, RegExp, “expected”, I said till evening. But an independent test script shows things are coming up from elsewhere. If you last evening’s post, the matchers returned a false negative every alternate run. Pulled the flow out to a script out of the environment only to find it is consistent. Add to that the fact that the run returns a consistent response when gets loaded with each request. ...

To pick newer stuff that you’ve wanted to play with but were not able to, is quite a wonderful feel. Put mild, that was Day 2 in all. I’ve wanted to get my feet wet with the ELK stack for some time now. 2.5 years, to be precise, from when I wanted to nail down certain bottlenecks with Tenreads’ components. At long last, things came about to fruition as I sat down today to get going with init tasks. At par with getting accustomed, lies identifying lapses (or trade-offs for political correctness). And nothing like adding a good profiling layer, to arrive at the latter. ...

A couple of weeks back, I stumbled upon an interesting piece over at Twitter. The crux being not committing lockfiles into the code base; rather odd at the outset. The rationale does make sense from a different perspective into things. When package.json files with scripts and other requirements change, so do lock files. So far, so very good the situation. Where the unseen enemy creeps up from, is with the latter’s content. ...

To put a long-winded story short, it has been quite a mix of a day, this one. From being active by 5 to welcome the first day of the new work despite lack of proper sleep, to wrapping it up talking about a good friend, hardly one that lacked action. I do have a certain something against spaghetti code and the likes, but at times, those are good places to see how things evolved. Add to that, the insights into constraints in place, as a system took baby steps, so to speak. Where things get a bit messy is when one is completely alien to and is not privy to any of the above. Quite an interesting mental exercise imo. ...

ப த ி ெ ள ன ் ் ள ன ை ா ய ட ே ் ட ( வ உ ர ர ை ை க ய ் ே ) க ர இ ு ல த ் ி ல ா த ம ெ ல ள ் ி ந இ ் ந த ் ந த ா ம ள ி ் ழ ி வ ல ர ு ை ம ் ம ல த ட ி ா ட க ் வ ட ே ம ா ந க ி ன ம ் ொ ற ழ ு ி வ ப ி ெ ட ய ் ர ட ் த த ு ் . த ு ள ் ள ே ன ் . Two rather troubling statemednts from vedAntavAvadUka villivalam nArAyaNAcAr swAmi, almost 40 years back. Both from an introductory note about his vyAkhyAna for swAmi deshikan’s paramatabha~Ngam. ...

A week back (if I remember right), I had quoted Swami Desikan and how the school has opined of Rudra/Paramashiva (at least traditional ones, laity and newer adherents can be discounted on the basis of ignorance) Was rehashing while writing a while back and something came up. Swami Desikan during the course of his commentary on IshAvAsya upaniShat, quotes harivamSha’s bhaviShyatparva and in particular Paramashiva’s statement. What’s of interest is how he refers to Rudra here "आह च सवज्ञः" (cf सर्वज्ञ्னான रुद्रன் தானே சொன்னானிறே) ...