Saw a post flit across my timeline which intimated that TDD will help you write correct code, and a linter clear code.

Naw.

Writing tests before writing runtime code simply means your code will pass the tests you already wrote. Whether or not the code is "correct" is entirely a separate matter (and you can write "correct" code before you write any tests).

Similarly, code can be any shade between clear and unclear…and linters rarely are a magic solution and sometimes will cause the problem!

I understand some people find great comfort in the rigidity and discipline which comes with strictly adhering to semi-automatable norms when programming. I've always been quite on the other end of the spectrum. To me, coding is much less like solving a math problem and much more like playing jazz music or composing an essay. Will I sometimes TDD? Sure. Other times, that would be an utter waste of my time. It's just a tool. It's not "the thing".
@jaredwhite Oddly enough, I come from a mathematical/scientific background and my approach (which is much the same as yours) was drilled into me at university - you can't do anything innovative by following the same predefined steps each time. I think software is just pragmatic art.
@paulhmason That's a good way to put it!