Agree or !Agree?

the fuckkkkkk? code ONCE? are you saying people cant improve their code?

@calmyourtities
So this one?!

I think I’ll finish off coding 100 times after that... lol

!agree

think > code > think > code

repeat.

I can't even think once.
I'm coding all the time until work and improving my code.

@mshokoohi yes

Thats been my desktop @ work since our last shit developer left. Reminds me to think before I code, unlike that prick.

Debug 20x

var code
var goodEnough = qualityStandards( code )

while !goodEnough {
think()
code = code()
goodEnough = qualityStandards( code )
}

More like design once, code once, review once, repeat many.

@CurseMeSlowly i want to correct you there:

code > think > code > think

repeat.😋

Well it depends. If you do it as a hobby, definitely think once, code twice.
It's like saying dribble twice, score once to a soccer player. Doesn't really make any sense.:D

BUT imho you cant do that in a company with deadlines.. so..:b

@daintycode I used to do that approach but lately I try to think first before I open my code editor. 🤔

I am also trying to

think > document > code

repeat 😬

@CurseMeSlowly not a bad thing at all. I see the whole "you MUST think before you do it" as a problem. If you do it on your own behalf - why the heck not.(:

But for me, documenting as i go is an absolute no-go. Not because i don't like it, it's just the fact that i completely change everything sometimes and i don't want to document everything again.:D

@daintycode that's a very valid point. 🤔 I might have to reconsider my approach.

"Code once" yup. Totally.
*Runs programs*

300 errors. I coded once. I guess I'm done for the day 😂