<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>remove</title><link>https://evotec.xyz/de/tags/remove</link><description>Evotec Main Website</description><atom:link href="https://evotec.xyz/de/tags/remove/index.xml" rel="self" type="application/rss+xml" /><item><title>How to Efficiently Remove Comments from Your PowerShell Script</title><link>https://evotec.xyz/de/blog/how-to-efficiently-remove-comments-from-your-powershell-script</link><description>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.</description><pubDate>Sun, 20 Aug 2023 15:43:09 GMT</pubDate><guid>https://evotec.xyz/de/blog/how-to-efficiently-remove-comments-from-your-powershell-script</guid><category>cleanup</category><category>comment</category><category>powershell</category><category>remove</category><category>script</category></item></channel></rss>