-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hide banner temporarily #180
Conversation
retain code for future use
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In general the idea of leaving code in "in case we need it later" is pretty bad practice when using version control. It just leaves clutter and damages readability for future maintainers. When using version control it's unnecessary because the changes can just be pulled out of the history if required.
I guess I'm happy to be overruled on this if necessary
Very good point and one I hadn't thought about. Perhaps we raise an issue reminding us to add this in again ~August 2022? |
in the meantime the website says "if you're joining us in september" and it's october so it cannot remain up, temporary fix or not. |
I really don't like the idea that the code is there, and is actually transmitted and can be seen in the source, but just isn't displayed. That's so messy and wasteful. |
retain code for future use