bicep

es, as well as providing mentorship to junior colleagues. We're not looking for any specific language experience, but are looking for demonstrable leadership, mentoring and collaboration skills. If you're looking to be Atlanta-based, we offer relocation packages within the US. Feel free to contact me directly (antmarti@microsoft.com) if you'd like to discuss before applying; otherwise, you can apply here: https://careers.microsoft.com/us/en/job/1245575/Senior-Softw... [0] https://docs.microsoft.com/en-us/azure/azure-resource-manage... [1] https://github.com/Azure/bicep

nking of a single service in particular or more generally, but assuming the latter, I mostly disagree about Azure's SDKs. Some of the SDKs have had too much churn for my liking, and the docs don't always keep pace with those changes. In general though, I find them really good. I'm not a huge fan of ARM templates for anything but the simplest deployments, but they get the job done. Bicep[0] shows MS are improving things, and there are a couple of nice OSS alternatives now, like Farmer[1]. I'm not a big fan of PowerShell in any form, but it's cross-platform, and I use it on occasion for Azure automation, and again it gets the job done without issues. Azure CLI, I really like - it's OSS, cross-platform, and covers pretty much all services. Extensions/plugins mean that even new services are covered quickly. The syntax and commands are very consistent (there are a few exceptions, of course), and being able to output results in either JSON or CSV is great for parsing from the likes of Bash scripts. Also like the way you can filter and project output, without the need for something like jq. Don't recall a single instance of something I could do in the UI but not via automation; aside from monitoring, cost reporting and quickly deploying throw-away stuff during dev, I don't feel compelled to use the UI. [0] https://github.com/Azure/bicep [1] https://compositionalit.github.io/farmer/