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.
El Libro de Urantia es una de las obras literarias, filosóficas y espirituales más extensas y complejas del siglo XX. Desde su publicación original en 1955, ha despertado el interés de millones de lectores en todo el mundo que buscan respuestas profundas sobre el origen del universo, el destino de la humanidad y la naturaleza de Dios.
Debido a su densidad conceptual, leer El Libro de Urantia de principio a fin como si fuera una novela suele ser abrumador. Te recomendamos seguir estos consejos:
El Libro de Urantia es un texto religioso y filosófico que fue publicado por primera vez en 1955. Presenta una cosmología y una teología que intentan explicar la naturaleza del universo, la existencia de Dios, y el papel del ser humano en el esquema universal. El libro consta de 187 capítulos y más de 1.700 páginas, ofreciendo una visión detallada de la creación, la evolución de la vida en la Tierra, y el destino final de la humanidad.
: Presenta una visión optimista del futuro, con la humanidad avanzando hacia una era de paz, armonía y entendimiento universal.
El Libro de Urantia: Guía Completa para Descargar el PDF Gratis y Comprender sus Enseñanzas
Publicado originalmente en 1955, este extenso volumen de más de 2,000 páginas afirma ser una revelación entregada por seres celestiales para expandir la conciencia cósmica de la humanidad. ¿Qué es El Libro de Urantia?
Descargar es una excelente manera de explorar una filosofía que busca el progreso personal y social. Ya sea que busques respuestas a preguntas existenciales o una nueva perspectiva sobre la espiritualidad, este libro ofrece una perspectiva única y profunda sobre nuestro lugar en el cosmos.
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.