What is frustrating is TDD evangelists insisting everyone do purist TDD in their regular development (like the guy being quoted in this article).
You set your standards as a team of what you will consider acceptable tests and as long as the dev submitting the PR meets that standard why does it matter if they did TDD or not? TDD is a means to end, it's not a religion. As long as you write tests that meet the standard it doesn't matter when you write those tests.
The level of micromanaging that TDD evangelists seem to want in people's workflows is infuriating. It's literally cultish.
Edit: I realize this came across more negative and abrasive than I intended. I think TDD has some good parts (primarily around gamification of writing tests and giving a serotonin hit whenever a test goes from red to green). I practice TDD around 50% of the time when appropriate, but most people who have worked in the industry that TDD as sold by purists is impractical and adds negative value.
Even if the data you showed were true (I have seen similar arguments from the pro-DST side), of all decisions were based on optimizing public health outcomes then any kind contact sport among kids/teens would be banned (including soccer, basketball, baseball, football, hockey), sugary soda's would be outlawed, fast food heavily restricted and other dangerous activities like skiing and snowboarding aggressively regulated to outright banned.
We make tradeoffs all the time to give the people the option to do the things they enjoy doing even if it means non-optimal public health outcomes. perma-DST is incredibly popular as most people prefer having the option of extra daylight in the evening.
This is ridiculous. Why don't they make the DST permanent? And if people want to have more light in the MORNING, then they just WAKE UP LATER. Surely that is easier than permanent REGULAR time.
OP is Canadian. If they want pursue an opportunity in the US- a degree is a requirement for the TN Visa (technically you can get the visa with "equivalent experience" but that is much more cumbersome and unpredictable where as the process is a breeze with a CS degree). Since he mentioned in the article something about "overseas opportunities", I am guessing that is part of his consideration.
Individuals overpaying is not enough to raise average values of houses in a market. In you example the person who owned the 250k house got a nice windfall selling their price above market value but that is not enough to raise the value at large of houses in that market. It would take people systemically overpaying and overpaying in large volume for it to affect housing prices and there's simply no evidence of that.
> The Californians, after years of having higher salary, more savings, and a job that lets them move, goes to Texas and offers $400k for that same house. The Californian thinks it's a great deal, because they get the same size house they previously lived in for only half the price! And the seller thinks it's great, because he now suddenly gets a huge premium on his previously-valued-at-$250k-house. All of the real estate responds in kind, expecting to get $400k+ from all the Cali transplants. However, the average Texan, who doesn't have that high paying salary, gets priced out and can no longer afford a house in their city.
That makes no sense. If the housing prices in a market go up, it is because there is more demand without an increase in supply. Not because a certain group is paying almost double the market value for absolutely no reason.
Why is this a newsletter that you need to give your email address even to just sample the content? It would be much nicer if the website showed you the content with an option to subscribe to the newsletter or rss feed.
You set your standards as a team of what you will consider acceptable tests and as long as the dev submitting the PR meets that standard why does it matter if they did TDD or not? TDD is a means to end, it's not a religion. As long as you write tests that meet the standard it doesn't matter when you write those tests.
The level of micromanaging that TDD evangelists seem to want in people's workflows is infuriating. It's literally cultish.
Edit: I realize this came across more negative and abrasive than I intended. I think TDD has some good parts (primarily around gamification of writing tests and giving a serotonin hit whenever a test goes from red to green). I practice TDD around 50% of the time when appropriate, but most people who have worked in the industry that TDD as sold by purists is impractical and adds negative value.