Skip to main content
added 43 characters in body
Source Link
cl-r
  • 127
  • 5

Welcome to creative developers circus.
Instead of respecting all 'legal/reasonable' way to code at the beginning,
try intuition, above all if it is important and new for you and if no sample around looks like you want:

Welcome to creative developers circus.

  • Write with your instinct, from things you already know, not with your mental and imagination.
  • And stop.
  • Take a magnifying glass and inspect all words you write : You write "text" because "text" is near to String, but "verb", "adjective" or something more accurate is needed, read again and adjust method with new sense
    ... or, you wrote a piece of code thinking about future? remove it
  • Correct, do other task (sport, culture or other things outside business), come back and read again.
  • All fit well, pass to UML
  • Correct, do other task, come back and read again.
  • All fit well, pass to TDD
  • Now all is correct, good
  • Try benchmark to point out things to be optimized, do it.

    What's appear :
  • you wrote a code respecting all rules
  • you get an experience, a new way for work,
  • something change in your mind, you'll never afraid by new configuration.

    And now, if you see an UML looking like the above, you will be able to say
    "Boss, I begin by TDD for this...."
    it is another new thing ?
    "Boss, I would try something before decide the way I'll code.."

    Best regards from PARIS
    Claude

Instead of respecting all 'legal/reasonable' way to code at the beginning,
try **intuition**, above all if it is important and new for you and if no sample around looks like you want:

- Write with your instinct, from things you already know, not with your mental and imagination.
- And stop.
- Take a magnifying glass and inspect all words you write : You write "text" because "text" is near to String, but "verb", "adjective" or something more accurate is needed, read again and adjust method with new sense
... or, you wrote a piece of code thinking about future? remove it
- Correct, do other task (sport, culture or other things outside business), come back and read again.
- All fit well, pass to UML
- Correct, do other task, come back and read again.
- All fit well, pass to TDD
- Now all is correct, good
- Try benchmark to point out things to be optimized, do it.

What's appear :
- you wrote a code respecting all rules
- you get an experience, a new way for work,
- something change in your mind, you'll never afraid by new configuration.

And now, if you see an UML looking like the above, you will be able to say
"Boss, I begin by TDD for this...."
it is another new thing ?
"Boss, I would try something before decide the way I'll code.."

Best regards from PARIS
Claude

Welcome to creative developers circus.
Instead of respecting all 'legal/reasonable' way to code at the beginning,
try intuition, above all if it is important and new for you and if no sample around looks like you want:

  • Write with your instinct, from things you already know, not with your mental and imagination.
  • And stop.
  • Take a magnifying glass and inspect all words you write : You write "text" because "text" is near to String, but "verb", "adjective" or something more accurate is needed, read again and adjust method with new sense
    ... or, you wrote a piece of code thinking about future? remove it
  • Correct, do other task (sport, culture or other things outside business), come back and read again.
  • All fit well, pass to UML
  • Correct, do other task, come back and read again.
  • All fit well, pass to TDD
  • Now all is correct, good
  • Try benchmark to point out things to be optimized, do it.

    What's appear :
  • you wrote a code respecting all rules
  • you get an experience, a new way for work,
  • something change in your mind, you'll never afraid by new configuration.

    And now, if you see an UML looking like the above, you will be able to say
    "Boss, I begin by TDD for this...."
    it is another new thing ?
    "Boss, I would try something before decide the way I'll code.."

    Best regards from PARIS
    Claude

Welcome to creative developers circus.


Instead of respecting all 'legal/reasonable' way to code at the beginning,
try **intuition**, above all if it is important and new for you and if no sample around looks like you want:

- Write with your instinct, from things you already know, not with your mental and imagination.
- And stop.
- Take a magnifying glass and inspect all words you write : You write "text" because "text" is near to String, but "verb", "adjective" or something more accurate is needed, read again and adjust method with new sense
... or, you wrote a piece of code thinking about future? remove it
- Correct, do other task (sport, culture or other things outside business), come back and read again.
- All fit well, pass to UML
- Correct, do other task, come back and read again.
- All fit well, pass to TDD
- Now all is correct, good
- Try benchmark to point out things to be optimized, do it.

What's appear :
- you wrote a code respecting all rules
- you get an experience, a new way for work,
- something change in your mind, you'll never afraid by new configuration.

And now, if you see an UML looking like the above, you will be able to say
"Boss, I begin by TDD for this...."
it is another new thing ?
"Boss, I would try something before decide the way I'll code.."

Best regards from PARIS
Claude
Source Link
cl-r
  • 127
  • 5

Welcome to creative developers circus.
Instead of respecting all 'legal/reasonable' way to code at the beginning,
try intuition, above all if it is important and new for you and if no sample around looks like you want:

  • Write with your instinct, from things you already know, not with your mental and imagination.
  • And stop.
  • Take a magnifying glass and inspect all words you write : You write "text" because "text" is near to String, but "verb", "adjective" or something more accurate is needed, read again and adjust method with new sense
    ... or, you wrote a piece of code thinking about future? remove it
  • Correct, do other task (sport, culture or other things outside business), come back and read again.
  • All fit well, pass to UML
  • Correct, do other task, come back and read again.
  • All fit well, pass to TDD
  • Now all is correct, good
  • Try benchmark to point out things to be optimized, do it.

    What's appear :
  • you wrote a code respecting all rules
  • you get an experience, a new way for work,
  • something change in your mind, you'll never afraid by new configuration.

    And now, if you see an UML looking like the above, you will be able to say
    "Boss, I begin by TDD for this...."
    it is another new thing ?
    "Boss, I would try something before decide the way I'll code.."

    Best regards from PARIS
    Claude