fsdghrth3

4 ms·

1. 1.▲
   by fsdghrth3 4y ago

   > TDD is not a testing process. It is a design process. The article actually discusses whether this is accurate or not. TDD started out as a testing process but got adopted for its design consequences which is why there is a lot of confu
2. 2.▲
   by fsdghrth3 4y ago

   See my other comment below. I don't recommend doing it all the time specifically because with experience you can often skip a lot of the rgr loop. > Everyone understands the idea, it's just a massive time sink for no more benef
3. 3.▲
   by fsdghrth3 4y ago

   I use TDD as a tool. I find it quite heavy handed for maintenance of legacy code where I basically know the solution to the task up front. I can either just rely on having enough existing coverage or create one test for my change and fix it
4. 4.▲
   by fsdghrth3 4y ago

   > This ultimately means, what most programmers intuitively know, that it's impossible to write adequate test coverage up front Nobody out there is writing all their tests up front. TDD is an iterative process, RED GREEN REFACTOR. -
5. 5.▲
   by fsdghrth3 4y ago

   React is great. Vue is wannabe angular (not sure what version though was it 2, 3 or 4 now?) svelte is too busy shipping bugs to fix any and I don't even know what the others are.
6. 6.▲
   by fsdghrth3 4y ago

   Reading these comments make me sad. It's like everyone has forgotten the cookie cutter server architecture pattern. https://dzone.com/articles/monoliths-cookie-cutter-or I really don't understand microservice