A new blog - childrens book "reviews"

I put the "reviews" in quotes because it's less review-y and more comment-y. Writing is my "theme" for Q1 2025 and I'm pretty happy about the fact that I've started a new blog about the childrens' books that our lives revolve around thanks to Luffy -rahulandluffyread.blogspot.com. I've written 20 posts this month - some of the books came into our lives this month and others have been in our lives for more than an year.

I realize that I'm happy writing "slice of life"-style posts instead of writing strict review-style posts. For reasons I can't describe, I was interested in writing review-y posts about books in my life but I was never able to do justice to the format. To me, a review needs additional work from me to look into critique of the book, and I barely have time to put together a blogpost, so the posts just stay in the "drafts" folder, never to be published. This is a surprising revelation to me and it only occurred after writing 20 posts on a wide variety of books. I think this is the direction I will be taking when I talk about books now - how did the book end up in my life, what did I feel as I was reading the book, how did I relate (or could not relate) to what is in the book, and what are the long-term effects of the book on my life, if any.

The frequency of posts on this blog will likely remain low - but I hope to maintain a regular cadence over on the childrens' books blog. Luffy and I will likely continue looking at new books throughout Q1 2025 so it should be doable.

Popular posts from this blog

Farewell to Enthought

I started my professional career at Enthought , at the Pune office in India, on Feb 29, 2016. Over the course of eight long years, I spent time at the Austin office in the US, the Cambridge office in the UK, and I worked remotely from India. I was let go on March 27, 2024 . I had an unbelievably great time. I had three amazing mentors - Pankaj Pandey, Senganal Thirunavukkarasu, and Mark Dickinson. Pankaj mentored me in my first year at Enthought. I started paying attention to the craft of software after working with him. Senganal started mentoring me in my second year at Enthought, and continues to mentor me, even after the both of us have moved on from Enthought. He instilled professionalism in me, ensuring that the code I wrote produced precise scientific results, and that I tackled the known unknown aspects of a project first, to ensure timely communication about project progress. I was eager to manage people at the time and Senganal made me realize that I didn't want to manage ...
Read more

Arxiv author affiliations using Python

So, I wanted to get author affiliation information from papers on arXiv. arXiv provides with an API to bulk query their database and get information. Following that, I look for the attribute 'arxiv:affiliation' in the html data. Here's the code - import urllib from BeautifulSoup import BeautifulStoneSoup   url = 'http://export.arxiv.org/api/query?search_query=all:astro&start=0&max_results=1000'   data = urllib.urlopen(url).read() soup = BeautifulStoneSoup(data) #print(soup.prettify()) #list = soup.findAll('arxiv:affiliation') #for i in range(len(list)): #        print list[i].contents   test = [tag.string for tag in soup.findAll('arxiv:aiffiliation')] Now, the problem I'm having is that I'm getting affiliation of all authors which I want to split into sets of affiliations of authors of a paper, which I'm stuck on at the moment. Once I get that part, I can move on to the next part of this pet project, displaying these...
Read more

You need to start writing Architecture Decision Records

If you write software, you need to start maintaining Architecture Decision Records (ADRs). ADRs roughly fall into the category of Developer Documentation. They aren't aimed at the Users of the software. Instead, they are aimed at the developers and maintainers of the software. They usually contain information about the layout of the package and what the code does. ADRs, in this context, are an absolute necessity. By definition, ADRs are simply a Record of a Decision that has an impact of the Architecture of the application. In fact, Any meaningful technical decision made in a software project, irrespective of whether it has an impact on the architecture of the application, needs to be documented. I first came across ADRs in Chapter 17 of Fundamentals of Software Architecture book. A few of us (at Enthought ) read this book earlier in the year and ADRs are one of the things that we took away from the book. You can find more information on ADRs here and here . Here's what the f...
Read more