1/ I do TDD; write the test, then the code. Test works, so code works. Remove debugging printfs. Run it again. Fails. Add debugging code. Passes. Remove debugging code. Fails. OMFG ...then have an insight. replacing debugging printf with sleep(1) works real problem >>>
-
-
3/ The POST is synchronous! Notice how I specifically said "EVENTUAL consistency". The POST reports back (a) success, (b) the data you posted / patched is XYZ." The data had to percolate from their machine A to B so that the following GET got it.https://twitter.com/JASutherlandBks/status/1271535686794055687 …
Show this thread -
4/ oh, gosh, another bug I've got a test that posts ADD_ITEM then gets LIST_ITEMS ...and it stopped working. Suspiciously, the number of items is exactly 200. Suspiciously, ADD_ITEM reports success, but then number of items at server is still 200. I smell a junior coder.
Show this thread
End of conversation
New conversation -
-
-
That one "300 mile range" Daily WTF. With that said, if the timeout is measured in O(minute), this is actually an extremely useful prober/metric/page.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Nothing like await available on the post results?
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.