1. Don't use twitter. Remain offline as long as possible.
2. During the time you're offline do this: think / code / think / remove code / think / code tests / code (order may vary)
I esp. like removing code. "Every line of code not written is a correct one" !! I recently did a very successful project for a demanding customer by cutting the code by 60%.
3. Make your time window for learning, comparing code, check others' code. Resist coding during that time. Use the right source of information - the best would be analyzing the whole programs to have a better context. Avoid CPDD (Copy/Paste Driven Development) like a plague. Read paper books on programming - the brain works in a different way when reading a dead tree text.
Sorry for not answering your question directly. This was a polite - I hope - way to say that gists on twitter won't win the game.
Just follow more people on Github or something, it's easier to find programmers on there for your interests, and you just get all things programming-centric on there.
That being said, I follow @codinghorror, @migueldeicaza, @jonskeet, and a few others.
That being said, I'm with travisjeffery and Osiris on this. Twitter may be a good way to start a conversation related to coding and such, but is by no stretch of the imagination a good place to hold that conversation.
My advice, buy the book, read the titles, then read the chapters (translates beyond Java imo).
I just joined today (asking for an invite almost instantly got me one, by the way) so don't know how quality it is.
I suppose you can't see it if you don't have the new interface though.