Explore >> Select a destination
|
You are here 
|
trunk.io | ||
| | | | |
mill-build.org
|
|
| | | | | ||
| | | | |
jonathan-frere.com
|
|
| | | | | Why do you write tests? I've been thinking about this question a lot recently. I've been trying to motivate some teammates that tests are worth writing. But I'm going to convince them of that, I need to be able to answer that question for myself, right? Tests sometimes get portrayed as one of the chores of software development. As a new developer, that's how I saw tests for a long time: something I did because it was what I was told to do - besides, if I got the coverage to 100%, I got a little green checkbox to put on my README.md file on Github. I knew that tests were good, because they make Good Code? - I just didn't know how that happened, or why my tests were still so painful to work with! | |
| | | | |
nikoheikkila.fi
|
|
| | | | | How can we improve the developer experience in writing tedious browser-based tests? | |
| | | | |
architecturenotes.co
|
|
| | | How Relational Databases Work. This post talks about how indexes and transactions work on the inside of relational databases. | ||
