HN user

mledu

32 karma
Posts0
Comments16
View on HN
No posts found.

I will also add that many problems in the US and other countries stem from the perversion of incentives and benefits of the few over the many. What I mean is that keeping this broken system in place as it greatly benefits the insurance companies, of which there are a few. It’s so valuable that they have the money and resources to buy the politicians, pay for the media campaigns and lobby the propaganda outlets to mitigate any power the populace has to address the issue. This allows industries to control pretty much all policy in the US. It’s a sad state of affairs.

It took the ER 4 hours to give me pain meds for my kidney stone. They sent me to imaging where the tech asked “did they give you any pain meds?” and I said no, and she sighed. The PA knew within two minutes I had a stone but it took them hours to give me anything for it while I lay in a gurney in on the open floor while Covid patients coughed all around me during the height of the pandemic.

This is the point Nassim Nicholas Taleb makes in his book Fooled by Randomness. In a long enough timeline luck plays a big part in performance. People or firms like Melvin can perform well in a short timeline but when you stretch the timeline out the reality becomes clearer.

I agree, the removal of the 75kWh S/X is probably to somewhat offset the margin hit they are taking by offering the mid-range M3. They seem to be working down market but each step comes with lower margins so they have to go slow to maintain some profit.

If anything I think this article makes a great case for TDD. If your developers aren't good at design and refactoring and that is showing up in your tests, that is an indication that your design needs to be refactored to be less coupled. TDD isn't a panacea, developers have to have some level of sense and see the signs of a less than optimal design. Pain in test creation is a great way of showing that as it simulates client code.

I also don't understand people thinking that you have to write the entire test suite up front. You build your test along with your code. You start simply and build up, this way if you don't have concrete specs your tests are helping you with the design by thinking about consumption as well as implementation.