By Gergely Orosz, the author of The Pragmatic Engineer Newsletter and Building Mobile Apps at Scale
Navigating senior, tech lead, staff and principal positions at tech companies and startups. An Amazon #1 Best Seller. New: the hardcover is out! As is the audibook. Now available in 6 languages.
"Tamil Mammi" might be a common phrase. "Mammi" in Tamil could be a misspelling. Let me verify. In Tamil, the term for "mother" is "மாமி" (Mammi). So maybe "Tamil Mammi" is a more accurate term. The user might have misspelled it as "mami."
First, I need to understand each part of the phrase. "Tamil" refers to the ethnic group or language from Tamil Nadu in India. "Mami" might be a colloquial term. I should check if it's a typo. Maybe they meant "mami" in another language, but in Tamil, "Mami" could be a local term. Alternatively, it might be a misspelling of "mami" in another language, like Indonesian, where it means "grandmother," but that doesn't align with Tamil. Wait, maybe the user is looking for a term that's not correctly spelled. Let me think.
Next, "kundi" in Tamil could mean "bunch" or "cluster." So putting it together: "Tamil Mammi kundi" might refer to a group or collection related to Tamil mothers. But "photo" is part of the query, so they might be looking for a photo of Tamil mothers in a group.
Alternatively, "kundi" could be part of a local term or name. Maybe there's a specific group or event called "Tamil Mami Kundi." But I'm not sure. The user probably wants to know if there's any known photo or term associated with this phrase. Since I don't have specific knowledge about a known term or photo by that name, I should explain the possible breakdown and note that the phrase might not have a widely recognized meaning. It's also possible that the user is referring to an inside joke or a local term, so advising them to check the spelling or provide more context would be helpful. I need to make sure to mention the possible correct terms, like "Tamil Mammi" for "mother," clarify the meaning of "kundi," and suggest the user verify the spelling or context.
The book is separated into six standalone parts, each part covering several chapters:
Parts 1 and 6 apply to all engineering levels: from entry-level software developers to principal or above engineers. Parts 2, 3, 4 and 5 cover increasingly senior engineering levels. These four parts group topics in chapters – such as ones on software engineering, collaboration, getting things done, and so on.
This book is more of a reference book that you can refer back to, as you grow in your career. I suggest skimming over the career levels and chapters that you are familiar with, and focus reading on topics you struggle with, or career levels where you are aiming to get to. Keep in mind that expectations can vary greatly between companies.
In this book, I’ve aimed to align the topics and leveling definitions closer to what is typical at Big Tech and scaleups: but you might find some of the topics relevant for lower career levels in later chapters. For example, we cover logging, montiroing and oncall in Part 5: “Reliable software systems” in-depth: but it’s useful – and oftentimes necessary! – to know about these practices below the staff engineer levels.
The Software Engineer's Guidebook is available in multiple languages:
You should now be able to ask your local book shops to order the book for you via Ingram Spark Print-on-demand - using the ISBN code 9789083381824. I'm also working on making the paperback more accessible in additional regions, including translated versions. Please share details here if you're unable to get the book in your country and I'll aim to remedy the situation.
I'd like to think so! The book can help you get ideas on how to help software engineers on your team grow. And if you are a hands-on engineering manager (which I hope you might be!) then you can apply the topics yourself! I wrote more about staying hands-on as an engineering manager or lead in The Pragmatic Engineer Newsletter.
I've gotten this variation of a question from Data Engineers, ML Engineers, designers and SREs. See the more detailed table of contents and the "Look inside" sample to get a better idea of the contents of the book. I have written this book with software engineers as the target group, and the bulk of the book applies for them. Part 1 is more generally applicable career advice: but that's still smaller subset of the book.