Peer reviewing your apologies is always important.
Peer reviewing your apologies is always important.
I feel like “just” is doing a lot of heavy lifting.
In swoops the project team to sign a contract with a software vendor without any architectural or Product input, then expects you to implement changes for whatever the software does and however it works. They do not know.
“Who were you…”
He’s already been approved to do so. That’s why this is now in the news.
If the remaining Twitter employees thought they had it bad before…
I can’t help but feel that we’re all waiting for you to get there… but we’re rooting for you!
Your own rationale for why it doesn’t work supports it working… unless you feel info is not a requirement to fix issues.
Having worked as a phone monkey and letter monkey previously, this is painfully accurate. The first skill you have to learn is effective questioning, as you only get a certain number of question attempts and the number is different per user.
Barry Atman?
Ahhh… AS400… what a beautiful system.
I’m starting to get the feeling that you don’t approve of Discord.
The notifications in one of our systems is aligned with UTC because it needs to be for a whole bunch of background services to function. Periodically (every couple of years) someone raises a ticket to complain that the time of their notifications is an hour out, and the 2nd line support worker will think “well that’s easy, I’ll just change the server time to BST”. This then brings this whole suite of applications to a crashing halt as everything fails.