Weekly Notes 2026/40

  • I’ve started work at Progress. Not much interesting happened this week. I barely engaged with anything other than on-boarding at new job.
  • I replaced my existing broadband connection with Airtel today. My current connection is run by a local guy. Speed was good and I barely got any disconnect over the last couple of years. So why change? Six months ago, he switch off my connection without telling me that payment is due. This time as well, I had to remember when the payment is due. He doesn’t send invoices or receipts so getting refund wasn’t even possible.
  • My neighborhood dog Jumbi bit a couple of delivery guys in last few months. Not a serious bite but he sank his teeth enough to break skin. He was vaccinated by BBMP a couple of years ago. My neighbors called BBMP to take him away but they haven’t acted on it yet. I’ve put up a notice on a pole in my street with his picture. My street is a dead end and sometimes people wander into it. He is not fond of barking. He doesn’t look dangerous and he sneaks and it makes him dangerous.
  • I learnt about Golu (Gombe Habba). A friend is very fond of it and she has been working on her dolls for this Navaratri (picture below). Ookie play-school asked kids to bring a few dolls to the play-school.
Golu (Golle Hemba) at a friend home.

Weekly Notes 2026/39

  • I went to Western Ghats near Ettina Bhuja: an overnight stay in a homestay, and easy hike early in the morning. It was a long weekend so a few friends also joined. Kaalu enjoyed hiking in the mountains.
  • My on-boarding has started at Progress.

Reading list

Weekly Notes 2026/38

  • Yesterday (Sep 25, 2026) was my last day at Toyota Connected India (🚗️TCIN, Bengaluru). I’ll be starting a new position (Principal Engineer, tech-stack: Rust) at Progress Software (Bengaluru) from Oct 1. I’ve mostly positive things to say about my 7 months long stint at TCIN. I recommend them for Rust and C++ roles.
  • Over last few months, I turned a C firmware to Rust/embassy. The first iteration was done using Claude. After couple of days, I had a non-blocking firmware which worked without any bug!! This is very rare in other languages where things just work if they compile (Haskell also comes pretty close but it doesn’t work on embedded systems).
    • Claude did a decent job i.e. we had non-blocking firmware that has similar behavior. The code is also better than I’d have gotten if people wrote it. I am cleaning it up now especially around error handling. I’d say it was overall positive. On the other hand, the firmware I was working at TCIN, requires keen eyes if you are using Claude/Copilot.
    • When multiple people are working on a codebase, the trouble with LLM generated code is same as LLM generated text. Its hard to know what is important in the wall of text. When people write decent text or code, the important bit is usually obvious and review process starts from there. This is not to say that people don’t write vacuous or disjointed prose and code.
  • Ookie had annual sports day at her daycare this week. It was a fun gathering though clouds didn’t offer help. It was a sunny morning and kids got tired soon. Parents were as usual more tired!
  • SIR has been going on in my neighborhood where I’ve been voting for last ten years. Yesterday, the ECI appointed contact person called and asked for 2000 bribe to “take care of SIR notice”! I’ve blocked his number and will take care of notice by myself.

Reflection On Interviews (last 9 months)

Since late December 2025, I participated in over 20 interviews. First, I tried maintaining a database of all success & failures but I gave up after a while. I only added entry to my Notion database when I went through at least one round successfully. I must have applied at over 100 places and heard back from 20 of them, gave interviews at 15 to 17 places, crossed half-way mark at 6 of them, and had offer from 3 of them. I was shooting for 5 to 10 YoE roles with larger scope if possible.

More importantly, I was looking for positions that were either fully remote or required at most one or two day in office with as little traveling as possible. This removed most of the usual suspect I’d have applied. I was pretty liberal in my applications. It is the best strategy when you have no other strategy.

It seems to me that the single most important factor in my success was whether someone read my resume carefully and liked something on it. At one place, they went through my GitHub and they liked what I saw. During interview, you can almost tell if someone has read your resume or just skimmed though it. When they read it, they jump quickly into the details of a project/work they liked. Since you are talking about things that you’ve done well in the past, you can easily set the tone of the interview. More importantly, you start your interview with a lot of headwinds in your favor.

Other important factor was a presence of a “friendly face” in the panel, especially if the interview is online (most of them were). You occasionally meet people who are unusually nice to strangers, and they try to help them you as much as possible. Perhaps they don’t like to see any kind of suffering in their midst. Bless their soul! Most people on interview panels are usually from schools where competition is a celebrated norm. Which means that they expect you to do handle anxiety and pressure well which I guess is fair if not ideal for me. Sadly, I am not one of those friendly face myself when I am in panel!

I had much better results when interviewers were senior engineer/manager and technically hands-on. These folks are usually more worried about maintaining and running a system than developing new features. The tone of the conversation is immediately set to an abstraction level where I articulate better. I am terrible when HR or non-tech person starts the conversation. I think I am getting better at it. The trick is to answer slowly and nothing more. You can’t have a conversation with a person you don’t share vocabulary/language.

I guess what I am saying that interviewing is a social process. And like every other social process, it is ridden with ambiguity. Things that are easier for other will be hard for you and vice versa. Quite a lot depends on figuring this part out that you can’t unless you had gone through enough interviews without feeling paralyzed. Like any other skill, you need to train for it. AI live interviews (audio mode) helped me a lot. The questions and feedback/response you get from the AI is not the point; the point is that you get to practice and get to notice occasional bullshit you say.


My recommendation is to start interviewing at places where you don’t have much interest in joining (though you’d never know) so rejection doesn’t take as much emotional toll. And you get to work your interview muscle before it matters. If you have friends who are going though interviews, team up.

If you are not getting good vibe from the team during interview, my recommendation is to not join them (if you have a choice, some job is better than no job). I know some people who are genuinely not very interested in interviewing even if they would be excellent co-workers but I don’t think it is worth the risk. “Vibes” reflect culture. Personally, I am against the practice where the team interviewing is different than team hiring you because this model is tilted in favor of large organization and can work against candidates who enjoy being part of a capable team.

For a principal/staff role, and perhaps even for a senior role, you’d do well not to show (or worse fake) interest in something that you’ve no decent experience which could be hard if you are a generalist. Sine they can genuinely find almost everything interesting. I see all of them as software problems, no matter how different is the domain. Whether you are like me or not, it’d help not to do this (perhaps except at early stage startups). Keep focus on things that you are interviewing for and link it to things that you have done before. Closer they match, better are the chances of success at senior role.

If you genuinely excited about the role without having too much experience (e.g. I’d give a shot at Oxide Computers despite not doing any hardware for last 9 years), you may need to clearly articulate why you are excited in football now even though you’ve played hockey, cricket etc. so far. Remember that money they ware willing to pay you correlated with what your are most skilled at and how well it aligns with the job at hand. If you are willing to take a pay-cut then by all means explore new (potentially nearby) territories. I don’t think playing cricket everyday makes you any better as hockey, just like solving puzzles everyday won’t make you any better at combinatorics, let alone at linear algebra. It just shows that you are a good athletes and have what it takes to become a good athlete but I am not paying a price of a good footballer to a no-matter-how-good hockey player. If you willing to come as a rookie football player, fine! I am not yet not convinced that a good generalist could be an excellent specialist with LLM.


Follow the classic advice: you can never over-prepare and work on your resume. I spent weekends preparing for interviews. A friend was going through interviews and helping them also helped me lot. I recommend going though videos that talks about interviews (e.g. Hello Interview channel) if you have not given interviews for a long time. It is good if someone keeps continuously remind you (CRY) what is important. The point behind these exercise to learn how to leave a better impression on people who are going to pay you. To do better, you need to practice. And you can always do better no matter how good you are. Besides, if you can’t put effort during interview, what signal you are sending to your interviewer that says the you gonna put effort in your job?

I’ve been pretty bad as resume, and I still think I am not great at it. I usually don’t find enough excitement working on it (except for occasional urge to use LaTeX). It is tricky to figure out what to add or remove from the resume and what to highlight. I have a resume of a generalist which works well at startup and small enterprises but not at large organizations. Large orgs look for a specific skill. This is a tradeoff I am yet to learn how to make properly.

Weekly Notes 2026/37

  • 🏃️I’ve completed 700 km of running. More than 3 months are left. I should be able to finish my 1000 km run this year without trying extra hard in Nov and Dec.
  • I’ll be starting a new job from Oct this year. My role will be focused on (Rust) tooling around infrastructure management for self-hosted, air-gapped, or hybrid infra. Think of software supply chain management and lifecycle management of apps. Pretty much like docker/Kubernetes on one hand; and ansible/puppet on the other.
  • A friend got excited about newly opened something called Brick Oven in our neighborhood. We went there for dinner earlier this week. I found the place to be OK. Among such places, I still prefer Onesta. Usually, I prefer to go to traditional south Indian eateries with self-serving. Those are most efficient eateries and food quality is very good. But if you are catching up with someone, I guess places like Brick Oven, Onesta, CCD are fine.
  • Lately, I’ve not been feeling like visiting HN. I am spending more time on lobste.rs and RSS feed. I also discovered something called Webring (https://webring.xxiivv.com/) — interesting idea but I won’t see myself browsing them just yet.
  • I feel more energetic when I write code by myself. In retrospect I now understand why. Because there are occasional dopamine rush when I discover a better pattern and whole codebase is now slightly better and when I learn something on the job. This works because getting better and learning matters to me emotionally. I am almost certain that a long-term LLM usage will burn me out in a year. I’ve been seeing signs.
    • Another solution to this problem is that I use 30% of my time coding using LLM and 70% of time solving problems and designing systems by hand. This will also work for me. What is not going to work in long run is being a developer and only using LLM.

Weekly Notes 2026/36

  • 🌦️As of today, the southern peninsula is very rain deficit. Interesting summer ahead of us. Some twenty five years ago, when I went to Chennai for college, I was pleasantly surprised to learn that rain-water harvesting was mandatory for every building. Why it is so hard for such good-practices to become popular?
Bengaluru is extremely rain deficient this year. The whole southern peninsula is ~30% rain deficit.
  • The generative AI is on my mind for last couple of weeks but I don’t want to write to think about it too much. The genie is out of the bottle and we have to deal with it somehow.
    • Most people think of throughput when they think of AI. IMO, throughput is not a value-add of AI though the limelight is on the throughput. It doesn’t increase throughput without costing you in long-term. I think the real advantage of AI is getting to a higher altitude easily. That also means you should know the questions you need answers to. AI can’t ask good questions. Also see “Do you sill read the code“.
  • It is now pretty obvious that many (perhaps most) don’t see tech (at least the IT) as inherently good. We have squandered most of the goodwill that our predecessors accumulated.
    • Software companies needs to see FOSS and community engagement as long-term investment. Unfortunately, not many companies can think beyond a few quarters.
  • I spend some time on my old FOSS work, without using any AI. I felt a little better. The temptation to use it very strong to use it on boring part but when you touch it, you don’t usually stop there!
  • Creatine supplements have positive impact on my fatigue levels.
  • I love dua: I use it to analyze disk usage, and recently they’ve added a feature to clean up temporary files easily. Oh joy!

Weekly Notes 2026/35

  • I successfully ran Kodagu Marathon 2026! I wasn’t sure if I will be able to finish it this year. I ran my last half-marathon three years ago. I have been feeling completely out of shape for last couple of years: my running pace had been abysmal. But not only I finished the half-marathon but beat my PR by 2 minutes! I should have gotten a hair cut before the run.
    • My manager at Toyota finished with me 💪🏼! He helped me save at least 5 minutes. I saw him after half-way return point. We ran last 4 km together. Fun times!
    • My labmate and friend from Ph.D. times Adiya and his wife Chinmayee joined us for this half-marathon. He finished it in about 2 hours despite not in best of his form. We get to meet his 1.5y old daughter.
    • Kaalu had really good time at homestay near Gonikoppal! She got to eat fresh chicken and eggs which she gulped down like a hungry monster. The homestay manager was extremely pet-friendly and he took extra care of Kaalu (I say almost spoiled her).
  • Kodagu felt very dry this year. The local manager at homestay told me that there is hardly any rain this year. When driving past Brahmagiri range, I noticed no water streams which is a common sight during monsoon time. The Irfu waterfall had very little water.
    • We couldn’t go the waterfall since they don’l allow dogs there. So we played downstream where people come to wash clothes! Ookie loved time in the stream and Kaalu was shirt-scared of deep and noisy water, as usual. But this time, she stood inside the water.
  • Near Mysore, we found a pet-friendly cafe called Queens Coffee. It is ran mostly by women. It had all the good vibes — clean, colours that are easy on eyes, clean toilets, and very pet-friendly. If you pass-by, please visit and support.
  • On lobte.rs, I was complaining about recent increase in LWN subscription prices and how declining Rupee has made it harder for me to continue with “starving hacker” plan. One kind soul on internet bought me a subscription gift. I felt guilty accepting the gift since I can surely afford it. But I didn’t want to threw cold water at the kind gesture. So I accepted the gift whole-heartedly and I donated $35 (starving hacker plan that I used to subscribe) to PARI (https://ruralindiaonline.org).
  • I did some maintenance work for a few FOSS projects especially Smoldyn. The cmake build system major version is 4.x and pybind11was updated to 3.x series. Removed Cygwin support from build system since smoldyn can built on Windows now.
  • I’ve resigned from Toyota this month. I am service notice period. I’ll be joining Progress software from October 1, 2025 as a Principal Engineer on habitat/chef team.

Weekly Notes 2026/34

  • I went through a few interviews and got a couple of offers. I’ll be switching into a Principal Engineer role early Oct. I picked the offer where team gave me the best vibes. I’ve started giving team the highest weightage.
    • I also learnt how to negotiate the offer. I was a little nervous but it went well.
    • Negotiations are most effective if you have some leverage. Or your interviews were great.
  • 📔️Read ‘Designing Distributed Systems’ by Brenden Burns. Its a good book and very readable if you are just starting with them.
  • 🦀️Interesting study https://dl.acm.org/doi/pdf/10.1145/3830438.3830958
    Abstract: (notes in () are mine). We investigate the effects on code quality of the design patterns typestate and newtype in the language Rust, by conducting three case studies… The findings:
    • Typestate improves code faultlessness and testability, but comes at the cost of more boilerplate code and can degrade readability (use macros?). Code with extensive branching logic and many invariants likely benefits most from the pattern.
    • Newtype combined with the “Parse, don’t validate” principle improves code quality at a low cost and prevents invalid states at runtime.
  • 🏃️I’ve finished 620 km of running so far. 4 more months, less than 400km to go to complete 1000km run. My pace is very slow but I don’t mind it. Also looking forward to Kodagu Marathon early next month.
  • I’ve been spending more and more time on rust-lang and rust-for-linux Zulip. Zulip is good but they have kept ‘mark it as resolved’ and ‘mark it as read’ so close that I ended up marking a few thread resolved and annoying a few folks 🥹️.
  • Funny to see LinkedIn added 'Seems like AI slop' to feed options. There is something so bad even LinkedIn is willing to filter!

Weekly Notes 2026/33

  • 🌧️ No rain this week! This is the driest I’ve ever felt in Bengaluru.
  • 📚️”Domain Driven Design” by Eric Evans is an excellent book. I am half-way through. I plan to write a review later. Its written by a practitioner for other practitioner. There are a few powerful ideas in the book which I often find articulated bits and pieces often.
  • 🏃️Kodagu half-marathon in couple of weeks! Not really prepared for it but looking forward.
  • 🥤️Creatine supplements works for me. I’ve been feeling like 2024. For last one year, I’d been very low on energy. Tried multiple things like vit-D and b12 supplements (I was low on them) but only creatine helped.
    • It also brought back my nightly leg cramps. I think APT production is normal in my muscle :).
  • 🏦️I’ve closed my GST registration today. I’ll be accepting a full-time offer soon and closing the consultancy gig this month.

What Kind of Work I Want (in 2026)

  • I like spending time building systems! I build (software) systems because I enjoy it. I enjoy working at places where that is the vibe.
  • I almost always prefer to work remote unless your office is in my neighborhood. I hate commuting: 10 to 20 mins of walking, cycling or train commutes are fantastic. But I don’t see any city where cycling to work is feasible. Quarterly in-person off-sites or similar are OK. Occasional in office sync for white-boarding are fun. I rather work extra couple of hours for free than spend an hour commuting.
  • I prefer feeling average in a very talented team over feeling like a big fish in a small pond, imposter syndrome not withstanding. Stupider I feel talking to your senior engineers about systems, better are the chances I’ll lean towards you. And no, inverting binary tree on whiteboard is not a measure of that.
  • I want to work on something central to the company. I enjoy “pressure” of ownership, it brings the best out of me.
  • I don’t mind extending legacy systems but I don’t like maintaining them.
  • I do not care much about doing greenfield or fancy work or building the most interesting part of the product. I will happily build CI pipelines or a boring API, write documents, and do performance improvements if that’s what needs doing.
  • These days, I am learning how to use AI. I like what it has to offer but I am also very concerned about both organizational and individual skill-rot. If you have a culture of toxen-maxxing, I am out.
  • I want a low-process management style that trusts me to do my job. I act like a grown-up (as far as my work is concerned) and would like to be treated as responsible adult. A company that takes Agile software development very seriously or has no process at all is unlikely to be a good fit for me.
  • I like teams that articulate its engineering values clearly e.g. do we value stability over speed? In other words, how do you make hard decisions.

Weekly Notes 2026/32

  • 🌧️ No proper rain this week either. The Cauvery catchment areas had some good times with rain which is very fortunate. This summer may be pretty painful for Bengaluru if the water reservoir doesn’t fill up fully!
  • I bought physical copy of “Domain Driven Design” By Eric Evans. I sincerely hope more folks read this book. This kind of books are even more relevant in this LLM generated code age.
  • Talking of LLM generated code, I am not surprised to read this blog post by Raymond Chen on something very fundamental to merge requests. LLM are straining and breaking some well established social contracts (i.e. reader spending much more time than writer!). It is good to often remind that there are still humans at the other side of table.
  • I think fil-c has a bright future: I really liked this article https://domenkozar.com/2026/08/13/i-want-extern-fil-c/. It solves some very practical problems in a pragmatic ways.
  • Bookmark this if you are interested in QR codes.
  • I learnt about this thesis “Making reliable distributed systems in the presence of software errors” by Joe Armstrong in one of Rich Hickey talks. Planning to read this this week.

Weekly Notes 2026/31

How good are LLM agents? Depends on whom you ask!

Depending on whom you ask, you get very different answers.

Depending on whom you ask, you get very different answers. I’ve been noticing a pattern.

If you ask a generalist who is B+/A- on any job you throw at them, they are likely to find LLMs very useful.

If you ask a specialist who has spent a lot of time doing a few things and has deep expertise in them, they are more likely to call LLMs garbage.

I think both of them are right.

My own experience with LLMs is that they are very good at doing “average”. Being a generalist, I only know a few things very well (learnt during my Ph.D. and startup), and I can see LLM sloppiness in those areas. But for most other things, I’ve no way to evaluate LLM output—a plausible answer looks as good as a correct one.

I totally understand when Zig maintainers or database developers ban the use of LLMs. I also understand when a good application developer, who understands some part of her system very well, relies heavily on LLMs for other important jobs like adding a demo site, integration, or a front-end in a language she doesn’t know.

What about enterprise and large organizations? If their products are technically “average” like a social media client, then I see some advantage of using coding agents (though I’m not sure if long-term costs are worth it). If their product has critical components that require very specialized knowledge — such as compilers, database engines, or encryption algorithms — I’d be running away from them if I get to know they are trading their hard-earned tribal knowledge for short-term, LLM-induced gains.

Async Rust: An example of future cancellation

Spooky action at distance when using async Rust.

Read the following code and guess the output.

It has two concurrent tasks. The first task sets a cancellation token after 150ms. The second task accepts a variable initialized to 0, increments it twice with 100ms sleeps in between, and finally resets it to 0.

Then we have a tokio::select! that returns the first branch that completes, and cancels the second branch.

use std::sync::{Arc, Mutex};
use tokio_util::sync::CancellationToken;
#[tokio::main]
async fn main() {
let cancellation_token = CancellationToken::new();
let token = cancellation_token.clone();
let cancelled = tokio::spawn(async move {
// X1
tokio::time::sleep(tokio::time::Duration::from_millis(150)).await;
token.cancel();
});
let a = Arc::new(Mutex::new(0));
tokio::select! {
_ = cancelled => {
println!("cancellation token is set.");
}
_ = long_task(a.clone()) => {
}
};
println!("a ={}", a.lock().unwrap());
}
async fn long_task(state: Arc<Mutex<i32>>) {
println!("long task started...");
{
let mut lock = state.lock().unwrap();
*lock += 1;
}
// Y1
tokio::time::sleep(tokio::time::Duration::from_millis(100)).await;
{
let mut lock = state.lock().unwrap();
*lock += 1;
}
// Y2
tokio::time::sleep(tokio::time::Duration::from_millis(100)).await;
{
// clean up (reset to 0)
let mut lock = state.lock().unwrap();
*lock = 0;
}
println!("long_task has ended.");
}

If you guessed an answer other than 2, you need to read about cancellation safety. The Tokio documentation also talks about it extensively.

Why is the output 2?

Because at 150ms, the spawned task completes, causing tokio::select! to select that branch and immediately drop the long_task future before it can reach the cleanup step. Note that long_task is dropped not because it checks the CancellationToken, but because tokio::select! automatically drops all non-winning futures.

This behavior can be dangerous: what if the remaining code was cleaning up a resource (like running a database cleanup query or releasing a lock) rather than resetting a variable? You could leave your system in a broken state.

Execution Sequence

  • 0 ms: long_task starts, sets a = 1, and yields at Y1 (sleep 100ms).
  • 100 ms: Y1 finishes. long_task sets a = 2 and yields at Y2 (sleep 100ms).
  • 150 ms: X1 finishes. The cancelled task completes, and its JoinHandle resolves.
  • 150 ms: tokio::select! receives the completed branch and drops long_task while it is sleeping at Y2. The final cleanup block is never executed, leaving a = 2.

Weekly Notes 2026/29

This week, Digit Insurance pulled a “scam” in me. It almost succeeded! They sent the following WhatsApp message.

I bought this car from Spinny almost a year ago. Under the impression that Digit is my car insurer, I went ahead and renewed the policy pending KYC and pre-inspection video. KYC was easy to do using PAN but I could not login in their app (that’s a different story). Frustrated, I cancelled the policy, refund pending.

So where is the scam? First, after wasting an hour on their app, when I double checked, my insurance is not expiring on Aug 3, not in next 5 days as they mentioned. And the insurer is United Insurance company, not Digit! Should’ve known better since they used the fear “fine of 2000” etc in the message to nudge me click!

I now understand that they advertise heavily in IPL and a famous cricketer is their scammer-in-chief or brand ambassador or whatever. Enjoy your cut, motherfucker!

I was “saved” by AI slop (refund is still not in my bank though). Their app didn’t let me login for inspection because my phone number starts with 91 and it confused it with ISD code (+91 part) and complained that mobile number is not complete but also won’t let me type more than 10 digits 🥁️🤣️. I had similar experience with these websites/apps when I was purchasing life-insurance. I ended up buying from LIC because their PHP website still works. Perhaps I should start using the govt. entities, they don’t seem to change their color-scheme and look & feel every other week and they sites seems to work better than most fancy looking websites I’ve lately used.

  • I had some recognition at work by my peers 🥹️. Its nice to be appreciated by your peers you appreciate. There is nothing more to the “career” IMO.
  • At work, there is a hard limit on AI tokens. I burned my limited monthly quota in a week or two and then went through withdrawal symptoms 🥹️. I’ve started writing some code by hand now. Most of the time, I do not ping anyone when I have a doubt about code-base. LLM works great because a lot of people invested time and effort in writing docs and great MR reviews.
  • The expectations from AI is a bit more saner these days but I don’t think the AI psychosis is going away anytime soon. We had an internal hackathon where AI was the judge! So did Kaggle last week.
    • I am yet to see AI increasing revenue per head or keeping folks focused enough to finish it off. There are some productivity gains here and there. More people are now talking about it.
  • I learnt about this ecological event in Mizoram last week. Every few decades mass blooming in their forests causes a rodent boom, and devastation to crops.
  • I filed my ITR for this year. I think finally I know the process. I created a Notion template to use next year. I also filed my GST returns. The GST website is not bad, it is not as good as ITR website though.

Weekly Notes 2026/28

  • I learnt the Boko Haram has been using AI and killing themselves.
    > We saw in a movie how motorcycles can jump over bridges. We used AI to learn how to do this. We gave it information, like what motorcycles we use and the distance we need to jump and so on and it gave us steps on what we have to do. We practiced a lot and kept asking questions. We dug holes and filled them with broken glass and fire to practice. 18 of us died in the process. Eight of us managed to do it. The next time we attacked, we could jump.
  • I watched a few videos of Casey Muratori talking. Nice guy.
  • This season for Rick & Morty is excellent. I enjoyed the episode 9, Mortgully, thoroughly 👍️.
  • I don’t follow football much. I read the Donald Trump got Fifa to reverse a red card! Then learning that USA lost to Belgium was pretty nice. Donald Trump has lowered the bar so much as even lowest among the lowest don’t compare to him when it comes to pettiness.
  • This week was busy at work. I am participating in an internal competetion.

Weekly Notes 2026/27

  • The popular version of the Dunning-Kruger effect says that stupid people overestimate their capabilities. This is true, but the effect is much more general than that. It says if your expertise level is different from the average, then you judge the “average competency” differently. So if you have above-average expertise, you might overestimate what the average competency is. Folks who had above-average education tended to overestimate what average education looks like (and vice versa), and so on.
  • Embassy is a great project. I am porting a blocking C firmware to non-blocking firmware using Rust, and it is a joy to write in. I hope things are still as good as now when I need to take a not-so-happy path. The other option was using ROS or FreeRTOS, but I am not very excited about writing in C or C++ or even Python.
  • Things are getting interesting at work. The AI pricing is increasing, token usage is being curbed, and folks are demanding their dosage back.
  • All sync communication like Slack must be banned around serious work unless they are moderated by grumpy old people who get heart attacks every time someone shoots 10 notifications when one would have done :-). Go back to emails, please! Put effort into writing and reading. And no, I don’t mean write in Victorian English or have perfect grammar.
  • I had to go see the mechanic about my Tata Nano. It’s been 8 months since the car went to his garage. Man, he can lie with a straight face! I may have to explore legal options from next month onwards.
  • The monsoon has arrived in Bengaluru, but rains are still deficient. Lantana plants in my neighborhood are doing great, sadly for local flora.
  • Yesterday, I had a chat with my neighbor. He is a retired bus driver from KSTRC. Nice guy and very helpful. Old people love to talk about plot price, house price, cars, and other stuff. He has experienced an automatic car in Bengaluru traffic and is now planning to sell his manual.
  • Today, I filed my ITR and GST returns. I am getting a bit used to them now. Both government portals are actually fine. The ITR portal is pretty good, and the GST portal works after some practice. This year, I had to file ITR2 (due to some stock selling/buying). It was easy to get the details from the CSDL repository and add them to the form. It takes a while to learn the acronyms and abbreviations. Last year notes in Notion helped.
    • I thought of hiring a CA but I didn’t see much value. They save the hassle of knowing how to file ITR, which I was keen on learning anyway. And to file ITR by CA, I need to collect all data and share it with them, which would take the same amount of time. So what’s the point? Perhaps they know something that Reddit/Gemini doesn’t about saving taxes?

Weekly Notes 2026/26

  • I got my 3D printer back from my cousin. He stopped using it for a few years. He sent it back to me when he had to move. I’ve been printing a lot of useless stuff, like the one below.
  • I have been reading “Medieval India 1” (edited by Irfan Habib). I found a few papers in it quite interesting — especially on social mobility and travelers accounts of Hindu religious practices at many famous places; many of them don’t exist anymore. Perhaps I will write a review later. Mr. Habib has an excellent, readable body of work on Indian history. Indian history was a very emotional subject when I was in college. Mere mention of a historian was likely to invite accusations of partisanship. I’ve mostly read what people would call “leftist” historians. Mr. Habib, D. D. Kosambhi, etc., were/are my favorites. Though I don’t touch Romilla Thapar anymore. I don’t like her as a person anymore after her stint at EPW.
  • The economy and the reality are catching up with the AI usage at work. Costs have been rising, and token-maxxing by a few is burning through the monthly budgets in a week. Given its effect on memory prices, I am a bit glad that I bought a Linux machine a few years back, though I didn’t need any. It is quite a weird situation; the promise of AI is replacing labor and jobs, then who’s going to buy it, and what is its point other than being a tool of economic destruction?
  • Congrats to Ireland and New Zealand for their wins over India and England. I didn’t watch any of those matches.
  • The government pulled a statistical sleight of hand to show the rural wage has increased by 13%! This data will go into official statistics soon.
  • My favorite podcast, In Our Time, continues after its host retired from the show :-). I’ve listened to a few new episodes. It will take some time to get used to the absence of Mr. Melvyn Bragg. Content produced by the BBC is still one of the best in the world, but this podcast had been out of this world.
  • Work was very slow this week. I also took a few technical interviews for a client who has been using AI to screen resumes. I am not a fan of using AI in the interview process, but it is what it is. Earlier, I didn’t like structured interviews, but now I prefer them since comparison across becomes a bit easier. I don’t have anything against unstructured interviews if you practice beforehand and make sure it doesn’t derail candidates. Now I wish the candidate also practiced interviews, especially how they answer the questions; please get to the point as soon as possible.
  • Something is perhaps churning in the PHP community: RFC for geneic was rejected! And I saw a talk about the RFC process. I think it is usually a VERY GOOD idea to make the lives of programmers easier.

Weekly Notes 2026/25

  • 📚️I ordered a few of Prof. Andre Beteille books. He dies a few months back. He is perhaps the only sociologist that I could read. MN Srinivas’s “A remembered village” was also a great read.
    • I also bought a few books on software engineering in general, especially on refactoring, design patterns, and architecture. Books on software engineering becomes outdated pretty soon. I prefer blog posts or papers.
  • 🥭️ The peak mango season in Bengaluru is over!
  • 🏏️I think I’ve lost all interest in cricket. I can no longer watch a full game, even watching highlights takes some effort. While the heart misses the test matches but I don’t have that much of time or attention. Then the T20, the “pornography of cricket”, fun as it is, has already killed neural circuitry that appreciated delayed-gratification required for test cricket. Good riddance, perhaps!
  • 🤖️I learnt that Hyundai bought Boston Dynamics a few years back (80% stake) and now finished the deal by buying the remaining stakes. Automotive industry is betting on “physical AI”. Toyota, where I currently work, also have significant focus on physical AI.
  • 🛵️ It was a WFO week at work. I think I should once a week to office just to ensure that bike is in good shape. My office bag content remain relevant to seasons. I got caught in rain and I didn’t have my rain jacket in my bag.
  • This year is going to be most tumultuous as far as “coding” is concerned. Either we’ll figure it out how to use AI properly. Or I’d have gone through the stage of griefs and reached acceptance by then. I’ve been thinking about AI or pushing back on it till December this year.