3 ms·

Good call out. There are a lot of unnecessary complexity plaguing the tech scene. Scalability, microservice, SRE, SPA, unit testing, design system, Restful/gra

by a_c 4y ago

Good call out. There are a lot of unnecessary complexity plaguing the tech scene. Scalability, microservice, SRE, SPA, unit testing, design system, Restful/graphQL everything. Not saying there isn't a place for them, there is. But probably not at day 1 when the thing you intended to make your living didn't even exist.

ch4s3 4y ago
I agree in general, but think that unit testing has a place even in small scale settings. Clearly chasing 100% coverage is dumb, but if you have tricky business logic you should clearly unit test it and automate running the tests. The cost/benefit ratio seems super obvious to me on this.
- ansgri 4y ago
  Unit testing is an obvious choice for something like a parser or algorithm library, for common business logic integration tests provide most of the benefit, and then some. Also, unit tests slow down development as they need to be refactored alongside code, while integration tests can use a more stable interface. This is typically true at smaller scale, one smallish team; when build and test times or team isolation becomes a concern, it's time to rethink your testing strategy.
- BizarreByte 4y ago
  There’s definitely a value to unit tests in the right situations. When I start a new project I don’t aim for any specific coverage percent, I just write them where I know for sure I need them. Right now I’m working on some reasonably complex reclusive logic in a personal project and unit testing that has saved an unbelievable amount of time when I inevitably mess something up.
JamesSwift 4y ago
> not at day 1 when the thing you intended to make your living didn't even exist This is the most valid criticism of k8s use. Do not skip square one and roll it in k8s when you haven't even built the product POC and tested the consumer appetite. Definitely consider it after getting validation of the POC and deciding to build it out "for real".

by a_c 4y ago

ch4s3 4y ago

I agree in general, but think that unit testing has a place even in small scale settings. Clearly chasing 100% coverage is dumb, but if you have tricky business logic you should clearly unit test it and automate running the tests. The cost/benefit ratio seems super obvious to me on this.

ansgri 4y ago
Unit testing is an obvious choice for something like a parser or algorithm library, for common business logic integration tests provide most of the benefit, and then some. Also, unit tests slow down development as they need to be refactored alongside code, while integration tests can use a more stable interface. This is typically true at smaller scale, one smallish team; when build and test times or team isolation becomes a concern, it's time to rethink your testing strategy.
BizarreByte 4y ago
There’s definitely a value to unit tests in the right situations. When I start a new project I don’t aim for any specific coverage percent, I just write them where I know for sure I need them. Right now I’m working on some reasonably complex reclusive logic in a personal project and unit testing that has saved an unbelievable amount of time when I inevitably mess something up.

JamesSwift 4y ago

> not at day 1 when the thing you intended to make your living didn't even exist This is the most valid criticism of k8s use. Do not skip square one and roll it in k8s when you haven't even built the product POC and tested the consumer appetite. Definitely consider it after getting validation of the POC and deciding to build it out "for real".