Any fucker not writing tests is more productive in the short term, but in the long term risks your entire business. Unless your business is getting hired by mar

Any fucker not writing tests is more productive in the short term, but in the long term risks your entire business. Unless your business is getting hired by marketing directors who want pretty demos to laud over their internal developers, in which case you practically have to write garbage to hit the deadline (not your fault; fault of the internal devs for not quitting instead of working for a twat). But on the bigger issue, correlation is not causation. Many new developers start with an IDE because. So you’ll see a lot of inexperienced developers using an IDE. On the other hand, back in the day, if I wanted to have any chance of editing this file on the arse end of a 9600baud dumb terminal then vi is the answer. So there are old bastards still programming, who therefore have a ton of experience, who use vim. Does using vim make you a good coder? Fuck no. Does using an IDE make you a bad coder. Also no. I use an IDE. I’ve used an IDE since ‘92. Then it was slick edit on OS/2, at a company working on some of the hard bits of supermarket system, and everyone used it. One of the best programmers I know uses vim. However every other best programmer I know uses an IDE. I suspect the vim guy is wired differently. So if vim seems right to you then use it. If an IDE works then use that. Anyone tells you you aren’t a proper coder unless you use vim or emacs or edlin then they are telling you that they are a pretentious twat. My friend who uses vim will not tell you to use vim. He’ll tell you why he likes it. But write fucking tests.