Me right now, discovering that our archives data have file sizes… sometimes in bytes, sometimes in kilobytes. I found some pattern this morning thinking I could know which was which, then the pattern collapsed at some date in the past.
Joy.
Love it , wouldnt work where i live , no flat roads. , Would be a new extreme sport going downhill though :) but I think I am gonna go for the one in the comments perhaps hackaday.io/…/180836-desk-ercising-with-the-exer-…
The worst case is when someone requires changes, you address them, but then they disappear/go on a leave.
If the repository rules require all conversations to be resolved before merging and only the original reviewer can mark them as solved, the PR is stuck forever even if the rest of the team approves it.
Upon the web, a cipher dance delayed, An SSL error in its code displayed. In cryptic realms, where data ought to flow, A falter in the handshake, whispers woe.
Sometimes that’s part of the issue (or the whole deal), but sometimes it’s not even that.
Sometimes it’s that someone asked something difficult and elaborate to answer, which has been answered a ton of times, and it’s tedious to answer again and again. But if someone answers with misinformation or even straight FUD, then one needs to feel the urge to correct that to prevent misinformation.
I suffered that with questions in r/QtFramework. Tons of licensing questions, repeated over and over, from people who have not bothered to read a bit about such a well known and popular license as LGPL. Then someone who cares little for the nuance answers something heavy handed, and paints a wrong picture. Then I can’t let the question pass. I need to correct the shitty answer. :-(
programmer_humor
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.