« first day (4315 days earlier)   

00:01
@pacmaninbw I'm aware of this, hence why I didn't ping you directly
00:22
REFRESH! There are 5046 unanswered questions (93.4917 answered)
00:39
@SᴀᴍOnᴇᴌᴀ You probably won't. The common vernacular was "broken" then we (Mast) fixed the broken wording with "working as intended". I don't recall any meta posts about tests, except maybe if tests are valid code and/or we need unit tests. The phrasing is one of pacmaninbw's creations.
@SᴀᴍOnᴇᴌᴀ I would say yes.
@Peilonrayz Did my creation misstate anything?
@Peilonrayz I contemplated whether it is worth asking on Meta whether "works as far as the OP knows" entails that the OP has to have tested their code
I'm not sure if it has merit or not
@SᴀᴍOnᴇᴌᴀ Perhaps... But idk. I rarely test the code in my answers, people will every now and then go "you made a few typos" and which I fix and everyone's happy. So IMO you don't need to test your code. However I feel a bunch of people will have the knee jerk reaction "how can you know the code works if you haven't run the code?" If we go [specific-question] then honestly the argument does have more weight because I never implement something new correctly first time.
okay; we can see if the OP complains
01:11
Whenever I can, I compile and run the code in the question.
I have found bugs and reported them as part of the code review.
I barely ever run the code in the question. I just read and edit the code and jot the rough changes I make down in a notepad to convert into an answer.

« first day (4315 days earlier)