Skip to content

Commit e14eaa5

Browse files
cleared up files folder
1 parent 2717aba commit e14eaa5

39 files changed

+55
-7718
lines changed

content/backend/node.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,6 @@ script = 'animation'
3636
<dt>NPM Scripts</dt>
3737
<dd>Npm has a run command that can run scripts defined in the scripts property of a package.json file. It provides additional commands to the CLI, such as <mark>npm run test</mark>. This functionality reduces the need for third-party tooling like Grunt or Gulp. </dd><br/>
3838
<dd>You can add even more functionality to NPM scripts by installing open source dev dependencies. npm-run-all can run scripts in parallel (usually multiple tasks are run in sequence with &&). onchange will automatically re-run the task by watching for changes in your code.</dd>
39-
4039
</dl>
4140
</div>
4241
<div style="text-align:right"> <a href="#top">&#8593; Top</a></div>

content/devops/testing.md

Lines changed: 24 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -46,3 +46,27 @@ script = 'animation'
4646
</div>
4747
<div style="text-align:right"> <a href="#top">&#8593; Top</a></div>
4848

49+
### Whenever possible, use TDD
50+
51+
TDD is a _design process_, not a testing process. TDD is a robust way of designing software components ("units") interactively so that their behaviour is specified through unit tests.
52+
53+
How? Why?
54+
55+
#### Test-first cycle
56+
57+
1. Write a simple failing test
58+
2. Make the test pass by writing the minimum amount of code
59+
3. Refactor the code by applying design principles/patterns
60+
61+
During phase 2, don't bother with quality.
62+
63+
#### Consequences of the test-first cycle
64+
65+
+ Writing a test first makes the code design more testable
66+
+ Writing just the amount of code needed to implement the required functionality makes the resulting codebase minimal, thus more maintainable
67+
+ The codebase can be enhanced using refactoring mechanisms, the tests give you confidence that the new code is not modifying the existing functionalities
68+
+ Cleaning the code in each cycle makes the codebase more maintainable, it is much cheaper to change the code frequently and in small increments
69+
+ Fast feedback for the developers, you know that you don't break anything and that you are evolving the system in a good direction
70+
+ Generates confidence to add features, fix bugs, or explore new designs
71+
72+
Note that code written without a test-first approach is often very hard to test!

content/files/ai.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,6 @@
11
+++
2-
description = ""
2+
description = "Resources on AI"
33
title = "Artificial Intelligence"
4-
54
draft = false
65
weight = 200
76
bref="A curated list of Artificial Intelligence (AI) courses, books, video lectures and papers"

content/files/ai2.md

Lines changed: 0 additions & 26 deletions
This file was deleted.

content/files/angular.md

Lines changed: 0 additions & 895 deletions
This file was deleted.

0 commit comments

Comments
 (0)