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.
So the paper can have two angles: cultural translation and technical subtitling. But the user probably wants a focus on the translation aspect. I should prioritize that. Maybe combine both briefly to show interdisciplinary approach.
I need to make sure the paper is original and adheres to academic standards. Maybe focus on a specific aspect like the translation of cultural terms in the drama's subtitling process. Since it's a TV show, analyzing specific scenes where subtitles played a crucial role in conveying the intended message could be useful.
Need to verify if there's any existing academic work on this specific drama's subtitling. Since it's a specific example, the paper might focus more on case study analysis. Alternatively, if there's no prior work, the user might be starting a new research topic here. ssis787 eng sub my abhorrent fatherinlaw720
Potential challenges: Ensuring that the drama is appropriately referenced, addressing any copyright issues if using content from the show. Also, finding primary sources like subtitlers' interviews or user feedback on English subtitles.
I should consider angles like how subtitles transfer cultural elements, differences in humor or idioms between Korean and English, the technical process of adding subtitles to a 720p video, or the impact of such localization on the global audience. Also, maybe the role of streaming platforms in distributing dubbed/subtitled content. So the paper can have two angles: cultural
Possible structure: Introduction, Literature Review, Methodology (case study of the subtitling of this drama), Analysis (cultural adaptation, technical aspects, audience reception), Conclusion.
Putting it all together: The user is likely looking for an academic or technical paper discussing the English subtitling of the Korean drama "My Abhorrent Father-in-Law", specifically the version with ID ssis787 at 720p resolution. But why would someone want a paper on that? Maybe analyzing the localization process, subtitling challenges for cultural nuances, or technical aspects like video resolution affecting subtitle presentation. Since it's a TV show, analyzing specific scenes
Also, considering the technical aspect, encoding subtitles in a 720p video (ssis787) might involve technical details like subtitle file formats, synchronization issues, etc. However, that might be more niche and perhaps not as interesting as the cultural translation part.
SSIS could refer to SQL Server Integration Services, which is a Microsoft tool for data integration and workflow. The numbers 787 and 720 might be versions or specific identifiers, like the difference between DVD (720p) and Blu-ray (1080p) resolutions. "Eng sub" usually means English subtitles. "My abhorrent father-in-law" is a Korean drama title, probably.
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.
