I talk a lot about how you can’t be a great developer without great communication skills, but I don’t think people grok how _directly_ your communication skills are reflected in your codebase. Let me give you an example.
-
-
Some points are subtle and take a lot of words to explain well. You can't tl;dr subtlety. Also, code has multiple paths and this thread has only one: statement; statement; statement; etc
-
## should be 3 letters: KiS ;-)
-
-
gender gun ;-)
-
If you can’t focus long enough to read 35 tweets, you’re not going to do well as a software developer. ¯\_(ツ)_/¯
-
naa, I just like it short & sweet ;-) I like your tweet btw essentially though !
- 1 more reply
New conversation -
-
-
I think more people (on twitter) will read a twitter thread than click on a link to a blog post. People can also react to individual thoughts within a thread. And a blog post can be produced later as well, not instead.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
nope, that's not what irony means; also, you should show some respect
-
Actually it’s a perfectly acceptable example of irony.
-
nuh-uhh!
-
New conversation -
-
-
Hm? The thread wasn’t hard to read. Each tweet was a thought, each followed naturally from the one before, and it all was just as long as it needed to be. Just like a good codebase.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Rude. But it IS ironic that you “like” a thread about communication but didn’t double check that your sentence could be parsed.
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.