![]() ![]() It is a mind-numbing and error-prone process, especially when it's performed while context switching with other development and operational tasks. 1 shows, it is not a technically challenging process. If a user has been inactive for three or more months and has been assigned an expensive license, we revert the user to a less functional and free license.Īs Fig. Don't automate broken processes-fix them before automating.įor example, my team continuously inspects hundreds of user activities on our common collaboration and engineering system, looking for inactivity that is wasting precious dollars.Don't automate highly volatile processes-it is too complex and expensive.Don't automate processes that are a one-off-it is not worth the investment unless you reuse it as reference documentation and regularly validate to ensure it remains functional.More importantly, what should you not automate? ![]() Automate processes you will perform regularly and continuously.Automate processes you perform manually more than once or twice.If you have ever dusted off an inviable Azure Resource Manager (ARM) template or a precious maintenance script you wrote a long time ago, expecting it to execute flawlessly months or years later, you will understand that automation, like any other code, is brittle and needs continuous maintenance and nurture. ![]() Having used automated processes and toolchains since the early '80s, I always twitch when I hear or read the recommendation to "automate everything." While it is technically possible to automate everything, automation is complex and comes at a price in terms of development, debugging, and maintenance.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |