Julio Biason
6 years ago
3 changed files with 27 additions and 1 deletions
@ -0,0 +1,25 @@
|
||||
+++ |
||||
title = "Things I Learnt The Hard Way - Good Languages Come With Tests" |
||||
date = 2019-06-20 |
||||
|
||||
[taxonomies] |
||||
tags = ["en-au", "books", "things i learnt", "programming languages", "tests"] |
||||
+++ |
||||
|
||||
You can be sure that if a language brings a testing framework -- even minimal |
||||
-- in its standard library, the ecosystem around it will have better tests |
||||
than a language that doesn't carry a testing framework, no matter how good the |
||||
external testing frameworks for the language are. |
||||
|
||||
<!-- more --> |
||||
|
||||
The reason is kinda obvious on this one: When the language itself brings a |
||||
testing framework, it reduces the friction for people to start writing tests, |
||||
and that includes the authors of the language itself and the community. |
||||
|
||||
Sure, better frameworks may come along, and languages that don't have a |
||||
testing framework in their standard library may have options with better |
||||
support and easier access but, again, when they are there from the start, the |
||||
start is better and the final result is better. |
||||
|
||||
{{ chapters(prev_chapter_link="/books/things-i-learnt/throw-away", prev_chapter_title="Be Ready To Throw Your Code Away") }} |
Loading…
Reference in new issue