🌏 Living and working in Canada
🧑💼 Microsoft 365 Developer at 2ToLead.
💻 SharePoint Specialist | React Developer | Power Platform Enthusiast
💽 Always learning, experimenting, and finding better ways to get things done
🌏 Living and working in Canada
🧑💼 Microsoft 365 Developer at 2ToLead.
💻 SharePoint Specialist | React Developer | Power Platform Enthusiast
💽 Always learning, experimenting, and finding better ways to get things done
PowerShell is one of my favorite tool when it comes to automation. It has lot of functionalities and one of its cool features is Start-Job. This will let you run tasks in the background while you keep using PowerShell for other things. Start-Job is ideal to use when … Tasks take a long time to complete You want to avoid module conflicts by isolating them in separate jobs You need to resolve assembly conflicts by running jobs in isolated processes How to Use Start-Job I will try to explain this with a simple example below. ...
Well, today I learnt an important lesson. 🤔 The Problem In a recent coding effort, I found myself faced with the classic choice between JavaScript’s forEach and for… loops. As I was iterating through an array of data, I realized that my code required asynchronous operations. Async/Await in forEach: Initially, I opted for the simplicity of forEach, but soon hit a roadblock. Despite my attempts to use async/await within the loop, I encountered unexpected behaviour. The asynchronous nature of forEach proved to be a block which led to unhandled promises and unpredictable results. Here’s what I was using: ...