<feed xmlns="http://www.w3.org/2005/Atom"><title>remove</title><id>https://evotec.xyz/fr/tags/remove/index.atom.xml</id><updated>2023-08-20T15:43:09.0000000Z</updated><subtitle>Evotec Main Website</subtitle><link href="https://evotec.xyz/fr/tags/remove" /><link href="https://evotec.xyz/fr/tags/remove/index.atom.xml" rel="self" type="application/atom+xml" /><entry><title>How to Efficiently Remove Comments from Your PowerShell Script</title><id>https://evotec.xyz/fr/blog/how-to-efficiently-remove-comments-from-your-powershell-script</id><link href="https://evotec.xyz/fr/blog/how-to-efficiently-remove-comments-from-your-powershell-script" /><updated>2023-08-20T15:43:09.0000000Z</updated><summary>As part of my daily development, I create lots of code that I subsequently comment on and leave to ensure I understand what I tried, what worked, and what didn’t. This is my usual method of solving a problem. Sure, I could commit it to git and then look it up, and I do that, but that doesn’t change my behavior where I happen to have lots of “junk” inside of my functions that stay commented out. While this works for me, and I’ve accepted this as part of my process, I don’t believe this should be part of the production code on PowerShellGallery or when the code is deployed.</summary><category term="cleanup" /><category term="comment" /><category term="powershell" /><category term="remove" /><category term="script" /></entry></feed>