[wsl2]
firewall = true
[wsl2]
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| { | |
| // "cmake.pinnedCommands": [ | |
| // "workbench.action.tasks.configureTaskRunner", | |
| // "workbench.action.tasks.runTask" | |
| // ], | |
| // "C_Cpp.intelliSenseEngine": "disabled", | |
| // "C_Cpp.formatting": "clangFormat", | |
| // "C_Cpp.autocompleteAddParentheses": true, | |
| // "C_Cpp.inlayHints.autoDeclarationTypes.enabled": true, | |
| // "C_Cpp.inlayHints.autoDeclarationTypes.showOnLeft": true, |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| "schemes": | |
| [ | |
| { | |
| "background": "#D5CCBA", | |
| "black": "#20111B", | |
| "blue": "#426A79", | |
| "brightBlack": "#5E5252", | |
| "brightBlue": "#426A79", | |
| "brightCyan": "#989A9C", | |
| "brightGreen": "#858162", |
-
Constant Time
$$O(1)$$ : The algorithm's execution time remains constant regardless of the input size. This is the most efficient time complexity. Example: accessing an element in an array by index. -
Logarithmic Time
$$O(\log n)$$ : The algorithm's execution time increases logarithmically with the input size. This is often associated with algorithms that divide the input in half at each step, like binary search. Example: binary search in a sorted array. -
Linear Time
$$O(n)$$ : The algorithm's execution time increases linearly with the input size. This is common for algorithms that need to process each element of the input once, like searching for a specific element in an unsorted array. Example: iterating through an array. -
Linearithmic Time
$$O(n \log n)$$ : The algorithm's execution time grows slightly faster than linear time. This complexity is typically associated with efficient sorting algorithms like m
Picking the right architecture = Picking the right battles + Managing trade-offs
- Clarify and agree on the scope of the system
- User cases (description of sequences of events that, taken together, lead to a system doing something useful)
- Who is going to use it?
- How are they going to use it?