Woods A. Rules for Software Development: A Book About Professionalism

Independently published, 2021. — 114 p. — ISBN 978-1838472108.Software engineering isn’t just about writing code. It’s about much much more than that. Rules for Software development presents the reader with a 360° view of what it takes to truly be a professional software engineer. In today’s software industry, being proficient in the development of code is the baseline of a software engineer role. The most prominent engineers are those who understand software principles and patterns and who also understand soft skills and communication.This book will give you insight intoWhy you need to say NoHow to work with multiple stakeholders
Why micro-changes make a big impact
What technical excellence is expected of you
How to grow your own careerA handbook of career-changing advice and insightful real-world experience. - Dr. Jenny Munnelly, Senior Lecturer, Technological University Dublin...a succinct guide that every software developer must read regardless of programming language or experience - Paul Flanagan, Principal Software Engineer, Danalto...provides the reader with a road map to longevity and efficacy as a professional in the ever-changing tech industry landscape - Naomi Freeman, CTO Lingu...an invaluable book for IT professionals - Santiago García da Rosa, CTO, NowportsTeam Player
Communication
Keep Commits Small
Write Meaningful Commit Messages
Keep It Clean
Avoid Comments
Write Clean Tests
Do Code Reviews Properly
Boy Scout Rule
YAGNI
Always be Ready to Refactor
Share your Knowledge
Know When to Help OutWorking With People
Know the Time-Cost-Quality Triangle
Work with Stakeholders
Be Honest
Speak Up
Learn to say No
Respect Meetings
Encourage Better Meeting TimesTechnical Excellence
Understand the Fundamentals
Know SOLID
Know Design Patterns
Micro Changes = Macro Differences
Question Your Architecture
Be the Technical Knowledge Base
Be Selective with Libraries
Don’t be Afraid to Use Libraries
Strive for Technical Excellence
Strive for the Best Solution
Stick to the Process
Bad Code Costs Money
You Have Final CutProcess
Understand Agile
Code Reviews Are Still In-Progress
Be Involved in the Release Process
Be Involved in the Testing ProcessGrow Yourself
Use Slack Time Wisely
Continue Learning
Learn to Test
Consider Your Environmental Impact
How Do You Want to Help People
Smile