Software Engineering The Soft Parts

In "Software Engineering - The Soft Parts" Addy Osmani shares lessons from his first 10 years at Google on the "soft skills" that can help engineers become effective and scale their effectiveness. This guidance should help junior, mid-career and even senior developers move forward, deal with changing technology, and navigate building non-trivial systems. Becoming a good engineer is about collecting experience. Each project, even small ones, is a chance to add new techniques and tools to your toolbox. Where this delivers even more value is when you can solve problems by pairing techniques learned on one project with tools learned working on another. This short book tries to capture what the "soft skills" are and how they can all add up.

In the Guide to the Software Engineering Body of Knowledge (SWEBOK(R) Guide), the IEEE Computer Society establishes a baseline for the body of knowledge for the field of software engineering, and the work supports the Society's responsibility to promote the advancement of both theory and practice in this field. It should be noted that the Guide does not purport to define the body of knowledge but rather to serve as a compendium and guide to the knowledge that has been developing and evolving over the past four decades. Now in Version 3.0, the Guide's 15 knowledge areas summarize generally accepted topics and list references for detailed information. The editors for Version 3.0 of the SWEBOK(R) Guide are Pierre Bourque (Ecole de technologie superieure (ETS), Universite du Quebec) and Richard E. (Dick) Fairley (Software and Systems Engineering Associates (S2EA)).

Today, software engineers need to know not only how to program effectively but also how to develop proper engineering practices to make their codebase sustainable and healthy. This book emphasizes this difference between programming and software engineering. How can software engineers manage a living codebase that evolves and responds to changing requirements and demands over the length of its life? Based on their experience at Google, software engineers Titus Winters and Hyrum Wright, along with technical writer Tom Manshreck, present a candid and insightful look at how some of the world’s leading practitioners construct and maintain software. This book covers Google’s unique engineering culture, processes, and tools and how these aspects contribute to the effectiveness of an engineering organization. You’ll explore three fundamental principles that software organizations should keep in mind when designing, architecting, writing, and maintaining code: How time affects the sustainability of software and how to make your code resilient over time How scale affects the viability of software practices within an engineering organization What trade-offs a typical engineer needs to make when evaluating design and development decisions

In this book, you will learn design patterns, performance and rendering patterns for building high-quality web applications using modern JavaScript and React. Patterns are time-tested templates for writing code. They can be really powerful, whether you're a seasoned developer or beginner, bringing a valuable level of resilience and flexibility to your codebase. Whether it's better user-experience, developer-experience or just smarter architecture, the patterns in “Learning Patterns” can be a valuable consideration for any modern web application.

Provides a practical modern guide to delivering high-quality images on the web -- from formats and compression to delivery and maintenance. The book focuses on what matters: modern approaches to image compression and image delivery, practical tools and techniques to automate optimization, responsive images, current and emerging image formats, how browsers load, decode and render images, CDNs, lazy-loading, adaptive media loading and how to optimize for Core Web Vitals.

Whether you’re a student, tech recruiter or simply want a change of career, this book will cover many areas of software engineering, including: - Confusing terminology - The type of job roles available - Career progression with advice on how to break into the field - The recruitment process - Insight into some of the most popular programming languages, libraries, tools and frameworks used in the industry today. You will get a feel and basic understanding of the tech that is out there. It may give you a kick-start and the motivation to pursue a career or hobby in software engineering yourself. The book is broken into four parts: 1. The first part focuses on the software industry ranging from the types of roles out there, recruitment, and what a typical day as a software engineer looks like. 2. The second part is centred around programming and testing terminology used in the industry. 3. The third part is a collection of programming languages used by software engineers. This isn’t an exhaustive list, but a majority of the most common languages used commercially today. 4. The fourth part is focused on web-related libraries and frameworks. No longer will you give a long blank stare at those technical individuals in the office, trying to figure out what on earth are they talking about. I've had those stares before...If you can put up with the occasional lame joke, then pick up a copy today.

This proceedings consists of selected papers presented at the International Conference on Computer Science and Technology (CST2016), which was successfully held in Shenzhen, China during January 8–10, 2016. CST2016 covered a wide range of fundamental studies, technical innovations and industrial applications in 7 areas, namely Computer Systems, Computer Network, Security, Databases and Information Systems, Artificial Intelligence and Multimedia, Theory and Software Engineering and Computer Applications. CST 2016 aims to provide a forum for researchers, engineers, and students in the area of computer science and technology. It features unique mixed various topics in computer science and technology including big data, system architecture, hardware and applications. CST 2016 attracted more than 300 submissions. Among them, only 142 papers were accepted in to the conference after a stringent peer review process.

In my first few years as a developer I assumed that hard work was all I needed. Then I was passed over for a promotion and my manager couldn't give me feedback on what areas to improve, so I could get to the senior engineer level. I was frustrated; even bitter: not as much about missing the promotion, but because of the lack of guidance. By the time I became a manager, I was determined to support engineers reporting to me with the kind of feedback and support I wish I would have gotten years earlier. And I did. While my team tripled over the next two years, people became visibly better engineers, and this progression was clear from performance reviews and promotions. This book is a summary of the advice I've given to software engineers over the years - and then some more. This book follows the structure of a "typical" career path for a software engineer, from starting out as a fresh-faced software developer, through being a role model senior/lead, all the way to the staff/principle/distinguished level. It summarizes what I've learned as a developer and how I've approached coaching engineers at different stages of their careers. We cover "soft" skills which become increasingly important as your seniority increases, and the "hard" parts of the job, like software engineering concepts and approaches which help you grow professionally. The names of levels and their expectations can - and do! - vary across companies. The higher "tier" a business is, the more tends to be expected of engineers, compared to lower tier places. For example, the "senior engineer" level has notoriously high expectations at Google (L5 level) and Meta (E5 level, ) compared to lower-tier companies. If you work at a higher-tier business, it may be useful to read the chapters about higher levels, and not only the level you're currently interested in. The book is composed of six standalone parts, each made up of several chapters: Part 1: Developer Career Fundamentals Part 2: The Competent Software Developer Part 3: The Well-Rounded Senior Engineer Part 4: The Pragmatic Tech Lead Part 5: Role Model Staff and Principal Engineers Part 6: Conclusion Parts 1 and 6 apply to all engineering levels, from entry-level software developer, to principal-and-above engineer. Parts 2, 3, 4, and 5 cover increasingly senior engineering levels and group together topics in chapters, such as "Software Engineering," "Collaboration," "Getting Things Done," etc. Naming and levels vary, but the principles of what makes a great engineer who is impactful at the individual, team, and organizational levels, are remarkably constant. No matter where you are in your career, I hope this book provides a fresh perspective and new ideas on how to grow as an engineer. Praise for the book "From performance reviews to P95 latency, from team dynamics to testing, Gergely demystifies all aspects of a software career. This book is well named: it really does feel like the missing guidebook for the whole industry." - Tanya Reilly, senior principal engineer and author of The Staff Engineer's Path "Spanning a huge range of topics from technical to social in a concise manner, this belongs on the desk of any software engineer looking to grow their impact and their career. You'll reach for it again and again for sage advice in any situation." - James Stanier, Director of Engineering at Shopify, author of TheEngineeringManager.com