Jack of all trades
the developer has to be a DBA, security engineer, systems engineer, and programmer who understands the flows of *everything* in and out of their environment
Sounds like rubbish to me. Just because a service is, er, micro doesn't mean that it has to be developed in isolation by one person. Even if the function of each service is distinct that doesn't mean that you can't use the same security layer in each one, call on a DBA for support, and so on.
And surely "the flows of everything" becomes a lot simpler for a microservice?
As the article says, microservices are not the answer to everything but they should be understood for what they are, the same as any other tool in the box.