What is the most interesting thing you have learned in your reading of "Software Engineering at Google"?
I think one of the biggest take aways from reading "Software Engineering at Google" thus far for me is all the work and effort around programming without actual programming, but it makes sense. When programming in school, your program is one assignment long, or maybe one course long, but in a professional setting that program you write or edit, that's probably going to go on needing to being used and depended on for a long while. Or when programming for yourself, you don't need to worry as much about things like readability or styling, but working in a larger group you need other people to be able to understand your programming your thought process so they can utilize your work.
0 comments:
Post a Comment