Tech
-
How to shutdown windows without updating – cdm – shutdown /s /t 0
Windows often prompts users to install pending updates during shutdown or restart. Fortunately, using the Command Prompt (cmd), you can bypass updates and shut down your system immediately. This article explains how to use the “shutdown /s /t 0” command effectively. Understanding the command The “shutdown /s /t 0” command is a simple Windows cmd instruction that forces the computer to shut down instantly without processing updates. Here’s what each parameter means: Command Description shutdown /s Shuts down the computer after a default 30-second delay (can be modified with /t). shutdown /s /t 0 Shuts down the computer immediately (similar to /p). shutdown /f Forces running applications to close without…
-
Informed captain decision making in team
Informed captain decision making in team is another idea, from netlifx, to make everything in a company better, decentralized and so on and so forth. Fater, better harder stronger 😉 The generic idea is about “empowering teams and individuals” but here are the key points about this concept. Short story : Informed captain listens to everyone than is trusted to take the best decision to move forward. Informed Captain Responsibilities The captain owns the team’s mission, mandate, and metrics, and has full decision-making authority within their scope. Decision-Making Process Decisions are not made by consensus or committee votes. The captain has the final say after considering different viewpoints. Kinda like…
-
GitLab dev to qa merge conflict with no resolution options
GitLab dev to qa merge conflict with no resolution options can occur on multiple different occasions. One of the main reasons You can run into is : You can still check it out locally. The merge request You will be able to see and resolve in intellij or command line, whatever You fancy. At least you will be able to pull and just use the things that causes the conflic from QA. Unfortunetly it might require You to work on some changes again. For more stability i would do it one branch after the other so gitlab will not have issues when we first merge everything from QA using qa…
