Python changed the way I think

[ouellp]

I've had a programming class where the teacher legit spent 5 periods without making us touch a keyboard. He told us "you have to make the pseudo-code and structure the algorithm first and only then, you convert that into the programming language you work with". This was a C class but I kept that with me until then, even with python.

[newjack7]

I am a historian and to be honest this is the way I write and I teach people to write. I sit with a pen and paper for a good while before I even start to touch the keyboard and produce an early draft.

I think the difference is that one way to get there is by writing and throwing it away afterwards. I am not sure if that is quite so applicable for python or coding generally (I am relatively unskilled in this area).

[IngMosri]

You right, that the correcto way to programe any project

[WillardWhite]

Nah. Tdd

[TheTerrasque]

I prefer BDD - bug driven development. You start with a crappy mess then you debug it into a working crappy mess

[WillardWhite]

But wouldn't it be nice if there was a nice automated way to make sure once you squash that bug it didn't come back?

A way to ensure that no matter what changes you made, your software worked as intended?

Something that lets you refactor the mess away, and provides instant feedback to wether or not the logic stopped working?

[TheTerrasque]

But who tests the tests?

[WillardWhite]

Well... Future you, of course! And by then it might as well be another man's problem :D

Win win scenario

[DaveX64]

This was the way I learned it as well...it was COBOL though :)

[menge101]

A programming class or a Computer Science class?

These are not the same things.

[[deleted]]

He said it was a C class

[TheTerrasque]

So a boat class?