PUBLIC MARKS from greut with tags code & programming

It seems to me getting good at writing comments is an under-appreciated part of a Programmer's development. However, I feel that this is a part of programming that's almost as important as writing code itself.

1. A writes a new test and sees that it fails.
2. B implements the code needed to pass the test.
3. B writes the next test.
4. A implements it.

I'm not speaking from experience, but rather from logic. My experience is that I've learned more about programming from programming than from reading. My logic is that, given the many irrelevant parts of my personal programming-related readings, I could increase learning by focusing more on the act of programming itself.

read less, do more.

Here’s an idea: if you are spending more time writing code, than thinking about what code you should write - you are doing something wrong. Very wrong. Or it’s something trivial enough to not be of much importance. Or it’s Java.

Pisser du code, comme on dit couramment.

Let's see what happens when we introduce a seed of bad code into an organization

and it grows like a cancer.