Gaurav Poudel

In my experience, IT Operations Managers should keep the technical details to themselves and just not bother explaining everything in detail. By attempting to explain complex technical data to C-Level executives, you will waste both your time and their time, as - 1. Its not useful for them to learn these intricacies. 2. Executives are good at getting things done, not debugging. 3. If its too hard to explain, do it yourself. If you have something that needs change or implementation, prepare a report of required cost, potential savings or benefits, and draw a diagram or flowchart that includes everything complicated that you cannot explain, so if you ever leave the company, someone in your position should be able to decode it.

New Cloud Security concepts I have loved studying is the concept of partial authentication, for e.g., Using PIN will give you access to login to bank app and check balance, password to send low amounts, fingerprint for large amounts, and voice match if using untrusted devices. Hardware-based security, Trusted Execution Environment (TEE), and Multi-factor authentication has been growing together in mostly right direction. Personally, I believe Zero-Trust is also good to learn because of positive changes it brings via paradigm shift from "Always Trust, but Verify" to "Never Trust, Always Verify". By assuming that the system may already be compromised, we can stay one step ahead of the attackers in securing our data & business processes.

Here are some nifty tricks to boost security of Microsoft Windows 10/11 - 1. Turn off SMB 1.0 from Feature Options 2. Set powershell execution policy to restricted (or atleast RemoteSigned if your organisation issues self-signed security certificates & applications with those certificates) 3. Turn off Auto-play for USB and new devices. 4. Enable Secure Boot and BitLocker 5. Set script extensions such as .js and .vba files to notepad instead of JS or VB runtime, so that an application cannot directly invoke these files.

The only thing more important than writing the complex scripts is writing documentation/comments to go with it. In today's rapidly evolving IT landscape, you may not know where your script may come into use, so make life easier for the person who has to read your code to solve their issue.

Agile and Double Diamond Methodologies are some of the most used frameworks for continuous development. These methods are extremely versatile and adaptable to millions of use cases. If your project is strong in vision but lacks proper direction, implementing these frameworks can provide magical results; these frameworks don't just work on your product, they also give a sense of purpose and motivation to your team members so that they are can work together to build a solid product.

Here are some tips to get started with choosing the best solution - * Clearly define your essential and non-essential requirements and separate your potential solutions into two groups. Sometimes there are tailored solutions that focus on exactly the issue you are trying to solve, and then there are those that cast a wide net to *probably cover your use case; but as a side effect and not as the main goal. In such a case, research both groups and see if any other features of the proposed solution may match your product vision. Sometimes, this can also provide a unique direction, niche, or application for your project to pursue. Ideally, you are looking for a solution that can transform your product into something completely reliable.