This is a knowledge project to document and share things in tech that I find useful for myself and the teams that I work with. The things which help in bettering the decisions that we take, and the things which help us deliver better software.
While we’re (almost) building better softwares and building them in better ways than we were doing several years ago, we haven’t really harnessed the full potential of various literatures and researches available at our disposal as we could have; especially for the industry which closely associates itself with engineering (software engineering). We continue to rely upon anecdotes, past experiences, frameworks, and on-the-fly thinking in our decision making. These are definitely not bad heuristics. But relying only upon them is certainly bad.
This newsletter uncovers philosophies, and research on Software and its Makers
What you can expect from the newsletter:
Paper Club : I make it a habit to read one academic/research paper every fortnight. This is the space where I put down my summary, annotations, and takes on them. Infrequently, I also host physical/virtual paper reads with small groups.
Systems Thinking. Why Systems Thinking? How to get started with it. Case studies and analysis using systems thinking. Archetypes and heuristics for engineering leaders, architects and staff engineers.
Review of talks and literature related to software and its makers
Essays on software engineering and culture/methodologies around it.
Learnings from various books that I read. They might not always be technical books, and my musings might not directly correlate with software engineering. I find good inspirations from these alternative readings and posit that they might be useful for you too.
