> if you're in the habit of writing tests after your function is made - it shows you haven't put much thought, which means you haven't done the proper analysis

> if you're in the habit of writing tests after your function is made - it shows you haven't put much thought, which means you haven't done the proper analysis of why the function exists, if the function is really one function or should be two functions, what arguments it can take, what it should return etc. I'd say that's a pretty broad brush you're painting there with