When you look at failed-Agile orgs, the root problem is often that nobody on top trusts the people who do the work. If they'd understood that agility required giving up control, they'd have run in the other direction as fast as their little feet could take them.
I don't much like the idea of teams owning microservices (or services used as a way to decouple teams from each other). I'd prefer to use bounded contexts for that. Teams work on stories—full end to end implementations of a narrow vertical slice. 1/4
Chatting with @ChandlerDBA #aced at #OUGIreland@UKOUG today we came to the conclusion that
"No plan of execution survives contact with the optimizer untransformed!"
If your app doesn't perform well and scale on one server it will be terrible on two. Containers are great, but some developers use them as an excuse to skip optimization, profiling and scaling. Get performance on one container... Then scale.
If you're going to cite NIST as an authority on industry-standard practices, you can't also say that regularly rotating passwords is industry-standard practice
Corporate Infosec sends a phishing test email, I click, and somehow I'm the asshole because "[I] failed the test; had this been real it would have destroyed the company network"?
If me clicking can destroy the network, I'm not the one in this conversation who sucks at their job.
@ilmarkerm Assuming the numbers are AWR averages (not correlated foreground seesion & lgwr traces): lfs is from many fg sessions waiting simultaneously on one lgpw/rtm to finish. The lgwr has to post all fg procs (semaphores, sys-call switches,etc.), then all these proc want to go on CPU...