The melting pot of JavaScript (2017)

Re:The melting pot of JavaScript (2017) by BigJono on Monday January 07, 2019 @09:26PM (#18852554)

I know a couple that would tell me to go jump if I suggested they aim for 90% code coverage on a CRUD app. They also write very clean, maintainable code and do it very, very quickly.

There's always a trade off.

[ Parent | on HN ]

Re:The melting pot of JavaScript (2017) by spricket on Tuesday January 08, 2019 @02:49AM (#18854003)

I'm one of those. Unit tests are a waste of time IMO. It usually takes almost as much code to test logic as it does to write it, so I always wondered why the TDD folks don't just implement the code twice and check the result at the end :)

[ Parent | on HN ]

Re:The melting pot of JavaScript (2017) by 2trill2spill on Monday January 07, 2019 @09:40PM (#18852627)

I'm not writing a CRUD app, I'm writing a program that my company expects to put into production. Writing tests is very much a part of writing production code.

[ Parent | on HN ]

Re:The melting pot of JavaScript (2017) by TeMPOraL on Tuesday January 08, 2019 @02:20AM (#18853914)

If you're in webdev, CRUD apps is probably 95+% of what gets put into production. CRUD isn't meant as pejorative here, it's just most of the things people do with software fits in the model of Create/Read/Update/Delete access to a DB.

[ Parent | on HN ]

Re:The melting pot of JavaScript (2017) by BigJono on Monday January 07, 2019 @11:23PM (#18853128)

CRUD apps generally go into production, unless something goes horribly wrong.

[ Parent | on HN ]