tddfuckwitz

3 ms·

1. 1.▲
   by tddfuckwitz 11y ago

   A good point. I think the bigger learning exercise for this team in particular would be: do we need this test and why? To make them examine a bit more about what they are trying to achieve and not just succumb to testing by numbers. Ultimat
2. 2.▲
   by tddfuckwitz 11y ago

   To be fair, you don't have to use LLVM or Swift, if you don't want to - there are other compilers and languages out there, some already cross platform (hello C++). I understand the unhappiness though that so called techies and dev
3. 3.▲
   by tddfuckwitz 11y ago

   Does this eventually end up as yet another virtualization layer? How big and bloated does the web stack become before we start again, with a lean protocol and markup language for text documents?
4. 4.▲
   by tddfuckwitz 11y ago

   Can't blame him for asking. He has obviously sized you up correctly, given you didn't say no to him straight off the bat. Unless you expect lawyer cannons to be fired broadside at your startup on an hourly basis, how much involve
5. 5.▲
   by tddfuckwitz 11y ago

   I have just come onto a project that has tests up to the armpits, mocked everything, and the test lead wielding an almost evangelical bent across the developers. And the codebase and system is still shit. Why? Because the team though loads