FOCUS:
- Try to always use Python, Powershell and Github for “things”
- Most of the code should be focused on Python and Powershell
- Best practise:
- TODO notes, write them in Python
- Think automation
- AZ-104 (VM, network and storage)
- PaaS
- RabbitMQ
- Montitoring automation
- Embrace the 5 min TODO
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.
spawnmarvel (Espen Kl) (github.com)
spawnmarvel/quickguides: quickguides, markdown, nutshell reference (github.com)
#checklistriskmanagement: muda #wastefulness, mura #imbalance, muri #overload
- 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)
| Set up general | |
| VSC Py, ARM, Ps1 | Python Extensions: 1 Magic Python (MagicStack Inc.), syntax highlighter 2 Python, IntelliSense 3 Azure Resource Manager (ARM) Tools for Visual Studio Code (MS) Azure Resource Manager (ARM) Tools – Visual Studio Marketplace 4 PowerShell 5 TODO highlights |
| Tools | 1 Git Bash: GIT, Curl, SSH (or with Putty), BASH, NANO 2 Azure Cli or Powershell: Install-Module -Name Az 3 Greenshot 4 Np++, Plugin: XML Tools, Compare 5 BareTail 6 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://help.ubuntu.com/community/LinuxFilesystemTreeOverview
ss64
SSL
https://certlogik.com/decoder/
MS SQL:
https://docs.microsoft.com/en-us/sql/?view=sql-server-ver15
Game or fun:
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.