Well, there's kind of a divide between people who think it should not be there on the main line and people who think it is ok as long as there is a flag controlling it.
Thing is none of us have real experience with web applications outside this project. So I am interested in knowing how do other frontend devs deal with this.
Keeping things behind a flag and only turned on in particular environments or for particular accounts is a common practice in web development, so I agree this is a good idea.
Want an example? GitHub has a staff mode where they can browser github.com and see stats on how the page loads in production. Check out some of the screenshots in this article to see it in action.
Thanks for your answer.
Well, there's kind of a divide between people who think it should not be there on the main line and people who think it is ok as long as there is a flag controlling it.
Thing is none of us have real experience with web applications outside this project. So I am interested in knowing how do other frontend devs deal with this.
Keeping things behind a flag and only turned on in particular environments or for particular accounts is a common practice in web development, so I agree this is a good idea.
Want an example? GitHub has a staff mode where they can browser github.com and see stats on how the page loads in production. Check out some of the screenshots in this article to see it in action.
This is exactly what I was looking for, thanks!