Why I Write

I first blogged on 24 July 2011 and I've been blogging on and off for the past decade. There were a few years when I felt bad about not writing more than a few times. I also felt great when old friends or new acquaintances told me they liked a few of my blog posts. When I ask myself now why I wrote what I wrote in the past, I realize that I don't have a concrete answer. Mostly, I wrote about information that I had just gained that I found interesting. Once or twice I wrote because I thought it would help my professional career. Over the past 3 months, I wrote because it was part of my course work. Briefly, I wrote because I felt a need to explain complicated scientific concepts to the general public.

In 2023, I'm trying to be mindful about what I do and consciously ask myself why I do what I do.

And I write because it helps me think. It is incredibly helpful to me to occupy myself for a meaningful amount of time with a piece of information, digest it, put it into words and move those words around a few times. I've heard this from a number of people and it definitely holds true for me. I think that's a damn good reason to write.

I also write because others writing helped shape my own. I've spent most of my 20s reading everything I could find on the internet. What I read helped me understand cultures and religions other than my own, it helped shaped my thought process and it helped me appreciate quality writing. I would not be the person that I am today if I hadn't read the hundreds of thousands of words that people put on the internet for everyone to read freely.

I write because it helps me process and because it might become a part of someone else on the internet.

Popular posts from this blog

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

Talk proposals submitted in Dec 2024

So far, I've submitted talk proposals for three FOSS conferences. See the list of conferences and my proposals below. I'm expecting to submit a couple of more proposals for PyConf Hyderabad - a talk proposal on the GIL-ectomy (that I presented internally for a client), a talk proposal about the fossunited.org platform that we have been building at FOSS United, and a workshop proposal on the Frappe Framework that powers fossunited.org! Why am I sharing this here? Because not all of my talk proposals get accepted at conferences but that doesn't mean that the ideas or talks are useless. In fact, I've been wondering for a couple of years now that if a talk proposal gets rejected, I should just livestream the talk on my own personal YouTube channel instead of letting the idea die. This post is me taking one step in that direction. PyConf Hyderabad by HydPy community - 22-23 Feb 2025  DEVCONF India by Red Hat India - Feb 28, March 1 2025 FOSSMeet'25 by FOSS Cell NITC -...
Read more