I feel like listening to Theo about anything technical is like consulting a Labrador retriever for advice on quantum physics.

Every time I've ever seen one of his videos it's pretty clear he has very little understanding of development or engineering. I first became aware of him from his early "unit tests are a waste of time" stuff, and it seems his skillset is building a personal brand. Fair play, he's clearly talented at that, but that doesn't make his opinion on anything else worthwhile.

▲

patates 24 minutes ago | parent | next [-]

> it's pretty clear he has very little understanding of development or engineering

I cannot prove it but I have a feeling that you may be conflating "he clearly has different opinions on things I consider non-negotiable" to "he doesn't know what he's talking about".

I also watched a lot of his videos. I wildly disagree with him a lot of times, but he has his reasoning, and I can see (and verify!) that those ideas are coming from an engineering perspective.

▲

Havoc 19 minutes ago | parent | prev | next [-]

And half his videos are him coming up with indirect ways of saying look how amazing I am.

▲

ttoinou 32 minutes ago | parent | prev [-]

There is a whole religion about tests that is worth attacking though

	▲	bashtoni 16 minutes ago \| parent [-]
		Sure. If his take was "100% unit test coverage is a waste of time" I think that's not unreasonable. You could make a case that the "you must write tests before you write code, every single time!" stuff is needlessly dogmatic. I also think that sometimes people focus too much on unit tests to the detriment of end to end tests that better model actual system interactions. None of these were Theo's take. He was pushing the idea that unit tests in general were a waste of time because you could be shipping new features instead. https://www.youtube.com/watch?v=pvBHyip4peo for an example of this. The nicest possible interpretation on this is that he's deliberately saying something he knows is wrong to attract attention.