93 karma · joined June 29, 2018
But with regards to purely technical stuff like what tools to choose and how to use them you’ll need experience, either your own or someone elses. There’s really no replacement in my opinion. I had loads of experienced people around me previously, but now that I work more or less alone in the field I rely a lot on community slack channels for the various tools and debugging. It’s amazing to be stuck trying to figure out how to best use Loki for logging, jump on their slack and get advice from the Lead Engineer working on the tool. Or getting input on what tools to use from 50 different people in different companies through /r/devops on reddit.
It is very painful to lose friends you care about. It’s much worse to lose them because you made them feel unimportant by not staying in touch. An app like this could really help in that way. Just by being the nudge to start the interaction.
Is there some well defined way of doing this remotely from say a Gitlab pipeline?
In many apps, these login redirects happen inside the app window, hiding the url. And even if the URL isn’t hidden, there’s suddenly a browser window inside my app and many unconscious “security checks” fail to load.
I’d much rather have the OAuth provider send me an email or get a notification that can be actioned within the OAuth providers app so that I know I’m not giving my credentials to something that looks like the OAuth providers sign in page.
In other teams, a comment like this would have meant a chat with HR. We can't make rules for these things, because people and thus teams are different.
1. How will you fix it?
2. How will you prevent it from happening again?
An apology, in my head atleast, is for when you have caused emotional distress to someone and there isn't much you can physically do to fix it other than to convey how you now feel about what you have done. When you make a practical mistake an apology is implied by you fixing it.Edit: had to disable 2FA to get it to work.