After 15 years, I use Outlook as my build pipeline
iwriteaboutcode.blogspot.com
After 15 years, I use Outlook as my build pipeline
1–10 of 73 posts
Re: After 15 years, I use Outlook as my build pipeline
#2Re: After 15 years, I use Outlook as my build pipeline
#3But it seems like an enormous security hole, even with a codeword "password". The author didn't mention it, but I hope they're using whatever version of their company's E2E email encryption is for these messages.
Re: After 15 years, I use Outlook as my build pipeline
#4[flagged]
Re: After 15 years, I use Outlook as my build pipeline
#5As a dev currently working at a company where getting an access request fulfilled can sometimes take weeks, I feel this author's pain. But it seems like an enormous security hole, even with a codeword "password". The author didn't mention it, but I hope they're using whatever version of their company's E2E email encryption is for these messages.
Ultimately the problem is that in a lot of big corps, IT is basically unaccountable for setting things up wrong. Their only KPI is tickets closed, not the quality or success rate of their fixes.
Re: After 15 years, I use Outlook as my build pipeline
#6[flagged]
Re: After 15 years, I use Outlook as my build pipeline
#7[flagged]
If you're doing anything else, are you really an engineer?
bwahaha.
Re: After 15 years, I use Outlook as my build pipeline
#8Re: After 15 years, I use Outlook as my build pipeline
#9Re: After 15 years, I use Outlook as my build pipeline
#10[flagged]