1. Pushing code and being unaware of the build system that does anything else.
2. Unable to comprehend that there can be teams/companies where some products are written and maintained by one person, and does not have any practical code reviewing. (This is not a good thing, but it is not difficult to imagine how that can be).
3. (and lately), people explaining things that come off to me as SWE/SRE friction, as opposed to the typical google SRE hiring/book propaganda.
I'll add anything I can think of, but obviously it's one persons opinion.
Can you elaborate on #3 a bit? I'm not sure what you mean and m really curious. I've always gotten the vibe that the SRE recruiters were not giving me an honest view of the realities of that job.
1. Pushing code and being unaware of the build system that does anything else.
2. Unable to comprehend that there can be teams/companies where some products are written and maintained by one person, and does not have any practical code reviewing. (This is not a good thing, but it is not difficult to imagine how that can be).
3. (and lately), people explaining things that come off to me as SWE/SRE friction, as opposed to the typical google SRE hiring/book propaganda.
I'll add anything I can think of, but obviously it's one persons opinion.