I feel that isn't going to give good SNR. Not everyone is good at *explaining* process. Not everyone is honest either.
-
-
I don't know a developer who isn't happy to sit down with a beer talking for an hour about the hardest bug they ever tackled.
1 reply 0 retweets 0 likes -
Honestly, I hate those questions. I don't have an index in my mind of "bugs ranked by difficulty". *Once* I manage to find a topic, sure.
2 replies 0 retweets 1 like -
So if we were talking and I asked you about your work you would have absolutely nothing to say?
1 reply 0 retweets 0 likes -
If you asked me about my work I'll be happy to talk. Just don't use words like "hardest" or "best" or whatever. "Interesting" is better.
1 reply 0 retweets 0 likes -
I mentioned hardest because it's like people talking about fishing or war stories. We have some memorable problems we worked on.
1 reply 0 retweets 0 likes -
I get that, but I really wish people didn't use absolute terms like that. It needlessly causes people to go sorting.
2 replies 0 retweets 0 likes -
For fuck's sake, it's Twitter! You get 140 characters to express a thought! Don't condemn a process over one word semantics!
1 reply 0 retweets 0 likes -
Hey, you picked the word, not me. Those "-est" questions really are stereotypical. I think there are better options.
1 reply 0 retweets 0 likes -
Like making people write linked lists on a white board with everyone staring at them?
1 reply 0 retweets 0 likes
We already established I'm nitpicking about the word choice; general discussion format is fine. I think both that + coding have value.
-
-
Replying to @marcan42 @RedQueenCoder and
Also FFS coding questions should be 1 on 1. N:1 is just cruel.
0 replies 0 retweets 0 likesThanks. 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.