3 ms·
I’ve seen it go off the rails though. I’ve seen people exhibit traumatic responses to it. Pain is information, but there are less helpful ways to interpret it.
by hinkley 4y ago
I’ve seen it go off the rails though. I’ve seen people exhibit traumatic responses to it.
Pain is information, but there are less helpful ways to interpret it.
There are some architectural decisions I resist energetically because they create a lot of consequences for testing, with not a lot of value added compared to other alternatives. If you introduce something that makes writing code 30% harder you’d better be getting a lot of profit margin out of the deal. Otherwise you’re just torturing people for no good reason
- hbrn 4y agoI haven't seen a single case where it doesn't go off the rails. One problem with tests is that benefits are immediate, but costs are delayed. When you're writing tests it feels like you're creating nothing but value. By the time you realize that tests made your architecture stiff as a board, they have already spread everywhere. I've seen numerous cases where teams were not able to refactor because too many tests were failing. Quite ironic, given that tests are supposed to help refactoring.
- hinkley 4y agoI don’t think it’s an accident that I’ve had more testing mentors than anything else. Testing is hard. There’s a huge number of mistakes you can make and I’ve only made 70% of them so I deflect people calling me an expert. I’m not an expert, but I can look at tests and enumerate all of the rookie and sophomore mistakes, and let me tell you that can keep some people busy for their entire tenure. I don’t say it in front of policy people much, but I immediately suspect anything as hard as this of being done incorrectly.