Thanks @cassidoo for sharing. I've been hesitant to re-engage in work travel the last few years for reasons. You've inspired me now to not only get back on this platform but also to events. See yall in person somewhere
I'm still getting used to coming back to this app after a few years. I didn't realize how important performance was to me.
I also started a new account (cooking in the background). I got so many wonderful bots following.
We @VetsWhoCode are building a platform to automate admin tasks we have. It's a Nextjs app with Github and Slack integrations so far.
We were seriously blocked and I was afraid we wouldn't be able to scale local dev to have any other contributor than me 🧵
We created a bunch of bots (5 so far). @github didn't like that and instantly flagged all our accounts. This obviously breaks Terms of Service and when I submitted a support ticket they let me know.
Long story long, they finally approved my request to keep the accounts after I sent a pleading message stating my case. It's honestly nice to get good customer service.
Don't be afraid to reach out for help.
I've heard of greenfield projects. Projects that are brand new.
Just learned of brownfield projects. Projects that already have pre-existing consideration.
Always have just called it legacy. Like the idea of a brownfield.
ALT golden field project, is a project that you actually want to work on
I don't care if you adopt Azure. But this is such a valuable primer on how to plan/adopt cloud. I wish I knew about this earlier.
learn.microsoft.com/en-us/az…
However, the dependencies of networking, identity management, and security weren't properly identified at the outset. Leading to the effort grinding to a halt
IMO this type of documentation is a subtle indicator of company values between AWS and Microsoft. I read so many random AWS white papers trying to create a mental model of this stuff. It shows thoughtfulness of product uses on Azure's part to have these docs.