Code

Try to always use Python, Powershell and Github for “things”, TODO notes, write them in Python in Notepad ++

Most of the code should be focused on Python and Powershell.

Quick sheets Python, AMQP, Powershell, Github, SQLPLus, BASH:

spawnmarvel/quickguides: quickguides, markdown, nutshell reference (github.com)

Think automation and monitoring, embrace the 5 min you have and tutorials.

Microsoft Certified: Azure Administrator Associate – Certifications | Microsoft Learn

NOTE:

Some of the things I have done or not done, spent time on or not spent time, liked or not liked, tested or not tested, used hours on or just minutes on, changed or not changed, started to enjoy or changed my mind about, started and finished or started but not finished, found out or not found out yet, could be stored here.

CODE:

Usually it has been done before and / or there is best practices, the key is to dismantle it and understand its’s pieces.

Github:

spawnmarvel (Espen Kl) (github.com)

Quickguides (maybe not that quick):

spawnmarvel/quickguides: quickguides, markdown, nutshell reference (github.com)

Azure-quickstart-templates:

azure-quickstart-templates/quickstarts at master · Azure/azure-quickstart-templates · GitHub

Checklist risk management:

What are the top risks, how severe is their impact and how likely are they to occur? THEY WILL HAPPEN.
How often do we refresh its assessment of the top risks?
Who owns the top risks and is accountable for results, and to whom do they report?
Always use LTS version of software, dlls, libs etc (TEST, TEST AND TEST AGAIN)

VSC Py, ARM, Ps1 extensions:

  • Magic Python (MagicStack Inc.), syntax highlighter
  • Python, IntelliSense
  • TODO highlights
  • Azure Resource Manager (ARM) Tools for Visual Studio Code (MS)
  • Azure Resource Manager (ARM) Tools – Visual Studio Marketplace
  • PowerShell

Tools:

  • Git Bash: GIT, Curl, SSH (or with Putty), BASH, NANO
  • ssh -l user host
  • Azure Cli or Powershell: Install-Module -Name Az
  • Greenshot
  • Np++, Plugin: XML Tools, Compare
  • BareTail
  • NSSM

Tips:

  • A space at the end can ruin your day (either strip() | ” ” replace “” np+
  • pip(3) –version
  • python –version
  • import sys
  • print(sys.version)

Linux (Linux System Admin Command):

https://www.javatpoint.com/linux-system-admin-commands

BASH101

https://devhints.io/bash

https://help.ubuntu.com/community/LinuxFilesystemTreeOverview

ss64

https://ss64.com/convert.html

https://ss64.com/

SSL

https://certlogik.com/decoder/

MS SQL:

https://docs.microsoft.com/en-us/sql/?view=sql-server-ver15

Game or fun:

https://xkcd.com/1335/

https://sudoku.com

VM

Azure “good-to-know” about any VM, with example on SKU:General purpose virtual machine sizes:

https://docs.microsoft.com/en-us/azure/virtual-machines/sizes-general


Ever wondered why?

A factor is considered the root cause of a problem if removing it prevents the problem from recurring. A causal factor, conversely, is one that affects an event’s outcome, but is not the root cause. Although removing a causal factor can benefit an outcome, it does not prevent its recurrence with certainty.
The causal factor isn’t the single factor that drove the event. Instead, a causal factor was one of a few influences. The event could still occur again, or would have happened without the causal factor.

Identify Possible Causes:

This can be done in a brainstorm session. Start with the problem definition and ask “why?” it happened. Keep on asking “why?” repetitively until you have found the root cause.