Just like its physical analog, a hoarded codebase only improves if you intensively work on changing those habits. This means deciding you will always do small, opportunistic refactorings when they appear to you in the course of fixing a bug or adding a feature.
Promising start but disappointing. Notice how communication suddenly becomes 'communication with superiors'. Communication to achieve collective action to tell your superiors you do not work this way? Also why should I give f about quality as long as my goal is financial survival
-
-
As I said in the very first tweet of the thread, this is an example - not an exhaustive list of all the ways communication skills can help you write better code. You are welcome to write up other examples!
-
On a separate note, you might ask yourself why you felt compelled to offer such a weirdly aggressive comment, unsolicited, to a stranger on the internet.
-
Sorry for not noticing and agressing, but how is it aggressive?
End of conversation
New conversation -
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.
who take an individual, moralistic approach to organizational pressure.
“It’s your job as a professional!” they say. “Just write good code! If they push back, just tell them ‘that’s not how I work!’”