tome export
This commit is contained in:
parent
52278c3a53
commit
7a52afab5f
960 changed files with 3670 additions and 2229 deletions
|
@ -82,15 +82,15 @@
|
|||
],
|
||||
"body": [
|
||||
{
|
||||
"value": "\n <p>When you start a new project, when should you start writing tests and doing test-driven development?<\/p>\n\n<p>Is it before you write any code, or is it something you can start later?<\/p>\n\n<p>When starting <a href=\"/daily\/2024\/02\/19\/introducing-versa\">versa<\/a>, I was only scaffolding the console commands and running some basic commands such as \"composer install\" and \"phpunit\".<\/p>\n\n<p>At that point, there wasn't any business logic to test.<\/p>\n\n<p>The first versions only supported PHP, so there was no complexity around which language the project used.<\/p>\n\n<p>There was no logic to determine which language or package manager was used.<\/p>\n\n<p>Now I've started to add this functionality - such as determining the project type from its composer.json or package.json file - there is logic to test, and I've started to write tests and do test-driven development.<\/p>\n\n<p>At this phase, I can see the value, which I couldn't when setting up the application to begin with, and different have any logic worth testing.<\/p>\n\n ",
|
||||
"value": "\n <p>When you start a new project, when should you start writing tests and doing test-driven development?<\/p>\n\n<p>Is it before you write any code, or is it something you can start later?<\/p>\n\n<p>When starting <a href=\"\/daily\/2024\/02\/19\/introducing-versa\">versa<\/a>, I was only scaffolding the console commands and running some basic commands such as \"composer install\" and \"phpunit\".<\/p>\n\n<p>At that point, there wasn't any business logic to test.<\/p>\n\n<p>The first versions only supported PHP, so there was no complexity around which language the project used.<\/p>\n\n<p>There was no logic to determine which language or package manager was used.<\/p>\n\n<p>Now I've started to add this functionality - such as determining the project type from its composer.json or package.json file - there is logic to test, and I've started to write tests and do test-driven development.<\/p>\n\n<p>At this phase, I can see the value, which I couldn't when setting up the application to begin with, and different have any logic worth testing.<\/p>\n\n ",
|
||||
"format": "full_html",
|
||||
"processed": "\n <p>When you start a new project, when should you start writing tests and doing test-driven development?<\/p>\n\n<p>Is it before you write any code, or is it something you can start later?<\/p>\n\n<p>When starting <a href=\"/daily\/2024\/02\/19\/introducing-versa\">versa<\/a>, I was only scaffolding the console commands and running some basic commands such as \"composer install\" and \"phpunit\".<\/p>\n\n<p>At that point, there wasn't any business logic to test.<\/p>\n\n<p>The first versions only supported PHP, so there was no complexity around which language the project used.<\/p>\n\n<p>There was no logic to determine which language or package manager was used.<\/p>\n\n<p>Now I've started to add this functionality - such as determining the project type from its composer.json or package.json file - there is logic to test, and I've started to write tests and do test-driven development.<\/p>\n\n<p>At this phase, I can see the value, which I couldn't when setting up the application to begin with, and different have any logic worth testing.<\/p>\n\n ",
|
||||
"processed": "\n <p>When you start a new project, when should you start writing tests and doing test-driven development?<\/p>\n\n<p>Is it before you write any code, or is it something you can start later?<\/p>\n\n<p>When starting <a href=\"http:\/\/default\/daily\/2024\/02\/19\/introducing-versa\">versa<\/a>, I was only scaffolding the console commands and running some basic commands such as \"composer install\" and \"phpunit\".<\/p>\n\n<p>At that point, there wasn't any business logic to test.<\/p>\n\n<p>The first versions only supported PHP, so there was no complexity around which language the project used.<\/p>\n\n<p>There was no logic to determine which language or package manager was used.<\/p>\n\n<p>Now I've started to add this functionality - such as determining the project type from its composer.json or package.json file - there is logic to test, and I've started to write tests and do test-driven development.<\/p>\n\n<p>At this phase, I can see the value, which I couldn't when setting up the application to begin with, and different have any logic worth testing.<\/p>\n\n ",
|
||||
"summary": null
|
||||
}
|
||||
],
|
||||
"feeds_item": [
|
||||
{
|
||||
"imported": "1970-01-01T00:33:45+00:00",
|
||||
"imported": "1970-01-01T00:32:50+00:00",
|
||||
"guid": null,
|
||||
"hash": "1579ff874773390b1129bfc1dc1f1c57",
|
||||
"target_type": "feeds_feed",
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue