I Don't Understand What "uncommented" and "commented" means... :/

I Don't Understand What "uncommented" and "commented" means... :/
0.0 0


I don’t quite understand what leaving elements “uncommented” means:

Your code so far

<h1>Hello World</h1>
<p>Kitty ipsum dolor sit amet, shed everywhere shed everywhere stretching attack your ankles chase the red dot, hairball run catnip eat the grass sniff</p>

Your browser information:

User Agent is: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:60.0) Gecko/20100101 Firefox/60.0.

Link to the challenge:


From my understanding, you can compare it to our hand & sign languages.

When many programmers are into the project you can use this ‘uncommented element’ to hide it from the web page original publish design and other programmers see it as a sign that there’s a problem or the codes needs some improvements.


when you’re finish on that task you can see that on the output layer on our screen the sentences were hidden after you’ve just removed the uncommented element. hope it helps :slight_smile:


Okay so, what’s the purpose of hiding the text? Also, could you give a example of an uncommented piece of code and commented piece of code so that I could compare the two? Thanks ~TheUltimateMarioFan


Hey @TheUltimateMarioFan - mostly I believe what they are trying to say here is as a development tool. commenting and un-commenting some section of your code is a great tool to temporarily disable it, that is, disable it without removing it or cutting it out while you are still working on it.

I use this technique constantly when troubleshooting. In fact my IDE has built in tools to do just this for html, css, JavaScript, php, etc…


Commenting is a way for human developers to include notes for themselves and/or other human developers. Computers don’t see what’s inside comments (“commented out”) whether it’s code or not. That means that commenting out pieces of code is a very convenient way to temporarily remove that code without losing all your work. Maybe you’re trying to decide between two different things. You can write them both, comment one out, look at the results, uncomment it, comment out the other thing, look at the results. You might also comment out code that is temporarily not working because of outside factors . You can also put code snippets in comments to remind yourself/others how to implement something weird and tricky.

TLDR - Yes, people really comment and uncomment code all the time.


Okay thank you for explaining guys :):grin: