4 ms·
110% this, especially as a security engineer who might have to know about all the microservices in a product, while the software engineers might only have to kn
by Sohcahtoa82 4y ago
110% this, especially as a security engineer who might have to know about all the microservices in a product, while the software engineers might only have to know about a few of them.
It's especially bad when there's a major lack of documentation, so I gotta either set up tons of meetings or spend time examining code just to figure out what Galactus, Omega Star, and Papaya all do.
- thaumasiotes 4y ago> It's especially bad when there's a major lack of documentation, so I gotta either set up tons of meetings or spend time examining code just to figure out what Galactus, Omega Star, and Papaya all do. But you have to do that anyway. If you don't bother examining a service's most-commonly-used functionality just because the service's name implies different functionality, what kind of security engineer are you?
- Sohcahtoa82 4y agoTrue, I have to do it eventually anyways, but having an idea of what each service is before diving in helps a lot. This is especially true when working with Java or Kotlin apps where there's 100 levels of abstraction and calls to functions named "invoke" and "run".